|
|
Post by puwen on Jun 25, 2022 8:38:58 GMT
What to think about products that claim to support old Schema Supplement (DSP0268)?
Here is a real situation:
(1) [Product A] says it follows DSP0266 1.11 and DSP2068 2019.2
(2) The current version of Processor schema is v1.5.1 ("@odata.type": "#Processor.v1_5_1.Processor")
(3) Customer requested to add "OperatingSpeedMHz" property but unfortunately it supported since v1.8
In my opinion, claiming to follow old schema only means the baseline version in use.
It doesn't restrict developers from using newer versions in certain resources if they really need to.
So I expected to replace v1.5.1 with v1.8 and add property directly (and backend functionality).
Is this legally implemented and is there a risk?
What would you do in this situation?
Thanks for any suggestions and sharing.
BR,
Puwen
|
|
|
|
Post by jautor on Jun 26, 2022 17:18:10 GMT
What to think about products that claim to support old Schema Supplement (DSP0268)? Here is a real situation: (1) [Product A] says it follows DSP0266 1.11 and DSP2068 2019.2 (2) The current version of Processor schema is v1.5.1 ("@odata.type": "#Processor.v1_5_1.Processor") (3) Customer requested to add "OperatingSpeedMHz" property but unfortunately it supported since v1.8 In my opinion, claiming to follow old schema only means the baseline version in use. It doesn't restrict developers from using newer versions in certain resources if they really need to. So I expected to replace v1.5.1 with v1.8 and add property directly (and backend functionality). Is this legally implemented and is there a risk? What would you do in this situation? Thanks for any suggestions and sharing. BR, Puwen
Yes, that is perfectly fine and very much expected. The schema "bundle" release versions are there solely to reduce the amount of attention that developers have to spend keeping up with the individual schemas. We had originally expected to just release individual schemas as they were enhanced, but it's clear now (since for example, there were 30+ minor revisions in our last release) that that would have been very confusing. So we "bundled" all the changes together to release them 3-4 times per year.
But each schema is still versioned independently, and it is certainly common for implementations to base their support on a bundle release as a target, but use later versions of particular schema as necessary. This does provide some common point to set expectations with users, suppliers, or project managers.
So stating that you support "release bundle 2019.2" as your baseline, but Processor v1.8.0 (and perhaps any other schema from later bundles) is exactly what we would expect.
In terms of reporting - my opinion is that this is the best approach, because it gives the most accurate but simple answer to the question of "what version do you support". The fact that you have a one or a few schema updated to later bundles is a minor detail. My analogy would be to talk about a car - if you say you have a 2010 Honda Accord - folks will know what to expect. The fact that you upgraded the car's stereo to a newer one with Bluetooth and USB ports, doesn't make it a 2022 model - and calling it as such would give the wrong impression. Certainly would upset a buyer! 
Hope that helps,
Jeff
|
|
|
|
Post by puwen on Jun 29, 2022 6:33:54 GMT
Hi Jeff,
Thanks for the clarification.
This is very helpful to me.
BR,
Puwen
|
|
