XML ITS R1 schema change management

Introduction

This is a document that is maintained by the XML SIG. Change requests to the XML schema are managed in this document. Please add any issues that you have with the design of the schemas to it.

Tooling errors

Bugs in the schema generator should be reported directly to the tooling committee that is responsible for maintaining the schema generator.

The following issue has been repeatedly send to the list without any response: The schema as present in the May2006 edition for the MFMI_MT700701UV01 message type misses some classes. See schema. See the R-MIM, top-right hand corner, subject1 and priorRegisteredRole. Note that priorRegisteredRoles is NOT a stub. Either the serialization or the schema generator contains a bug. I know this is a tricky model because it has multiple stubs, but these classes are in an area of the model unrelated to stubs. Rene spronk 09:20, 21 Jun 2006 (CDT)

Process

All changes to the XML schema since the production of the 2006 normative edition should be documented on this page. Anyone may add an issue to this page, and provide a suggested solution. The change must then be notified to the XML list, and if there is any sustained objection on the list to the change, then the proposal must be discussed on an INM or XML SIG conference call to obtain a resolution. This document will be reviewed at each WGM by INM. This is the final step in the approval of a change, though when there is an urgent requirement changes can be made and published before this has been done (though they MUST be notified to the XML SIG list.

Change Proposals

Null flavor disallowed on mandatory classes and attributes

The nullFlavor attribute should be excluded from the attributeGroup that is referenced for mandatory classes and attributes. This proposal has been notified to the XML SIG list Charliemccay 06:04, 21 Jun 2006 (CDT)

xsi:nillable be added wherever needed

This will allow the use of xsi:nil in the instance, which in turn will allow the mandatory contents of null classes to be left out. This should also be considered for the datatypes where there are non-optional components