OASIS Darwin Information Typing Architecture (DITA) TC

Michael Priestley wrote:

>  > Or have I missed something?
> 
> <data> might be a better choice than </data>

  
  


Or you could just add the arbitrary attribute as an
attribute in a customization, Eliot, then maintain a transform to turn
it into a data element with a "name" attribute of the same name if you
want to produce valid DITA for export.


That's what I'm doing in a customized subset of DITA I'm implementing -
plus changing a few element names to reflect local locutions, and
maintaining transforms for them as well.


It seems such a process should be generalizable in future for adding
arbitrary attributes, generalizing them as data elements, then
respecializing them as attributes - perhaps by adding some flags to the
data element to govern the process.


--Dana



W. Eliot Kimber wrote:

Michael
Priestley wrote:


  
 > Or have I missed something?


<data> might be a better choice than <ph> but otherwise I
think you are correct.

  


Data, yes, that might be better.


Cheers,


E.

Dana Spradley wrote:
> Or you could just add the arbitrary attribute as an attribute in a 
> customization, Eliot, then maintain a transform to turn it into a data 
> element with a "name" attribute of the same name if you want to produce 
> valid DITA for export.

In this case I'm trying to create a pure DITA system that doesn't 
require any sort of pre-process transform.

Cheers,

E.

-- 
W. Eliot Kimber
Professional Services
Innodata Isogen
8500 N. Mopac, Suite 402
Austin, TX 78759
(214) 954-5198

ekimber@innodata-isogen.com
www.innodata-isogen.com