dita — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
FW: Reasoning for not cascading
Forwarding from dita-comment.
Best, Kris Kristen James Eberlein Chair, OASIS DITA Technical Committee Owner, Eberlein Consulting LLC [email protected]
Skype: kriseberlein; voice: +1 (919) 622-1501
From: Kirkilis, John (Nokia - US/Austin) <[email protected]> Sent: Wednesday, November 16, 2022 9:24 PM
To: Kristen James Eberlein <[email protected]>; [email protected]
Subject: Re: Reasoning for not cascading <othermeta> metadata Whoops. Auto-correct error. What I meant to ask is why does one "other" cascade and the other one does not (<othermeta> vs @otherprops), regardless of whether one is an element and one is a conditional attribute. They are both meant to handle use cases where the built-in choices are insufficient. I asked Jarno how we, Nokia, would extend the processing to do this ourselves in DITA-OT, and he highly recommended not doing it. I don't recall his specific reason however, but could find out. It might have required that we fork the OT project, which would be a very last resort. Get Outlook for iOS
From: Kirkilis, John (Nokia - US/Austin) < [email protected]
> Sent: Wednesday, November 16, 2022 8:35 PM
To: kris eberleinconsulting.com < [email protected] >; [email protected] < [email protected]
>
Subject: Re: Reasoning for not cascading <othermeta> metadata Following up after DITA-OT day. The conditional attribute “otherprops” cascades, so how does its use case differ ? Get Outlook for iOS
From: kris eberleinconsulting.com < [email protected]
> Sent: Sunday, October 2, 2022 8:18:20 PM
To: Kirkilis, John (Nokia - US/Austin) < [email protected] >; [email protected] < [email protected]
>
Subject: RE: Reasoning for not cascading <othermeta> metadata 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 [email protected]
Skype: kriseberlein; voice: +1 (919) 622-1501
From: Kirkilis, John (Nokia - US/Austin) < [email protected]
> Sent: Saturday, October 1, 2022 9:27 AM
To: [email protected]
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: Can you explain the reasoning for this exception so I can better understand the matter? How have you or others propagating <othermeta> metadata to child topicrefs? Best Regards, John
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]