[foaf-protocols] new spec version out
henry.story at bblfish.net
Tue Oct 18 14:31:51 CEST 2011
On 18 Oct 2011, at 14:12, Sergio Fernández wrote:
> On 17 October 2011 19:54, Henry Story <henry.story at bblfish.net> wrote:
>> And the RSA and cert ontology have been updated.
> Where are stored the sources of those vocabularies'? I don't find them
> on the mercurial, and I think I found an error (read below).
yes, I have been pushing them straight to their namespace location ever since their creation.
But you are welcome to copy them to mercurial, so that we can make edits more easily -- CVS is very slow to
work with. Just copy the .n3 files over (e.g. http://www.w3.org/ns/auth/cert.n3 ). I can then do pushes
when things are agree on over there.
>> Obvious things todo are:
>> -1 The sequence diagram steps need to be synchronised with the language in the spec
>> -2 In the cert ontology I tried putting my comments using rdf:RDFLiteral datatypes so that this could
>> appear in the html. But the transformation specgen does not seem to deal with that.
> Not sure which is the right way to add html markup on literals...
> a) Escape the characters '<' and '>' (as you are already doing for
I am not sure I am escaping it. Am I? Not in the cert.n3 file on the
cert:hex skos:editorialNote """<span ns="http://www.w3.org/1999/xhtml"><p> .... </span>"""^^rdf:XMLLiteral .
> b) Use the white-space selector of CSS:
That's also a solution. There are a lot of links in the notes currently so unless we move to a wiki format, I think it would be nice if one could just put in some simple and light weight html...
>> -3 If the specgen generated spec could also use the editors notes from the n3 that would be nice.
> I've just added support to skos:editorialNote on this version of specgen.
> On the previous thread Dominik requested support to
> owl:equivalentClass. I've just added on specgen. Debugging the new
> feature I detected that you were wrongly using owl:equivalentClass on
> datatypes (on cert:hex for instance), when it must be
> owl:equivalentProperty, right?
datatypes are classes. cert:hex used to be a property and is now a datatype too.
That is allowed by rdf in fact, though there is a debate which direction the arrows should go.
The details of that transition are explained in the notes I think.
> BTW, rdfs:Datatypes are not showing right now on the spec (e.g.
> cert:int). Would you like to add it?
yes, please. Thanks a lot :-)
> Sergio Fernández
> CTIC - Technological Center
> Parque Científico y Tecnológico de Gijón
> C/ Ada Byron, 39 Edificio Centros Tecnológicos
> 33203 Gijón - Asturias - Spain
> Tel.: +34 984 29 12 12
> Fax: +34 984 39 06 12
> E-mail: sergio.fernandez at fundacionctic.org
Social Web Architect
More information about the foaf-protocols