[rdfweb-dev] Tidy up your FOAF week

Libby Miller Libby.Miller at bristol.ac.uk
Fri Jun 18 08:41:36 UTC 2004


Christopher, you still need a creator property for each person, i.e.

        <dc:creator>
            <foaf:Person rdf:nodeID="ChristopherAllen">
        </dc:creator>
        <dc:creator>
            <foaf:Person rdf:nodeID="TimDierks">
        </dc:creator>

Libby

On Thu, 17 Jun 2004, Christopher Allen wrote:

> Morten Frederiksen wrote:
> > This looks wrong, as you are saying that the creator is the containing
> > RDF/XML document?
>
> I think this is fixed in the current version.
>
> >>         <dc:format>rfc2246; (&#38; (type='text/plain')
> >> (charset=US-ASCII) )</dc:format>
> >
> > Hmm, the format should likely be just "text/plain" or possibly
> > "text/plain; charset=US-ASCII"?
>
> I've seen a bunch of different examples of use for dc:format when I search it in
> google -- it looks like this is one tag that needs more examples and
> explanation.
>
> For now, I've got with the version used in example 2 at
> http://dublincore.org/documents/dcmes-xml/
>
> > Simply include two properties, one for each.
>
> Fixed.
>
> Current version:
>
> <foaf:Document rdf:nodeID="RFC2246>
>     <rdf:Description rdf:about="http://www.rfc-editor.org/rfc/rfc2246.txt">
>         <dc:title>RFC 2246 - The TLS Protocol (Version 1.0)</dc:title>
>         <dc:description>
>             This document specifies Version 1.0 of the Transport
>             Layer Security (TLS) protocol. The TLS protocol provides
>             communications privacy over the Internet. The protocol allows
>             client/server applications to communicate in a way that is designed
>             to prevent eavesdropping, tampering, or message forgery.
>         </dc:description>
>         <dc:creator>
>             <foaf:Person rdf:nodeID="ChristopherAllen">
>             <foaf:Person rdf:nodeID="TimDierks">
>         </dc:creator>
>         <dc:date>1999-01</dc:date>
>         <dc:type rdf:resource="http://purl.org/dc/dcmitype/Text" />
>         <dc:format>text/plain; charset=US-ASCII</dc:format>
>         <dc:language>en</dc:language>
>         <dc:publisher>IETF</dc:publisher>
>         <dc:identifier>RFC2246</dc:identifier>
>         <dc:rights>Copyright (C) The Internet Society (1999);  freely
> distributable</dc:rights>
>     </rdf:Description>
> </foaf:Document>
>
> Still seeking advice on the following:
>
> Christopher Allen wrote:
> > Hmm, I think I got the multiple dc:creator problem solved, but I
> > realized that my example before was just in the dc:* name domain
> > space, but I want to be in the foaf:* name space:
> >
> > Does this look correct? When I'm done I'll be adding it to my example
> > foaf document at http://web.lifewithalacrity.com/christophera/foaf.rdf
> >
> > Some questions: First question, I'd like to have this not be enclosed
> > by my foaf:person (the same way I cross-reference my foaf:knows so
> > that the full knows items are not enclosed my foaf:person), so do I
> > just put: <foaf:Document rdf:nodeID-"RFC2246"/> inside my foaf:person?
> >
> > My next question is the <rdf:Description
> > rdf:about="http://www.rfc-editor.org/rfc/rfc2246.txt"> line -- is
> > this the best place to define where the source document is located?
> > I've seen examples where that rdf:about refering to that document is
> > located in foaf:document instead.
> >
> > Another question: should I be using foaf:topic somehow? I'm confused
> > on how foaf:topic fits in with dc:* document descriptions.
> >
> > I also can't seem to find a way to represent the version of this
> > document (version 1.0), and I wasn't sure about any of the other dc:*
> > items, such as dc:subject, dc:contributor (there is a long list of
> > credits at the end of the RFC), dc:format, dc:source, dc:relation,
> > and dc:coverage.
>
> -- Christopher Allen
>
>
>
> _______________________________________________
> rdfweb-dev mailing list
> rdfweb-dev at vapours.rdfweb.org
> wiki: http://rdfweb.org/topic/FoafProject
> http://rdfweb.org/mailman/listinfo/rdfweb-dev
>



More information about the foaf-dev mailing list