Re: [oslc-core] Changes to valueType and representation shape properties (was: Dialog discovery: triple and Link header for discovery of dialogs won't be on same resources)

[Nick Crossley <ncrossley@us.ibm.com>]

I agree with all Martin's points, and would add:

> 2. There isn't a problem in changing the shape documents to reflect this, as no v2 clients will be relying on them as we didn't publish any at v2.

While the specs themselves did not publish any shape documents, there is considerable usage of shapes in existing code. IBM tools publish shapes, and use them in reporting. Deprecating the terms will not, of course, break any of that existing code.

> 3. Any references in the spec to oslc:LocalResource would become oslc:AnyResource with an oslc:representation of oslc:Inline.

And any usage of oslc:LocalResource in existing producers should be changed to oslc:AnyResource with an oslc:representation of oslc:Inline; consumers are advised to allow oslc:LocalResource and treat it as oslc:AnyResource with an oslc:representation of oslc:Inline for compatibility.

> 4. [ ... Clients that can only work with blank nodes or hash URIs for inline resources ...]

I doubt this is an issue.

> 5. Any references in the spec to oslc:Resource become oslc;AnyResource with an oslc:representation of oslc:Reference.

And any usage of oslc:Resource in existing producers should be changed to oslc:AnyResource with an oslc:representation of oslc:Reference; consumers are advised to allow oslc:Resource and treat it as oslc:AnyResource with an oslc:representation of oslc:Reference for compatibility.

Nick.