Re: [dita] Follow-up questions on specialization

MHonArc v2.5.0b2 -->

















dita message






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]








Subject: Re: [dita] Follow-up questions on specialization




From: Michael Priestley <>
To: "Paul Prescod" <>
Date: Mon, 7 Mar 2005 22:35:58 -0500




1) since keyword doesn't currently allow
nesting of markup, and uicontrol has optional child elements, uicontrol
had to be specialized from ph rather than keyword. One of the suggestions
for DITA 1.1 is to allow keywords to nest, which would remove the reason
for this particular ancestry and potentially allow us to respecialize uicontrol
from keyword.

2) not currently documented outside
the DTD/schema. Could potentially be added to the language spec, which
started as a straightforward user's reference but is now being used for
a different audience (ie implementers rather than users). 


Michael Priestley



Dept PRG IBM Canada  phone: 416-915-8262

Toronto Information Development







"Paul Prescod"
<> 
03/07/2005 09:23 PM




To
<>


cc



Subject
[dita] Follow-up questions
on specialization








1. Can anyone describe why "uicontrol" is
different


<!ATTLIST shortcut    %global-atts;  class CDATA "+
topic/keyword

ui-d/shortcut ">

<!ATTLIST uicontrol   %global-atts;  class CDATA "+ topic/ph

ui-d/uicontrol "    >

<!ATTLIST wintitle    %global-atts;  class CDATA "+
topic/keyword

ui-d/wintitle ">


2. In general, is the specialization structure (both details and

rationale) documented anywhere except in the actual DTD? For example,

how would I find out from the spec that task/postreq is a kind of

topic/section?


----

 Paul Prescod

 Group Program Manager

 Blast Radius XMetaL









References:

Follow-up questions on specialization
From: "Paul Prescod" <>






[Date Prev]
 | [Thread Prev]
 | [Thread Next]
 | [Date Next]

--

[Date Index]
 | [Thread Index]
 | [List Home]