This wiki has undergone a migration to Confluence found Here

Difference between revisions of "XML ITS R1 schema change management"

From HL7Wiki
Jump to navigation Jump to search
Line 22: Line 22:
 
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 [[User:Charliemccay|Charliemccay]] 06:04, 21 Jun 2006 (CDT)
 
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 [[User:Charliemccay|Charliemccay]] 06:04, 21 Jun 2006 (CDT)
 
=== xsi:nillable be added wherever needed ===
 
=== xsi:nillable be added wherever needed ===
Status: Notified
+
Status: Closed
  
 
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. [[User:Charliemccay|Charliemccay]] 05:24, 22 Jun 2006 (CDT)
 
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. [[User:Charliemccay|Charliemccay]] 05:24, 22 Jun 2006 (CDT)
 
This should also be considered for the datatypes where there are non-optional components
 
This should also be considered for the datatypes where there are non-optional components
 +
 +
--[[User:MatthewStephens|MatthewStephens]] 09:08, 26 Jun 2006 (CDT) Nillable is generated by the schema generator wherever it is needed
 +
 
=== xsd:any in ED ===
 
=== xsd:any in ED ===
 
Status: Draft -- awaiting a concrete proposal
 
Status: Draft -- awaiting a concrete proposal

Revision as of 14:08, 26 June 2006

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.

There is a separate document for maintaining XML ITS R1 schema tooling issues

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.

The status of each issue should be includeed as the first line of the issue. If there is a planned next step that shoudl also be included. Possible states are: "Draft", "Notified", "WGM approved", "Done, WGM approved", "Done, WGM review needed". Once there is a concrete proposal the XML SIG list should be notified, and the status changed to "Notified". At that point a toolsmith can make the change and the change proposal will be reviewed at the next WGM (these can happen in either order - with the change being rolled back if there are WGM objections to it).

Issues / Change Proposals

Null flavor disallowed on mandatory classes and attributes

status: Notified

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

Status: Closed

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. Charliemccay 05:24, 22 Jun 2006 (CDT) This should also be considered for the datatypes where there are non-optional components

--MatthewStephens 09:08, 26 Jun 2006 (CDT) Nillable is generated by the schema generator wherever it is needed

xsd:any in ED

Status: Draft -- awaiting a concrete proposal

The schema currently allows no markup in an ED -- which is wrong - but we assumed that in practice someone using markup in ED would want to tweek the schema to allow the appropriate content. (There is no comment to this effect in the distributed schema however. Charliemccay 05:24, 22 Jun 2006 (CDT)

The options that we considered included just allowing other namespaces, or putting the thumbnail and reference elements as globally declared elements in the HL7v3 namespace, with a stated rule that they can only be used in ED. This would then let us have xsd:any namespace="##any" in the ED datatype.