<?xml version="1.0" encoding="UTF-8"?>
 <rdf:RDF xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:cc="http://web.resource.org/cc/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://pinboard.in">
    <title>Pinboard (jtyost2)</title>
    <link>https://pinboard.in/u:jtyost2/public/</link>
    <description>recent bookmarks from jtyost2</description>
    <items>
      <rdf:Seq>	<rdf:li rdf:resource="http://www.w3.org/blog/news/archives/4167"/>
	<rdf:li rdf:resource="http://boingboing.net/2014/01/14/requirements-for-drm-in-html5.html"/>
	<rdf:li rdf:resource="http://coding.smashingmagazine.com/2013/11/13/laying-the-groundwork-for-extensibility/"/>
	<rdf:li rdf:resource="https://www.eff.org/deeplinks/2013/10/lowering-your-standards"/>
	<rdf:li rdf:resource="http://www.w3.org/blog/2013/10/on-encrypted-video-and-the-open-web/"/>
	<rdf:li rdf:resource="http://techblog.netflix.com/2013/04/html5-video-at-netflix.html"/>
	<rdf:li rdf:resource="http://www.w3.org/News/2012"/>
	<rdf:li rdf:resource="http://meyerweb.com/eric/thoughts/2006/09/25/w3c-change-full-independence/"/>
	<rdf:li rdf:resource="http://dev.w3.org/csswg/css3-hierarchies/"/>
	<rdf:li rdf:resource="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034506.html"/>
	<rdf:li rdf:resource="https://hacks.mozilla.org/2011/08/introducing-webapi/"/>
	<rdf:li rdf:resource="http://appcachefacts.info/"/>
	<rdf:li rdf:resource="http://news.cnet.com/8301-30685_3-10402642-264.html"/>
	<rdf:li rdf:resource="http://html5doctor.com/aside-revisited/"/>
	<rdf:li rdf:resource="http://www.quirksmode.org/blog/archives/2009/09/the_html5_drag.html"/>
	<rdf:li rdf:resource="http://www.osnews.com/story/22182/Microsoft_Endorses_HTML5_Audio_Video_Tags"/>
      </rdf:Seq>
    </items>
  </channel><item rdf:about="http://www.w3.org/blog/news/archives/4167">
    <title>HTML5 is a W3C Recommendation | W3C News</title>
    <dc:date>2014-10-30T00:43:32+00:00</dc:date>
    <link>http://www.w3.org/blog/news/archives/4167</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The HTML Working Group today published HTML5 as W3C Recommendation. This specification defines the fifth major revision of the Hypertext Markup Language (HTML), the format used to build Web pages and applications, and the cornerstone of the Open Web Platform.]]></description>
<dc:subject>html5 w3c standards browser webdevelopment</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:35fc76a07eef/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://boingboing.net/2014/01/14/requirements-for-drm-in-html5.html">
    <title>Requirements for DRM in HTML5 are a secret - Boing Boing</title>
    <dc:date>2014-01-16T06:15:44+00:00</dc:date>
    <link>http://boingboing.net/2014/01/14/requirements-for-drm-in-html5.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[DRM, by its nature, has secret requirements. That's why attempts to standardize it always end up with unworkable garbage, like the DVB's CPCM. DRM relies on me installing software on your computer that stops you from running other software. For example, you install a browser that plays video in such a way that another program on your computer can't grab the video as the browser shows it on the screen.

This is silly. It's your computer. Whatever steps the browser takes to obscure how it is playing the video back can be unpicked by you, at your leisure, so you can make a tool that gets around it.

Standards are, by their nature, public: they say, "This is what you are expected to do." But if you make DRM's workings public ("here's how we hide the keys from you"), you provide a roadmap for defeating it. Standardized DRM is an oxymoron, like a secret law.

The ensuing Hacker News thread is well worth a read on this]]></description>
<dc:subject>drm privacy legal w3c standards encryption browser webstandards</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:95202b342556/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:encryption"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webstandards"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://coding.smashingmagazine.com/2013/11/13/laying-the-groundwork-for-extensibility/">
    <title>Laying The Groundwork For Extensibility | Smashing Coding</title>
    <dc:date>2014-01-02T19:24:20+00:00</dc:date>
    <link>http://coding.smashingmagazine.com/2013/11/13/laying-the-groundwork-for-extensibility/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[In an earlier time, attempting such a sweeping cultural change might have been foolish. Starting at a declarative level was undoubtedly a good idea. However, explaining even a bit of the underlying magic goes a long way: Exposing a DOM tree JavaScript opened new worlds to developers and bolstered the competitiveness of the platform. It also enabled the community to adapt through experimentation and enabled libraries to compete. This allows valuable, popular API ideas to potentially be standardized. The community can do it faster and with less risk than browser vendors and standards organizations can.
