[foaf-protocols] Debugging results

[Stéphane Corlosquet]

On Mon, Aug 2, 2010 at 10:44 AM, Henry Story <henry.story at gmail.com> wrote:

> Well spotted Sarven.
>
> These bugs, as all the remaining ones, are left there just to see if anyone
> is following :-)
>
> I have updated the cert.rdf to reflect cert.n3 and updated the rsa ontology
> to use the cert:int datatype.
>
> Let me know of any further bugs, and ideas for improvement.
>

Minor in comparison, but http://purl.org/dc/elements/1.1/created does not
exist in this dc elements schema. All you need to do is to switch to the dc
terms namespace http://purl.org/dc/terms/ instead which describes the
created property (affects cert and rsa). Note that using the dc prefix with
the dcterms namespace is common practice nowadays.

Steph.


>
>        Henry
>
> Social Web Architect
> http://bblfish.net/
>
> On 2 Aug 2010, at 16:23, Sarven Capadisli wrote:
>
> > f I'm not mistaken:
> >
> > $ curl -H "Accept: text/n3" http://www.w3.org/ns/auth/rsa
> >
> > [snip]
> >
> > :public_exponent a rdf:Property;
> >   vs:term_status "unstable";
> >   rdfs:comment """
> >       The exponent used to encrypt the message. Number chosen between
> >       1 and the totient(p*q). Often named 'e' .
> >    """;
> >   rdfs:domain :RSAPublicKey;
> >   rdfs:range cert:Integer .
> >
> > and
> >
> > $ curl -H "Accept: application/rdf+xml" http://www.w3.org/ns/auth/rsa
> >
> >    <rdf:Property rdf:about="rsa#public_exponent">
> >        <comment>
> >       The exponent used to encrypt the message. Number chosen between
> >       1 and the totient(p*q). Often named 'e' .
> >    </comment>
> >        <domain rdf:resource="rsa#RSAPublicKey"/>int a rdfs:Datatype;
> >   vs:term_status "unstable";
> >   owl:equivalentClass xsd:nonNegativeInteger;
> >   skos:editorialNote """
> >      We may decide to make it easier to write integers than what
> > xsd:integer provides, if needed.
> >   """@en;
> >   rdfs:comment """
> >      A positive integer in base 10 notation.
> >      xsd:nonNegativeInteger could be used, but is a bit long to write,
> > and may be too strictly defined.
> >      This is here to provice a pair with cert:hex, to avoid needing to
> > import a new namespace, and to give a bit more flexibility in the
> > future.
> >   """@en .
> >
> >        <range rdf:resource="cert#Integer"/>
> >        <vs:term_status>unstable</vs:term_status>
> >    </rdf:Property>
> >
> > both have range cert#Integer.
> >
> > The n3 and rdfxml serializations for http://www.w3.org/ns/auth/cert are
> > not equivalent as;
> >
> > $ curl -H "Accept: text/n3" http://www.w3.org/ns/auth/cert
> >
> > uses :int
> >
> > [snip]
> >
> > :int a rdfs:Datatype;
> >   vs:term_status "unstable";
> >   owl:equivalentClass xsd:nonNegativeInteger;
> >   skos:editorialNote """
> >      We may decide to make it easier to write integers than what
> > xsd:integer provides, if needed.
> >   """@en;
> >   rdfs:comment """
> >      A positive integer in base 10 notation.
> >      xsd:nonNegativeInteger could be used, but is a bit long to write,
> > and may be too strictly defined.
> >      This is here to provice a pair with cert:hex, to avoid needing to
> > import a new namespace, and to give a bit more flexibility in the
> > future.
> >   """@en .
> >
> > however,
> >
> > $ curl -H "Accept: application/rdf+xml" http://www.w3.org/ns/auth/cert
> >
> > uses :Integer
> >
> > [snip]
> >
> >    <owl:Class rdf:about="cert#Integer">
> >        <comment>
> >    The class of all integers, however large they be.
> >    This should probably be defined in another ontology.
> >    Different representations for each can be defined via relations to
> > string
> >    literals.
> >    This is equivalent to the values of xsd:integer literals, except
> > that we don't want to be locked into having to use a particular literal
> > notation. Some of these integers are so long it is much better to
> > express them in hexadecimal format.
> >    </comment>
> >        <vs:term_status>unstable</vs:term_status>
> >    </owl:Class>
> >
> > They appear to be different documents as opposed to same source document
> > with different serializations.
> >
> > So, initially I went with rsa's range for public_exponent and what cert
> > had for rdfxml.
> >
> > I think http://www.w3.org/ns/auth/cert 's n3 serialization should be
> > updated to reflect http://www.w3.org/ns/auth/rsa 's range for
> > public_exponent.
> >
> > If I'm mistaken or overlooking something, I'd like to learn why. Thanks.
> >
> > -Sarven
>
> _______________________________________________
> foaf-protocols mailing list
> foaf-protocols at lists.foaf-project.org
> http://lists.foaf-project.org/mailman/listinfo/foaf-protocols
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.foaf-project.org/pipermail/foaf-protocols/attachments/20100802/0d7f3955/attachment-0001.htm