ISSUE-195: qualified vs unqualified attributes

qualified vs unqualified attributes

State:

CLOSED

Product:

MMIArchLLC

Raised by:

James Barnett

Opened on:

2011-07-05

Description:

From: Jakob Sachse <jakobsa@gmail.com>
Date: Tue, 3 May 2011 17:48:05 +0200
Message-ID: <BANLkTinWBuXUkECHJRqeOrBaY05n67fP-Q@mail.gmail.com>
To: www-multimodal@w3.org

Hi,

I have been rechecking my findings and found another point that i would
like to comment on.

In contrast to what i wrote in my prior mail, not all .xsd files in Appendix
C
have attributeFormDefault and elementFormDefault set.

- mmi.xsd (Appendix C.1)

Neither has elementFormDefault = "qualified" on the schema element
nor form="qualified" on the mmi-element definition set. Since
"unqualified" is the default value all mmi elements are to be used
unqualified only.
This, as far as I know, makes most of the examples invalid as they
use the mmi element in a qualified way.

- mmi-datatypes.xsd (Appendix C.2)

Does not have attributeFormDefault nor elementFormDefault set. Which makes
it being set to the default value "unqualified". Types and Attributes
defined in this
xsd will have to be used without namespace prefix. But other .xsd documents
(e.g.
mmi-attribs.xsd (Appendix C.3)) reference them with prefix.


I am not a great expert on the XML Schema spec but I think someone should
look into
this. One thing I had to find out (while investigating my findings) was that
elementFormDefault and attributeFormDefault won't get inherited by child
documents
included in the parent documents.

Any comments are welcome!

Thanks & Regards,
Jakob.

2011/3/27 Jakob Sachse <jakobsa@gmail.com>

Subsequent email:

From: Jakob Sachse <jakobsa@gmail.com>
Date: Mon, 16 May 2011 16:16:33 +0200
Message-ID: <BANLkTimos=YTHD99xZycxN23U_DwMw2mig@mail.gmail.com>
To: www-multimodal@w3.org
Cc: Jim Barnett <Jim.Barnett@alcatel-lucent.com>, Ingmar Kliche <Ingmar.Kliche@telekom.de>

I have an update on my comment on the mmi element which is used qualified.
It was *my mistake* not to consider the difference between global and local
elements.
Global elements as mmi always have to be used qualified, regardless of the
value of
elementFormDefault. Thats why the examples given are valid regarding this
point.

I am sorry for the confusion.

Regards,
Jakob.

STATUS=CLARIFICATION
ACCEPTANCE=EXPLICIT

Related Actions Items:

No related actions

Related emails:

1. ISSUE-195: qualified vs unqualified attributes [MMIArchLLC] (from sysbot+tracker@w3.org on 2011-07-05)

Related notes:

Display change log