The answers aren’t always obvious, but the process of asking “How does that work?” is often more fruitful than it first appears. Details come into focus and missing explanations are uncovered, layer by layer. At each layer, it’s tempting to throw up our collective hands and say “It’s too hard” to explain all the stuff down there. Throw it all out. Start over. At least we won’t make the same mistakes, right?
Perhaps. But we’d also be starting from zero. Zero users, zero developers and zero useful content. The Web is the open, extensible, multi-vendor, universal platform of our lifetime. Small, meaningful changes to the Web can have an outsized impact relative to the effort involved. It’s a straightforward way to do a great deal of good. Encouraging layering, bit by bit, doesn’t mean giving up or “slowing down.” Just the opposite: It’s our only credible hope of making a Web that’s worthy to succeed the Web we have today.]]></description>
<dc:subject>standards html5 html webdevelopment software api w3c</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:de34a823e606/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://www.eff.org/deeplinks/2013/10/lowering-your-standards">
    <title>Lowering Your Standards: DRM and the Future of the W3C | Electronic Frontier Foundation</title>
    <dc:date>2013-12-26T21:22:46+00:00</dc:date>
    <link>https://www.eff.org/deeplinks/2013/10/lowering-your-standards</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[Just five years ago, font companies tried to demand DRM-like standards for embedded Web fonts. These Web typography wars fizzled out without the adoption of these restrictions, but now that such technical restrictions are clearly "in scope," why wouldn't typographers come back with an argument for new limits on what browsers can do?

Indeed, within a few weeks of EME hitting the headlines, a community group within W3C formed around the idea of locking away Web code, so that Web applications could only be executed but not examined online. Static image creators such as photographers are eager for the W3C to help lock down embedded images. Shortly after our Tokyo discussions, another group proposed their new W3C use-case: "protecting" content that had been saved locally from a Web page from being accessed without further restrictions. Meanwhile, publishers have advocated that HTML textual content should have DRM features for many years.

In our conversations with the W3C, we argued that the W3C needed to develop a clearly defined line against the wave of DRM systems it will now be encouraged to adopt.

A Web where you cannot cut and paste text; where your browser can't "Save As..." an image; where the "allowed" uses of saved files are monitored beyond the browser; where JavaScript is sealed away in opaque tombs; and maybe even where we can no longer effectively "View Source" on some sites, is a very different Web from the one we have today. It's a Web where user agents—browsers—must navigate a nest of enforced duties every time they visit a page. It's a place where the next Tim Berners-Lee or Mozilla, if they were building a new browser from scratch, couldn't just look up the details of all the "Web" technologies. They'd have to negotiate and sign compliance agreements with a raft of DRM providers just to be fully standards-compliant and interoperable.

To be clear, we don't think all of these proposals will come to fruition. We appreciate that there's no great hunger for DRM at the W3C. Many W3C participants held their nose to accept even the EME draft, which was carefully drafted to position itself as far away from the taint of DRM as was possible for a standard solely intended to be used for DRM systems.

But the W3C has now accepted "content protection". By discarding the principle that users should be in charge of user agents, as well as the principle that all the information needed to interoperate with a standard should be open to all prospective implementers, they've opened the door for the many rightsholders who would like the same control for themselves.

The W3C is now in an unenviable position. It can either limit its "content protection" efforts to the aims of a privileged few, like Hollywood. Or it can let a thousand "content protection systems" bloom, and allow any rightsholder group to chip away at software interoperability and users' control.

EFF is still a W3C member, and we'll do our best to work with other organizations within and without the consortium to help it fight off the worse consequences of accepting DRM. But it's not easy to defend a king who has already invited its attackers across his moat.

Still, even if the W3C has made the wrong decision, that doesn't mean the Web will. The W3C has parted ways with the wider Web before: in the early 2000s, its choice to promote XHTML (an unpopular and restrictive variant of HTML) as the future led to Mozilla, Apple and Opera forming the independent WHATWG. It was WHATWG's vision of a dynamic, application-oriented Web that won—so decisively, in fact, that the W3C later re-adopted it and made it the W3C's own HTML5 deliverable.

