Simon Reinhardt wrote:
Kingsley Idehen wrote:
All,
To be clear, the resource URI associated with the resource
description page:
<http://kingsley.idehen.name/page/artist/3c79e3ff-f41b-45d8-af26-40151798056b>
is:
<http://kingsley.idehen.name/music/artist/3c79e3ff-f41b-45d8-af26-40151798056b>
(*we need to add the missing foaf:primarytopic link to the
description page*).
Also currently missing is an "owl:sameAs" triple that express link
to:
<http://musicbrainz.org/artist/3c79e3ff-f41b-45d8-af26-40151798056b>
(should they someday publish RDF based Linked Data).
Btw, be aware that MusicBrainz is in the process of changing a lot of
things. First, they're currently re-writing the frontend with a
different template engine to make the code cleaner and make it more
attractive for new developers, allow for i18n, etc. If you're planning
to bring RDFa to their pages, now's the time. ;-)
After that they will tackle major schema changes that will add new
resource types and change the semantics of the existing types quite
considerably. Just to make you aware that things might not be very
stable, looking into the future.
Another way of merging descriptions of MusicBrainz linked data is by
using MusicBrainz identifier properties (to be added to the Music
Ontology) that would be IFPs pointing to the UUIDs directly.
Yes, this is also where UMBEL can help. For instance the homepage
property is an IFP, ditto a few others. UMBEL and a middle layer binding
ontology delivers value in this regard.
Note, Yves, Fred, and other people from the Music Ontology effort will
naturally track the MBZ evolution in concert with us etc. :-)
Kingsley
Simon
--
Regards,
Kingsley Idehen Weblog: http://www.openlinksw.com/blog/~kidehen
President & CEO
OpenLink Software Web: http://www.openlinksw.com
