Next in thread →
Next in month →
RE: [dita] Negative 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 From: "Chris Wong" <> To: "Michael Priestley" <>,"Paul Prescod" <> Date: Tue, 18 Apr 2006 10:42:13 -0400 I think he means "scoped values". From your spec: audience="programmer/database programmer/Java programmer/Web" I'm surprised to see this in the spec too, since I was not aware that there is significant demand for this. Maybe I missed the discussion. Chris From: Michael Priestley [mailto:] Sent: Tuesday, April 18, 2006 10:24 AM To: Paul Prescod Cc: Subject: Re: [dita] Negative values What scope attribute? Michael Priestley IBM DITA Architect and Classification Schema PDT Lead http://dita.xml.org/blog/25 "Paul Prescod" <> 04/18/2006 10:03 AM To <> cc Subject [dita] Negative values This document describes negative values: http://www.oasis-open.org/committees/download.php/17329/IssueNumber20.ht ml It isn't explicit about the semantics of them. For example, it implies that negative and positive values can be combined in a single attribute (otherwise why say that the NOT operator only applies to a single value). But I would have thought that a negation of value A implies value B by definition. Therefore explicitly stating value B is redundant. audience="NOT paul" Means everybody but paul. Therefore saying "everybody but paul plus janice" is redundant. In programming language terms: If Audience!=paul OR audience=janice Although I am a fan of the goals of this feature, I am not convinced that we can work out the details in the time we have. Plus I think that it is a bit of scope creep beyond what the TC agreed to. The same goes for the scope attribute. Paul Prescod Follow-Ups: RE: [dita] Negative values From: Michael Priestley <> [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Next in thread →
Next in month →