W3C home > Mailing lists > Public > public-schemaorg@w3.org > June 2019

Arrangements, attribution and edge cases...

From: <schema@webfeet.org>
Date: Mon, 3 Jun 2019 08:29:01 +0200
To: public-schemaorg@w3.org
Message-ID: <0e012e65-662f-3939-0369-0b54175662cb@webfeet.co.uk>
A collection of thoughts, gaps and edge cases...

For recordings...

1..

    For a MusicComposition it is possible to specify a composer. What is
    not clear is how to markup that a tune is traditional...

    There are many shades of meaning here; something can be
    'traditional'; be written by 'anon'; the source is 'unknown' (or the
    source is simply not mentioned),

2...

    In a similar case, it is possible to specify that there's been an
    arrangement (musicArrangement property), but I don't see a property
    where you can give the arranger (who can be a person or group).

    I can imagine that it's possible to use a Role for the arranger but
    it would be nice to have a canonical example

3...

    Further, for a 'collected' (or 'recollected') traditional tune, how
    might one markup whom the tune was collected from or which published
    collection it was found in...

4...

    How do you mark up a Spoken Word recording (something that is not
    music), specifically so that it is not assumed to be music. Looking
    for something like "musicCompositionForm" but a little broader.
    Again a canonical example would be nice.

5...

    It would be nice to have an example of markup of an album
    re-released with bonus tracks. It seems overkill to duplicate markup
    for the common tracks - but it is not clear how you might include
    additional tracks in a different MusicRelease

6...

    It seems as if the schema.org markup differs from that used in
    MusicBrainz, do we assume that anything consuming this data has to
    handle both formats?

And for events...

7...

    A CreativeWork can have a genre; it would make sense for an Event
    also to have the same...

So many things, so many things...

    Webfeet
Received on Monday, 3 June 2019 06:31:50 UTC

This archive was generated by hypermail 2.3.1 : Monday, 3 June 2019 06:31:50 UTC