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 [email protected] Rational Software, IBM Software Group From: Dave <[email protected]> To: oslc-core <[email protected]> Date: 02/03/2011 08:19 AM Subject: Re: [oslc-core] Core WG topic: Attachments and non-RDF resources Sent by: [email protected] 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 <[email protected]> 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 [email protected] http://open-services.net/mailman/listinfo/oslc-core_open-services.net
