In that case, could the @class attribute be removed from the XForms WD?
XHTML can add it when an XForms+XHTML profile comes about...
- Ryan
-----Original Message-----
From: Micah Dubinko [mailto:MDubinko@cardiff.com]
Sent: Tuesday, September 03, 2002 3:33 PM
To: 'Roman Huditsch'; AndrewWatt2001@aol.com; www-forms@w3.org
Subject: RE: XForms WD 20020821 - 3.2.1 Host Languages, Foreign Attributes
and XForms
It means that anyone designing an XForms+Something language can include
@style, @xlink:href, @xml:base, or whatever else makes sense for their
needs.
Thanks,
.micah
-----Original Message-----
From: Roman Huditsch [mailto:roman.huditsch@hico.com]
Sent: Thursday, August 29, 2002 7:38 AM
To: AndrewWatt2001@aol.com; www-forms@w3.org; www-forms-editor@w3.org;
xforms@yahoogroups.com
Subject: AW: XForms WD 20020821 - 3.2.1 Host Languages, Foreign Attributes
and XForms
Would that mean that I can specify a @style for each Xform control (which is
since 2 or 3 WD versions ago not part of the spec any more)?
wbr,
Roman
-----UrsprÃ¼ngliche Nachricht-----
Von: AndrewWatt2001@aol.com [mailto:AndrewWatt2001@aol.com]
Gesendet: Donnerstag, 29. August 2002 16:12
An: www-forms@w3.org; www-forms-editor@w3.org; xforms@yahoogroups.com
Betreff: XForms WD 20020821 - 3.2.1 Host Languages, Foreign Attributes and
XForms
What is the design rationale behind the statement that all XForms elements
must accept foreign attributes?
Does this mean that all XForms elements must accept XLink elements, for
example? Or is 3.2.2 intended implicitly to exclude XLink elements in the
context of 3.2.1?
If the only foreign attributes NOT allowed generally on XForms elements are
XLink attributes what is the cause for such anti-XLink prejudice in the
XForms WG?
Am I correct in assuming that "foreign attributes" means attributes from
namespaces other than the XForms namespace?
3.2.1 also states that a host language "must" include an attribute of type
xsd:ID on each XForms element. Why?
I suggest that either some explanation be provided in 3.2.1 or a forward
reference given to some discussion of the thinking behind these decisions.
Andrew Watt