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] Does it make sense to have a default with a nillable element?

Think of it the other way around: if the value can't be nill then what point is there in having a default? If it is nill, then you're telling people what value is used instead...

On Wed, Jul 10, 2019 at 7:01 AM Costello, Roger L. <costello@mitre.org> wrote:
Hi Folks,

The following XML Schema declares an element to be nillable and the element has a default value:

<xs:element name="test" type="xs:string" nillable="true" default="Hello, world" />

That is legal but is it meaningful?

What does this (schema-valid) XML instance mean:

<test xsi:nil="true"></test>

xsi:nil="true" indicates that there is no information available for the <test> element. The default value indicates that there is information available for the <test> element and the information is "Hello, world".


Isn't that a contradiction?



XML-DEV is a publicly archived, unmoderated list hosted by OASIS
to support XML implementation and development. To minimize
spam in the archives, you must subscribe before posting.

[Un]Subscribe/change address: http://www.oasis-open.org/mlmanage/
Or unsubscribe: xml-dev-unsubscribe@lists.xml.org
subscribe: xml-dev-subscribe@lists.xml.org
List archive: http://lists.xml.org/archives/xml-dev/
List Guidelines: http://www.oasis-open.org/maillists/guidelines.php

Peter Hunsberger

[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