libby.miller at b...
Fri Jul 26 07:58:28 UTC 2002
I don't think the format you suggest is unreasonable. There might be a
case for separating out the project url to be at the end of a
projectHomepage or somesuch property if you think it might change.
I recently wasted a chunk of a day trying to disentangle a mess that
happened when RDF merged data in unexpected ways because as a shortcut I
collapsed the notion of an organisation with its homepage. I'm not sure
if that applies here. Basically the test is - is any given project
likely to have more than one title and/or description, and if it is,
does it matter if they all get hung off that one node?
On the other hand, this might be what you want if you are pulling in
information from various places separately about title and description
of a given project.
You might be asking about the range of currentProject. We've
deliberately left ranges general (after some false starts). So the form
you use is compatible with the current range of Resource.
On Fri, 26 Jul 2002, Earle Martin wrote:
> <delurk />
> Howdy do. I have a question/suggestion regarding the nature of the currentProject
> At the moment its range is rdfs:Resource. However, I'd like to do something
> like the following:
> <rdf:Description rdf:about="http://example.com/">
> <dc:title>Example Project</dc:title>
> <dc:description>A truly exemplary project.</dc:description>
> Is this a reasonable idea? Or have I misgrasped something imporant?
> despite all the computations
> you could just dance to a rock'n'roll station
> To unsubscribe from this group, send an email to:
> rdfweb-dev-unsubscribe at egroups.com
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
More information about the foaf-dev