Regarding RDF embedding: we're focusing on lyrics (and there's mo:Lyrics), and have at least song title, album name, and artist name. Lyrics can be associated with a mo:MusicalWork, a subclass of frbr:Work. Seems to be distinct from mo:Track, which is used by both MO's XSPF RDFizer and xiph's/XSPF's XSPF.xsl, which encode similar data, except for lyrics. They also employ FOAF, which has some generic properties and can indeed easily be attached/used, though they use strings (names) in place of foaf:Agent. It doesn't seem right, even though gets used that way from time to time.

By the way, MO examples use MusicBrainz to link the artists, but MusicBrainz only embeds some metadata in ld+json, which doesn't seem to be widely supported (not supported by librdf in particular, and AFAIK it's merely RDF-compatible, not quite one of serialization formats). Perhaps wouldn't harm to link them as an alternative, if we'll be fetching links to them in the future, but not very usable or easy to link right now.

I think we'll need to properly attach artist/album/song names to lyrics, possibly in different ways (using different ontologies/relations, that is), and perhaps will have to introduce separate artist and album IRIs that would be consistent across lyrics pages/search results (so, not just #artist).

Perhaps better to focus on other interfaces for now, since it's tricky and not immediately useful.

Design APIs #4

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions