Although, both of those are possible with the little-known (and little-implemented) XML Linking Language (XLink), a W3C standard. XLink allows one to define links on arbitrary tags, many-to-many links, links between external resources, and links to specific positions and ranges using XPath.
Not sure if that could be a good option to specify some content within a web document. First of all it is not a URL that you can normally use in web browser's address bar and share from social media. Secondly, not sure if it can specify arbitrary part of attribute value.
Thank you for sharing the information anyway and will take a look.
I've really enjoyed using jxnblk's approach to styling. I started with basscss [1], then moved on to rebass, and finally settled on axs [2]. They all take more or less the same approach, but operate differently. Rebass generates inline styles; basscss is simply a CSS file that defines a set of utility classes (like `mb2`, `p3`, `flex-none`, etc.); and axs dynamically generates CSS classnames and stylesheets.
...Or at least, that used to be the case. Looking at the most recent version of rebass, it looks as if it uses the same dynamic classname/stylesheet generation strategy. Now I'm not so sure what the difference between rebass and axs are, except that the former seems to be a comprehensive set of UI components, and the latter a tool for generating your own component library.
In any case, I'm glad jxnblk keeps experimenting with these libraries, even if it's hard to keep up with the changes. Their surface area is so small that it's easy to pick up the API and it doesn't feel like a risk or burden to stay on older versions.
Similarly, I've been enjoying JSS[1] a lot... it works similar to inlined, but under the covers it creates classes per component and renders to styles... can pre-render via server pass too.
Yeah the newest version of rebass uses styled-components[0] under the hood which does the same thing as axs does. (generate an actual stylesheet with classnames)
PeriodO | Front-end developer | Part-time | Austin, TX and Chapel Hill, NC | http://perio.do/ | REMOTE
PeriodO (Periods, Organized) is a two-year grant-funded project to help scholars, students, librarians, archivists, and museum curators understand and manage differences in how time periods are defined. For example, many archaeologists may use the term “Bronze Age,” yet each may define the spatial and temporal extent of that period differently. During the first phase of the project (funded by the National Endowment for the Humanities) we collected over 3500 of these time period definitions and developed a tool for curating them. The Institute of Museum and Library Services is now funding the next phase, which will focus on tools for visualizing differences and patterns among period definitions.
We are hiring one part-time JavaScript developer who will help our two programmers (a PhD student and professor at the University of North Carolina) build interfaces that will allow our users to visualize, find, and curate relevant time periods for their work. This developer should have experience with React, d3, and modular JavaScript design. Familiarity with RDF would be beneficial. The time commitment is negotiable, although all work must be completed by May 2018 at the latest. All work will be remote. Email ryanshaw@unc.edu with a resume and short introduction if interested.
On points 1 and 3 especially, I highly recommend Bike Snob NYC's new book "Bike Snob Abroad." [1] He writes about the viability and acceptability of everyday cycling in New York City (his home), and then does the same while travelling to London and Amsterdam. One of his observations is that infrastructure isn't everything-- cycling is still a "special" thing to do in Portland, the Bay Area, or New York City, after all. Rather, in a place like the Netherlands, cycling is just a normal thing to do that doesn't require specialized, expensive gear, lycra, or even (gasp) helmets.
I don't think there's a simple way to get to that point anywhere in America. His hunch, one I agree with, is that people in this country have to make things The Biggest and The Fastest and The Best, which is why we are at the forefront of bike technology & craftsmanship but are so
pisspoor when it comes to cycling as a safe, simple means of transportation.
I'd be interested to see the fatality rates for riders without a helmet. The article seems to suggest that it's fine to do because cars are careful around cyclists - but that misses the point completely. The helmet is not there to save you from a car crash. It's there to save you when you get distracted and miss a pot hole or hit something.
Perhaps my perception is skewed because I've had two friends be saved from a serious head injury only thanks to their helmets. One rode into a parked car (she doesn't remember how it happened due to amnesia), riding at relaxed speed, and was unconscious for a couple days.
It seems really weird to take that risk just to avoid a slight discomfort.
It's a very hard thing to measure, mostly because double-blind studies are unethical, and well-controlled case-control studies are generally difficult. An 85% reduction in head injuries is often cited, but it's based on a study from the mid-'80s that, it turns out, had some pretty substantial methodological flaws, so it's generally agreed that that number overstates helmets' efficacy pretty considerably. More recent studies put the number somewhere around a 20% reduction in head injuries for adults in the US, accompanied by a slight increase in the rate of torsional injuries to the neck because of the larger circumference of a helmeted vs. unhelmeted head. In general, though, helmet use is not an especially good predictor of the outcome of a bike accident; it's much less well correlated with likelihood of death than, say, the cyclists's speed at the time of the accident.
Because there isn't much risk, really. It is very, very uncommon for an experienced Dutch cyclist to have a serious one-sided accident. Children learning, sick elderly and tourists on the other hand do have accidents more often and for them helmets is a good idea. You see more and more young children wear helmets in the Netherlands when they start out learning to ride a bicycle.
I've been riding bikes in traffic for almost 30 years and never had a serious accident one-sided or not. For about 6 years I also did cycling racing and wearing a helmet was obligatory to participate in training and official KNWU races. And that's a good thing for I did have a number of accidents while racing: falling in the bunch, not holding a bend, jumping from small sand cliffs, breaking equipment, and so on. However, these accidents only happen because while racing one takes risks one does not while riding a bike to work: the speed is significantly lower, they way one sits on a bike is different, the stakes (i.e., winning) are lower, the bikes themselves are a lot sturdier than those racing bikes, and so on.
I think many foreigners don't really understand this difference between riding for transportation and riding for sport or challenge.
To add: I've had many more accidents, serious and not, while walking. Tripping isn't uncommon for me, I've tripped at least once or twice a year. The same for injuring my ankle, walking against a door or window, falling from stairs, and so on.
On the last point, that's something that comes up occasionally when helmet laws are discussed in Denmark: is there evidence that wearing a helmet on bike is more helpful than wearing a helmet as a pedestrian? If not, shouldn't a mandatory helmet law also mandate it for pedestrians?
There is also evidence that wearing a helmet in a car can reduce head injuries in some kinds of accidents, especially at highway speeds. Therefore one might wonder if a mandatory-helmet law should actually include all forms of transportation, including cars, bicycles, and walking. Or perhaps a subset, such as required for bicycles only when on major streets, and for cars only when on highways.
Helmets only protect from certain types of injuries and they are often misworn. The larger analysis also need to consider that some people won't ride a bike if required to wear a helmet; eg, to prevent helmet hair while on the way to an opera. There are also health benefits to biking, vs. driving or taking mass transit.
My personal view is that biking slower than 10 mph (which is the same as running a 6 minute mile) doesn't need a helmet for the cases you are talking about any more than street runners need a helmet.
10mph is considered a slow biking speed, but it's what you'll find with city bikes in an urban environment like the Netherlands.
The larger analysis also need to consider that some people won't ride a bike if required to wear a helmet; eg, to prevent helmet hair while on the way to an opera.
In Denmark a more common reason isn't hair so much as where to put the helmet. People bike everywhere, and usually you just leave your bike in some random location on a sidewalk, with the rear wheel immobilized with a built-in device that most bikes have (minor theft deterrent). Then you're left either having to carry the helmet with you everywhere, or to try to lock it to the bike somehow (presumably with an extra lock you carry just for that). Also, it drizzles a lot, so your helmet will be very wet if you leave it outside, unless you carry an extra bag or cover for it that works together with a lock.
For commuting between home and office it's not an issue, and more people wear helmets in that case. Of my coworkers, I would say about 1/3 wear a helmet when commuting, skewed towards those who live further (~10km), and those who are somewhat older (>40 y/o). Parents with young kids also tend to wear helmets, rather than trying to explain to the kids that they have to but mom and dad don't.
I think people make the "where to put the helmet" into a bigger problem that it is. I wear a helmet when biking, and I ride my bike everywhere (I'm Danish). I always just hang the helmet on the handlebar, my reasoning "who would steal a helmet". I've been right the last 10 years.
Also really, do you care it's wet? It has holes in it, your going the get your head wet anyway.
I have taken the view that helmets don't usually help much, but that people often perceive wearing a helmet as being the definition of safety, rather than obeying the rules of the road and paying attention to the road and what is going on around you. In my view, those are far more important than what you have on your head.
Personally, I haven't seen anyone saved thanks to a bike helmet, but I have seen people get into minor accidents because they were ignoring traffic rules and not paying attention to the road. Lots of people in the US seem to treat bikes as more of a kid's toy, to be cruised around the local neighborhood without a care in the world. They don't have the damage potential or expense of cars, but they are still vehicles that are many times faster and less maneuverable then you are on your feet, and so deserve your respect and attention.
There have been various studies done regarding bicycle helmets. My conclusion on those: helmets make biking more annoying. You need a helmet, you need to put it on and off. It is a minor annoyance, but huge problem in making biking popular and easy/thoughtless.
Secondly on the safety: there are studies where they compared the average distance between people on bikes with helmets and without. Cars gave bikes less distance to people wearing helmets. The likely explanation is that because they seem more safe, you need to pay less attention to their safety (decreasing distance is a result).
Lastly: There is a TED talk about making bikes more stable using electronics. Apparently the most common bike accident is a one-sided accident by "old people", IIRC.
That site helped a lot when I was first getting the gist of CBVs. Browsing Django's source for the views was surprisingly unpainful, and doing that was aided by iPython's introspection capabilities (typing ?? after an object will show you the source of the class).
wow, thanks for posting this! Very impressive resource. I was trying to speak more to the general challenge of learning this sort of OO system (I pretty much learned class based views by reading the code already), but I'm happy that you shared this, I will pass it on to others.
http://ln.hixie.ch/?start=1086387609