This is a static archive of the previous Open Grid Forum GridForge content management system saved from host forge.ogf.org file /sf/go/projects.ggf-editor/discussion.rec_ws_agreement_spec.agreement_name_optional at Sun, 06 Nov 2022 09:02:43 GMT SourceForge : Post

Project Home

Tracker

Documents

Tasks

Source Code

Discussions

File Releases

Wiki

Project Admin
Project: Editor     Discussion > REC: WS-Agreement spec > Agreement name optional > List of Posts
Forum Topic - Agreement name optional: (2 Items)
View:  as 
 
 
Agreement name optional
It is hard to see the justification for making the name of an Agreement optional.
An Agreement is in effect a contract between provider and consumer. Accounting, auditing and logging will be necessary 
for commercial and regulatory reasons.

Any service layer interaction between consumer and provider will be in the context of a specific agreement and there 
should be some unambiguous way of identifying which agreement is relevant.

The Name element would be an easy way to achieve this. An alternative would be to use some combination of information 
from the Context element which may make implementations more complicated than they need to be.
group response
Name's are not unique ids
  in any case, so we don't see how requiring the names helps.  The
  agreement can be named by its EPR in any event if a unique id is
  needed.  Some other contracts, e.g. mortgages, don't necessarily
  have a specific name on them.

 
 


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/projects.ggf-editor/discussion.rec_ws_agreement_spec.agreement_name_optional at Sun, 06 Nov 2022 09:02:43 GMT