History:Technology Ideas Proposal
Status: This page collects various ideas how new technologies could be used with or integrated into MusicBrainz. Note however, that this is just a DumpList. If you want to help TurningYourIdeasIntoReality, then please create a page of its own for your idea and link to it from different related places.
Make a DAML+OIL ontology for music
The DAML language is being developed as an extension to XML and the Resource Description Framework (RDF). The latest release of the language (DAML+OIL) provides a rich set of constructs with which to create ontologies and to markup information so that it is machine readable and understandable.
How about this idea?
- DAML+Oil has been standardised into OWL as of late 2004: http://www.w3.org/2004/OWL/ -- DanielOconnor
Wow, impressive stuff. When looking at: http://www.daml.org/2001/03/daml+oil-walkthru.html a high level introduction it is easy to see that they have set a high goal with their bag of army money.
Work on MB is still at the basic level when comparing to these guys plans. We still need genre, replication, moderation etc. Johan
Have a look at the FreeDataLicense page.
Extending the MusicBrainz Database
I had a couple of thoughts about the way that MB's technology, or just the fact that it is a huge database of music information, could be used. Not sure any are realistic or actually useful, but here we go:
Ability to attach information about music/albums/artists in an InternetMovieDatabase type manner. Some of this is already there with the "others who liked this also liked..." and the fact that everyone is linked together. Adding links to album art, quotes, and random information could be interesting as well.
Scottm: In general, there are issues with putting links to off-site materials, esp. copyrighted materials such as album art. Fan sites may be a possibility, and there has been talk about consulting lawyers about how to handle these links.
A way to get album art. IIRC there was an album art site that had jpgs available for download which got shut down. However, other sites like amazon and walmart.com have album art there already, and it would just be a matter of figuring out the URL scheme (or just having a user submit field) to allow people pointers to the jpg itself, or to be more legal, a page with the album art on it.
Scottm: There was a reason the site was shut down! I am currently trying to contact Sony about album art, but the last thing we want to do is get sued by labels for illegally posting album art.
"buy this album" type links. Again, not necisarily something I'd use, but it could be used to make a deal with amazon or something and make MB more "commercial friendly".
Scottm: I agree! Espeically if MB gets a share of the profits :). There was also talk of the Donate CD to MB where we may be able to get a buck for every album donated.
Integrate with the apple music store. I'm not sure exactly how (other than maybe a itms:// link that would let mac users preview/buy a song right from the MB interface (or from any app that had that written in). This would also be handy to check to see if the variation of the song you are tagging is the correct one.
Scottm: I hope Apple releases a webservice to aid this type of functionality... It would be awesome to be able to purchase songs directly through MB
Creating an LDAP schema
LDAP stores data in a tree hirarchy. It thus translates perfectly from/to XML. This would allow to store MusicBrainz data in a directory. What would this be good for ? Well, personal networking gets more common day by day. Many users have installed MP3 jukeboxes in their Intranet. These rely on the traditional "pls" or similare playlist format.
Now with MusicBrainz, this could be extended and data could be stored central, and be available for all personal clients. The mediaplayers would simply connect to the server using the ldap-protocol and retreive information.
Advantages over a web-server ? Maybe none, but this would be an alternative that produces less overhead per connection.
LDAP (and ActiveDirectory) directories are actually "Yellow Pages". Now we would have such "Yellow Pages" for media files.
Public Namespace URIs?
Just read an interesting article on Slashdot (http://developers.slashdot.org/article.pl?sid=03/09/30/164210&mode=thread&tid=126&tid=95) about how the IETF has published a draft paper for an info: URI to set up public namespaces. I know that Musicbrainz already uses HTTP URIs (and I agree with that), but perhaps MusicBrainz could at least register and use this new set of URIs? (At least to prevent others from registerring such a base namespace as "musicbrainz").
-- Pipian 30-Sep-2003
I'd love to be able to use musicbrainz to identify the music I love; then reward the artist directly. Is it worth considering taking FOAF descriptions of artists (or an artist specific login for them that makes their FOAF for them); digitally signed, with a foaf:tipjar for their paypal. You would have trouble asserting artists are who they say they are; thats where the digital signing comes in.
-- DanielOconnor Aug-2004
Music Ontology (MO) project
The Music Ontology Specification provides main concepts and properties fo describing music (i.e. artists, albums, tracks, but also performances, arrangements, etc.) on the Semantic Web. Their document contains a detailed description of the Music Ontology. This project was based on MusicBrainz. In June 2007 some Music Ontology people hosted Robert Kaye of Musicbrainz at a seminar in London.
- http://musicontology.com/ - main page
- http://groups.google.com/group/music-ontology-specification-group - Music Ontology Specification Group mail list archive
It's a widely-shared opinion among contributors to ClassicalMusic content that MusicBrainz must have some way of describing MusicalWorks in order to solve tough problems of describing this genre. Defining a Music Ontology is an important part of that work. I haven't looked hard at the Music Ontology Specification itself to see how well it suits our needs. But it is interesting and worth watching. --JimDeLaHunt 2008-01-27