RE: Naming Registry Roles

[Krishna Sankar <ksankar@cisco.com>]

Hi all,

	We had these roles defined in the document
http://www.ebxml.org/specs/secREG_print.pdf. As David points out, we could
also provide a "normal-human-being" translation to the ISOese.

cheers

  |-----Original Message-----
  |From: Breininger, Kathryn R [mailto:kathryn.r.breininger@boeing.com]
  |Sent: Tuesday, September 25, 2001 5:12 PM
  |To: 'David RR Webber - XMLGlobal'; Damodaran, Suresh
  |Cc: 'regrep@lists.oasis-open.org'
  |Subject: RE: Naming Registry Roles
  |
  |
  |Yes, let's use the terms from ISO 11179 where possible:
  |Submitting Organization instead of Publisher
  |Responsible Organization instead of Content Creator
  |Registration Authority instead of Registry Operator
  |
  |If we can use existing understood terminology, it will help us
  |communicate clearly with each other, and with others who are
  |familiar with the ISO 11179 standards.
  |
  |As far as the other terms go, as simple and as accurate as
  |possible seems best.
  |
  |
  |-----Original Message-----
  |From: David RR Webber - XMLGlobal [mailto:Gnosis_@compuserve.com]
  |Sent: Tuesday, September 25, 2001 4:58 PM
  |To: Damodaran, Suresh
  |Cc: 'regrep@lists.oasis-open.org'
  |Subject: re: Naming Registry Roles
  |
  |
  |Suresh,
  |
  |The problem is you seem to have four terms in some cases for the
  |same one thing?!?
  |
  |Reader, User, Guest, Client are all the same.  Publisher, Operator
  |and Administrator again same.
  |
  |Can we narrow this down here?
  |
  |Operator - operates the registry service.
  |Librarian - manages the content and approves changes.
  |Contributor - inserts and submits content and change requests.
  |Subscriber - uses content from the registry.
  |Owner - contributes and takes business responsibility for content,
  |  (may not be either a subscriber or contributor - may simply be
  |   an organization with a proxy contributor).
  |
  |We then also have security control around organization, groups
  |and user profiles.  You can belong to a group, organization, or
  |simply has a user profile.
  |
  |Also - contracts?  I do not want to get into these very murky
  |waters.  If some operator feels they need this - let them
  |pay a lawyer to do it.  Otherwise terms and conditions should
  |be standard internet practice and liability based - along the
  |lines of internet good business practices - no need for us to
  |re-invent these, plenty of good web sites for these already.
  |
  |Thanks, DW.
  |
  |======================================================
  |Message text written by "Damodaran, Suresh"
  |>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?
  |
  |<
  |
  |
  |----------------------------------------------------------------
  |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>
  |