Re: [dita] Limitations of titlealts

[Kristen James Eberlein <kris@eberleinconsulting.com>]

OK, we are talking about titles and topics here, correct?

I think Healthwise is using <navtitle> and <searchtitle> in a way that it was not intended to be used.

If you want topics to have different titles based on the publishing context/audience, here are the commonly used strategies:

• Filtering and branch filtering
  
• Key references and key scopes

Is part of the issue here also related to the Healthwise CCMS and the factory publishing environment?

One of the proposals for DITA 2.0 was to add <titlealts> to map, and we've come very close to deciding that it is too complex and will lead to myriad difficulties with implementation.

Best,
Kris

Kristen James Eberlein
Chair, OASIS DITA Technical Committee
Principal consultant, Eberlein Consulting
www.eberleinconsulting.com
+1 919 622-1501; kriseberlein (skype)

On 8/28/2018 10:53 AM, Bill Burns wrote:

Hello,

We're running into some problems with the limitations of the titlealts model. We have about 9 different channels to which we publish and have different needs for titling

We are using navtitle for a number of purposes, but we're finding that one navtitle or one searchtitle isn't cutting it. For example, we have a product called a patient instruction, which is very flat. We use navtitle for clinical titles. However, if we decided to use that map as part of a knowledge base article (which is a much longer piece), we'd need the navtitle to generate the navstack, and we'd want that not to be what a clinical sees but what a consumer would see. In addition, we have Content-as-a-Service, which has a whole different set of requirements for titles, as the service presents content at the topic level. Ideally, we'd be able to specialize navtitle for these purposes, but because of the restriction of one navtitle or one search title, we're no better off.

I'd like to propose that we add a general purpose alternative title that can occur more than once and can be used as a basis for specialization would allow us to create proper semantics for our various title type, and we'd be less likely to just shove our titles into navtitle or search title.

Thoughts?

Bill Burns
Content Architect | Healthwise
bburns@healthwise.org<mailto:bburns@healthwise.org> | www.healthwise.org<http://www.healthwise.org/>
208.331.6917 (office)  |  208.345.1897 (fax)

Healthwise helps people make better health decisions.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that 
generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php