RE: [saf] Some cleaning up

See inline.

 

From: Isaiadis, Stavros
[mailto:] 

Sent: Monday, June 13, 2011 5:15 AM

To: 

Subject: [saf] Some cleaning up

 

Hi
all,

 

Following
Jeff’s addition to the spec of the ProtocolGroup as a first class entity
(which I think I liked) I think we should become a bit more consistent with the
way we handle groups of things in XML, e.g. in the case of potential syndromes
we currently have a flat collection of syndrome uris as opposed to a more
structured collection like we have for associated protocols. So I will make the
following changes and please let me know if you have any objections.

 

Potential
Syndromes:

From:

<PotentialSyndromes>xsd:anyURI</PotentialSyndromes>*

 

To:

<PotentialSyndromes>

<Syndrome
uri=”xsd:anyURI”/>+

</PotentialSyndromes>*

Jeff – No need for grouping here as in
AssociatedProtocols, but I like your proposed change.  No point in
allowing just anyURI when we are expecting Syndromes.

What about Symptom.RelatedSymptoms.RelatedSymptom?  Instead
of xsd:anyURI, maybe better to have <Symptom uri=”xsd:anyURI”/>

 

Also
removed <IssuedPrescription>xsd:anyURI<\IssuedPrescription>* from
the pseudoschema to reflect our decision to remove it from the spec.

Jeff – Oops.  Thought I had removed that last go ‘round.

 

Finally,
a question about incidents: did we decide that a symptom can indeed participate
in more than one incidents??If so then maybe this should also be changed
according to the “rules” above.

Jeff –Multiple Symptoms can be associated with a single
Incident, but the inverse of one Symptom involved in multiple Incidents would
be unusual.

 

Finally
(again), currently content is specified as anyType[0..n] but as 

<Content>xsd:any</Content>* 

in
the pseudoschema. Shouldn’t that be 

<
Content >

   
<xsd:any/>+

</
Content >?

Jeff – I think xsd:any (without the brackets) is correct. 

 

Any
advice from someone more in touch with XML? (Vivian?)

 

Thanks
and speak soon,

 

Stavros

 

This message w/attachments (message) is intended solely for
the use of the intended recipient(s) and may contain information that is
privileged, confidential or proprietary. If you are not an intended recipient,
please notify the sender, and then please delete and destroy all copies and
attachments, and be advised that any review or dissemination of, or the taking
of any action in reliance on, the information contained in or attached to this
message is prohibited. 

Unless specifically indicated, this message is not an offer to sell or a
solicitation of any investment products or other financial product or service,
an official confirmation of any transaction, or an official statement of
Sender. Subject to applicable law, Sender may intercept, monitor, review and
retain e-communications (EC) traveling through its networks/systems and may
produce any such EC to regulators, law enforcement, in litigation and as
required by law. 

The laws of the country of each sender/recipient may impact the handling of EC,
and EC may be archived, supervised and produced in countries other than the
country in which you are located. This message cannot be guaranteed to be
secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of
America Corporation. Securities and Insurance Products: * Are Not FDIC Insured
* Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal
Government Agency. Attachments that are part of this EC may have additional
important disclosures and disclaimers, which you should read. This message is
subject to terms available at the following link: 

http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you
consent to the foregoing.