[
Lists Home |
Date Index |
Thread Index
]
Thanks very much for your help!
This is all the information I need
best regards,
Evert
Alain Pannetier wrote:
> 1/ Which is best ?
> - "unqualified" is the default for attributes
> - for elements (elementFormDefault) as well actually and that has
> been quite controversial.
> - Attributes with no explicit namespace don't inherit the namespace
> of their parent element. They belong to the null namespace.
> - So that it all depends on how you intend to use them (e.g. if you
> also develop Xpath expressions).
> - If you have "unqualified", you can write your xpath
> "/a:element[@att1='hello']
> - if instead you have "qualified" you must use
> "/a:element[@a:att1='hello']
> I'd say that since the vast majority of users use "unqualified" you're
> less likely to uncover bugs in parsers if you stick to the default
> rather than the other way around.
>
> 2/ Most parsers are namespace aware now (for Xerces that's the default
> behaviour).
>
> On 7/1/06, Evert | Collab <evert@collab.nl> wrote:
>> Thank you very much for your answer.
>>
>> Two more question regarding this..
>>
>> Are there any drawbacks using either attributeFormDefault="unqualified"
>> or attributeFormDefault="qualified"...
>> My preference goes to unqualified, but thats just for 'beauty' reasons..
>>
>> Is there a chance if some (XSD enabled or not)parsers will run into
>> problems with the unqualified method? For example.. they could give the
>> attribute the wrong namespace?
>>
>> Thanks again,
>> Evert
>>
>> Alain Pannetier wrote:
>> > Hi Evert,
>> >
>> >> From what I understand :
>> > - If you are validating
>> > - against an XML Schema (XSD) and XSD declares
>> >
>> > <schema xmlns="http://www.w3.org/2001/XMLSchema";
>> > targetNamespace="urn:mynamespace"
>> > xmlns:a="urn:mynamespace"
>> > attributeFormDefault="unqualified" elementFormDefault="qualified">
>> >
>> > Then you can use
>> >
>> > <a:element att1="hello" />
>> >
>> > If instead you have
>> >
>> > attributeFormDefault="qualified"
>> >
>> > Then you should use
>> >
>> > <a:element a:att1="hello" />
>> >
>> > Regards,
>> >
>> > Alain Pannetier
>> >
>> >
>> > this On 7/1/06, Evert | Collab <evert@collab.nl> wrote:
>> >> A quick question.. I working on a modular xml parser for php.. not
>> too
>> >> complicated and mainly used in private projects.
>> >>
>> >> The 'modules' are loaded based on their xml namespace.. I simply pass
>> >> through what element should be parsed and its attributes..
>> >>
>> >> Here's my question, Say I use a namespace.. referred to as
>> >> "urn:mynamespace" and the prefix 'a'
>> >>
>> >> Considering this element. Should I always prefix the attributes
>> with the
>> >> same prefix, or can I just skip that:
>> >>
>> >> <a:element att1="hello" />
>> >>
>> >> or
>> >>
>> >> <a:element a:att1="hello" />
>> >>
>> >> Evert
>> >>
>> >> --
>> >> http://www.rooftopsolutions.nl/
>> >>
>> >>
>> >> -----------------------------------------------------------------
>> >> 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://www.oasis-open.org/mlmanage/index.php>
>> >>
>> >>
>> >
>>
>>
>> --
>> http://www.rooftopsolutions.nl/
>>
>>
>
--
http://www.rooftopsolutions.nl/
|
