This wiki has undergone a migration to Confluence found Here
R2 XML ITS structures
Revision as of 16:38, 5 April 2006 by MatthewStephens (talk | contribs)
Contents
- 1 R2 XML ITS Structures Issues
- 2 A sentence needs to be added describing the root element of a batch transmission. (STR-001)
- 3 XML Representation of collection type and nullFlavor (STR-002)
- 4 Language - review vocab binding in XML (STR-003)
- 5 Review way that xml spec handles removed properties (STR-004)
- 6 What to do about xsi:type on RTO implementations (and why isn’t RTO in the generics) (STR-006)
- 7 which XML attributes can be used (xml:base) (STR-008)
- 8 Associations originating from a choice rather than from a specialized class in the choice are pushed into the element model of each of the specialized classes. Need to show an example of this (including RMIM/HMD) (STR-009)
- 9 XML representation of RIM-level associations - i.e. how can a generic RIM processor distinguish source->target vs. target->source relationships or player vs. scoper associations (STR-010)
- 10 ITS needs to indicate how cardinality is determined (based on a combination of 'optionality' as well as base cardinality) (STR-011)
- 11 Need guidance on when xsi:type should be populated where it's known from the message schema, but not necessarily known when parsing from a RIM perspective (STR-012)
- 12 How is the root element name determined for structured documents? (They don't have an interaction id.) (STR-013)
- 13 Move away from talking about rows and columns in the HMD and use HL7 static model instead (STR-014)
