[OASIS Issue Tracker] Commented: (SAF-11) Symptom Grouping/Linking

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/SAF-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24845#action_24845 ] 

Stavros Isaiadis  commented on SAF-11:
--------------------------------------

A proposed schema for RelatedSymptoms:


<xsd:complexType name="Symptom_Type">
        <xsd:sequence>
            <xsd:element name="SymptomId" type="xsd:anyURI"/>
            <xsd:element name="SymptomType" type="xsd:anyURI"/>
            <xsd:element name="CreationDate" type="xsd:dateTime"/>
            <xsd:element name="Confidence" type="sym:ConfidenceType"/>
            <xsd:element name="Reporter" type="xsd:anyURI"/>
            <xsd:element name="Subject" type="xsd:anyURI"/>
            <xsd:element name="ExpirationDate" type="xsd:dateTime" minOccurs="0" maxOccurs="1"/>
            <xsd:element name="IssuedPrescription" type="xsd:anyURI" minOccurs="0" maxOccurs="unbounded"/>
            <!-- removed: <xsd:element name="ProbableCause" type="xsd:anyURI" minOccurs="0" maxOccurs="unbounded"/> -->
            <xsd:element name="RelatedSymptoms" type="sym:RelatedSymptomsType" minOccurs="0" maxOccurs="1" />
            <xsd:element name="Content" type="sym:ContentType" minOccurs="0" maxOccurs="1"/>
        </xsd:sequence>
    </xsd:complexType>

    <xsd:simpleType name="RelationshipType">
        <xsd:restriction base="xsd:string">
            <xsd:enumeration value="Causal"/>
            <xsd:enumeration value="Supersedes"/>
            <xsd:enumeration value="Repetition"/>
            <xsd:enumeration value="Other"/>
        </xsd:restriction>
    </xsd:simpleType>
    
    <xsd:complexType name="RelatedSymptomsType">
        <xsd:sequence>
            <xsd:element ref="sym:RelatedSymptomType" minOccurs="0" maxOccurs="unbounded"/>
        </xsd:sequence>
    </xsd:complexType>

    <xsd:complexType name="RelatedSymptomType">
      <xsd:attribute name="Relationship" type="sym:RelationshipType" />
      <xsd:sequence>
      <xsd:element name="RelatedSymptomId" type="xsd:anyURI"/>
</xsd:sequence>
    </xsd:complexType>

Questions:
- Consider SymptomID as a separate element/type?
- Relatedsymptoms and IssuedPrescription should be made consistent in their schema. In the above, RelatedSymptoms is a collection of children elements, while Issued Prescription is not. I lean towards collections in order to have a cleaner, more hierarchical XML...
- How do we provide extensibility for the RelationshipType? I like enumerations, but "Other" is not enough for future or application specific customization and extensibility. Ideas?

> Symptom Grouping/Linking
> ------------------------
>
>                 Key: SAF-11
>                 URL: http://tools.oasis-open.org/issues/browse/SAF-11
>             Project: OASIS Symptoms Automation Framework (SAF) TC
>          Issue Type: Task
>            Reporter: Jeffrey Vaught
>            Assignee: Alvin Black
>            Priority: Critical
>
> In the pre standards phase of this work, it was suggested that some form of "Group Id" or "Linking Tag" be included at the top level of the Symptom to indicate that this Symptom was in someway related to other Symptoms and that this relationship was identifiable by the creator of the Symptom.
> Notes
> •	Jeff: Could capture in the signature, but emitter is uniquely positioned to provide.
> •	Alvin: On/Off (state).  Alarmid.
> •	Vivian: Prototypes show this is important for performance.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira