[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: Technical content specializations to add to proposal #647
I would generally prefer to allow it everywhere and let users ignore it where itâs not relevant. If pressed I can imagine a credible use case for classifying anything a topicref might point to
😊 Itâs hard to see a harm in allowing @subjsectref on all topicrefs since it has no required processing associated with it. Cheers, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 LinkedIn | Twitter | YouTube | Facebook From:
dita@lists.oasis-open.org <dita@lists.oasis-open.org> on behalf of kris eberleinconsulting.com <kris@eberleinconsulting.com> [External Email] There are a lot of specializations of <topicref> in the technical content edition! Here are my thoughts of what to include (and what to exclude): Elements to include:
I was a little on the fence about enabling @subjectrefs on <glossref>, since glossary topics are tightly focused topics about a single term. But then I thought of a few (credible?) use cases for it:
Elements to exclude:
Thoughts? Let me know if you object, preferably before I send an updated proposal to the list. Best, Kris |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]