XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] a namespace definitions related question(s)

On 2/19/07, Shlomo Yona <S.Yona@f5.com> wrote:
>
> Hello,
>
> Please consider the following XML instance:
>
> <a:foo xmlns:a="foobar">
>             <a:bar xmlns:b="foobar">
> </b:bar>
> </a:foo>
>
> A few cases should be considered:
>
> XML Schema is/isn't available (should this matter?!) – i.e., should
> namespaces be considered only with the presence of a schema?! Is so, how?
> Value of elementFormDefault (should this matter?!)
>

Having accessibility to the XML Schema only matters if you plan to use
the schema for processing, e.g., validation. Compliance with the
schema, whether or not it is present, matters if the application
processing the XML expects the element to conform to the schema. And
if the application expects conformance to the schema, then namespaces
must be considered, including the value of elementFormDefault.

Anne

>
> Questions:
>
> is the above well formed?
> If this is not well formed, then why?
>
>
>
>
>
>
>
> Thanks.
>
>
>
> Shlomo


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS