I agree with this proposal and have added it to the issues page for later resolution.
Thanks, - Dave On Mon, Apr 26, 2010 at 10:16 AM, Steve K Speicher <[email protected]> wrote: > To be consistent across different usages and identification of what version > of what domain a service provider implements I recommend these changes: > > 1) Have a single HTTP header called "OSLC-Version". Its value is limited to > each domain's "Version string". For example, of OSLC-CM 2.0 it would be > "oslc-cm-2.0" > > 2) Within the definition of the oslc:domain property on oslc:Service (and on > oslc:ServiceProviderCatalog): > > Currently it states: > oslc:domain (Resource, exactly-one) - namespace URI of the OSLC domain > specification that is implemented by this service. > > I recommend we change this to use the "Version string" above, such that it > reads: > oslc:domain (String, exactly-one) - Version string of the OSLC domain > specification that is implemented by this service. > > OR...Another approach would be to eliminate the version string and just use > namespace URI in HTTP header parameter > > Thanks, > Steve Speicher | IBM Rational Software | (919) 254-0645 > > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net > >
