{"action":"opened","issue":{"url":"https://api.github.com/repos/marl/jams/issues/40","labels_url":"https://api.github.com/repos/marl/jams/issues/40/labels{/name}","comments_url":"https://api.github.com/repos/marl/jams/issues/40/comments","events_url":"https://api.github.com/repos/marl/jams/issues/40/events","html_url":"https://github.com/marl/jams/issues/40","id":86611342,"number":40,"title":"A schema for collections?","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":0,"created_at":"2015-06-09T14:09:02Z","updated_at":"2015-06-09T14:09:02Z","closed_at":null,"body":"Going back to [this comment](https://github.com/marl/jams/issues/5#issuecomment-73518564), we punted on the idea of managing extrinsic data (eg, file paths) explicitly from within a JAMS object. Now that the dust has settled a bit on JAMS schema, I'm wondering if we can come up with a better solution than sandboxing this stuff.\r\n\r\nI bring this up because maintaining links between audio content and annotations is still kind of a pain, and I'd prefer to not solve it over and over again.\r\n\r\nHow do people feel about introducing an interface/schema for managing collections of jamses?  At the most basic level, this would provide a simple index of audio content, jams content, and collection-level information.  (It might also be useful to index which annotation namespaces are present in each jams file.)  This kind of thing can spiral out of control easily, so if we do it, we should keep it tightly scoped."}}