From iwxxm-sx created by ilkkarinne: blchoy/iwxxm-sx#3
The current TSML XML schemas import the O&M 2.0 XML Implementation Schema. It does not seem feasible to add the O&M 2.0 XML schema into the IWXXM aerodrome forecast XML Schema, especially since the O&M XML implementation is based on the now deprecated O&M 2.0 abstract specification (ISO 19156:2011), and there is currently no clear timeline for revising the OGC O&M XML Implementation Specification to conform to the current OMS abstract specification (ISO 19156:2023, OGC abstract specification topic 20, OGC 20-082r4).
Perhaps we could suggest a small change to a future TSML specification to break the tight coupling between the TSML and O&M XML Schemas and replace them with non-schema-specific references? Or to split the TSML XML schema in more than one namespace, and only import the O&M XML Schemas into the those namespaces where it clearly is useful.
I concur with your views. But I think we should proceed with the discussion under #16 first and if there is still a need we can coming back for further discussion.
From iwxxm-sx created by ilkkarinne: blchoy/iwxxm-sx#3
The current TSML XML schemas import the O&M 2.0 XML Implementation Schema. It does not seem feasible to add the O&M 2.0 XML schema into the IWXXM aerodrome forecast XML Schema, especially since the O&M XML implementation is based on the now deprecated O&M 2.0 abstract specification (ISO 19156:2011), and there is currently no clear timeline for revising the OGC O&M XML Implementation Specification to conform to the current OMS abstract specification (ISO 19156:2023, OGC abstract specification topic 20, OGC 20-082r4).
Perhaps we could suggest a small change to a future TSML specification to break the tight coupling between the TSML and O&M XML Schemas and replace them with non-schema-specific references? Or to split the TSML XML schema in more than one namespace, and only import the O&M XML Schemas into the those namespaces where it clearly is useful.