You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
schema:TVEpisode owl:equivalentClass po:Episode ; rdfs:subClassOf po:Programme .
schema:TVSeason owl:equivalentClass po:Series ; rdfs:subClassOf po:Programme .
schema:TVSeries owl:equivalentClass po:Brand ; rdfs:subClassOf po:Programme .
schema:episodes shouldn't be using a list as a range - I suggest using po:episode there.
schema:episodeNumber owl:equivalentProperty po:position .
schema:seasonNumber owl:equivalentProperty po:position .
schema:seasons owl:equivalentProperty po:series .
MO (http://musicontology.com):
schema:AudioObject owl:equivalentClass mo:AudioFile.
schema:MusicAlbum owl:equivalentClass mo:Record.
schema:MusicRecording owl:equivalentClass mo:Track. (not sure about this one - the schema.org definition is ambiguous to say the least!)
schema:Event owl:equivalentClass event:Event .
schema:Festival owl:equivalentClass mo:Festival .
schema:MusicEvent owl:equivalentClass mo:Performance .
Another note - I am unsure how Duration is supposed to be used, as it seems to map straight to a datatype.
The text was updated successfully, but these errors were encountered:
Yves, these are great. Don't worry too much about precision—schema.org is quite fuzzy, and intentionally so I believe, so our mappings can be fuzzy too. Do you consider these complete or can you come up with more?
Just a few comments and additions to the MO mapping:
re schema:MusicRecording - I guess, it really depends here on what is represented on the related, whether it is a mo:Signal (expression level) or mo:Track (manifestation level); I would exclude the item level for now, since one can relate the concrete encoding via the 'encoding' relation (which is of the schema:MediaObject)
re. schema:MusicAlbum - I would tend to suggest mo:Release instead since a mo:Release can contain several mo:Record instances, e.g., a music album that consists of two CDs; however, the problem there is that schema:MusicRecording instances can be related to schema:MusicAlbum which would then be equivalent to mo:Record instances - to sum up the do not really deal with releases that consists of multiple "records"
Just wondering whether we could map the resulting schema to PO and MO. A couple of mappings that come to mind:
BBC PO (http://www.bbc.co.uk/ontologies/programmes):
schema:TVEpisode owl:equivalentClass po:Episode ; rdfs:subClassOf po:Programme .
schema:TVSeason owl:equivalentClass po:Series ; rdfs:subClassOf po:Programme .
schema:TVSeries owl:equivalentClass po:Brand ; rdfs:subClassOf po:Programme .
schema:episodes shouldn't be using a list as a range - I suggest using po:episode there.
schema:episodeNumber owl:equivalentProperty po:position .
schema:seasonNumber owl:equivalentProperty po:position .
schema:seasons owl:equivalentProperty po:series .
MO (http://musicontology.com):
schema:AudioObject owl:equivalentClass mo:AudioFile.
schema:MusicAlbum owl:equivalentClass mo:Record.
schema:MusicRecording owl:equivalentClass mo:Track. (not sure about this one - the schema.org definition is ambiguous to say the least!)
schema:Event owl:equivalentClass event:Event .
schema:Festival owl:equivalentClass mo:Festival .
schema:MusicEvent owl:equivalentClass mo:Performance .
Another note - I am unsure how Duration is supposed to be used, as it seems to map straight to a datatype.
The text was updated successfully, but these errors were encountered: