dita — archive
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]
Re: [dita] Status values
MHonArc v2.5.0b2 -->dita message
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [dita] Status values
- From: Don Day <[email protected]>
- To: [email protected]
- Date: Tue, 23 Aug 2005 00:19:35 -0500
Actually, 25 was the original number, then it was #6 on another list. The title, regardless of its number, is "Make @role (and other enumerated attributes) un-enumerated. ." I am attempting to revise the overall issues list, since we need to add a few new items to it. Regards, -- Don Day Chair, OASIS DITA Technical Committee IBM Lead DITA Architect Email: [email protected] 11501 Burnet Rd. MS9033E015, Austin TX 78758 Phone: +1 512-838-8550 T/L: 678-8550 "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot Don Day/Austin/IBM@IB MUS To "France Baril" 08/22/2005 11:18 <[email protected]> PM cc [email protected] Subject Re: [dita] Status values In discussing this with Michael, we think this is basically Feature #25 proposed for OASIS DITA 1.1 to remove enumerations from attribute value lists, one that we just haven't gotten around to evaluating it yet. The originally given values for this attribute came out of early usage long before DITA was donated to OASIS, and seemed like a good idea at the time. Regards, -- Don Day Chair, OASIS DITA Technical Committee IBM Lead DITA Architect Email: [email protected] 11501 Burnet Rd. MS9033E015, Austin TX 78758 Phone: +1 512-838-8550 T/L: 678-8550 "Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?" --T.S. Eliot "France Baril" <France.Baril@ixi asoft.com> To <[email protected]> 08/19/2005 12:22 cc PM Subject [dita] Status values I am starting a new project with DITA, it has different requirements then other projects I have worked on and I thought it could be interesting to use the status attribute. Why did we lilmit the possible values, as soon as you have specific client requirements you loose use of this attribute? And you have to fallback to otherprops... again!!! Maybe this is irrelevant with our move to specializable attributes, but still I thought it might be worth mentionning. France Baril Documentation Architect/Architecte documentaire IXIASOFT tel.: + 1 514 279-4942 fax: + 1 514 279-3947 toll free: + 1 877 279-IXIA [email protected] [ www.ixiasoft.com ] Let's Talk XML
- References:
- Re: [dita] Status values
- From: Don Day <[email protected]>
- Re: [dita] Status values
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
— [Date Index]
| [Thread Index]
| [Month Index]
| [List Home]