fix-orchestra-spec

fix-orchestra-spec copied to clipboard

Clarify implicit link between field and code set scenarios

2

Section 3.8.2 *Data domain of a field* defines the following: >Since `` is also qualified by scenario, a field will link to the code set of the same scenario. By...

kleihan

Orchestra v1.1 added scenarios as top level element and added a numerical identifier. References are now possible by name and/or identifier whereby both are optional but also have a default...

kleihan

Add verbiage for all attributes provided in the XSD file

1

The Orchestra spec does not include a description of all attributes. Some are only defined in the XSD file. The following attributes should be added to the spec together with...

kleihan

A subsection of Chapter 3.11 *Workflow* currently has the following text, defined as non-normative. >3.11.1.1 Mapping a message to a scenario > >*This section is non-normative.* > >The task of...

kleihan

Sharing of namespace for code sets and datatypes

1

Namespace for code sets and datatypes share a single namespace in Orchestra v1.0. With Orchestra v1.1 there are now separate attribute for a field having either a datatype or a...

kleihan

ISO 20022 datatype "identifer set" versus Orchestra discriminator fields

4

Section 3.8.5 *Discriminator fields* defines fields that link to another field to limit its range of values: >FIX contains fields for which its value domain is modified by another field....

kleihan

Section 3.7.1.4 *Union datatypes for code sets* does not explain the use case of this in the context of a standards organization using Orchestra. The current text is as follows....

kleihan

Section 3.6.3 *Datatype mappings* has the following text: >Rather than creating numerous one-off mappings to other type systems, is it likely more efficient to map each to ISO 11404 once,...

kleihan

Section 3.2.1 *Provenance* contains a subset of DC terms that are relevant in the context of electronic interfaces. The proposal is to update this section to make a clear recommendation...

kleihan

Section 2.1 *Message Structures* shows an outdated UML metamodel. Should this high-level version be part of the spec and updated for v1.1 or should a detailed version be a separate...

kleihan