Skip to content
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

Updating the SALAMI namespaces #128

Open
bmcfee opened this issue Aug 12, 2016 · 2 comments
Open

Updating the SALAMI namespaces #128

bmcfee opened this issue Aug 12, 2016 · 2 comments
Assignees
Labels
enhancement schema Issues pertaining to schema definitions

Comments

@bmcfee
Copy link
Contributor

bmcfee commented Aug 12, 2016

After a chat with @jblsmith yesterday, it sounds quite likely that the SALAMI namespaces will need to be updated to include a "non-music" segment type at all levels.

As I understand it (and Jordan, correct me if I'm wrong here) this would to some extent replace the semantics of the Z boundaries to be more explicitly non-music-related, akin to the Silence label.

This should go out ahead of the next JAMS release, so I'm tagging it as 0.2.2. I know that it will be a little while before the SALAMI data gets revised for this change, but if we can settle on the label name now, we can have support for it when it's ready.

Sound good?

@bmcfee bmcfee added this to the 0.2.2 milestone Aug 12, 2016
@bmcfee bmcfee self-assigned this Aug 12, 2016
@urinieto
Copy link
Contributor

Sounds great, thanks!

On Fri, Aug 12, 2016 at 10:52 AM, Brian McFee [email protected]
wrote:

After a chat with @jblsmith https://github.com/jblsmith yesterday, it
sounds quite likely that the SALAMI namespaces will need to be updated to
include a "non-music" segment type at all levels.

As I understand it (and Jordan, correct me if I'm wrong here) this would
to some extent replace the semantics of the Z boundaries to be more
explicitly non-music-related, akin to the Silence label.

This should go out ahead of the next JAMS release, so I'm tagging it as
0.2.2. I know that it will be a little while before the SALAMI data gets
revised for this change, but if we can settle on the label name now, we can
have support for it when it's ready.

Sound good?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#128, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADhisZxClGjcThNu-rouYrRGhus-N8Sdks5qfJbEgaJpZM4JjN4B
.

@bmcfee bmcfee modified the milestones: 0.3.0, 0.2.2 Feb 11, 2017
@bmcfee bmcfee removed this from the 0.3.0 milestone Jul 6, 2017
@bmcfee bmcfee added the schema Issues pertaining to schema definitions label Aug 12, 2019
@bmcfee
Copy link
Contributor Author

bmcfee commented Aug 12, 2019

@jblsmith did that change to the salami annotations ever happen / could it? Or should we close this issue out?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement schema Issues pertaining to schema definitions
Projects
None yet
Development

No branches or pull requests

2 participants