MHonArc v2.5.0b2 -->
















dita message






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

--

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








Subject: RE: [dita] DITA 1.1 issue 20: Extensible metadata attributes




From: "Paul Grosso" <pgrosso@arbortext.com>
To: "Christopher Wong" <cwong@idiominc.com>
Date: Fri, 3 Jun 2005 10:24:59 -0400









Epic handles both DTDs and XML Schemas. When using a 
DTD,
any prefixed (namespaced) attribute not declared in the DTD 
is
allowed. 
 
Namespacing attributes is an easy way to allow arbitrary 
attributes
to be added without having to modify the DTD or schema and, 
at
the same time, to make it easy to recognize and provide 
special
processing for a certain set of attributes.
 
paul



  

  

  From: Christopher Wong 
  [mailto:cwong@idiominc.com]
Sent: Friday, 03 June, 2005 
  9:00
To: Paul Grosso
Cc: DITA TC list
Subject: 
  Re: [dita] DITA 1.1 issue 20: Extensible metadata 
  attributes


  
Isn't Epic's DITA support still DTD-based? How would namespacing 
  extensions to %select-atts; help in DTD-land?

Chris

Paul Grosso 
  wrote: 
  
I haven't thought a lot about this yet, but I was having
a discussion with some of our developers today who also
felt the need for extensible metadata attributes, and 
they felt the right way to do it was to have a separate
namespace for metadata attributes.  

Then the DITA schema could allow any attribute in
that namespace on any element, so it would be easy 
to add "profiling" attributes or other metadata.

paul 

  
    
-----Original Message-----
From: Christopher Wong [mailto:cwong@idiominc.com] 
Sent: Wednesday, 01 June, 2005 17:15
To: DITA TC list
Subject: [dita] DITA 1.1 issue 20: Extensible metadata attributes

Could I get an idea from our XML gurus how this could be 
achieved in a 
compatible manner? The issues list does not quite have a lot 
of details.