[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Namespace handling in XML Processors
Hey Guys my mailbox is flooding with the namespace mails. So why not I ask all of you one question. Can the XML Document contain namespace?? Pleae know whether this is a valid XML Doc or not ====================== its in the attachment =========================== --- David Brownell <david-b@p...> wrote: > schen@f... wrote: > > > > Hi David, everyone, > > > > Thanks for clearing up all the different issues. > > > > So if I'm to understand this correctly, for > processing to occur in the > > right way involves the following steps: > > It'd normally happen in the other order ... > namespace processing after > XML processing, but I think the implied order wasn't > intentional! > > > > Namespace processor: > > apply scoping, defaulting, and URI comparison to > all elements so that each > > element and attribute has a namespace prefix, > normalizing all elements and > > attributes in the same URI namespace to have the > same prefix. > > That'd be one kind of namespace processor; there are > others. This > can all be done dynamically. And of course, > prefixes aren't supposed > to matter except to be mnemonic to folk writing XML > by hand -- many > "namespace processors" will ignore prefixes except > for output concerns. > Applications doing "semantic" processing should use > the namespace URI > and the local part of the name, ignoring everything > else. > > > > DTD: > > using external/internal subsets, define DTD using > normalized namespace > > prefixes. This would require somehow combining > the DTD's of each > > namespace being used. An example would be in > XSLT, validating stylesheets > > using the XSLT DTD fragment. > > > > XML Processor: > > process as usual, all element and attribute names > having been > > "fully-qualified", is treated just like any other > XML document. > > DTD processing is done by the XML processor, and > doesn't know > a thing about XML namespaces. They're orthogonal. > > > > Do I have this right? > > No, DTD processing is part of XML processing and > doesn't know > anything at all about namespaces. "Normalizing" > prefixes isn't > required (if it were done, a namespace processor > could do it), > and if you can use DTD mechanisms to combine your > vocabularies > you didn't really need to use namespaces. > > > > So currently the tricky part is merging the > DTDs, > > and without standardization on schemas and > namespace semantics mapping, > > many people feel that namespaces are confusing at > best and useless at > > worst as it is today. > > The most effective way to think about XML namespaces > is without > letting DTDs enter the discussion. There's a set of > documents > that can use them together, but the conflicts are > more evident. > > The XML Namespace spec was pretty much rushed to REC > status a bit > on the early side ... without a good general > understanding of its > place in the suite of XML standards. Hence that > confusion. > > > > But at least I can recognize the utility of > namespaces in XSLT, which > > would be more difficult to handle without this > facility. Less clear to me > > is the raging XHTML debate in the parallel > thread(s). > > > > Sorry for stirring up anything that was rehashed > before, I've only just > > subscribed to the list. Thanks again. > > There seem to be no flames on this thread! (Knock > on wood ... ;-) > > - Dave > > xml-dev: A list for W3C XML Developers. To post, > mailto:xml-dev@i... > Archived as: > http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on > CD-ROM/ISBN 981-02-3594-1 > To (un)subscribe, mailto:majordomo@i... the > following message; > (un)subscribe xml-dev > To subscribe to the digests, > mailto:majordomo@i... the following message; > subscribe xml-dev-digest > List coordinator, Henry Rzepa > (mailto:rzepa@i...) > > __________________________________________________ Do You Yahoo!? Bid and sell for free at http://auctions.yahoo.com <?xml version="1.0"?> <PKT N="WDogSystemInit"> <NSP N="SKUP"> <NSP N="DataPump"> <GRP> <HDR> <DSC T="LST" N="bla bla bla" R="t"> <DFM/> </DSC> </HDR> <BDY> <LST N="bla bla bla"> <L I="1">googoo</L> <L I="2">abracadabra</L> <L I="3">open sesame</L> <L I="4">baboom</L> <L I="5">break on through to the other side</L> </LST> </BDY> </GRP> </NSP> <!-- End of the data pump namespace --> <NSP N="WDog"> <GRP> <COMMENTS> <P><L>WDog is a COM component that will log the operation of another COM component running in a seperate process space.</L> <L>In the event of exceptional behavior -- i.e. error conditions etc. it will take actions according to the initialization instructions it has been insantiated with.</L> </P> </COMMENTS> <HDR><!-- contains descriptors --> <!-- descriptor for one pathname - path value record pair --> <DSC T="RCD" N="PathRecord" NSP="SKUP::WDog"> <DFM T="F" I="2"/> <F N="NameOfPath" R="t"><DFM T="str" MXL="63" MIN="32" MAX="120"/></F> <F N="Path" R="t"><DFM T="str" MXL="255" MIN="32" MAX="120"/></F> </DSC> <!-- descriptor for a table of PathRecord type records --> <DSC T="TBL" N="Paths" ID="0F46F8D3-5693-11d3-A67C-0050046C4B19" NSP="SKUP::WDog" R="t"> <DFM T="RCD" N="PathRecord" MIN="0" MAX="10"/> </DSC> <!-- descriptor for a SysMsg table & its' record type --> <DSC T="RCD" N="SysMsgRec" ID="040911A4-D2DB-4a84-BD58-0B1012FFDF19" NSP="SKUP::WDog"> <DFM T="F" I="4"/> <F N="MsgNumber" R="t"><DFM T="UINT" MIN="0" MAX="100" /></F> <F N="MsgDescriptor" R="t"><DFM T="str" MXL="255" MIN="32" MAX="120" /></F> <F N="MsgTypeCode" R="t"><DFM T="char" SET="(,){I,W,E,N}" /></F> <F N="OptionalMsg" R="f"><DFM T="str" MXL="1024" MIN="32" MAX="120" /></F> </DSC> <!-- descriptor for a System message table --> <DSC T="TBL" N="SysMsg" ID="1CA51EA1-5699-11d3-A67C-0050046C4B19" NSP="SKUP::WDog" R="t"> <DFM T="RCD" N="SysMsgRec" MIN="0" MAX="100"/> </DSC> </HDR> <BDY> <TBL N="Paths" ID="0F46F8D3-5693-11d3-A67C-0050046C4B19"> <R I="1"><F I="1">RootPath</F><F I="2">D:\~Dev\WatchDog</F></R> <R I="2"><F I="1">LogPath</F><F I="2">log</F></R> <R I="3"><F I="1">ExceptionPath</F><F I="2">Err</F></R> </TBL> <TBL N="SysMsg" ID="1CA51EA1-5699-11d3-A67C-0050046C4B19"> <R I="1"><F I="1">01</F><F I="2">Null Message</F><F I="3">N</F><F I="4"/></R> <R I="2"><F I="1">02</F><F I="2">okay</F><F I="3">I</F><F I="4">this is an optional message for this particular system message</F></R> <R I="3"><F I="1">03</F><F I="2">okay false</F><F I="3">I</F><F I="4"/></R> <R I="4"><F I="1">04</F><F I="2">Unknown Error</F><F I="3">W</F><F I="4">this is an unknown error optional message!!!!!</F></R> </TBL> </BDY> </GRP> </NSP> <!-- end of the WDog namespace --> </NSP> <!-- end of the skup namespace --> </PKT> <!-- end of the WDogSysInit packet -->
|
PURCHASE STYLUS STUDIO ONLINE TODAY!Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced! Download The World's Best XML IDE!Accelerate XML development with our award-winning XML IDE - Download a free trial today! Subscribe in XML format
|