{"action":"created","issue":{"url":"https://api.github.com/repos/marl/jams/issues/24","labels_url":"https://api.github.com/repos/marl/jams/issues/24/labels{/name}","comments_url":"https://api.github.com/repos/marl/jams/issues/24/comments","events_url":"https://api.github.com/repos/marl/jams/issues/24/events","html_url":"https://github.com/marl/jams/issues/24","id":56927294,"number":24,"title":"JAMS beyond music?","user":{"login":"bmcfee","id":1190540,"avatar_url":"https://avatars.githubusercontent.com/u/1190540?v=3","gravatar_id":"","url":"https://api.github.com/users/bmcfee","html_url":"https://github.com/bmcfee","followers_url":"https://api.github.com/users/bmcfee/followers","following_url":"https://api.github.com/users/bmcfee/following{/other_user}","gists_url":"https://api.github.com/users/bmcfee/gists{/gist_id}","starred_url":"https://api.github.com/users/bmcfee/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bmcfee/subscriptions","organizations_url":"https://api.github.com/users/bmcfee/orgs","repos_url":"https://api.github.com/users/bmcfee/repos","events_url":"https://api.github.com/users/bmcfee/events{/privacy}","received_events_url":"https://api.github.com/users/bmcfee/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/marl/jams/labels/enhancement","name":"enhancement","color":"84b6eb"},{"url":"https://api.github.com/repos/marl/jams/labels/question","name":"question","color":"cc317c"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-02-07T21:44:33Z","updated_at":"2015-02-11T16:29:57Z","closed_at":null,"body":"Just opening up a separate thread here (rather than the already bloated #13): is it worth considering designing JAMS to be extensible into domains outside of music/time-series annotation?\r\n\r\nI think the general architecture is flexible enough to make this possible with roughly zero overhead, and it might be a good idea.\r\n\r\nFrom what I can tell, all that we'd have to do is restructure the schema a little so that \"*Observation\" is slightly more generic.  We currently define two (arguably redundant) observation types that both encode tuples of `(time, duration, value, confidence)`.  It wouldn't be hard to extend this into multiple observation forms, say for images with bounding-box annotations, we would have `(x, x_extent, y, y_extent, value, confidence)`.  For video, we would have `(x, x_extent, y, y_extent, t, duration, value, confidence)`, etc.\r\n\r\nWithin the schema, nothing would really change, except that we change \"DenseObservation\" to \"DenseTimeObservation\" (and analogous for Sparse), and then some time down the road, allow other observation schema to be added.\r\n\r\nI don't think we need to tackle this for the immediate (next) release, except insofar as we can design to support it in the future in a backwards-compatible way.\r\n\r\nOpinions?"},"comment":{"url":"https://api.github.com/repos/marl/jams/issues/comments/73912113","html_url":"https://github.com/marl/jams/issues/24#issuecomment-73912113","issue_url":"https://api.github.com/repos/marl/jams/issues/24","id":73912113,"user":{"login":"justinsalamon","id":3009670,"avatar_url":"https://avatars.githubusercontent.com/u/3009670?v=3","gravatar_id":"","url":"https://api.github.com/users/justinsalamon","html_url":"https://github.com/justinsalamon","followers_url":"https://api.github.com/users/justinsalamon/followers","following_url":"https://api.github.com/users/justinsalamon/following{/other_user}","gists_url":"https://api.github.com/users/justinsalamon/gists{/gist_id}","starred_url":"https://api.github.com/users/justinsalamon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/justinsalamon/subscriptions","organizations_url":"https://api.github.com/users/justinsalamon/orgs","repos_url":"https://api.github.com/users/justinsalamon/repos","events_url":"https://api.github.com/users/justinsalamon/events{/privacy}","received_events_url":"https://api.github.com/users/justinsalamon/received_events","type":"User","site_admin":false},"created_at":"2015-02-11T16:29:57Z","updated_at":"2015-02-11T16:29:57Z","body":"I think a lower-hanging fruit would be non-music audio datasets (e.g. environmental sounds). I'm probably biased, but I feel this is an area where the need for annotated datasets is growing rapidly and would require minimal (or zero?) additional work to accommodate, right? Oh, and there's speech too..."}}