RE: Tasks in support of HTML Microdata

Yes, I disagree about point (c); but only requesting its scope be reduced. Its not the purpose of the SPEC itself to talk about anything OTHER than the cert key property and a matching rule for a value set from a cert and a value set from a webid profile. Nothing in this particular universe requires validating agents to be processing or understanding, or preparing for, or countencing other properties. Other universes (such as the foaf project) can wrap around this one, and use foaf cards for such as account mapping, or foaf grouping. Similarly, others might use owl:sameAs for synonyms handling in other universes. Yet others might wrap a particualr rdf/xml stream in the PGP wot vocab, but again that is NOT in our scope. Sopmeone might write sparql queries to be executed at a webid-powerd sparql protocol server, even, which walks trust graphs and computes a chain of trust anchors. But, those are "value adds". We ensure they MIGHT exist but only becuase of we sure a common architectural baseline, at the very lowest common demoninator level. Here on the list all those topics are in discussion scope, so the baseline in the spec makes it a solid baseline for all those value adds. Lets not forget this is not a working group. its JUST an incubator...  > Date: Thu, 22 Dec 2011 10:22:08 -0800
> From: patrickdlogan@gmail.com
> To: public-xg-webid@w3.org
> Subject: Tasks in support of HTML Microdata
> 
> I'd like to begin a new thread on this list for tracking and closing
> the issue of supporting HTML Microdata. Please put non-specific (i.e.
> not strictly aimed at resolving this issue) in a separate thread with
> a different subject line.
> 
> Let's keep this thread short and to the point.
> 
> There is an issue on record:
> 
> http://www.w3.org/2005/Incubator/webid/track/issues/66
> 
> The next tasks toward completion are the following:
> 
> 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.)
> 
> * Does anyone disagree that these are the next steps in support of
> HTML Microdata for WebID profiles?
> 
> * Does anyone have questions about these tasks?
> 
> * Does anyone intend to take these on?
> 
> * Is anyone obligated to take these on?
> 
> * What happens to Issue 66 if no one moves it forward?
> 
> Thanks
> -Patrick
>