Hi Paul,
It has been that way since DITA 1.0. It looks like it was correct back in
the pre-OASIS version, which means it may have been a casualty of the DTD
spacing/comment cleanup at the time the standard was approved.
Because it was in DITA 1.0, this gets into the realm of the backwards
compatibility vs bug area. It is clearly a bug. But, it's just as clearly
backwards incompatible to change the name of an attribute. Changing it will
break existing 1.0 documents, if by any chance somebody is using the
attribute today.
Robert D Anderson
IBM Authoring Tools Development
Chief Architect, DITA Open Toolkit
(507) 253-8787, T/L 553-8787
"Grosso, Paul" <> wrote on 01/06/2007 11:32:10 AM:
> We just noticed that the longdescref attribute on the
> object element in commonElements.mod is missing the
> trailing "f" in the version 1.1 dated 30 Nov 2006 available at
> http://www.oasis-open.org/apps/org/workgroup/dita/download.php/21381/dit
> a1.1.zip
>
> <!-- LONG NAME: Object (Streaming/Executable
> Data) -->
> <!ELEMENT object ((%desc;)?, (%param;)*,
> (%foreign.unknown.incl;)*) >
> <!ATTLIST object
> declare (declare) #IMPLIED
> classid CDATA #IMPLIED
> codebase CDATA #IMPLIED
> data CDATA #IMPLIED
> type CDATA #IMPLIED
> codetype CDATA #IMPLIED
> archive CDATA #IMPLIED
> standby CDATA #IMPLIED
> height NMTOKEN #IMPLIED
> width NMTOKEN #IMPLIED
> usemap CDATA #IMPLIED
> name CDATA #IMPLIED
> tabindex NMTOKEN #IMPLIED
> longdescre CDATA #IMPLIED
> %univ-atts;
> outputclass
> CDATA #IMPLIED >
>
> Is there a later version that I missed?
>
> If not, then this looks like a bug in the DTDs.
>
> paul
