[oslc-cm] Version compatibility story for 2.0 and 1.0

[Steve K Speicher]

I wanted to raise the discussion of this open issue to the mailing list:

25. OPEN Seems undesirable to require OSLC-Core-Version as it will require 
every version going forward to have it. Would be better if there was a 1.0 
requirement or way that it would be clear (SteveSpeicher for JDR, 
06/15/2010) 

One consideration is that there is almost a known number of 1.0 
implementations.  In two years, will all or most implementations be based 
on 2.0 and the new core guidance?  It would seem undesirable to require 
all these new implementations to have this header and test of it if 
eventually all implementations will be 2.0 based.

I'd be interested in feedback on:
- Is there a version story that can allow no special treatment for 2.0 
implementers?  For example, require only 1.0 impls to use 1.0 defined 
content/mime types.
- Tolerance for changes that may affect some 1.0 implementations
- Whether working group sees this HTTP request/response header 
(OSLC-Core-Version) as an issue?

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645