John, Thanks for doing this, I have some feedback on this:
1. How does a client know that an OSLC provider will accept the query-by-POST? The idea client will just try and get appropriate 415 response if server doesn't accept it? 2. Form encoded content MUST be interpreted as "run query": I wonder if this paints us into a corner with future ldp:Containers, where one might have a container implementation that accepts form encoding content for create. Perhaps it would be better to phrase in such a way that states that when an OSLC Server receives a form encoded content of OSLC Query, it MUST interpret that as "run query". So this would require servers to inspect content and then take right action, instead of branching based on content-type alone. Thanks, Steve Speicher IBM Rational Software OSLC - Lifecycle integration inspired by the web -> http://open-services.net "Oslc-Core" <[email protected]> wrote on 05/21/2013 07:09:07 AM: > From: John Arwe/Poughkeepsie/IBM@IBMUS > To: [email protected] > Date: 05/21/2013 07:09 AM > Subject: [oslc-core] Proposal for Core issue 17: Handling of long URIs > Sent by: "Oslc-Core" <[email protected]> > > Somehow I finished building this last week and then never sent it. Remediating now. > > http://open-services.net/wiki/core/OSLC-Core-V2-Issues/ > Best Regards, John > > Voice US 845-435-9470 BluePages > Tivoli OSLC Lead - Show me the Scenario [attachment "Query By POST for OSLC > Spec.pdf" deleted by Steve K Speicher/Raleigh/IBM] > _______________________________________________ > Oslc-Core mailing list > [email protected] > http://open-services.net/mailman/listinfo/oslc-core_open-services.net
