dita message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [dita] specialization question
- From: Erik Hennum <ehennum@us.ibm.com>
- To: "Grosso, Paul" <pgrosso@ptc.com>
- Date: Mon, 30 Apr 2007 10:12:50 -0700
Hi, Paul:
There are several issues in the approach sketched below for DITA 1.1:
- A specialization has to change the element name. There is a DITA 1.2 proposal for element aliasing to remove that limitation.
- A domain module cannot specialize from a topic type module. There is a DITA 1.2 proposal for domain-topic unification to remove that limitation.
- All topic and topic domain elements are effectively global. Consequently, designers can't create a new element name that's the same as an existing name without collision.
The collision underscores why DITA would benefit from aliases and namespaces so elements could be namespaced when needed to avoid collisions. People have raised valid concersn about the scope of that effort, but naming collisions will be an increasing problem until DITA has aliasing and / or namespacing.
Erik Hennum
ehennum@us.ibm.com
"Grosso, Paul" <pgrosso@ptc.com>
"Grosso, Paul" <pgrosso@ptc.com>
04/30/2007 09:47 AM
|
|
One of our consultants has created a new domain specialization
in which he specializes step. He doesn't change the name.
This works OK in the specialized topic DTD shell, but he runs
into trouble when he tries to include this domain in the ditabase
DTD shell. The problem is that there are two different step
elements, his from the domain and the regular one from task.
If I were doing this, I'd probably use a new name for the
specialized element, but that isn't what this person wanted
to do.
Should it be possible to do what he wants to do?
paul
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]