- From: Stéphane Corlosquet <scorlosquet@gmail.com>
- Date: Tue, 29 Nov 2011 12:47:21 -0500
- To: WebID Incubator Group WG <public-xg-webid@w3.org>
- Message-ID: <CAGR+nnFpnn45K4WtOz06yUV7QRDK7qL-qmbn2Ri95cTQ2CEt6Q@mail.gmail.com>
On Tue, Nov 29, 2011 at 11:39 AM, Stéphane Corlosquet <scorlosquet@gmail.com > wrote: > > > On Tue, Nov 29, 2011 at 4:27 AM, WebID Incubator Group Issue Tracker < > sysbot+tracker@w3.org> wrote: > >> >> WebID-ISSUE-66 (microdata): Microdata Support [WebID Spec] >> >> http://www.w3.org/2005/Incubator/webid/track/issues/66 >> >> Raised by: Ted Thibodeau >> On product: WebID Spec >> >> Kingsley Idehen proposed that we support Microdatata such as the one >> pasted below. >> http://lists.w3.org/Archives/Public/public-xg-webid/2011Nov/0270.html >> >> <div xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" >> xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"> >> <div itemscope="" >> itemid=" >> http://id.myopenlink.net/about/id/entity/http/graph.facebook.com/kidehen" >> itemtype="http://xmlns.com/foaf/0.1/Person"> >> <div itemprop="http://www.w3.org/ns/auth/cert#key" itemscope="" >> itemtype="http://www.w3.org/ns/auth/cert#RSAPublicKey"> >> <div itemprop="http://www.w3.org/ns/auth/cert#exponent">65537</div> >> <div itemprop="http://www.w3.org/ns/auth/cert#modulus"> >> e10aab5c72781f60eb8955b2ea903319c199edd2201842e0840d43048bf018cc92b160 >> fedb3af19a58f193d4a4dc22ea01ecaff1ced0e1d612670daacd6743474b00ca3305ce >> 2be6ebbd911d15137278d8ccc3455ef9478134ee5e292b6498c0d74c1fa240bca71175 >> 1674d8067b9984a0a3c98bdf9a0fb967f32ef1d59bad6d76e2d98b6ec4193db239ada7 >> c893fe479f59bf574f34a042e69fb3bd2536f1b730446ffc70806949daf6294ba35ccc >> d1b72bef08d3604a8daff1df2a8e53af9468d92bdd0a9a52574cafdec1630174057b31 >> fe8a6dffa7bcbcf24862f0ec9611c6a2e7bd66459d6e9e41d3775fa7851cd20d594309 >> 0b3fea44545e5abba4aa69 >> </div> >> </div> >> </div> >> </div> >> > There should be no xmlns in the microdata snippet. I should add that microdata does not support datatypes out of the box, so it's not possible to explicitly state them in HTML. There might be a need to do some value coercion at the application level in this case. Steph. > >> (the above uses the old ontology, so we'd need a version for the new one) >> >> Dan Brickley pointed out >> http://lists.w3.org/Archives/Public/public-xg-webid/2011Nov/0306.html >> >> "What I'd rather see now, instead of gigantic mail threads in my inbox, >> is a nice tight well-packaged and tested .js library that reads RDFa, >> Microdata and sure Microformats2 as well. If half the angst about >> 'picking the winner' I see here could go into coding a format-agnostic >> HTML reader in .js, we'd all be a better place. >> >> Mo McRobers identified the following tasks: >> http://lists.w3.org/Archives/Public/public-xg-webid/2011Nov/0326.html >> >> a. Spec how a WebID profile graph would look serialised in terms of >> Microdata >> b. Spec how an application can process RDF/XML _and_ RDFa _and_ Microdata >> in a uniform fashion for the basic verification (i.e, public key >> description) >> c. Spec how an application can process RDF/XML _and_ RDFa _and_ Microdata >> in a uniform fashion for arbitrary information, such as profile fields >> (display name, homepage, online accounts, etc.) >> >> > Note that Gregg Kellogg is working on a microdata to RDF conversion > algorithm [1], so once that spec is stable, and RDF libraries start to > support it, we could add microdata to the spec with very minimal changes. > > Steph. > > [1] > https://dvcs.w3.org/hg/htmldata/raw-file/62761f79513a/microdata-rdf/index.html >
Received on Tuesday, 29 November 2011 17:47:52 UTC