Hi Kris,
I agree with using -atts for those entities like we do in the main DTDs. For the most part, href/keyref are always together except for topicref/keydef we could move keyref into
reference-content-atts then have reference-content-nokeyref-atts for the topiref one.
That would also make it easier to get rid of the keyref entities. The only question mark is what will happen to the video element with Eliot's proposal.
Ãric Sirois
DITA Toolsmithâ
IXIASOFT
45 Chemin Bates, Suite 220 â Montreal, QC H2V 1A6
tel + 1 514 279-4942 / toll free + 1 877 279-4942
mobile + 1 647 462-3620
eric.sirois@ixiasoft.com
/
www.ixiasoft.com
From: dita-lightweight-dita@lists.oasis-open.org <dita-lightweight-dita@lists.oasis-open.org>
On Behalf Of kris eberleinconsulting.com
Sent: September 21, 2022 9:58 AM
To: dita-lightweight-dita (dita-lightweight-dita@lists.oasis-open.org) <dita-lightweight-dita@lists.oasis-open.org>
Subject: [dita-lightweight-dita] Suggested changes to the LwDITA grammar files
There are changes that Iâd like to make in the LwDITA grammar files:
- Get rid of any entities that simply declare a single attribute, and instead declare the attribute directly on the element. There are four entities that this would
apply to:
-
<!ENTITY
% control-variables
'keys CDATA #IMPLIED '>
<!ENTITY % variable-content
'keyref CDATA #IMPLIED '>
<!ENTITY % variable-links
'keyref CDATA #IMPLIED '> -
<!ENTITY
% fn-reuse
'conref CDATA #IMPLIED ' > - Standardize the names of the entities (and attribute groups) to match how they are used in the DITA spec. This would reduce cognitive dissonance for DITA architects
who work with both DITA and LwDITA, as well as spec editors.
Any objections or concerns? Letâs discuss this on list so that it does not need to wait until the next subcommittee meeting/
Best,
Kris
Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Owner, Eberlein Consulting LLC
kris@eberleinconsulting.com
Skype: kriseberlein; voice: +1 (919) 622-1501