W3C home > Mailing lists > Public > www-webont-wg@w3.org > January 2002

Re: defaults

From: Deborah McGuinness <dlm@ksl.stanford.edu>
Date: Wed, 23 Jan 2002 09:22:19 -0800
Message-ID: <3C4EF14A.7A92FC3E@ksl.stanford.edu>
To: Jeff Heflin <heflin@cse.lehigh.edu>
CC: Dan Connolly <connolly@w3.org>, www-webont-wg@w3.org
I agree - I do not think we are at the point where we should say
"we have failed if we do not put in defaults"  thus would agree that
defaults is
in the goal classification.

if we had as classified non-monotonicity at the breakout meeting with this
kind of discussion, in my opinion, we would have put it in the
"open issues" category - a place for discussion because the topic is very
important but a topic for which consensus has not been reached.


Jeff Heflin wrote:

> > It would be really nice to start in that direction by
> > putting defaults in the "goal, but not requirement" section
> > of our requirements/use-cases document, citing the implementation
> > challenges Peter et. al. have pointed out on the one hand,
> > and the use cases Guus et. al. have pointed out on the other.
> Considering the current level of disagreement among group members, I
> would support putting defaults as a goal but not a requirement.
> > Hmm... I wonder if we have an un-stated requirement for
> > monotonic reasoning? I know monotonicity is a requirement,
> > for scalability, in my view. I'd like to see that
> > discussed in the design goals, if not listed as a specific
> > requirement. (In order to make it a specific requirement,
> > I should provide a compelling use case that depends
> > on it. I hope to do so, but I'm not confident I'll  find
> > time, nor am I confident that we'll want to devote
> > much space in our document
> > to that sort of thing; I hope it's sufficiently
> > clear to folks after a brief design-goal level discussion).
> >
> > JeffH and requirements editors, please let me know what
> > you think of this suggestion.
> I don't know if there is enough of a group consensus to make monotonic
> reasoning a requirement. A number of individuals (Pat Hayes, Peter
> Patel-Schneider, etc.) have made extremely strong cases why it should
> be, but I think those who support defaults and similar techniques are by
> definition against it. Thus, I think the issue should be discussed
> further before we decide how to treat it in the Requirements document
> (note this is my personal opinion, and does not necessarily represent
> the opinions of the other editors).
> Jeff Heflin
> Lehigh University

 Deborah L. McGuinness
 Knowledge Systems Laboratory
 Gates Computer Science Building, 2A Room 241
 Stanford University, Stanford, CA 94305-9020
 email: dlm@ksl.stanford.edu
 URL: http://ksl.stanford.edu/people/dlm
 (voice) 650 723 9770    (stanford fax) 650 725 5850   (computer fax)  801
705 0941
Received on Wednesday, 23 January 2002 12:17:48 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:56:41 UTC