Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Issues

Select view

Enter to search
Shift+Enter to add a new line
    Select search mode

     
    1 of 1

    AM 1.4 XML Schema: wrong minOccurs for C_PRIMITIVE_OBJECT.item

    Description

    C_PRIMITIVE_OBJECT.item has minOccurs=0 (see https://github.com/openEHR/specifications-ITS-XML/blob/master/components/AM/Release-1.4/Archetype.xsd#L119C7-L119C64) <xs:complexType name="C_PRIMITIVE_OBJECT"> <xs:complexContent> <xs:extension base="C_DEFINED_OBJECT"> <xs:sequence> <xs:element name="item" type="C_PRIMITIVE" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> C_PRIMITIVE_OBJECT.item in the AOM is 1..1 https://specifications.openehr.org/releases/AM/Release-2.2.0/AOM1.4.html#_c_primitive_object_class Solution: minOccurs should be 1 in the XML Schema for AM 1.4

    Details

    Reporter

    Components

    Affects versions

    Priority

    Created February 11, 2024 at 8:39 PM
    Updated April 8, 2024 at 12:27 PM
    Configure

    Activity

    Show:

    Ian McNicollApril 8, 2024 at 12:27 PM

    I don't think this has any connection with null_flavours on ELEMENT - this is just about constraints in the AOM itself.

    Suggest we apply this change, though AFAIK constraints on primitives e.g on a simple string are non-existent.

    Pablo PazosMarch 4, 2024 at 6:08 PM

    this is about the AOM C_PRIMITIVE_OBJECT and its schema, not sure about how this relates to null_flavour.

    C_PRIMITIVE_OBJECT has an item attribute which is 1..1 in AOM

    Severin KohlerMarch 4, 2024 at 3:56 PM
    Edited

    Isn’t the null flavour an item itself ?
    At least in compositions its contained in items.

    Diego BoscaFebruary 11, 2024 at 9:44 PM

    Isn’t this for allowing nulls and then provide null_flavour?

    Loading...