[
Lists Home |
Date Index |
Thread Index
]
- To: "Friedland, Zachary (TLP 2001)" <ZFriedland@exchange.ml.com>
- Subject: RE: [xml-dev] Namespaces best practices
- From: "Manos Batsis" <m.batsis@bsnet.gr>
- Date: Wed, 27 Feb 2002 11:06:09 +0200
- Cc: "XML DEV" <xml-dev@lists.xml.org>
- Thread-index: AcG/Dy4cD//mj+o0Q4WvhA7TSbKx5AAXqlBQ
- Thread-topic: [xml-dev] Namespaces best practices
Don't forget that the subject is political as well as technical ;-)
Cheers,
Manos
> -----Original Message-----
> From: Friedland, Zachary (TLP 2001)
> [mailto:ZFriedland@exchange.ml.com]
> Sent: Tuesday, February 26, 2002 11:41 PM
> To: 'xml-dev@lists.xml.org'
> Subject: [xml-dev] Namespaces best practices
>
>
> I'd like to get some feedback on a past topic that never
> seems to get resolved: Namespaces best practices. The 3
> options out there seem to be:
>
> (1) Homogeneous Namespaces across applications.
> - All XML schemas use the same namespaces, and the
> developers make sure to avoid collisions
>
> (2) Heterogeneous Namespaces across applications.
> - All XML schemas use different namespaces, and the
> developers have to do manage reading / writing / XSLT to
> different systems
>
> (3) Chameleon / Proxy namespaces.
> - All applications maintain one external namespace, and use
> proxies or chameleon methods to have many internal XML namespaces.
>
> I would love to hear developers / architect's feedback on how
> scaleable these different methods are, how easy it is to
> reuse XML Schema assets, and how manageable the namespaces are.
>
> Thanks
> Zach Friedland
>
>
> -----------------------------------------------------------------
> The xml-dev list is sponsored by XML.org <http://www.xml.org>, an
> initiative of OASIS <http://www.oasis-open.org>
>
> The list archives are at http://lists.xml.org/archives/xml-dev/
>
> To subscribe or unsubscribe from this list use the subscription
> manager: <http://lists.xml.org/ob/adm.pl>
>
>
|
