OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

dita-translation message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: FW: [dita] subelement instead of translatable label attribute of <data> element?

Please review Erik’s email before the meeting on Monday. I’ve asked Erik to attend the meeting to explain, if he is available.



JoAnn T. Hackos, PhD
Comtech Services, Inc.
710 Kipling Street, Suite 400
Denver, CO 80215
joannhackos Skype


From: Erik Hennum [mailto:ehennum@us.ibm.com]
Sent: Friday, July 07, 2006 9:04 AM
To: dita@lists.oasis-open.org
Subject: [dita] subelement instead of translatable label attribute of <data> element?


Hi, Translation-Aware TC:

My colleague, Mike Temple, alerted me to a potential translation issue with respect to the <data> element.

The current <data> element has a label attribute for providing a human-readable title for the property. That's convenient for processing because it can be defaulted but, of course, isn't optimal for translation.

I understand that we plan in DITA 1.2 to provide subelement equivalents for every translatable attribute. In conformance with that impending policy, I'd propose that, in DITA 1.1, the <data> element not have a label attribute but instead have a <title> subelement (with processing aggregating one <title> in output processing the same way as <section>).

In DTD syntax:

      <!ELEMENT data  (#PCDATA|%title;|%keyword;|%term;|%image;|%object;|%ph;|%data-about;|%data;)*>
      <!ATTLIST data    %univ-atts;
                        name        CDATA #IMPLIED
                        datatype    CDATA #IMPLIED
                        value       CDATA #IMPLIED
                        href        CDATA #IMPLIED
                        format      CDATA #IMPLIED
                        type        CDATA #IMPLIED
                        scope      (local | peer | external)        #IMPLIED
                        outputclass CDATA #IMPLIED

In Schema syntax:

      <xs:complexType name="data.class" mixed="true">
          <xs:choice minOccurs="0" maxOccurs="unbounded">
              <xs:group ref="title"/>
              <xs:group ref="keyword"/>
              <xs:group ref="term"/>
              <xs:group ref="image"/>
              <xs:group ref="object"/>
              <xs:group ref="ph"/>
              <xs:group ref="data-about"/>
              <xs:group ref="data"/>
          <xs:attributeGroup ref="univ-atts"/>
          <xs:attribute name="name"        type="xs:string"/>
          <xs:attribute name="datatype"    type="xs:string"/>
          <xs:attribute name="value"       type="xs:string"/>
          <xs:attribute name="href"        type="xs:string"/>
          <xs:attribute name="format"      type="xs:string"/>
          <xs:attribute name="type"        type="xs:string"/>
          <xs:attribute name="scope"       type="scope-att.class"/>
          <xs:attribute name="outputclass" type="xs:string"/>

Prior threads about the <data> element:



Erik Hennum

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]