ACTION-1936: Have a look at how other specifications style deprecated elements/attributes and come with a proposal for styling in the XForms Sepc

All,

after looking at several specs I conclude that there is no common way
of marking up deprecated features.

Currently, we have prose like "... XXX element (deprecated in favor of
using an AVT in the XXX attribute) ...". I propose to make deprecation
more apparent to the reader by removing the parenthesized deprecation
hint and inserting a leading paragraph like:

Note: The XXX element is deprecated in favor of using an AVT in the
XXX attribute. The XXX element may be dropped from future versions of
the XForms specification.

The change would apply to the following places:

- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_resource_Element
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_method_Element
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_mediatype_Element_.28for_output.29
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_mediatype_Element_.28for_upload.29
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_case_Element_Child_of_the_toggle_Element
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_control_Element_Child_of_the_setfocus_Element
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_name_Child_Element
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_targetid_Child_Element
- http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_delay_Child_Element

The leading paragraph of
http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_resource_Element_child_of_load
would have to be changed accordingly.

Ok?

Regards,
Uli.
--
Ulrich Nicolas Lissé

Received on Wednesday, 10 April 2013 13:46:54 UTC