Sam,
6.4.2 Servers that support prefill SHOULD include the value POST in the set of Allow header[s]...
Why is that SHOULD and not MUST? If a client's UI is optimized by the use of prefill I should think it would want to know that it can use prefill when negotiating
with the server. The alternative is to try a POST and see if it succeeds and returns a new resource URI - a less optimal integration experience.
Thanks,
Martin
Martin Sarabura
R&D Fellow, PTC
From: [mailto:]
On Behalf Of Samuel Padgett
Sent: February-19-15 5:30 PM
To: OASIS OSLC Core TC Discussion List
Subject: [oslc-core] Delegated Dialogs 3.0 Ready for Review
As discussed in today's Core TC call, the dialogs draft is ready for review. I'd appreciate any feedback you have. Please try to get me any comments by March 5, so I can prepare the document
for public review.
http://tools.oasis-open.org/version-control/browse/wsvn/oslc-core/specs/dialogs-v3.html
Thanks,
--
Samuel Padgett | IBM Rational |
Eclipse Lyo: Enabling tool integration with OSLC
