[oslc-core] Proposal for Core issue 17: Handling of long URIs

[John Arwe]

I think for the moment I will let this mold a bit.  We are having
notionally similar discussions in the W3C Linked Data Platform working
group which has a wider audience, and I want to see what new info that
draws out.  We can re-visit the week of June 26 after the next W3C F2F
where many of these issues should be discussed.

wrt 1: 415 response would be the most direct; completely open to mentioning
that in the draft; always a fine line between repeating what readers (in
theory) already know being pedantic vs useful.

wrt 2: I think LDP containers will have the same needs.  I did
intentionally make it a MUST to gauge the WG, since most people treat
SHOULD like MAY anyhow and few people object to weakening normative text
later.




Best Regards, John

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




From:	Steve K Speicher/Raleigh/IBM
To:	John Arwe/Poughkeepsie/IBM at IBMUS,
Cc:	oslc-core at open-services.net
Date:	05/22/2013 10:01 AM
Subject:	Re: [oslc-core] Proposal for Core issue 17: Handling of long
            URIs


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" <oslc-core-bounces at open-services.net> wrote on 05/21/2013
07:09:07 AM:

> From: John Arwe/Poughkeepsie/IBM at IBMUS
> To: oslc-core at open-services.net
> Date: 05/21/2013 07:09 AM
> Subject: [oslc-core] Proposal for Core issue 17: Handling of long URIs
> Sent by: "Oslc-Core" <oslc-core-bounces at open-services.net>
>
> 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
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20130610/86530735/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: graycol.gif
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20130610/86530735/attachment.gif>