Re: [oslc-core] Deprecating LocalResource: effect on POST requests

[Martin P Pain <martinpain@uk.ibm.com>]

But the server doesn't require the
resource to be a blank node ("LocalResource"), right? So "AnyResource"
(either URI or blank node) in the shape/table would work? (That is, AnyResource
would allow the client to choose, and the servers have to support both).
The case that would cause a problem is if the server doesn't support both,
but only supports blank nodes.

Having said that, it's not a problem
- domain specs can still use LocalResource if they really need to. While
we decided to deprecate LocalResource, we only said we would actively change
the Core shapes/tables.And the Core resources don't have ones that are
usually created via POST.

(Btw, I don't think "Either Reference
or LocalResource" makes sense - Reference is an oslc:representation
value, meaning "not inlined", and LocalResource is an oslc:valueType
value, meaning it must be a blank node [must not have a URI],
and therefore it also must be inlined. It sounds to me that the intention
is oslc:valueType of oslc:AnyResource [either blank node or resource with
URI] and oslc:representation of oslc:Either [either just the URI, or inlined].)

Martin Pain
Software Developer - Green Hat
Rational Test Virtualization Server, Rational Test Control Panel

E-mail: martinpain@uk.ibm.com Find me on:  and within IBM on:

IBM United Kingdom Limited Registered in
England and Wales with number 741598 Registered office: PO Box 41, North
Harbour, Portsmouth, Hants. PO6 3AU 



From:      
 Ian Green1/UK/IBM@IBMGB
To:      
 Martin P Pain/UK/IBM@IBMGB
Cc:      
 OASIS (oslc-core@lists.oasis-open.org)
<oslc-core@lists.oasis-open.org>
Date:      
 02/10/2015 13:10
Subject:    
   Re: [oslc-core]
Deprecating LocalResource: effect on POST requests
Sent by:    
   <oslc-core@lists.oasis-open.org>

---

Hi Martin 
I've not been following this thread, but the RM v2.0 spec declares creator
and contributor as "Either Reference or LocalResource". (I would
guess that the other domain specs would be the same for these two properties.)
 So the server needs to deal with the "LocalResource" case.

best wishes,
   -ian

ian.green@uk.ibm.com (Ian Green1/UK/IBM@IBMGB)
IBM 

<oslc-core@lists.oasis-open.org> wrote on 02/10/2015 07:57:47:

> From: Martin P Pain/UK/IBM@IBMGB 
> To: OASIS (oslc-core@lists.oasis-open.org) <oslc-core@lists.oasis-open.org>
> Date: 02/10/2015 07:57 
> Subject: [oslc-core] Deprecating LocalResource: effect on POST requests
> Sent by: <oslc-core@lists.oasis-open.org>
> 
> Do we know if any of the OSLC domains have domain resource types 
> that contain properties defined as "LocalResource" in v2?
> 
> If so, then creating them (at v2) involves POSTing a resource/
> representation containing blank nodes. Previously I've mostly been
> considering resource shape sin the context of GETs. I don't know how
> servers are likely to respond if they get an inlined resource that
> has a URI set. 
> 
> However, if no domains have this problem, then hopefully it's not
a problem...
> 

> 
> Martin Pain
> Software Developer - Green Hat
> Rational Test Virtualization Server, Rational Test Control Panel
> 
> E-mail: martinpain@uk.ibm.com
> Find me on: [image removed]  and within IBM on: [image removed]
  
> 
> [image removed] 
> 
> 
> 
> 
> IBM United Kingdom Limited Registered in England and Wales with 
> number 741598 Registered office: PO Box 41, North Harbour, 
> Portsmouth, Hants. PO6 3AU 
> Unless stated otherwise above:
> IBM United Kingdom Limited - Registered in England and Wales with
> number 741598. 
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire
PO6 3AU
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598. 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU