SourceForge : artf2647: (1112) Should multiple mappings be allowed

Project: DAIS-WG Trackers > WS-DAIR issues > View Artifact

Artifact artf2647 : (1112) Should multiple mappings be allowed

Tracker:	WS-DAIR issues
Title:	(1112) Should multiple mappings be allowed
Description:	There should only be one canonical mapping else inter-operation goes out the window and there's not much point in having a spec. If we must have multiple mappings then we must be very careful and have requirements. Either way the section as it stands, I feel, is too vague for a spec. Page 3 Section 1.2 Specification Organisation Paragraph 1.
Submitted By:	Brian Collins
Submitted On:	09/17/2004 7:45 AM EST
Last Modified:	10/14/2004 6:21 AM EST
Closed:	10/14/2004 6:21 AM EST

	Status / Comments		Change Log		Associations		Attachments

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

Comments

Brian Collins: 10/14/2004 6:21 AM EST
	Action:	Update artifact_status changed from Open to Closed close_date changed from - to 2004-10-14 12:21:56

Brian Collins: 10/14/2004 5:55 AM EST

Comment:

The specification and the mapping are deliberately separate and the spec must allow for more than one mapping. However the text did intimate that "
many different" mappings would be the norm so I've changed "This approach allows functions to be mapped to WSDL in many different ways" to "This 
approach allows functions to be mapped to WSDL in more than one way". Hopefully, that tones down the implied proliferation of mappings.

Action:

Update

Brian Collins: 09/17/2004 7:45 AM EST
	Action:	Create

Return

< Previous

Next >