Re: fwd: Re: ideas about the decision interface

[barkley@sdct-sunsrv1.ncsl.nist.gov (John Barkley)]

<> My understanding is that the resource space is flat only from the point of
<> view of the interface. In reality, the resource space could have any
<> dimensionality. A relational database is an example. The Access Decision
<> Object (ADO) can be called with a Resource referring to a table and/or to a
<> column in that table.
<
<it's correct. The question is whether resource space should be structured (i.e.
<be not flat). There are pros and cons on either side. For example, since the
<RFP is healthcare specific and most of the resources in healthcare are
<patient-centric, I can see a lot of sense to explicitly have resource space
<structured so that patient ID, according to PIDS, can be obtained in a
<standard/specified way.

If I understand what you are saying, I think we have violent 
agreement. The fact that the interface only
knows about flat resources with at least the operations CREATE, READ, WRITE,
USE, and DELETE does not preclude an implementation from having resources
with dimensionality like a relational database. The implementation maps
dimensioned resources to flat for the interface but the interface client
may know that they are dimensioned.
 
jb
----------------
Broadcast message to hrac-rfp from barkley@sdct-sunsrv1.ncsl.nist.gov (John Barkley).
Go to http://cadse.cs.fiu.edu/omg/hrac-rfp to browse the mail list archive.