Re: a remark on the webid spec

One of the things that drew me to the foaf spec was that the spec itself was machine readable (and added the rules to my rdfs reasoner). It told the semweb story, that is, by living it.

I wish webid spec could also do something similar. For example, it contains a default graph representing the key of test site. The spec tells one how to verify that a site has passed conformance tests, for the current spec version.

I'd love to get the server cert of the test site, note its aia uri, pull the doc and learn the pubkey of ca from the spec. I'd trust the spec doc's own https endpoint using classical ca chains (controlled by few browser/server vendors).

It doesn't seem hard to now do something in the trust chaining arena that either obviates or complements the linked data tree walking that Iso specified for locating authorities, cosigners, or location(s) of status lists (on authorities).

Sent from my iPhone

On Dec 12, 2011, at 8:46 AM, "Henry Story" <henry.story@bblfish.net> wrote:

> 
> On 12 Dec 2011, at 15:24, Pierre-Antoine Champin wrote:
> 
>> Hi all,
>> 
>> having a look at the WebID spec, I spotted a few mistakes in the RDF/XML
>> example:
>> 
>> * the rdfs namespace is not declared
>> * the closing tag for rdfs:label misses the leading '/'
>> * the datatypes xsd:hexBinary and xsd:integer should be expanded URIs,
>> not CURIEs
> 
> very well spotted, Pierre. Thanks a lot. We have updated the spec here
> 
>  https://dvcs.w3.org/hg/WebID/rev/add4f836470d
> 
> WE fixed this in today's meeting
> 
>   http://www.w3.org/2011/12/12-webid-minutes.html
> 
> and we should have a new spec with all the latest changes out today.
> 
> Does one really have to use full URLs for datatypes? That's really a bit lame...
> 
> Henry
> 
> 
>> 
>> best
>> 
>> pa
>> 
> 
> Social Web Architect
> http://bblfish.net/
> 
>

Received on Tuesday, 13 December 2011 00:10:57 UTC