[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Subject: Re: [rights-requirements] Terms to define in the requirementsspecification
Aaron,
One of the constraints regarding a definition of terms section in a
standard is that the term(word) itself is used in the text of the standard
and a definition is needed in order for the reader (reviewer) to ascertain
context/meaning in which it is used in the text they are reading. Simply
generating a list of nice-to-know about terms may well confuse a reviewer
and is not what standardization is about...
Pete Schirling
Digital Media Standards
IBM Research Division
Office: +1 802 769 6123/Mobile: +1 802 238 2036/E-Fax: +1 802 769 7362
Mobile text messaging 8022382036@msg.myvzw.com
Internet e-mail: schirlin@us.ibm.com
Aaron Burstein
<burstein@boalthall.be To: rights-requirements@lists.oasis-open.org
rkeley.edu> cc: burstein@boalthall.berkeley.edu, drowan@boalthall.berkeley.edu
Subject: [rights-requirements] Terms to define in the requirements
10/16/2002 04:46 PM specification
Please respond to
burstein
Here are some terms that would be helpful to define in the RLTC
requirements specification, to assist public reviewers who have not
followed the TC closely. We suggest these terms as a place to start.
1. architecture
2. permission
3. right (appears in TC name but not in requirements document; we should
explain why this is so)
4. realm
5. core
6. role, group, attribute
7. noun
8. verb
9. condition
10. license - (appears only in R20)
11. profile - (appears only in R24 and SX11)
Aaron Burstein
Dean Rowan
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]
Powered by eList eXpress LLC