I took an action from the last call to document some guidelines/guidance on URI naming. I started a draft at [1]
It is a work in progress at the moment, so comments are welcome [1] http://open-services.net/bin/view/Main/OSLCCoreURINamingGuidance Thanks, Steve Speicher | IBM Rational Software | (919) 254-0645 [email protected] wrote on 09/22/2010 10:38:06 PM: > From: Scott Bosworth <[email protected]> > To: [email protected] > Date: 09/22/2010 10:38 PM > Subject: [oslc-core] Namespace uri's > Sent by: [email protected] > > Per the decisions made in today's Core workgroup call, I've configured things on > open-services.net so that references to OSLC namespace uri's will be handled > according to the W3C Best Practices for publishing RDF Vocabularies [1]. > > I followed recipe 3 for hash namespaces: handling both html and rdf+xml > requests. Html requests for an OSLC namespace uri (e.g. open-services.net/ns/core > ) will result in a redirect to the appropriate specification wiki page. > Additionally, rdf+xml requests are also configured, though no rdf documents > have been published at this point. The default response is html. > > Things should work for namespace uris that have adopted the http://open- > services.net/ns/* convention, specifically the core, am, cm, qm, rm, and scm > namespace uri's. You can test them out by typing an oslc namespace uri in your > browser. You should be redirected to the appropriate spec page. > > Thanks...Scott > > [1] http://www.w3.org/TR/swbp-vocab-pub/_______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net
