[rdfweb-dev] Tidy up your FOAF week
mof-rdf at mfd-consult.dk
Thu Jun 17 22:13:28 UTC 2004
On Thursday 17 June 2004 23:49, Christopher Allen wrote:
> <foaf:Person rdf:nodeID="ChristopherAllen">
> <foaf:Person rdf:nodeID="TimDierks">
This is invalid (and not well-formed), each property must have exactly one
object - see http://www.w3.org/2001/10/stripes/ .
> 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
In that file, you can move the properties in the first rdf:Description
element to the foaf:personalProfileDocument element - since they have the
> 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?
What do you want to say, that is, how do you relate to the document (if you
do)? Remember, you don't have to reference everything from yourself, having
more than one thing described in a single file is quite allright.
> 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.
As with the properties about your FOAF file, there's really no difference.
The above are two ways of writing the same thing. I know which way I would
> Another question: should I be using foaf:topic somehow? I'm confused on how
> foaf:topic fits in with dc:* document descriptions.
foaf:topic is for relating a document to what it is about. In the case of an
RFC, I'm not sure which resource it could reasonably be said to be about,
unless you want to separate the document from the RFC-as-a-concept - which
might be reasonable in some situations.
More information about the foaf-dev