The use case is Producer control over
the data. First level is to just encrypt the data before sending it to
the Consumer. There are cases (financial, privacy and national security
reasons rise to mind) where the most one wants to do is hand out a reference
and then require the importing Producer to come get the data via proprietary
means as this also allows for validating the new Producer. Because the
reference wants to refer to the current customizations (they can continue
to change), a snapshot is required and therefore one ends up with the question
of how long the exporting Producer should keep this snapshot. Explicit
removal and leasing come to mind as possible solutions, but we haven't
discussed the whole area yet.
Rich
"Coco, Christopher"
<>
09/15/2004 02:48 PM
To
Rich Thompson/Watson/IBM@IBMUS,
<>
cc
Subject
RE: [wsrp-interfaces] Groups
- Import_Export2.html uploaded
What is the use case for
allowing the Producer to merely export a reference to a snapshot of the
customization data?
Christopher
-----Original Message-----
From: Rich Thompson [mailto:]
Sent: Wednesday, September 15, 2004 11:34 AM
To:
Subject: RE: [wsrp-interfaces] Groups - Import_Export2.html uploaded
Once one allows for a Producer merely exporting a reference to a snapshot
of the customization data, then one must also account for how does a Producer
know when it can throw away that snapshot. Andre is reminding us that there
does need to be a way for the Consumer to provide that notification to
the exporting Producer in a verifiable manner.
Rich
"Coco, Christopher"
<>
09/15/2004 01:32 PM
To
<>
cc
Subject
RE: [wsrp-interfaces] Groups
- Import_Export2.html uploaded
Could you explain a little more? I don't understand what you mean when
you say the "data a Producer is holding onto that it did not ship
on "export" in expectation of (further) imports". And which
Producer is the Consumer signaling this to? The "export" Producer
or the "import" Producer?
Christopher
-----Original Message-----
From: Andre Kramer [mailto:]
Sent: Wednesday, September 15, 2004 10:24 AM
To: '';
Subject: RE: [wsrp-interfaces] Groups - Import_Export2.html uploaded
One issue we did not get around to discussing is the need
for a 3rd operation to allow the consumer to signal that no more "imports"
will be attempted from the results of an "export". This would
allow the producer to garbage collect any data it did not ship on "export"
and may still be holding in the expectation of (further) imports.
Regards,
Andre
-----Original Message-----
From: [mailto:]
Sent: 15 September 2004 00:17
To:
Subject: [wsrp-interfaces] Groups - Import_Export2.html uploaded
The document revision Import_Export2.html has been submitted
by Michael Freedman () to the WSRP Interfaces
SC document repository.
This document is revision #3 of Import_Export.html.
Document Description:
Download Document:
http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/download.php/9182/Import_Export2.html
View Document Details:
http://www.oasis-open.org/apps/org/workgroup/wsrp-interfaces/document.php?document_id=9182
Revision:
This document is revision #3 of Import_Export.html. The document
details page referenced above will show the complete revision history
PLEASE NOTE: If the above links do not work for you,
your email application
may be breaking the link into two pieces. You may be able to copy
and paste
the entire link address into the address field of your web browser.