Recently, WHATWG has diplomatically parted with the W3C again. Its "HTML Living Standard" continues to be developed in tandem with the W3C's version of the HTML standard, and does not contain EME or any other such DRM-enabling proposals.

By contrast, W3C has now put its weight behind a restrictive future: let's call it "DRM-HTML". Others have certainly bet against open, interoperable standards and user control before. It's just surprising and disappointing to see the W3C and its Director gamble against the precedent of their own success, as well as the fears and consciences of so many of their colleagues.]]></description>
<dc:subject>drm html5 eff privacy legal copyright w3c standards html</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:5686682474f4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:eff"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:privacy"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:legal"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:copyright"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/blog/2013/10/on-encrypted-video-and-the-open-web/">
    <title>On Encrypted Video and the Open Web | W3C Blog</title>
    <dc:date>2013-10-11T01:07:33+00:00</dc:date>
    <link>http://www.w3.org/blog/2013/10/on-encrypted-video-and-the-open-web/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[W3C is a place where people discuss possible technology. The HTML Working Group charter is about the scope of the discussion. W3C does not and cannot dictate what browsers or content distributors can do. By excluding this issue from discussion, we do not exclude it from anyone’s systems.

Some arguments for inclusion take this form: if content protection of some kind has to be used for videos, it is better for it to be discussed in the open at W3C, better for everyone to use an interoperable open standard as much as possible, and better for it to be framed in a browser which can be open source, and available on a general purpose computer rather than a special purpose box. Those are key arguments for the decision that this topic is in scope.

No one likes DRM as a user, wherever it crops up. It is worth thinking, though, about what it is we do not like about existing DRM-based systems, and how we could possibly build a system which will be a more open, fairer one than the actual systems which we see today. If we, the programmers who design and build Web systems, are going to consider something which could be very onerous in many ways, what can we ask in return?

The conversation has just started. The Restricted Media Community Group is one forum for discussing this. The www-tag@w3.org list is good for general Web architecture, and there is the HTML Working Group and a Web Copyright Community Group. And there are comments to Jeff’s posting or this post though I may not be able to answer them all.

Let us all continue to pursue creation of a powerful Web platform that is built on open standards. The use case of protected video content is a challenging one. We think this discussion will help get us there, but there is much more to do to achieve the level of openness I have personally sought for 25 years, and that W3C has pursued since its inception.]]></description>
<dc:subject>w3c drm technology browser internet software</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:0f15c4c2f48b/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://techblog.netflix.com/2013/04/html5-video-at-netflix.html">
    <title>The Netflix Tech Blog: HTML5 Video at Netflix</title>
    <dc:date>2013-04-16T06:56:29+00:00</dc:date>
    <link>http://techblog.netflix.com/2013/04/html5-video-at-netflix.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[We've been working with Google to implement support for the HTML5 Premium Video Extensions in the Chrome browser, and we've just started using this technology on the Samsung ARM-Based Chromebook. Our player on this Chromebook device uses the Media Source Extensions and Encrypted Media Extensions to adaptively stream protected content.  WebCrypto hasn't been implemented in Chrome yet, so we're using a Netflix-developed PPAPI (Pepper Plugin API) plugin which provides these cryptographic operations for now.  We will remove this last remaining browser plugin as soon as WebCrypto is available directly in the Chrome browser.  At that point, we can begin testing our new HTML5 video player on Windows and OS X.

 We're excited about the future of premium video playback on the web, and we look forward to the day that these Premium Video Extensions are implemented in all browsers!]]></description>
<dc:subject>netflix html5 html drm video software googlechrome internet browser standards w3c</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e6d38f72acf4/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:netflix"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:drm"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:googlechrome"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.w3.org/News/2012">
    <title>W3C News Archive: 2012 W3C</title>
    <dc:date>2012-12-18T15:41:41+00:00</dc:date>
    <link>http://www.w3.org/News/2012</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[W3C published today the complete definition of the HTML5 and Canvas 2D specifications. Though not yet W3C standards, these specifications are now feature complete, meaning businesses and developers have a stable target for implementation and planning. "As of today, businesses know what they can rely on for HTML5 in the coming years, and what their customers will demand," said Jeff Jaffe, W3C CEO. HTML5 is the cornerstone of the Open Web Platform, a full programming environment for cross-platform applications with access to device capabilities; video and animations; graphics; style, typography, and other tools for digital publishing; extensive network capabilities; and more. Read the full press release and W3C Member testimonials.
