SourceForge : artf3068: (1809) add optional "Unambiguous Web Service Endpoint Profile" and/or "Web Service Endpoint Address Identif

Project: OGSA-NAMING-WG Trackers > Naming Comments by Frank > View Artifact

Artifact artf3068 : (1809) add optional "Unambiguous Web Service Endpoint Profile" and/or "Web Service Endpoint Address Identif

Tracker:	Naming Comments by Frank
Title:	(1809) add optional "Unambiguous Web Service Endpoint Profile" and/or "Web Service Endpoint Address Identif
Description:	Comment from Frank by email (28 April 2006) ------------------------------------------------------ add optional "Unambiguous Web Service Endpoint Profile" and/or "Web Service Endpoint Address Identifier Profile" label to meta-data section of an EPR Description: To help the EPR consumer's processing logic, the minter or any intermediate with enough knowledge about the EPR usage can add a (optional) profile label to the EPR..
Submitted By:	Mark Morgan
Submitted On:	05/01/2006 3:09 PM EDT
Last Modified:	10/02/2006 12:10 PM EDT
Closed:	10/02/2006 12:10 PM EDT

	Status / Comments		Change Log		Associations		Attachments

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

Comments

Andrew Grimshaw: 10/02/2006 12:11 PM EDT
	Comment:	Don't have to do this because it is already handled by WS-Addressing.
	Action:	Update Closed set to 10/02/2006 Status changed from Open to Closed

David Snelling: 09/15/2006 10:05 AM EDT

Comment:

We have defined the performance claims in the document. These could be included in the potyType element of the service description. This is the normal
/expected place to put this information.

WRT the metadata extensibility, WS-Addressing states:

This is an extensibility mechanism to allow additional attributes to be specified. Some examples in this specification show use of this extensibility 
point to include a wsdlLocation[WSDL 2.0 Core Language] attribute to provide a hint for the location of a WSDL description of the service deployed at 
the endpoint.

These two aspects together provide a recommended approach for making this information available to the client. Therefore, we already have this 
functionality and can close this tracker with no action. Note however, that obtaining this information requires a second roundtrip if the client does 
not already have the WSDL.

Action:

Update
Priority changed from 0 to 2

Mark Morgan: 05/01/2006 3:09 PM EDT
	Action:	Create

Return

< Previous

Next >