Re: [whatwg] Custom microdata handling added to HTML5 spec
Manu Sporny wrote: ... We are currently working[1] on features to dynamically extending the base set of reserved words and the set of pre-defined prefixes through a mechanism called RDFa Profiles[2]. It is proposed that this mechanism would allow authors to do this in their documents: div profile=http://example.org/myprofile.html; ... span property=descriptionA description for this page./span span about=#me property=nameManu Sporny/span /div Note that 'description' and 'name' are not prefixed, but would be mapped to a full URI in the document listed by @profile. This allows the ease of Microformats-like markup but with all of the rigor of RDFa. ... So, to process the HTML fragment above, a recipient would always need to look up the profile resource, and extract RDF triples from *that* document (*) first? How do you prevent the problem we've seen with DTDs (consumers not willing or able to cache the resource, and thus re-requesting the same resource over and over again)? BR, Julian (*) Which specific media types would a recipient be required to support for profiles?
Re: [whatwg] Custom microdata handling added to HTML5 spec
On Sun, 10 May 2009, Manu Sporny wrote: Shelley Powers wrote: Since a new section detailing HTML5's handling of custom microdata has been added to the HTML5 spec http://dev.w3.org/html5/spec/Overview.html#microdata I've only had a brief chance to look over the HTML5 Microdata spec, but there is one big problem that overrides all of the other issues: The HTML5 Microdata spec is in direct conflict with planned RDFa extensions and will almost surely result in spurious triples being generated in RDFa processors in the future. I've renamed property= to itemprop=. -- Ian Hickson U+1047E)\._.,--,'``.fL http://ln.hixie.ch/ U+263A/, _.. \ _\ ;`._ ,. Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
[whatwg] Custom microdata handling added to HTML5 spec
Since a new section detailing HTML5's handling of custom microdata has been added to the HTML5 spec (tracked here http://html5.org/tools/web-apps-tracker?from=3073to=3074 and displayed here http://dev.w3.org/html5/spec/Overview.html#microdata and announced herehttp://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2009-May/019681.html ), I'm assuming my effort to re-examine the use cases Ian has published is irrelevant, and a waste of everyone's time. I will hence discontinue any and all effort associated with this specification. Shelley
Re: [whatwg] Custom microdata handling added to HTML5 spec
Shelley Powers wrote: Since a new section detailing HTML5's handling of custom microdata has been added to the HTML5 spec http://dev.w3.org/html5/spec/Overview.html#microdata I've only had a brief chance to look over the HTML5 Microdata spec, but there is one big problem that overrides all of the other issues: The HTML5 Microdata spec is in direct conflict with planned RDFa extensions and will almost surely result in spurious triples being generated in RDFa processors in the future. We are currently working[1] on features to dynamically extending the base set of reserved words and the set of pre-defined prefixes through a mechanism called RDFa Profiles[2]. It is proposed that this mechanism would allow authors to do this in their documents: div profile=http://example.org/myprofile.html; ... span property=descriptionA description for this page./span span about=#me property=nameManu Sporny/span /div Note that 'description' and 'name' are not prefixed, but would be mapped to a full URI in the document listed by @profile. This allows the ease of Microformats-like markup but with all of the rigor of RDFa. The HTML5 microdata proposal, as it stands right now, would create numerous spurious triples if implemented and would violate the purpose of @property as it is being developed in the RDFa community. I'll have more comments on the microdata proposal based on the response to this e-mail. -- manu [1]http://www.w3.org/2009/04/30-rdfa-minutes.html#item04 [2]http://rdfa.info/wiki/RDFa_Profiles -- Manu Sporny President/CEO - Digital Bazaar, Inc. blog: A Collaborative Distribution Model for Music http://blog.digitalbazaar.com/2009/04/04/collaborative-music-model/
