[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: RE: [regrep] V3 Proposal: Namespace Manager Function
Message text written by "CHIUSANO, Joseph" > I don't believe that having a namespace association at such a high level will cover the cases in which more than one namespace is referenced in a schema or XML document (I say documents because it is possible that someone can specify a local namespace in an XML document, thus overriding the target namespace). Rather, it would cause a single namespace to be associated with all constructs in a schema or XML document, which many times will not be the case as multiple namespaces may be used. Joe< >>>>>>>>>> Joe, That is why you can associate more than one classification to a schema. This is exactly how namespaces work - there's the parent one - and then optionally one or more supplemental ones. And even better - because the classification is a tree structure - you can know that if a schema is at this node - then potentially these other namespaces may be related by examining the tree. This you cannot do in Schema. DW.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC