search

GfSE / SpecIF

Specification Integration Facility - schema, constraint checker and examples
Apache License 2.0
15 stars 6 forks source link

Introduce 'extends' also on project level #25

Closed odungern closed 4 years ago

odungern commented 4 years ago

@oalt , you have provided a whole bunch of standard types to be used in different domains or for different purposes. Except for the basic ones, the files do not comply with the schema. When using 'extends' at the project level, we can indicate that together with another more basic file, there is complete and schema-compliant content.

odungern commented 4 years ago

In Telco on 2020-01-29 approved. @oalt points out, that it should be a list, as a schema-compliant file can be composed of multiple fragments. So another idea is to add a boolean property 'isFragment'. In this case it is expected that the content is schema-compliant not on its own, but in combination with any content loaded before. This does not allow to automatically collect all necessary fragments, but it is not the role of a fragment to organize the configuration.

odungern commented 4 years ago

A boolean 'isExtension' is added to schema v1.0.0. The idea is that an extension does not necessarily comply with the schema on its own, but together with another project which is loaded, before.