SUO: RE: Vote on SUMO
The original message was received at Fri, 10 Aug 2001 19:00:39 +0900 (JST)
from sp213.ei.sanken.osaka-u.ac.jp [133.1.32.87]
----- The following addresses had permanent fatal errors -----
<James.Schoening@mail1.monmouth.army.mil>
----- Transcript of session follows -----
... while talking to cecom10.monmouth.army.mil.:
>>> MAIL From:<miz@ei.sanken.osaka-u.ac.jp> SIZE=4485
<<< 451 <miz@ei.sanken.osaka-u.ac.jp>... Sender domain must resolve
... while talking to ns1.monmouth.army.mil.:
>>> MAIL From:<miz@ei.sanken.osaka-u.ac.jp> SIZE=4485
<<< 451 <miz@ei.sanken.osaka-u.ac.jp>... Sender domain must resolve
<James.Schoening@mail1.monmouth.army.mil>... Deferred: 451 <miz@ei.sanken.osaka-u.ac.jp>... Sender domain must resolve
Message could not be delivered for 5 days
Message will be deleted from queue
------------------------------------------
Dear Jim,
I received the mail.
I vote "No".
As we discussed at the SUO workshop, the current SUMO acitivity looks
so-called prototyping approach which doesn't fit SUO building. The first
SUO working document we would agree on should be something stating a methodology
for SUO building. This is because SUO building should take the so-called
structured programming approach rather than rapid prototyping.
Cheers,
Riichiro
On Thu, 19 Jul 2001 23:30:41 -0400
"Schoening, James R CECOM DCSC4I" <James.Schoening@mail1.monmouth.army.mil> wrote:
> ATTN Voting Members of SUO WG,
>
> 1. Please immediately acknowledge receipt of this email letter ballot. If I
> do not receive within 3-days, I will contact you again. We want to make
> sure all voting members receive this ballot. The wording of this ballot was
> developed and reviewed by the SUO Policies & Procedures Subgroup.
>
> 2. This message is to Ballot the question :
>
> "Should the IEEE P1600.1 Standard Upper Ontology Working Group
> commence work on the Suggested Upper Merged Ontology (SUMO) version 1.15
> [June 22, 2001] posted at http://suo.ieee.org/Merge.txt, with the intent of
> developing it into the final SUO document?
> Note 1: See background information below for more details.
> Note 2: This may be one of several candidate documents to be
> combined and aligned into the final SUO document via the consensus building
> process."
>
> 3. By 15 Aug '01, please vote YES (comments optional), NO (comments
> required), or ABSTAIN (comments optional). Please send your votes and
> comments directly to me, but you are also free to post to the SUO list and
> openly discuss this topic.
>
> 4. This vote will pass if it receives a majority of YES vs. NO votes.
> ABSTAINS and non-votes are not counted in determining majority. The Chair
> may vote to make or break a tie. As all voting members will have received
> and acknowledge receipt of this ballot and will therefore have an
> opportunity to vote, there will be no quorum of votes required for this
> motion to be determined.
>
> 5. Non-voting participants are welcome to express opinions and submit
> comments.
>
> 6. Background:
>
> a. The purpose of this vote is to determine the level of consensus
> we have for focusing work on this document. In other words, we need to
> decide if we are going to go down this path or not. A working group may
> decide to work on more than one document.
>
> b. The primary purpose of this vote is NOT to propose improvements
> to the document, unless they are major enough for you to vote against
> focusing work on this document. However, such general improvement comments
> are welcome and will be resolved (but not unless and until the vote passes,
> since there would be no sense resolving comments if the group does not want
> to proceed
> with this document.
>
> c. If this vote passes, this document will change from being the
> work (and under the control) of a group of individuals to being the work
> (and under the control) of the SUO WG. A Technical Editor will be appointed
> or elected, who will incorporate WG-approved changes into the document.
> This does not require frequent formal votes for every change. A better
> approach
> for daily or weekly updates is to develop consensus by resolving objections,
> as we did
> when revising the Scope and Purpose. In other words, (1) the Technical
> Editor leads the discussion by processing the issues and suggestions; (2)the
> issues/suggestions identify proposed additions, changes, or deletions to the
> wording in the document; (3) the Technical Editor asks the WG for any
> objections. Items that do not have clear consensus would be accumulated for
> later, more formal processing, i.e., the proposer of the issue/suggestion is
> responsible for making a formal proposal (with a WG vote) for the proposed
> change.
>
> Jim Schoening
> Chair, SUO WG
>
>
---------------------------------------------------------------------
Best wishes, Riichiro Mizoguchi
The Institute of Scientific and Industrial Research, Osaka University
8-1 Mihogaoka, Ibaraki, Osaka, 567-0047 Japan
Phone: +81-6-6879-8415, 2125
Fax: +81-6-6879-2126(Urgent) +81-6-6879-2123(for large volume)
URL: http://www.ei.sanken.osaka-u.ac.jp/
---------------------------------------------------------------------