- From: Richard Newman <r.newman@reading.ac.uk>
- Date: Fri, 9 Jul 2004 09:21:31 +0100
- To: www-rdf-interest@w3.org
Laurian, I would suggest using sameAs or equivalentProperty, if the semantics are equivalent (as may well be the case for, e.g. messageIDs). Similarly, use subPropertyOf if that's the actual case (as you suggest for DC identifier). You can do this for as many ontologies as you like to build mappings. I don't think seeAlso is really intended for this... anyone? I was under the impression that it referred to another document containing further description of a resource (though I may be wrong!). -Richard On 9 Jul 2004, at 03:55, Laurian Gridinoc wrote: > > Hello, > > When having such wide choice of partial overlapping vocabularies, what > would be the best solution -- to try to use from each the most > meaningful elements (mixing vocabularies), the result having a > namespace soup, or to create my own vocabulary and promote partial > understanding by usage of rdfs:seeAlso in its schema? > > Something like: > > <rdf:Property rdf:about="http://NEW/#messageid" rdfs:label="messageId" > rdfs:comment="The unique Message-Id"> > <rdfs:subPropertyOf > rdf:resource="http://purl.org/dc/elements/1.1/identifier"/> > > <rdfs:seeAlso > rdf:resource="http://xmlns.filsa.org/xmlns.filsa.net/emir/0.2/ > #messageid"/> > <rdfs:seeAlso > rdf:resource="http://www.openhealth.org/xmtp#Message-ID"/> > <rdfs:seeAlso rdf:resource="URN:ietf:params:rfc822:message-id"/> > > </rdf:Property> > > Or should I use owl:sameAs or owl:equivalentProperty instead of > rdfs:seeAlso? > > > Thank you, > -- > Laurian Gridinoc > Chief Developer > GRAPEFRUIT DESIGN > www.gd.ro >
Received on Friday, 9 July 2004 04:25:12 UTC