-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add property/properties to represent EIDR identifiers (of media works and edits/editions) #2469
Comments
Looking into the details, it seems there are two flavours of EIDR identifier, which share a common identifier space and which can't be distinguished by inspecting the identifier string:
The former identifies larger units of content, the latter is specific to edits. We may need two properties, in which case I suggest attaching them just to audio/visual types so that we don't over-clutter /CreativeWork. |
I got this far,
|
Related: I noticed this morning that MusicRecording does not have the ISWC identifier https://www.wikidata.org/wiki/Property:P1827 The ISWC is the global identifier for the work (this identifies the writer and publisher). The ISRC (which is already a property of MusicRecording (https://schema.org/isrcCode) designates a recording of a work. For instance, T-Bone Walker's "Stormy Monday" (ISWC = T0702439915) has been recorded hundreds of times by dozens of artists, each of those recordings will (eventually) have a unique ISRC. Since the schema for isrcCode mentions Musicbrainz, the collection of recordings related to the "Stormy Monday" ISWC are here. https://musicbrainz.org/work/cf688650-2a34-3700-aa7d-07157d0a7ec5 The format for ISWC on MusicBrainz is: ISWC: T-070.243.991-5 and the ISWC is one of the main identifiers for using the MusicBrainz API. The ISWC contains original publisher and author information for licensing and even an original artist will want to include the code to credit the original publisher. Additional "publishers" (https://schema.org/publisher) are generally licensed create / publish the recording (a rendition of the work) and pay residuals to the owners listed in the ISWC. When music is used in a film, a "sync" license is required, and the ISWC is the modern source for identifying the parties to obtain the sync license. |
Looking at this a bit more, https://ui.eidr.org/view/content?id=10.5240/7EC7-228A-510A-053E-CBB8-J (click around for full record and relationships) you can see the model is very FRBR-like. They have strong identifiers at the broadest level, aspiring to a single ID for a Work("Abstraction"). Then Edit is the different edits/cuts of a movie. So the first Ghostbusters movie gets a single ID at the top level and a bunch of edits, each of which can also be said to have manifestations. Individual copies/items seem to be out of scope. |
I think /workEIDR and /editEIDR for the two concepts here... see https://ui.eidr.org/view/content?id=10.5240/B752-5B47-DBBE-E5D4-5A3F-N (relationships tab) |
See #2482 (comment) for attempt at an example. |
This file got dropped accidentally during the fast-tracking of COVID-changes last month. See github issue for history; originally modeled with a single property but using two now to better capture the semantics of EIDR.
Implemented in commit 60c9674 |
#3297 Requesting update to the titleEIDR to add it to TVSeason and TVSeries as EIDR identifiers are used for those instances by the EIDR and Google: E.g.: Google's Media Action Developer site already recommends titleEIDR for both TVSeason and TVSeries. |
Analogous to /isbn, there is a widely used identifier called EIDR ( wikipedia, wikidata ) which we don't have a property for in schema.org.
I propose fixing this, using the same definition as Wikidata: "Identifier for a film or television work, edit or manifestation, in the Entertainment Identifier Registry".
According to Wikipedia, it is applicable to a wide range of entity types, so I suggest associating the property simply with CreativeWork.
In terms of expected adoption, we would expect to make some use of this at Google.
The text was updated successfully, but these errors were encountered: