[oslc-core] Core WG topic: Attachments and non-RDF resources

[Nick Crossley]

I agree with Jim's comments, and I was surprised to see no mention of the 
attachment factory left in the revised discussion.  If a service does not 
permit free-standing attachment resources, but insists they be related to 
the parent resource, then use case #1 needs a slightly different approach:

The consumer knows the appropriate URI for an attachment factory (perhaps 
from the service description), or gets that URI form the parent resource
The consumer POSTs the attachment to the attachment factory - the 
attachment factory URI is specific to the parent resource, or is passed 
the parent resource URI as a query string
The attachment factory creates the attachment resource, creates the link 
from the parent to the attachment*, and returns the URI of the new 
attachment
The consumer adds any additional properties it desires for the attachment 
itself, or for the link between the parent and the attachment

* In the meeting, someone brought up the question of whether the link 
should really go from the parent to the attachment, or from the attachment 
to the parent.  We did not discuss this in detail, and the wiki page 
suggests only the former.

Nick.




From:   James Conallen/Philadelphia/IBM at IBMUS
To:     Dave <snoopdave at gmail.com>
Cc:     oslc-core <oslc-core at open-services.net>, 
oslc-core-bounces at open-services.net
Date:   02/03/2011 06:23 AM
Subject:        Re: [oslc-core] Core WG topic: Attachments and non-RDF 
resources
Sent by:        oslc-core-bounces at open-services.net



I think there are a couple of points related to attachment lifecycle that 
Nick had mentioned that are critical to the definition of an attachment 
that could be added to this document.

1. Attachments are deleted when the referencing resource is deleted. 
Attachments can be explicitly deleted without deleting the referencing 
resource.
2. Attachments should (must?) be owned an managed by the same provider 
that manages the resource that references it.

<jim/>

jim conallen
CAM Lead Architect, OSLC AM Lead
jconallen at us.ibm.com
Rational Software, IBM Software Group



Dave ---02/03/2011 08:19:05 AM---We had a good discussion of the topics of 
Attachments and Non-RDF Resources. I think that some were

From: Dave <snoopdave at gmail.com>
To: oslc-core <oslc-core at open-services.net>
Date: 02/03/2011 08:19 AM
Subject: Re: [oslc-core] Core WG topic: Attachments and non-RDF resources
Sent by: oslc-core-bounces at open-services.net



We had a good discussion of the topics of Attachments and Non-RDF
Resources. I think that some were confused because I was conflating
the two topics and covered many approaches, including an overly
complex one, but I think it was useful to discuss both topics
together.

To follow up, I have written a page that focuses on Attachments only.
Here's what I believe are the three important use cases for
attachments and a simple pattern for each:

  http://open-services.net/bin/view/Main/OslcCoreAttachments

I think we want all domains to handle attachments in a consistent way,
so perhaps we should work to create a guidance document? Other ideas?

As always, feedback is most welcome.

Thanks,
- Dave




On Tue, Feb 1, 2011 at 4:17 PM, Dave <snoopdave at gmail.com> wrote:
> At the Core WG meeting tomorrow, we'll be discussing how to handle
> Attachments and non-RDF Resources.
>   http://open-services.net/bin/view/Main/OslcCoreMeeting20110202
>
> I'll be using this presentation to explore various approaches:
>   
http://open-services.net/pub/Main/OslcCoreMeeting20110202/attachments.pdf
>
> Whether you can attend the meeting or not your feedback is most welcome.
>
> Thanks,
> Dave
>

_______________________________________________
Oslc-Core mailing list
Oslc-Core at open-services.net
http://open-services.net/mailman/listinfo/oslc-core_open-services.net
_______________________________________________
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/20110203/3707c7ce/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 105 bytes
Desc: not available
URL: <http://open-services.net/pipermail/oslc-core_open-services.net/attachments/20110203/3707c7ce/attachment.gif>