To reduce browser fragmentation and extend implementations to the full range of tools that consume and produce HTML, W3C now embarks on the stage of W3C standardization devoted to interoperability and testing. W3C is on schedule to finalize the HTML5 standard in 2014. In parallel, the W3C community will continue its work on next generation HTML features, including extensions to complement built-in HTML5 accessibility, responsive images, and adaptive streaming.
The HTML Working Group also published first drafts of HTML 5.1, HTML Canvas 2D Context, Level 2, and main element, providing an early view of the next round of standardization. Learn more About HTML.]]></description>
<dc:subject>w3c webdevelopment programming software standards html html5</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:f56208686556/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:software"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://meyerweb.com/eric/thoughts/2006/09/25/w3c-change-full-independence/">
    <title>Eric’s Archived Thoughts: W3C Change: Full Independence</title>
    <dc:date>2012-04-05T04:54:07+00:00</dc:date>
    <link>http://meyerweb.com/eric/thoughts/2006/09/25/w3c-change-full-independence/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[As many of you have noticed, I’m effectively proposing that the W3C become a foundation instead of a consortium, albeit a foundation whose primary mission is to act as a consortium would. I’ve avoided using terms like “non-profit” and “not-for-profit” because they might imply specific things which I don’t fully intend in terms of tax law, or whatever, but I do think of it as a generically non-profit institution; that is, one that does not strive to create a profit, except as can be invested into the endowment.

I’ve tried to explain why I believe this is a good idea, but in the end, I think the most fundamental reason is that one I can’t explain: it just feels like the right thing to do. It’s like I can perceive a shape without grasping all its details, but the overall shape looks right, looks better.

I fully expect that some will recoil from this idea, convinced that a foundation is a poor substitute for a consortium. Obviously, I disagree. I think the W3C’s future could be made much more stable with this approach, especially in financial terms. I also believe, as I said before, that it would be no less of a force for the advancement of the web. In fact, I think it would be a much stronger force, and have a greater positive effect, over the long term.

It is not a small undertaking, but it is an important and worthwhile effort, and I hope it is one the W3C considers seriously.]]></description>
<dc:subject>standards W3C technology politics</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:5505659d69d6/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:W3C"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:technology"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://dev.w3.org/csswg/css3-hierarchies/">
    <title>CSS Hierarchies Module Level 3</title>
    <dc:date>2012-02-07T05:03:57+00:00</dc:date>
    <link>http://dev.w3.org/csswg/css3-hierarchies/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[CSS is a language for describing the rendering of structured documents (such as HTML and XML) on screen, on paper, in speech, etc. This module contains the features of CSS level 3 relating to the hierarchical nesting of style rules. It includes and extends the functionality of CSS level 2 [CSS21], which builds on CSS level 1 [CSS1]. The main extension compared to level 2 is the ability to nest a style rule within another rule, allowing greater modularisation and readibility of CSS documents.]]></description>
<dc:subject>css html css3 w3c standards webdesign webdevelopment programming politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:463184e0b031/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:css3"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034506.html">
    <title>[whatwg] Requests for new elements for comments</title>
    <dc:date>2012-01-26T07:18:25+00:00</dc:date>
    <link>http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2012-January/034506.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[We already have an element for comments and other self-contained document 
modules, namely, <article>. The spec in fact specifically calls out an 
<article> nested in another <article> as being, by definition, a comment 
on the outer <article>.]]></description>
<dc:subject>html html5 programming webdesign webdevelopment WHATWG w3c politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:ef1a9b5babb8/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdesign"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:WHATWG"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="https://hacks.mozilla.org/2011/08/introducing-webapi/">
    <title>Introducing WebAPI ✩ Mozilla Hacks – the Web developer blog</title>
    <dc:date>2011-08-24T08:24:29+00:00</dc:date>
    <link>https://hacks.mozilla.org/2011/08/introducing-webapi/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[WebAPI is an effort by Mozilla to bridge together the gap, and have consistent APIs that will work in all web browsers, no matter the operating system. Specification drafts and implementation prototypes will be available, and it will be submitted to W3C for standardization. Security is a very important factor here, and it will be a mix of existing security measurements (e.g. asking the user for permission, like Geolocation) or coming up with new alternatives to ensure this.]]></description>
