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] Key definition with key reference


Hi, Denis.

 

The DITA TC has discussed your e-mail at several meetings, and we have agreed that we need to do the following:

  • Clarify certain language in the DITA specification
  • Add some additional examples to the specification

 

We are in the process of doing the above work, and we will share a copy of an updated draft of the DITA 2.0 specification when we have completed the work.

 

Best wishes,

 

Kristen James Eberlein

Chair, OASIS DITA Technical Committee

 

From: Denis Troaca <denistroaca@gmail.com>
Sent: Tuesday, August 8, 2023 9:22 AM
To: dita-comment@lists.oasis-open.org
Subject: [dita-comment] Key definition with key reference

 

According to DITA Specification(https://docs.oasis-open.org/dita/dita/v1.3/os/part1-base/archSpec/base/example-keydef-with-keyref.html), if we have a keydef element with a keyref to another key, the first key should pull resources from the second if they are not already present in the initial keydef. Does this rule also apply to child elements of elements within that keydef?

 

Example: 

The initial keydef contains a "topicmeta" element with no "keywords" elements or contains a "topicmeta" with a "keywords" but no "keyword" elements inside and the referenced keydef has a "topicmeta" with "keywords" and "keyword" elements. Does the initial keydef pull the "keyword" from the referenced keydef or does it keep its empty "topicmeta" element?



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