12031 Controlled values / taxonomies

So the controlled values can be different
from time to time depending on which ditaval file is used? Or are the
controlled values used in the ditaval file, but defined somewhere else?  If
they are defined somewhere else, where is that?

 

   -Jeff

 











From: Erik Hennum
[mailto:]

Sent: Monday, August 20, 2007 9:49
AM

To: Grosso, Paul

Cc: 

Subject: Re: [dita] 12031
Controlled values / taxonomies



 

Hi, Paul:


Yes, the value of managing controlled values was discussed in a TC meeting
before the proposal was accepted as a condidate.


The proposal complements the ditaval file. The ditaval file is essentially
provides parameter to processes to inform processes how to treat instances
keyword values in the selection attributes.


The proposal defines controlled values so the set of controlled values for the
content have a standard representation and can be shared with the content. The
standard representation includes the ability to extend existing values, either
to add a value to the enumeration or to subsume one value in another. The
standard representation also includes a method to bind a controlled value to a
definitional topic. The defined controlled values can be used in selection
attributes and thus addressed in the ditaval file.


That's the quick summary -- the design will provide more detail.



Hoping that clarifies,



Erik Hennum





"Grosso, Paul" <> wrote on 08/15/2007 07:17:41 AM:


> Has there been any discussion of this beyond

> http://lists.oasis-open.org/archives/dita/200702/msg00059.html

> 

> Just what is being proposed here?  Is
this something that

> goes into the ditaval file, a separate file
that functions

> something like the ditaval file, some new
markup that goes

> into map files somewhere, or something else?

> 

> To what extent does this provide users with
capabilities

> that aren't already doable via the ditaval
file?