FW: [saf] RelatedSymptoms proposed schema

[Vivian Lee <Vivian.Lee@uk.fujitsu.com>]

Title: FW: [saf] RelatedSymptoms proposed schema

Hi Stavros,

Glad you had some technical discussion today...

Anyway my two cents after reading the modified schema:

1. not sure what is the criteria for defining RelationshipType, I only had “primary”, and “secondary”... to make up the grouping concept, so it will be great if you can explain what means Causal, Supersedes...
2. a minor suggestion – it will be more structured if we can make the SymptomId a standalone simple type, and refer to it in the <xsd:complexType name="RelatedSymptomType">
   

Thoughts?

Vivian

On 14/02/2011 16:09, "Stavros.Isaiadis@uk.fujitsu.com" <Stavros.Isaiadis@uk.fujitsu.com> wrote:

Hi all,
 
Since we seem to have reached consensus for adding a "RelatedSymptoms" field to Symptom, here is a portion of the proposed schema for the relevant type and the updated Symptom schema:
 
   <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>

 
What do you think? Also, can someone verify that this is valid (Vivian?). I think we can build along these lines the specification.
 
One last thing: we will have to rethink the whole "IssuedPrescriptions" concept cause some aspects are a bit fuzzy right now...
 
Cheers,
 
Stavros
 
______________________________________________________________________
                                        
 Fujitsu Laboratories of Europe Limited
 Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE
 Registered No. 4153469
 
 This e-mail and any attachments are for the sole use of addressee(s) and
 may contain information which is privileged and confidential. Unauthorised
 use or copying for disclosure is strictly prohibited. The fact that this
 e-mail has been scanned by Trendmicro Interscan does not guarantee that
 it has not been intercepted or amended nor that it is virus-free.

------ End of Forwarded Message

______________________________________________________________________
                                        
 Fujitsu Laboratories of Europe Limited
 Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE
 Registered No. 4153469
 
 This e-mail and any attachments are for the sole use of addressee(s) and
 may contain information which is privileged and confidential. Unauthorised
 use or copying for disclosure is strictly prohibited. The fact that this
 e-mail has been scanned by Trendmicro Interscan does not guarantee that 
 it has not been intercepted or amended nor that it is virus-free.