This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf3076?nav=1 at Sun, 06 Nov 2022 07:05:58 GMT SourceForge : artf3076: (1749) Split WS-Naming into three specs

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Search Tracker
Project: OGSA-NAMING-WG     Trackers > Naming Comments by Frank > View Artifact
Artifact artf3076 : (1749) Split WS-Naming into three specs
Tracker: Naming Comments by Frank
Title: (1749) Split WS-Naming into three specs
Description:
Personally, I would actually prefer to have three different specs for:

* the unique Address+RefParameter profile and recipe
* AbstractName definition
* EprResolver Service and RenewableReference

All these specs would be useful by itself: the first spec shows when we 
can use the Address+RefParams as an identifier/name, which could be used 
for policy/audit and EPR-resolution. The second one relies on the first 
and gives you the ability to define a more stable name and bind it 
through EPR-embedding - again useful for policy/audit/resolution. 
Finally, the last one specifies services and interface for 
EPR-resolution through two standard patterns.
.
Submitted By: Mark Morgan
Submitted On: 02/08/2006 11:08 AM EST
Last Modified: 07/18/2006 2:59 PM EDT
Closed: 07/18/2006 2:59 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:59 PM EDT
  Comment:
No.
  Action: Update
Closed set to 07/18/2006
Status changed from Open to Closed
Andrew Grimshaw: 03/17/2006 8:06 AM EST
  Action: Update
assigned_to changed from 100 to 126
Andrew Grimshaw: 03/17/2006 8:06 AM EST
  Comment:
I respect Frank's comment - but to me they all make sense together - they define a naming and binding protocol for Web Services that support a range 
of use cases. Together they follow a long established (in distributed systems) means of identification, addressing, and binding entities (I chose that
 word to avoid debate on the "type" of endpoint).

Further, each of the spec's would then be about a paragraph ... plus boiler plate and explanations - making the signal to noise ration in the spec's 
pretty high.
  Action: Update
Mark Morgan: 02/08/2006 11:08 AM EST
  Action: Create


 
 
 
< Previous
 
 
Next >
 


The Open Grid Forum Contact Webmaster | Report a problem | GridForge Help
This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/artf3076?nav=1 at Sun, 06 Nov 2022 07:06:02 GMT