SourceForge : artf3077: (1748) Why not reuse WSDM ResourceID for AN

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

Artifact artf3077 : (1748) Why not reuse WSDM ResourceID for AN

Tracker:	Naming Comments by Frank
Title:	(1748) Why not reuse WSDM ResourceID for AN
Description:	explain why we cannot reuse WSDM ResourceID for the AbstractName element. Steve Loughran mentioned that recently, while other have asked the same in the past..
Submitted By:	Mark Morgan
Submitted On:	02/08/2006 11:08 AM EST
Last Modified:	07/18/2006 2:58 PM EDT
Closed:	07/18/2006 2:58 PM EDT

	Status / Comments		Change Log		Associations		Attachments

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

Comments

Andrew Grimshaw: 07/18/2006 2:58 PM EDT
	Comment:	This was discussed a long time ago - including with some of the WSDM guys. We did not want to cause an alergic reaction - which WSDM causes in some areas.
	Action:	Update Closed set to 07/18/2006 Status changed from Open to Closed

Andrew Grimshaw: 03/16/2006 3:09 PM EST

Comment:

This was discussed at great length, including with the WSDM folks. Clearly the two share an identical purpose. The fundemental problem was that using 
WSDM might be construed to be endorsing WSDM - which is much more than just the ResourceID. Many felt that chosing WSDM would alienate many. Therefore
 we choose not to. On the other hand, WSDM could chose to use  AN's in the future.

Action:

Update

Andrew Grimshaw: 03/16/2006 3:09 PM EST
	Action:	Update assigned_to changed from 100 to 126

Mark Morgan: 02/08/2006 11:08 AM EST
	Action:	Create

Return

< Previous

Next >