RE: Naming Registry Roles

["Damodaran, Suresh" <Suresh_Damodaran@stercomm.com>]

Thanks for the wonderful comments.
Below is my response, I apologize for not responding to
individual comments - I have been swamped recently.

1. ISO 11179: 
 There are at least 3 terms (Submitting Organization, 
Responsible Organization, and Registration Authority)
that have direct mapping. As per Registry Design Objectives (Sec 4.1, RIM)
leveraging ISO 11179 is a design goal. However, we need to temper
this with the need to communicate to registry developers at large.
I leave it up to the TC to give "first class"
status to these terms by vote or consensus. Meanwhile,
we could use the terms in my mail (or variations thereof),
and provide mappings to ISO 11179.

2. Roles not identities: Actors fulfill roles, and two roles
may map to the same identity when deployed. For example, Registry Operator
and 
Administrator could be the same identity, though have
different roles (granted we may disagree on the "distinction" in the roles -
but that is something we can work out). The actors came up
based on security analysis. An earlier work, as Krishna pointed
out, had some of these roles (those are in RS Sec 9.4.1), but
we are further refining those roles and adding new ones.

3. I am working on some changes to the actors below, and will post
as soon as we are done reviewing in the security sub team.

Thanks again,

-Suresh

-----Original Message-----
From: Damodaran, Suresh 
Sent: Tuesday, September 25, 2001 9:33 AM
To: 'regrep@lists.oasis-open.org'
Subject: Naming Registry Roles



Oops... 
-----Original Message-----
From: Damodaran, Suresh 
Sent: Tuesday, September 25, 2001 9:19 AM
To: 'regrep@lists-oasis.open.org'
Cc: 'regrep-security@lists.oasis-open.org'
Subject: Naming Registry Roles



In the course of the security work, we have come to define certain
actors in the Registry ecosystem. Here are the actors, what I think
is the best mapping of some of these actors to ISO/IEC 11179 (in
parenthesis).
Please let me know of problems/comments on these actors.

Registry Publisher (Submitting Organization) - Does life cycle operations on
the RegistryObject
Registry Reader (?) - Reads Registry Object
Registered User - Has a contract with Registry Operator.
Registry Guest - is a Registry Reader but has no contract with Registry
Operator
Registry Client - Either Registered User or Registry Guest
Registry Content Creator (Responsible Organization) - Creates
RegistryObjects

Registry Operator (Registration Authority) - Entity that hosts
RegistryObjects
Registry Administrator - Evaluates and enforces registry security policy.
Facilitates definition
of the security policy

Relationships among actors:
Registry Publisher is always a Registered User.
Registry Reader is either a Registered User or Registry Guest
Registry Client is either a Registered User or Registry Guest.

Question: Should we adopt ISO 11179 terms where they apply above?

Thanks,
-Suresh


-----------------------------------------------------www.stercomm.com-------
------------------------------------------------------
Suresh Damodaran, Ph.D.					Sterling Commerce, a
SBC Company
Senior Software Architect					750 W. John
Carpenter Freeway
469-524-2676 (O) 						Irving, TX
75039-2505
								


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>