RE: Reasoning for not cascading <othermeta> metadata

[kris eberleinconsulting.com <kris@eberleinconsulting.com>]

Hi, John.

 

<othermeta> is a general purpose element. There is no knowing what people might use it for, so it does not cascade.

 

You certainly can customize your processing so that specific values for <othermeta> will cascade …

 

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: Kirkilis, John (Nokia - US/Austin) <john.kirkilis@nokia.com>
Sent: Saturday, October 1, 2022 9:27 AM
To: dita-comment@lists.oasis-open.org
Subject: [dita-comment] Reasoning for not cascading <othermeta> metadata

 

Hi Kris and company,

 

We’re building a new HTML5 HelpCenter in React that integrates with our products. For faceted search, metadata is essential.

 

The spec indicates in the cascade table that othermeta does not cascade as do the standard metadata elements.

 

I have two questions:

 

1. Can you explain the reasoning for this exception so I can better understand the matter?
2. How have you or others propagating <othermeta> metadata to child topicrefs?

 

Best Regards,

 

John