Steven,
Keep in mind that such changes also need to be reflected in the schema files (XML Schema and Relax NG).
Kind regards,
Nick Van den Bleeken
Product Evangelist
Phone: +32 3 425 41 02
Office fax: +32 3 821 01 71
nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com>
www.inventivedesigners.com
[cid:image001.png@01CBF2F8.1DA19110][cid:image002.png@01CBF2F8.1DA19110][cid:image003.png@01CBF2F8.1DA19110]
On 16 Apr 2014, at 16:55, Steven Pemberton <steven.pemberton@cwi.nl<mailto:steven.pemberton@cwi.nl>> wrote:
The current situation is that we have a content set called UI Common, that contains help, hint, alert and action, and an attribute set called UI Common that contains @appearance.
Almost all elements that use the UI Common content also use the UI Common attributes.
My plan is to put @label, @help, @hint, and @alert in the UI Common attribute set, take @appearance out of it, and then adjust the elements that don't include both.
Here is a list of all elements that use one or both: (apologies for layout)
Element Uses @UI Common Has label Uses UI Common
common (except <output/>) Yes Yes Yes
output No! * Opt Yes
select/1 Yes Yes Yes (but special)
label/help/hint Yes No No
alert No (to be fixed) No No
Action No No No
item no Yes Yes
group Yes Opt Yes
switch Yes No No
dialog Yes Opt Yes
repeat Yes No No
itemset No Yes Yes
* output has @appearance, but doesn't use @UI Common; no idea why not, but it is explicitly mentioned...
https://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_output_Element
"This form control does not use the UI Common attribute group, but nevertheless still contains an author-optional appearance attribute, as defined above."
Steven
________________________________
Inventive Designers' Email Disclaimer:
http://www.inventivedesigners.com/email-disclaimer
