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

 


Help: OASIS Mailing Lists Help | MarkMail Help

dita message

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


Subject: Re: [dita] Groups - Issue #85 Add ph to glossentry models - Hudson uploaded


Hi Scott,

It looks like this is still missing one thing that came up in our last discussion of the issue. The relevant section from the minutes is:

- Kris; does anyone know why it wasn't included in glossentry to begin with?
- Robert; it wasn't specifically left out, but highlighting is part of the phrase domain; the fix would be to add phrase to these elements, which would mean they also include all the phrase elements in the progrrmming, software, etc. domains; the original intent was to disalllow complicated phrase content in the glossentry elements.

- Eliot; the whole point of this is having to decide what elements we want to disllow, and where.
- Robert; since this is phase 1, I'd expert to see the stage 2 proposal, with its expected impacts, and see what happens if we add phrase elements.


Basically - adding phrase will add these two elements (which is the purpose of the proposal), but it also adds a bunch of other unrelated elements. It adds all the other items in the highlighting domain (b, i, u, tt, overline, line-through), and also adds the ph specializations from any other domain that's part of the shell. Assuming the same domains used in DITA 1.3, that would include <msgph>, <synph>, <codeph>, <filepath>, and several others. That long list is the reason <ph> was originally left out of these elements -- the fact that domains work this way regularly leads to questions like "Why do I have [some software or programming domain element] in this context where it clearly doesn't apply?"

This isn't an argument against the overall proposal - but to approve this I think we need to have a clear picture of the impact on content models. Can you check what other <ph> specializations will appear in these contexts, assuming the list of domains stays the same as what we have in DITA 1.3? I'm guessing that info should appear either under the "Costs" section, or more likely under the "Overall usability" item just above it.

Regards,

Robert D. Anderson
DITA-OT lead and Co-editor DITA 1.3 specification,
Digital Services Group


E-mail: robander@us.ibm.com
Digital Services Group
11501 BURNET RD,, TX, 78758-3400, AUSTIN, USA


Inactive hide details for Scott Hudson ---02/02/2018 12:25:13 PM---Submitter's message Stage 2 proposal ready for reviewScott Hudson ---02/02/2018 12:25:13 PM---Submitter's message Stage 2 proposal ready for review

From: Scott Hudson <scott.hudson@jeppesen.com>
To: dita@lists.oasis-open.org
Date: 02/02/2018 12:25 PM
Subject: [dita] Groups - Issue #85 Add ph to glossentry models - Hudson uploaded
Sent by: <dita@lists.oasis-open.org>





Submitter's message
Stage 2 proposal ready for review
-- Scott Hudson
Document Name: Issue #85 Add ph to glossentry models - Hudson

Description
The and elements are not allowed in several elements from glossentry,
which means that terms cannot be used properly in certain contexts. Since
and are specialized from , adding the element solves the issue.

Download Latest Revision
Public Download Link

Submitter: Scott Hudson
Group
: OASIS Darwin Information Typing Architecture (DITA) TC
Folder
: DITA Specification 2.0 Ideas and Proposals
Date submitted
: 2018-02-02 10:23:49





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