Subschema's are not deterministic about data-models HOT 4 CLOSED

What you say is completely right.
Eventually, a change in the GSMA-commons(or location commons) would alter the referred schemas. But we have very good reasons for not changing it or that the change does not affect current models (i.e. a new attribute but keeping all old ones)
In fact, our policy is that we never do backward incompatible versions. Could this happen in the coming future? Nothing is impossible but I cannot envision a reason to do it and of course never without deep consultation with the users and contributors.
Anyhow we are open to adopt other additional mechanism to fix this.

from data-models.

Besides now we have a draft of a database of data models' versions so you can gather the moment when the extract was created. Grabbing the information from model.yaml (which has the $ref attributes) should be solved.

from data-models.

Regarding these two options

1. https://smart-data-models.github.io/data-models/common-schema.json#/definitions/GSMA-Commons
   or

2. https://raw.githubusercontent.com/smart-data-models/data-models/c4ee5d39bcbacdc30700bcd2d916aaf2c50dc86e/common-schema.json#/definitions/GSMA-Commons

3. in the model.yaml of the data model these references are brought so it is like your solution 2. Quite deterministic.
   is this a solution for you?

from data-models.

finally, what you could use is to point not to json schema (non-deterministic) but to the yaml version which is deterministic for every version.

from data-models.