SAX, Java, and Namespaces (was Re: Restricted Namespaces forXML)

Borden, Jonathan jborden at
Fri Feb 5 15:57:51 GMT 1999

Healthcare applications have the same issues as other applictions, with the
added 'benefit' of multiple standards issuers and third party 'interested'

For example elements from the

hl7: namespace
dicom: namespace
hicfa: namespace

might be combined in a single document.

Namespaces aren't that difficult to deal with for the developer, but need to
be dealt with by organizations with are developing DTD's,Schemas etc which
span standards.

Now, getting the U.S. and U.K. to agree on a set of standards (and
namespaces) is its own issue :-) This is where XML and XTL has potential,

e.g. U.S. HL7 2.3 <->  HL7/XML transport <-  XTL -> U.K. EDIFACT XML
transport <-> EDIFACT

Transformations expressed in XSL/XTL can assist with interface of different
messaging systems and integration of different 'flavors' of HL7.

> Paul Prescod wrote,
> > I don't think that "average developers" need to worry about namespaces.
> ...
> > If you are building a
> > typical one-organization application then what are you doing with "other
> > people's tags" in your documents?
> Maybe my perspective is a little warped.  I'm working on healthcare
> applications in the UK - interoperability will (sometime) become a big
> deal. :-)

Jonathan Borden

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at
Archived as: and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at

More information about the Xml-dev mailing list