Re: Where do we currently stand with our position on PATCH?

> Once a patch format is agreed upon we will be able to make PATCH a 
> mandatory feature of LDP. 

I would not jump to "mandatory" in the sense of "MUST support PATCH". 
Container semantics are perfectly sensible and useful whether or not PATCH 
is supported.  A whole heck of a lot of clients use similar ones (*cough* 
Atom *cough*) in read-only or append-only mode (via methods other than 
PATCH) very happily.  Just knowing how to find and iterate over container 
members in a general fashion has benefits.

We have discussed the "If (iff) you support PATCH, then you MUST support 
format X", and that also is perfectly sensible and useful as a way to 
establish a baseline for wide interop.

Now get off my lawn ;-)


Best Regards, John

Voice US 845-435-9470  BluePages
Tivoli OSLC Lead - Show me the Scenario