XTCE11 — ESA-078

DESCRIPTION OF REQUESTED CHANGE
To be used within ESA projects, any data exchange mechanism shall ensure the integrity of the data that is exchanged. The proposed XTCE standard does not comply with this basic requirement and as
such cannot be used to safely transfer data.
RID RESPONSE:
· XML schema provides type checking thru schema validation, may be somewhat helpful here
· any translation should document what "falls out" if anything to another user, that seems unavoidable

With appropriate guidelines, magenta book, and maybe one for PUS or E70-31, XTCE can be used
without any ambiguity in the data contained.
We don't agree with the basic assertion : "The proposed XTCE standard does not comply with this
basic requirement (ensure the integrity of the data that is exchanged) and as such cannot be used to
safely transfer data". We don't understand the supporting analysis "does not guarantee unicity of their
content interpretation". If all the world used SCOS, then XTCE does not have value - all the world
does not use SCOS. If a new schema is created for every supplier/customer contract, then we don't
have a standard exchange format.
RID STATE: CLOSE

No Data Available