W3C home > Mailing lists > Public > w3c-rdfcore-wg@w3.org > August 2001

Re: RDF Issues from MusicBrainz

From: Graham Klyne <Graham.Klyne@baltimore.com>
Date: Mon, 13 Aug 2001 13:01:04 +0100
Message-Id: <>
To: Aaron Swartz <aswartz@upclink.com>
Cc: RDF Core <w3c-rdfcore-wg@w3.org>
At 12:52 AM 8/5/01 -0500, Aaron Swartz wrote:
>    - Do you have any tips on how to write a vocabulary spec
>      for inclusion into IETF spec? Drew Streib @ freedb wants to use
>      MM for CD lookups and he wants to push this through the IETF.
>      Has this been done before for an RDF vocab?

Here's one I did:


(This draft is currently expired, but still online (as of today).  I do 
intend to refresh it and complete the spec when some other work comes to 
fruition -- real soon, I hope.)

You may note that, in this case, I've focused on presenting the XML and 
brining in the RDF as an "afterthought".  It was very easy to sell this 
approach to one of our developers for inclusion into a product.

There is one problem with this that I think will be difficult to resolve to 
the complete satisfaction of all:  addresses are URIs, but presented as RDF 
literals.  It is my belief that, at this time, it would be very difficult 
to sell the idea of using rdf:resource= in this context.  (I would hope 
that, in due course, we could use an RDF schema with an xsdt:anyURI data 
type on the literal value and some inference rules to knit the graph 
together, but that would be outside standard RDF.)


Graham Klyne                    Baltimore Technologies
Strategic Research              Content Security Group
<Graham.Klyne@Baltimore.com>    <http://www.mimesweeper.com>

The information contained in this message is confidential and is intended 
for the addressee(s) only.  If you have received this message in error or 
there are any problems please notify the originator immediately.  The 
unauthorized use, disclosure, copying or alteration of this message is 
strictly forbidden. Baltimore Technologies plc will not be liable for direct, 
special, indirect or consequential damages arising from alteration of the 
contents of this message by a third party or as a result of any virus being 
passed on.

This footnote confirms that this email message has been swept by 
Baltimore MIMEsweeper for Content Security threats, including
computer viruses.
Received on Monday, 13 August 2001 10:14:36 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:50 UTC