SourceForge : artf2717: (932) Model for derived data services

Project: DAIS-WG Trackers > WS-DAI Issues > View Artifact

Artifact artf2717 : (932) Model for derived data services

Tracker:	WS-DAI Issues
Title:	(932) Model for derived data services
Description:	The model of derived services presented does not map consistently for all types of data resources E.g. you may create an empty file and the add data to it but you create a new database table and interact with the database to insert data This feels ok but we need a clear way of documenting expected use patterns. We need a new primer. .
Submitted By:	Simon Laws
Submitted On:	06/22/2004 4:28 AM EST
Last Modified:	08/25/2004 8:33 AM EST
Closed:	08/25/2004 8:33 AM EST

	Status / Comments		Change Log		Associations		Attachments

Status
Group: *
Status:*	Closed
Category: *
Customer: *
Priority: *	2
Assigned To: *	Simon Laws
Reported in Release: *
Fixed in Release: *
Estimated Hours: *	0
Actual Hours: *	0

Comments

Simon Laws: 08/25/2004 8:33 AM EST
	Comment:	Added comments to base spec for GGF12 pointing out that while the model is useful we recognise that it is not universally and consistently applicable.
	Action:	Update

Simon Laws: 08/25/2004 8:33 AM EST
	Action:	Update artifact_status changed from Open to Closed close_date changed from - to 2004-08-25 14:33:41

Norman Paton: 07/26/2004 5:21 PM EST

Comment:

This doesn't seem to be expressed quite precisely enough to make explicit the claim.  Is the claim:

(1) that there are things in the current realisations that seem inconstent, such as the use of fine-grained collection management interfaces in WS-
DAIX as against the use of a single language-based operation in WS-DAIR; or
 
(ii) the fact that different kinds of resource implement interfaces that seem different in nature (e.g. to stick with examples in the spec, that 
SQLAccess is not like RowSetAccess).

If (i), then I suspect we have no choice, as this directly reflects the varying capabilities of the underlying resource languages. If (ii) the only 
question is whether more common behavioral patterns should be pulled into the WS-DAI specification.  That may be worth wider consideration, but people
 haven't been coming forward with such patterns that I remember, so our  broad access patterns have been stable for a long time.

Action:

Update

Simon Laws: 06/22/2004 4:28 AM EST
	Action:	Create

Return

< Previous

Next >