Cascading <metadata> element in map

[Masayuki Yamane]

Hi,

It seems that map <othermeta> cascading behavior was changed for Issue #1899 by PR #3326.  Since my DITA-OT upgrade is not cascading it, I have a problem.

There are two different <othermeta> in map.

1. <topicmeta>/<othermeta>
2. <topicmeta>/<metadata>/<othermeta>

DITA 1.3 Reconciling topic and map metadata elements expects <othermeta> as <topicmeta> element won't cascade for reconciling, but <metadata> as <topicmeta> element will cascade for reconciling.  That does make sense, topic <prolog>/<othermeta> doesn't exist, but topic <prolog>/<metadata> is available for reconciling.

However, when I check DITA-OT 3.7.2, both of <othermeta> are not cascading regardless of whether it is in <metadata> or not.  It is strange, because PR #3326 seems to be trying to cascade <metadata>.  Is this a bug?

If this was expected, it won't be easy to set HTML <meta> to certain set of HTML topic output.  Do we always need to specialize <data> to accomplish that?

This is related with my recent question for dita-users mailing list.

Thank you,

Masayuki Yamane

[Chris Papademetrious]

Hi Yamane-san,

I was also investigating metadata cascading when you posted this, so I wanted to share my results.

When metadata is directly defined in a topic reference, then the HTML for that topic's HTML gets the metadata shown in green:

When this topic reference also contains a nested subtopic reference, then that subtopic's HTML gets the metadata shown in green:

When the metadata is placed in a <mapref> instead of a <topicref>, then the metadata does not go into the HTML output at all:

I did not spend time comparing these results against the DITA 1.3 specification at

https://www.oxygenxml.com/dita/1.3/specs/archSpec/base/reconciling-topic-and-map-metadata.html

but I wanted to at least share the data.

 - Chris

[Masayuki Yamane]

Thank you, Chris, for sharing your data!  While I have never tested the third submap case, the earlier two cases are representing exactly what I am seeing.

From my later research, I have realized that DITA 1.2 specification is stating <othermeta> will cascade.

http://docs.oasis-open.org/dita/v1.2/os/spec/archSpec/cascading-in-a-ditamap.html

Attributes and metadata that cascade

The following attributes and metadata elements cascade:

Metadata elements

• author, source, publisher, copyright, critdates, permissions
• audience, category, prodinfo, othermeta

It is not clear what is implied by the two bullets in the "Metadata elements" list, but I am feeling that first bullet is listing direct children of <topicmeta>, and second bullet is listing children of <topicmeta>/<metadata>.

So, this DITA-OT preprocessing behavior seems to be an issue for DITA 1.2 standard supportability at least.

Thank you and best regards,

Masayuki Yamane

--
You received this message because you are subscribed to a topic in the Google Groups "DITA-OT Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/dita-ot-users/xm9340MR-xc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to dita-ot-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/dita-ot-users/baa8e781-4d4c-45dc-949b-576a5e670635n%40googlegroups.com.