I agree with Elias. Multiple bindings are explicitly identified in DeltaV as something created when you have a version-controlled resource for a given version history as an immediate member of more than one collection in that workspace. Therefore, if anything is unclear about this in RFC-3253, please submit this as a bug against RFC-3253, and I'll make sure it gets addressed in RFC-3253bis. Cheers, Geoff Elias wrote on 04/26/2005 05:20:30 PM: > > Julian Reschke wrote: > > > [...] most of the open Bugzilla issues should have been closed [...] > > 5, Bindings and DeltaV aren't fully interspecified > The discussion of the issue seems to have stalled, with no additional > text being suggested or discussion of the issue for three months. Julian > seems to take the position that DeltaV servers can always choose to fail > a BIND request if the implementors don't want to deal with it, while > Lisa seems to want to at least state that interactions when a binding is > created are unspecified. Personally, I feel that the interactions should > have been specified in 3253, as bindings existed prior to 3253 being > published. This implies that any clarifications of these interactions > belong as errata against the same and if any additional text is > required, I would suggest that the reader is told as much. > > Comments? > > > Cheers, > Elias >Received on Wednesday, 27 April 2005 03:06:38 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:08 GMT