[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Terminology]
See my comments on Carol's terminology suggestions inline:
> ==============================================
> First - can we define some consistent Terminology? When I talk about
> "client" of the HRAC, I was talking about the application or the
> infrastructure that called the HRAC. It was clear that some people on the
> call were thinking the client of the service that called the HRAC... so...
> ===
> Target:
> Let's borrow a term from Bob Blakley's picture and use the term "target" as
> the
> client of the HRAC. Agreed?
OMA uses two main player names "client" and "target object". I suggest to stick
to "target object" and use "target" as a short name for "target object." The
meaning is the same -- client of the HRAC.
> ====
> Access Decision Object (ADO):
> And Konstantin has been using ADO as shorthand for the "Access Decision
> Object"
> . Agreed?
Actually, John Barkley coined the term and I just began to use it. I want to
clarify that Access Decision Object is what the client invokes methods on and
the item which is called "access decision" on Bob's model.
Konstantin
----------------
Broadcast message to hrac-rfp from Konstantin Beznosov <beznosov@baptisthealth.net>.
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.