OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [dita-comment] UI Messages With Titles: DITA Spec Modernization


Thanks, Shane.

I'll add this item to the TC agenda. When the TC discusses it, I (or another voting member of the DITA TC) will respond on this list with information about the resolution.

Best,
Kris

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

On 11/30/2016 4:57 PM, Shane Taylor wrote:
The DITA spec includes both <msgph> and <msgblock> elements for the content of software application messages, but two aspects of these elements' definitions seem to hark back to text-only interfaces and don't work well for modern GUI or web-based applications.

First, both elements preserve whitespace, with no option to treat whitespace normally. Modern UI messages typically don't care about whitespace, so it's restrictive and incorrect that this content model forces users to preserve whitespace.

Second, <msgblock> does not allow a <title>. Many modern messages include a title followed by descriptive text. 

I would love the DITA-TC to consider these two issues for the next iteration of the spec. Both enhancements should easily be backward-compatible.

Shane Taylor



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]