Re: [dita] Review of "Add a multimedia domain #27"

Keith,

Apologies for the long delay on this.
Things were a bit crazy before I went on vacation last week and this fell through the cracks.

Re: the decision to add nested elements with true/false values. In DITA 1.3 and lightweight DITA, we’re not allowed to add arbitrary attributes to specific elements; specializations of @base are global and can’t be targeted without extensive
constraints.
Since one of the drivers for this domain is consistency between DITA 1.3, DITA 2.0, and LwDITA, we have to use the ‘least common denominator’ approach here, which means using nested <data> specializations.
Also, of course, it’s impossible to have
an attribute without a value in XML.
That’s the main reasoning behind this design.

Note that the @value attributes on the nested elements are all #IMPLIED.
My thinking here – though I now realize I never made it explicit in the proposal – was that if the @value attribute is missing, “true” should be assumed.
Thus, the
mere presence of one of these elements will be sufficient to turn that option “on”.
For example:

<video data= >
<media-controls/>
</video>

The notes about the examples are well taken and I’ll address those in the Stage 3 proposal.

Chris
From: <> on behalf of Keith Schengili-Roberts <>
Date: Monday, March 5, 2018 at 12:48 PM
To: "" <>
Subject: [dita] Review of "Add a multimedia domain #27"

I had already sent this separately to Chris directly, but I think I am supposed to send this to the group.

The following was originally meant as a stage 2 critique, but I understand from Chris that the following should prove useful
for his work on stage 3.