RE: [dita] Proposed Issue: Recognizing DITA Documents

From
Erik Hennum <>
Date
2005-08-30T14:07:00+00:00
ID
Thread
RE: [dita] Proposed Issue: Recognizing DITA Documents
MHonArc v2.5.0b2 -->
















dita message






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

--

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








Subject: RE: [dita] Proposed Issue: Recognizing DITA Documents




From: Erik Hennum <>
To: "Paul Prescod" <>
Date: Tue, 30 Aug 2005 06:56:59 -0700







Hi, Paul:


Regarding


> Why not just put it on the root element always?



The outermost element of DITA content is always a map or topic. In other words, the root element for DITA content does have the architecture attribute.


The sole exception is the <dita> element, which has an odd role because it has no semantics and merely contains a list of topics.  Because the <dita> element cannot be specialized, it's name cannot be changed.  If someone wanted to make the case that, for convenience and consistency, the <dita> element should also take the architecture attribute, I could buy that.


On that basis, we can be confident that the following document contains a specialized DITA topics (mytopic) nested within some non-DITA content.  The <mydita> element cannot be a DITA specialization.


> Is this a DITA document?

>

> <mydita>

> <foo>

> <bar>

> <baz>

> <mytopic class="- topic/topic mytopic/mytopic "

> 		 xmlns:ditaarch=" http://dita.oasis-open.org/architecture/2005/"

> 		 ditaarch:DITAArchVersion="1.0">

> ...

> </mytopic>

> </baz>

> </bar>

> </foo>

> </mydita>




Hoping that's useful,



Erik Hennum















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

--

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