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


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

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

Subject: LwDITA: Questions about DTDs, part II

I've been looking at map.dtd and topic.dtd. Some things are standard; others will be unfamiliar to folks used to working with DITA 1.3 DTDs.


  • What is happening with the following section? What is the intent for the filter-adds entity?

    <!-- ============================================================= -->
    <!--                    ADD FILTERING ATTRIBUTES                   -->
    <!-- ============================================================= -->

    <!-- none-->
    <!-- ENTITY % filter-adds
          "ADD-ATTRIBUTE-HERE      CDATA                        #IMPLIED"-->

  • It looks as if there is a simpler mechanism for configuration by uncommenting lines; see the code sample below:

    <!-- ============================================================= -->
    <!--                    REMOVE ATTRIBUTE/ELEMENT GROUPS                    -->
    <!-- ============================================================= -->

    <!-- Remove a group by uncommenting its redefinition below -->

    <!--ENTITY % filters " " -->
    <!--ENTITY % reuse " " -->
    <!--ENTITY % variable-content " " -->
    <!--ENTITY % variable-links " " -->
    <!--ENTITY % reference-content " " -->
    <!--ENTITY % control-variables " " -->
    <!--ENTITY % localization " " -->

    <!--For each group removed add a corresponding constraint value to
        the excluded-domains entity. The constraint name should be "no-"
        followed by the name of the entity removed/constrained.
        For example, if you removed reuse attributes, add the value
        "no-reuse-c" to the excluded-domains entity definition-->

    <!ENTITY excluded-domains                         " "                >

    This might need to be documented for practitioners using the "beta" drop of the DTDs that will accompany the committee note -- certainly for the spec.

  • For 1.3, we made a point of standardizing the headers in the DTDs, so that we could refer to them in the spec. See http://docs.oasis-open.org/dita/dita/v1.3/errata01/csprd01/complete/part1-base/archSpec/base/dtd-coding-doctype-shell.html . Of course, there is nothing normative about headers, but do we want to be consistent? Below is a comparison between DITA 1.3 and LwDITA:

    • Domain entity declarations: In DITA 1.3 map.dtd, the header is "DOMAIN ENTITY DECLARATIONS", in LwDITA, this is "INCLUDE PHRASE MODULES".
    • Map element integration: In DITA 1.3 map.dtd, the header is "MAP ELEMENT INTEGRATION"; in LwDITA, this is "INCLUDE MAP MODULE".
    • Etc.


Same points and questions as map.dtd.


Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
+1 919 682-2290; kriseberlein (skype)

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