Hi Dana - if you remember any in particular, please let me (or the list)
know about them. A significant number of these were corrected for 1.1,
starting with the drafts from early January, but obviously some of them are
still present. Any that we catch should probably be corrected for the final
version of the spec.
Thanks-
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit
(507) 253-8787, T/L 553-8787
Dana Spradley <dana.spradley@oracle.com> wrote on 02/28/2007 02:50:49 PM:
I also have noticed that this is a common problem for many reused
attributes.
Those with element-specific meanings should be reviewed.
--Dana
Robert D Anderson wrote:
Hi Eliot - I can't speak to the value/content conflict, but I can speak a
little to the value attribute description. As many of you know, the
language reference was originally designed to reuse attribute
descriptions.
The value attribute was documented in DITA 1.0 for the <param> element,
where that description makes sense. The value attribute for the data
element and all of its specializations should have a new definition.
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit
(507) 253-8787, T/L 553-8787
"W. Eliot Kimber"
<ekimber@innodata
-isogen.com>
To
<dita@lists.oasis-open.org>
02/28/2007 09:57
cc
AM
Subject
[dita] Clarification on data
Element
The <data> element can have either a value= attribute or
directly-contained data. The description of data in the 2/13 spec
doesn't say what it means to have both a value= attribute and
content--should this case be disallowed?
Also, the description of value= is:
"Specifies the value of a run-time parameter specified by the name
attribute."
I think this must be a typo because it doesn't make any sense.
Cheers,
E.
--
W. Eliot Kimber
Professional Services
Innodata Isogen
8500 N. Mopac, Suite 402
Austin, TX 78759
(214) 954-5198
ekimber@innodata-isogen.com
www.innodata-isogen.com