Re: SUO: Re: Standard Upper Ontology Procedures
I don't think we would want to restrict this to voting members, since there
is a lot of latency in achieving that status, and a lot of the enthusiasm
and energy seems to comefrom people who are bringing fresh minds to the
group.
Doug McDavid
Almaden Services Research
IBM Academy of Technology
mcdavid@us.ibm.com
ASR - http://www.almaden.ibm.com/asr/
http://www.almaden.ibm.com/coevolution/
BASIS - http://www.research.ibm.com/basis/
Jon Awbrey <jawbrey@att.net>
Sent by: To: SUO <standard-upper-ontology@ieee.org>
owner-standard-upper-ontology@majordo cc:
mo.ieee.org Subject: SUO: Re: Standard Upper Ontology Procedures
11/13/2003 09:01 AM
Please respond to Jon Awbrey
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o
SUOP. Note 7
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o
Matthew and SUO WG,
Just reading for typos at this point.
Suggested changes in square brackets.
One substantive question at the end.
| 2.2. Stage [2]. Draft Material Development
|
| Draft Material may be developed towards or in support of the project
| deliverables. This may be circulated for comment at the discretion
| of the Project Manager. No formal vote on this Draft Material is
| taken, but interested parties can raise issues against it. It is
| good practice to develop and maintain a formal issues log, but at
| this stage it is not required.
|
| Issues shall be raised using the pro-forma in Annex A,
| and sent to the SUO list. The issue resolution process
| is defined below in Clause 3.
|
| 2.3. Stage [3]. Draft Standard Proposal
|
| When the project is satisfied that they have the material in a form
| that constitutes a technically complete Standard, they may propose it
| as a Draft Standard. A formal vote is taken. The following responses
| are allowed:
|
| - Abstain
| - Yes
| - Yes with comments
| - No with comments
|
| "Yes with comments" does not require the issues raised to
| be resolved before the document is accepted as a Standard.
| This might be appropriate when there are editorial issues,
| or perhaps minor technical ones.
|
| "No with comments" means that the document is not considered fit
| for purpose as a standard, i.e., there are major technical issues
| that need to be resolved. It does not mean that the voter does not
| support the intent of the standard. That is decided when the [W]ork
| Programme is approved.
|
| Following the result of the vote, if the majority vote
| in favour, the document may pass to the next stage.
|
| 2.4. Stage [4]. Standard Proposal
|
| The project should attempt to resolve any issues raised as a result of
| the Draft Standard ballot and then when the Project Leader is satisfied
| that as many issues as possible have been resolved, then the document can
| be submitted for vote as a Standard. The voting is as for a Draft
Standard.
| The standard is passed if a majority vote for it, but in the event that
there
| are any "no with comments" votes, the Project Leader should consider
resolving
| the issues and resubmitting the document for a further vote.
|
| 2.5. Stage [5]. Revision
|
| A Standard may have issues raised against it. A log of these issues
shall be
| maintained by the SUO Chair. A Project to resolve one or more issues
against
| a Standard may be proposed.
|
| 3. Issue Resolution Process
|
| Any voting member of the Standard Upper Ontology Group may raise an issue
| against a document. An issue has an importance level that is one of the
| following values: ...
Question for the WG: Do we really want to restrict this to voting members?
Jon Awbrey
o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o~~~~~~~~~o