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.
Home Page: http://purl.org/ontology/mo/
Create a representation of founding members, perhaps either (Barry's initial suggestion) as a subproperty of mo:member or (Yves' refinement) as a subclass of mo:Membership.
The mapping of the MBZ 'release types' seems to be a bit difficult, since they are directly related to MBZ 'release groups' which are mapped to mo:SignalGroup [1] instances. This class is on the expression level. However, the mo:release_type [2] property currently relates to mo:MusicalManifestation [3], i.e. to instances that are on the manifestation level, e.g., mo:Release [4] instances. I'm currently unsure whether we should switch the domain of mo:release_type to mo:MusicalExpression [5], or whether I should create a mapping for mo:Release instances that are related to their release types.
Currently, I would prefer the second one.
[1] http://musicontology.com/#term_SignalGroup
[2] http://musicontology.com/#term_release_type
[3] http://musicontology.com/#term_MusicalManifestation
[4] http://musicontology.com/#term_Release
[5] http://musicontology.com/#term_MusicalExpression
The 'encoding' link seems to be be broken found at http://musicontology.com/specification/#term-encoding references http://purl.org/ontology/mo/encoding, which returns a broken 302 redirect.
$ curl -i http://purl.org/ontology/mo/encoding
HTTP/1.1 302 FOUND
Server: nginx/1.4.6 (Ubuntu)
Date: Tue, 28 Aug 2018 17:17:01 GMT
Content-Type: text/html; charset=utf-8
Content-Length: 223
Connection: keep-alive
Location: http://pingthesemanticweb.com/ontology/mo/musicontology.rdfs
Access-Control-Allow-Origin: *
<!DOCTYPE HTML>
<html>
<head>
<title>302 Found</title>
</head>
<body>
<h1>Found</h1>
<p>The resource requested is available <a href="http://pingthesemanticweb.com/ontology/mo/musicontology.rdfs">here</a>.<p>
</body>
</html>
The 302 redirect points to the pingthesemanticweb.com domain, which appears to be a german bitcoin website. The /ontology/mo/musicontology.rdfs resource appears to be unavailable.
Add Pseudo-Release as mo:ReleaseStatus instance as it is one of the four release states of MBZ.
When opening or importing the MusicOntology in Protege, I get an error that the SimilarityOntology cannot be found. The purl URL http://purl.org/ontology/similarity/ for the ontology no longer resolves.
Add a property to relate work types to mo:MusicalWork instances. Currently, MBZ differentiate between 17 work types which are:
musicbrainz_db=# SELECT * FROM musicbrainz.work_type;
id | name
----+------------
1 | Aria
2 | Ballet
3 | Cantata
4 | Concerto
5 | Sonata
6 | Suite
7 | Madrigal
8 | Mass
9 | Motet
10 | Opera
11 | Oratorio
12 | Overture
13 | Partita
14 | Quartet
15 | Song-cycle
16 | Symphony
17 | Song
(17 rows)
This probably requires the creation of a new class for work types, e.g., mo:WorkType.
While dealing with this issue at the moment, I raised this agonized question one more time at the MBZ dev IRC channel:
<zazi> one release can different catalog numbers
<zazi> or
<zazi> a catalog number can have different releases
<zazi> ?
<ocharles> A release has multiple release labels (label/cat no pairs)
<reosarevok> zazi: all the labels and catalog numbers for a single release are supposed to be related to the same country-date (that is, the actual CD or whatever was published as a cooperation by two or more labels, or the label gave it several catalog numbers)
<reosarevok> (also, a catalog number can be in different releases, for example if the label gave the same catalog number to the CD and vinyl editions)
<reosarevok> (but AFAIK it doesn't link them in any way in the database, it just means they happen to have the same info in that field)
<zazi> yep, that's what I thought as well
My conclusion is that we should move the domain of mo:catalogue_number and mo:label to mo:ReleaseEvent instead of mo:Release. Any opinions?
See also [1] for an earlier discussion at the MO mailing list about this issue.
Hello,
I am looking at supporting rendering the Music Ontology specification using phpspecgen:
http://www.aelius.com/njh/phpspecgen/phpspecgen.php
One of the requirements is support for the Music Ontology's concept of levels - which is currently unique to the Music Ontology.
VANN gives a very similar concept of a Term Group:
http://vocab.org/vann/termGroup
nick.
Hello,
Just noticed that some of the arrows are not rendering properly ing the the Workflow diagram PNG:
http://musicontology.com/img/[email protected]
Could someone re-render it?
nick.
Added:
Add a property to relate release packagings to mo:MusicalManifestation instances. Currently, MBZ differentiate between 5 (6) release packaging types which are:
![http://musicontology.com/img/[email protected]](http://musicontology.com/img/workflow@2x.png){kind=link}
musicbrainz_db=# SELECT * FROM musicbrainz.release_packaging;
id | name
----+-----------------
1 | Jewel Case
2 | Slim Jewel Case
3 | Digipak
4 | Paper Sleeve
5 | Other
6 | Keep Case
(6 rows)
This probably requires the creation of a new class for release packagings, e.g., mo:ReleasePackaging. See also [1].
[1] http://wiki.musicbrainz.org/Next_Generation_Schema/Release_Packaging
rdf:type instead of rdfs:type, see https://groups.google.com/d/topic/music-ontology-specification-group/DqhKBGeOKXI/discussion
Add a property to relate label types to mo:Label instances. Currently, MBZ differentiate between 7 label types which are:
musicbrainz_db=# SELECT * FROM musicbrainz.label_type;
id | name
----+---------------------
1 | Distributor
2 | Holding
3 | Production
4 | Original Production
5 | Bootleg Production
6 | Reissue Production
7 | Publisher
(7 rows)
This probably requires the creation of a new class for label types, e.g., mo:LabelType.
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.