<dc:subject>api programming mozilla w3c standards browser politics</dc:subject>
<dc:source>https://pinboard.in/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b377e9b8db97/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:api"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:mozilla"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://appcachefacts.info/">
    <title>Appcache Facts</title>
    <dc:date>2011-03-20T16:08:48+00:00</dc:date>
    <link>http://appcachefacts.info/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA[The application cache is a poorly understood part of the HTML5 specification with a lot of potential. Let's get rid of some of the confusion and make the web a faster place.]]></description>
<dc:subject>appcache html5 cache webdevelopment programming w3c politics</dc:subject>
<dc:source>https://instapaper.com/</dc:source>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e16bea429542/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:appcache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:cache"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://news.cnet.com/8301-30685_3-10402642-264.html">
    <title>New standard lets browsers get a grip on files | Deep Tech - CNET News</title>
    <dc:date>2009-11-25T05:52:31+00:00</dc:date>
    <link>http://news.cnet.com/8301-30685_3-10402642-264.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA["The World Wide Web Consortium has published a draft of an interface that browsers can use to manipulate files better, one of a series of steps aimed at gradually improving the sophistication and polish of Web site interfaces. The draft File API (application programming interface) defines a number of ways that browsers and Web sites can handle files better. One big part of it: being able to select multiple files for upload, such as on photo-sharing sites or Web-based e-mail, a task that often relies on Adobe Systems' Flash today."]]></description>
<dc:subject>internet standards browser w3c politics</dc:subject>
<dc:identifier>https://pinboard.in/u:jtyost2/b:c87c9fce2f1c/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:internet"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:standards"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://html5doctor.com/aside-revisited/">
    <title>Aside Revisited | HTML5 Doctor</title>
    <dc:date>2009-10-28T16:11:09+00:00</dc:date>
    <link>http://html5doctor.com/aside-revisited/</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA["Aside is now acceptable to use for secondary content, such as a blogroll, groups of additional navigation and even advertising if that content is related to the page. When used within an article element, the contents should be specifically related to that article, for example a glossary. When using aside, please be aware of these changes of context."]]></description>
<dc:subject>html html5 w3c politics</dc:subject>
<dc:identifier>https://pinboard.in/u:jtyost2/b:e4def33c4185/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.quirksmode.org/blog/archives/2009/09/the_html5_drag.html">
    <title>QuirksBlog: The HTML5 drag and drop disaster</title>
    <dc:date>2009-09-25T04:32:38+00:00</dc:date>
    <link>http://www.quirksmode.org/blog/archives/2009/09/the_html5_drag.html</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA["After spending about a day and a half in testing I am forced to conclude that the HTML5 drag and drop module is not just a disaster, it’s a fucking disaster."]]></description>
<dc:subject>html5 html programming javascript webdevelopment ie w3c draganddrop browser politics</dc:subject>
<dc:identifier>https://pinboard.in/u:jtyost2/b:b9a1e40ca65e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:programming"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:javascript"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:webdevelopment"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:ie"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:draganddrop"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
<item rdf:about="http://www.osnews.com/story/22182/Microsoft_Endorses_HTML5_Audio_Video_Tags">
    <title>Microsoft Endorses HTML5 Audio, Video Tags</title>
    <dc:date>2009-09-19T22:30:45+00:00</dc:date>
    <link>http://www.osnews.com/story/22182/Microsoft_Endorses_HTML5_Audio_Video_Tags</link>
    <dc:creator>jtyost2</dc:creator><description><![CDATA["Technically, this endorsement does not have to say anything about the future prospects of the tags in Microsoft products, let alone the method Microsoft will choose. Most likely, the company will opt to go the Apple way, and use the DirectShow/Media Foundation frameworks." Well some decent news.]]></description>
<dc:subject>microsoft html5 html video audio w3c browser politics</dc:subject>
<dc:identifier>https://pinboard.in/u:jtyost2/b:1fe3f7cd097e/</dc:identifier>
<taxo:topics><rdf:Bag>	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:microsoft"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html5"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:html"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:video"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:audio"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:w3c"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:browser"/>
	<rdf:li rdf:resource="https://pinboard.in/u:jtyost2/t:politics"/>
</rdf:Bag></taxo:topics>
</item>
</rdf:RDF>