dita — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
RE: [dita] Negative values - scoped values
MHonArc v2.5.0b2 -->dita message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [dita] Negative values - scoped values
- From: Michael Priestley <[email protected]>
- To: "Esrig, Bruce (Bruce)" <[email protected]>
- Date: Tue, 18 Apr 2006 11:06:35 -0400
The scoped values also allow different kinds of classification: effectively, if one set of values has an "is-a" or "part-of" relationship to another set, it makes sense to express them as a single value, both semantically and for processing reasons.
For example, products have editions - but if you set product="A B C" and edition="2" then it's unclear which product the edition applies to; whereas if we set product="A B/2 C" it becomes much clearer.
Michael Priestley
IBM DITA Architect and Classification Schema PDT Lead
[email protected]
http://dita.xml.org/blog/25
| "Esrig, Bruce (Bruce)"
<[email protected]>
04/18/2006 10:57 AM |
|
As a taxonomy enthusiast, I like scoped values. From a logical point of view, scoped values are not necessary if you are only manipulating one value, because you can specify all its qualities in different attributes.
If the situation can only be described using two values both of which are scoped, then you need scoped values to avoid unintended combinations.
Without scoped values, you can describe items using multiple attributes as in this example:
establishment-type="bar hotel" establishment-name="NewYorker Plaza"
would have four intepretations
bar/NewYorker
bar/Plaza
hotel/NewYorker
hotel/Plaza
If you meant to say
establishment="bar/NewYorker hotel/Plaza"
then you need scoped values.
Bruce
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]