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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-comment message

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


Subject: Re: [dita-comment] DITA 1.3 Draft 01: Nested key scopes example


Hi, Jarno.

Many thanks for reviewing the draft spec. I have added your comment to our tracking list at https://wiki.oasis-open.org/dita/DITA-1.3-public-review-1

Best,
Kris

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

On 7/14/2015 5:30 PM, Jarno Elovirta wrote:
In “2.3.4.10.8 Example: Key definitions in nested key scopes” <http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part1-base/archSpec/base/example-nested-key-scopes.html>, the tables in the end of the topic have a column "Resource to which the key resolves”. The table contents however seem to refer to keys, not resources. To improve the readability of the examples and uniformity with “2.3.4.10.7 Example: References to scoped keys” <http://docs.oasis-open.org/dita/dita/v1.3/csprd01/part1-base/archSpec/base/example-scoped-key-references.html>, the example map should use href attributes on keydef elements to bind a resource to the keys:

<map>
  <title>Root map</title>
  <!-- Root scope -->
  <keydef keys=“a” href=""
  
  <!-- Key scope A -->
  <topicgroup keyscope="A">
    <keydef keys="b" href="">
        
And then in the table use those resources to clarify which resource is bound to that key
a topic-1.dita, defined in the root map
Jarno Elovirta



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