From: Melanie C. <mco...@gm...> - 2012-07-13 21:15:59
|
After checking the ID policy at http://obofoundry.org/id-policy.shtml. URIs should be of the form FOUNDRY_OBO_URI ::= "http://purl.obolibrary.org/obo/" IDSPACE "_" LOCALID which would prevent the below purl.obolibrary.org/obo/msrv/oae/ Happy to hear any suggestion as to how we could formalize the ID space hierarchy. Cheers, Melanie > > >> I still feel that some of these form a hub of closely interoperating ontologies, and would prefer to see that formalized. This might involve a parent ID space, similar to what I believe best for the IDO family of ontologies. > > I agree that having a parent space would be good (as you know in the context of IDO I am in favour of a scheme that would use /ido/ and then extend for other efforts) > I am just not sure how it would work out in this case - OAE and AERO pre exist so it may be hard to ask them to update their URIs (arguably, AERO is not being used, so I could update relatively easily in this case). We could ultimately have MSrv/OAE and MSrv/AERO, and then ask future extensions (e.g., MSrv/DAE for device adverse event) to abide by this scheme. > > I do see MSrv and OGMS at the same level - small umbrella efforts - so I don't think there ought to be a formalization there. > > If you think the above is better, I can commit on making the change for AERO, and will ask Oliver and the OAE team if they'd be willing to update to purl.obolibrary.org/obo/msrv/oae/ > > Melanie |