Re: Resolving outstanding issues in DeltaV

I agree with this approach and conclusion. Let's focus on making sure we 
have the full issue list and a set of candidate solutions to discuss. Some 
may interact. The working group activity indicates we're not done, but 
we're healthy and moving forward. Thanks to everyone for the thoughtful 
input.





"Clemm, Geoff" <gclemm@rational.com>
Sent by: ietf-dav-versioning-request@w3.org
06/22/2001 06:12 PM

 
        To:     ietf-dav-versioning@w3.org
        cc: 
        Subject:        Resolving outstanding issues in DeltaV

 

My current approach, unless guided otherwise by our working
group chair, is to only make changes to the protocol if there
is consensus that the change should be made.  Currently,
I do not see consensus on either the resourcetype issue, or
the working resource checkin issue (note: this means that
the current DAV:resourcetype values in the protocol stay in).

Since I believe that neither of these issues represent a critical flaw in
the protocol (but rather represent possibly useful extensions
that we could add in later), I propose that we table the issues
for now.

Would anyone like to take these topics to our Friday noon
conference call?  It is possible that we could make more
progress with that higher bandwidth medium.  In any case,
we will discuss them at the DeltaV working group meeting
in London.

Cheers,
Geoff

-----Original Message-----
From: Eric Sedlar [mailto:Eric.Sedlar@oracle.com]
Sent: Friday, June 22, 2001 11:07 AM
To: ietf-dav-versioning@w3.org
Subject: RE: Dav:resourcetype


I don't think we are getting close to a consensus on this issue.  I'm
personally in favor of using dav:resourcetype for type information 
(after Yaron used his Jedi mind tricks on me), but I don't care enough
to argue about it anymore.

Is there a defined IETF procedure for flipping a coin to decide on what
to do with a spec, or some other source of randomness?  How about if 
everybody agrees that if the Dow is an even number on Monday (at the
close, truncating fractional part) we will put type information in 
dav:resourcetype, and if it is an odd number,
we will use supported-*-resource-set (and go back to <dav:is-principal>
in the ACL spec)?

Deal?  Geoff?

(P.S.  I have a suggested topic as an alternative for those who want to 
argue about this more:  Is operator overloading in C++ a good idea or
not?  Discuss.)

--Eric

Received on Saturday, 23 June 2001 11:28:34 UTC