Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


HL7-v3-XML namespaces

From: "XML4Pharma" <info@----------.--->
To: <xmlschema-dev@--.--->
Date: 1/13/2009 7:55:00 PM
Dear all,

I am currently studying the set of HL7-v3-XML messages.

What surprised me is that different of these messages (each of them =
defined by its own standard) all have the same namespace associated =
("urn:hl7-org:v3").
So we find the same default namespace for the CCD/CDA, aECG and for the =
SPL standard - this though the root elements are really different:
- "ClinicalDocument" for CDA/CCD
- "Document" for SPL
- "AnnotatedECG" for aECG

So we find in the instance documents .e.g.:

CDA: <ClinicalDocument xmlns="urn:hl7-org:v3" ...
SPL: <Document xmlns="urn:hl7-org:v3" ...
aECG: <AnnotatedECG xmlns="urn:hl7-org:v3" 

I realize each of these three "standards" use a set of common elements =
and attributes, which are defined in schemas that are shared, but the =
main schema is different, and the composition (child elements) of the =
root elements is different each time.

Is this "good practice" or should have each of these "standards" =
essentially have their own namespace, and then have the common/shared =
elements in another, shared namespace ?

Your comments are appreciated.

Jozef

Jozef Aerts





transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent