[cssm] SACP Schema Development - yet another Update
Marcin.Gnat at dlr.de
Marcin.Gnat at dlr.de
Fri Mar 27 12:25:28 UTC 2020
I just uploaded the yet updated schema-drafts and examples. This time the cookie-cutter example is filled with same information as the generic one, for beter comparison. Also I've split the main schema to 902x05w0_01-ConfPrfl.xsd and 902x05w0_01-ccConfPrfl.xsd, to allow smoothly to validate respective examples, without any need for changes as proposed below.
As next, I will try to work on "full-blown-example" of Schema and Example-Profile including also parameter validation.
Here I need to think if we stay with our SM-AbstractParameter as a base class, or I go for the FRM classes (is there any reference I can use for that? Any XSD with base classes I could use?).. What do you think?
Cheers and stay healthy
From: SMWG [mailto:smwg-bounces at mailman.ccsds.org] On Behalf Of Marcin.Gnat at dlr.de
Sent: Dienstag, 17. März 2020 17:58
To: smwg at mailman.ccsds.org
Subject: [cssm] SACP Schema Development - Update
I just uploaded the presentation and updated Schemas to the CWE:
The example XML is autogenerated out of XSD and does not yet include some real parameters (I did that for the generic example already). I will fill it up next days, and upload, so that you can better compare the differences.
The section in the beginning of the main schema (902x05w0_01-ConfPrfl.xsd) needs to be changed, depending what content one needs (the cookie-cuter or generic one). So when you take examples (both point to the same main schema!) think about changing the schema as well (otherwise you won't get validated).
<xsd:element ref="configurationProfileHeader" minOccurs="1" maxOccurs="1"/>
Here, use this --> <xsd:element ref="configurationProfileFwdRtnSlsTrnsServData" minOccurs="1" maxOccurs="1"/>
Or this --> <!-- <xsd:element ref="configurationProfileData" minOccurs="1" maxOccurs="1"/> -->
<!-- we have a problem here!!! we can't restrict SrvMgtInfoEntityType with "choice", if we extend it, we have wrong schema (includes some other things then) -->
I tried to overcome that, but didn't manage. Whatever I did, sooner or later I hit some issue...
This is one of the things we have, which I mentioned, when I said the cookie-cutters does not fit perfectly into current schema landscape (maybe its not immediately obvious, but when you look at my first diagram from the presentation, and than come back to schema, you should see that).
I'd be glad if we can talk next time more about it.
Hear you soon
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the SMWG