- From: Vicki Tardif <vtardif@google.com>
- Date: Tue, 12 Nov 2019 20:50:18 -0500
- To: Andrew Crimer <andrew.crimer@gmail.com>
- Cc: Richard Wallis <richard.wallis@dataliberate.com>, Tudor Sfatosu <tudor@boomerangcreative.agency>, "public-schemaorg@w3.org" <public-schemaorg@w3.org>
- Message-ID: <CAOr1obGv7C74iTgkAQH7bxss2TL5qSKP7ehFsRqPcmO1kQYLSQ@mail.gmail.com>
It might be best to move this to GitHub for better tracking, but with that said, I agree that we should add key and BPM to the recording as those can change independent of the composition. I know fitness instructors will search based on BPM, so it seems useful. - Vicki On Tue, Nov 12, 2019 at 7:29 PM Andrew Crimer <andrew.crimer@gmail.com> wrote: > In the real world, key and bpm both vary by performance, even among > performances of the same composition. Additionally, they can and do vary > within a piece. > > The most obvious application of bpm in structured data being DJs and > choreographers looking for pieces at specific speeds, bpm seems like it > should belong to MusicRecording and not MusicComposition. Also, tempo > approximates bpm (or, bpm is a measure of tempo as performed) and is open > to interpretation, so most written western music has no specific bpm value > to make use of that property. > > On Tue, Nov 12, 2019 at 2:59 PM Richard Wallis < > richard.wallis@dataliberate.com> wrote: > >> MusicRecording <http://schema.org/MusicRecording> has a *recordingOf* >> property that links it to the MusicComposition >> <http://schema.org/MusicComposition> description which includes a >> *musicalKey* property. >> >> Not sure which data consumers would make use of a *bpm* value. >> >> Richard Wallis >> Founder, Data Liberate >> http://dataliberate.com >> Linkedin: http://www.linkedin.com/in/richardwallis >> Twitter: @rjw >> >> >> >> On Tue, 12 Nov 2019 at 18:42, Tudor Sfatosu < >> tudor@boomerangcreative.agency> wrote: >> >>> Hi, >>> >>> >>> >>> Should *MusicRecording* not include *BPM* and *Musical Key?* >>> >>> >>> >>> Thank you, >>> >>> Tudor >>> >>> Tudor Sfătosu >>> Frontend Developer >>> >>> [image: >>> http://www.bdzholdings.com/company-signatures/Boomerang/images/sign-boomerang-logo.jpg] >>> >>> >>> >>> Boomerang Creative >>> University House, Oxford Square, Oxford Street , Newbury, Berkshire, >>> RG14 1JQ >>> >>> [image: >>> http://www.bdzholdings..com/company-signatures/Boomerang/images/facebook-btn.png] >>> <https://www.facebook.com/BoomerangCreative/>[image: >>> http://www.bdzholdings.com/company-signatures/Boomerang/images/instagram-btn.png] >>> <https://www.instagram.com/boomerangcreative/>[image: >>> http://www.bdzholdings.com/company-signatures/Boomerang/images/linkedin-btn.png] >>> <https://www.linkedin.com/company-beta/5267278/>[image: >>> http://www.bdzholdings.com/company-signatures/Boomerang/images/twitter-btn.png] >>> <https://twitter.com/boomerang_web> >>> >>> t: 01635 517 569 >>> f: 01635 517 592 >>> e:tudor@boomerangcreative.agency >>> w: www.boomerangcreative.agency <http://www.boomeranginternet.co.uk/> >>> >>> Ltd Co. Reg: 5824956 >>> This email is from BDZ Holdings Limited or one of its Subsidiary >>> Companies. Its contents are confidential to the intended recipient(s) at >>> the email address(es) to which it has been addressed. It may not be >>> disclosed to or used by anyone other than the addressee(s), nor may it be >>> copied in any way. If received in error, please contact the sender, then >>> delete it from your system. Although this email and attachments are >>> believed to be free of virus, or any other defect which might affect any >>> computer or IT system into which they are received and opened, it is the >>> responsibility of the recipient to ensure that they are virus free and no >>> responsibility is accepted by BDZ Holdings Ltd for any loss or damage >>> arising in any way from receipt or use thereof. >>> >>> >>> >> > > -- > acrimer.com > <https://acrimer.com?utm_source=signature&utm_medium=email&utm_campaign=passive> >
Attachments
- image/jpeg attachment: image001.jpg
- image/png attachment: image002.png
- image/png attachment: image003.png
- image/png attachment: image004.png
- image/png attachment: image005.png
Received on Wednesday, 13 November 2019 01:50:35 UTC