Naming Registry Roles

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

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>