Re: [dita-lightweight-dita] RE: <prolog> and <data>

I think we can provide a mapping without the components being identical - this may be what you're saying? That we don't have an exact equivalent between eg <prolog> and <header> because they organize content differently, but we can still map the contents of them? I think the main implication is that we should limit attributes on the <prolog> and <header> elements, since they are serving primarily as a grouping construct and we don't want to get into metadata cascading rules etc.

For example, in XDITA, we might have structures like:

<title>This is my title</title>

(I'm not sure if othermeta is directly containable in prolog in DITA 2.0 - there might need to be a <metadata> wrapper?)

And then in HDITAÂwe change the grouping structure but preserve the content:

<header>
Â Â Â Â Â<title>This is my title</title>
Â Â Â Â Â<h1>This is my title</h1>

Â Â Â Â Â<meta name="x" content="this is for passing to output"/>
</header>

I'm not going to attempt the MDITA syntax - but hopefully this gets the idea across.

On Mon, Jan 9, 2023 at 5:30 AM Kristen James Eberlein <kris@eberleinconsulting.com> wrote:

Hi, Frank. I certainly think that having the facility to apply metadata on a topic level in HDITA and MDITA is critical

Â

But I donât think that having a equivalent of <prolog> is necessary for HDITA and MDITA. There isnât really an equivalent in HDITA, and the representation for topic-level metadata is <meta> elements. For MDITA, Iâd think it should be variables defined in a YAML front-matter header.

Â

Best,

Kris

Â

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Owner, Eberlein Consulting LLC
kris@eberleinconsulting.com

Skype: kriseberlein; voice: +1 (919) 622-1501

Â

From: Wegmann, Frank <Frank.Wegmann@softwareag.com>
Sent: Sunday, January 8, 2023 4:03 PM
To: Kristen James Eberlein <kris@eberleinconsulting.com>; dita-lightweight-dita (dita-lightweight-dita@lists.oasis-open.org) <dita-lightweight-dita@lists.oasis-open.org>
Subject: RE: <prolog> and <data>

Â

In general, I find it legitimate to allow metadata on the topic not only in XDITA within <prolog>, but also in MDITA and HDITA. In collaborative environments, Iâd prefer the option of having metadata in each of the formats in use.

Â

In the committee note #2, it is mentioned for the extended profile for MDITA and the example from the samples shows metadata in its natural habitat, namely the YAML header.

For HDITA, the spec draft locates metadata in <meta> inside <head>.

The current XDITA example for metadata uses only <data>, compared to a number of specific metadata elements in DITA like <author> etc.

Â

For me, the question is also about how the distinction between <metadata> and <data> in DITA is reflected in LwDITA, where the task of representing metadata is on the shoulders of <data> alone. That element is supposed to be used for metadata and also serve as basis for specialization. Do others see a possible issue here?

Â

f.

Â

Â

From: dita-lightweight-dita@lists.oasis-open.org <dita-lightweight-dita@lists.oasis-open.org> On Behalf Of Kristen James Eberlein
Sent: Monday, 19 December 2022 23:01
To: dita-lightweight-dita (dita-lightweight-dita@lists.oasis-open.org) <dita-lightweight-dita@lists.oasis-open.org>
Subject: [dita-lightweight-dita] <prolog> and <data>

Â

I can understand why XDITA has <prolog>; itâs necessary to hold metadata that applies to the topic as a whole. However, there really is not an HDITA or MDITA equivalent.

Â

I suggest rather than defining prolog and data components identically in HDITA and MDITA, we simply state that there is no HDITA or MDITA equivalent for prolog.

Â

Thoughts?

Â

Best,

Kris

Â

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Owner, Eberlein Consulting LLC
kris@eberleinconsulting.com

Skype: kriseberlein; voice: +1 (919) 622-1501

Â

Â

Software AG â Sitz/Registered office: UhlandstraÃe 12, 64297 Darmstadt, Germany â Registergericht/Commercial register: Darmstadt HRB 1562 - Vorstand/Management Board: Sanjay Brahmawar (Vorsitzender/Chairman), Dr. Stefan Sigg, Daniela BÃnger, Dr. Benno Quade, Joshua Husk - Aufsichtsratsvorsitzender/Chairman of the Supervisory Board: Christian Lucas - https://www.softwareag.com

Â

dita-lightweight-dita message