RE: [hrac resources]

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

Juggy's examples illustrate exactly what I was trying to say, i.e., the 
structure of resources may be (typically is) different from the metadata 
structures.
 
Now, for the complication: What do you do when metadata really is content?
I would submit that Konstantin's #3 "accessor's relationship to
accessee" really is going to be content in either an accessor record,
an accessee's record, or some place else in the collection of resources. 
For example, Doctor Nick Riviera is Homer Simpson's
cardiologist. Somewhere in the resources of the information system, 
there is content that says that Doctor Nick has Homer as a patient and/or 
that Homer has Doctor Nick as a consulting physician.

Do you reproduce content which is needed for access decisions as metadata
somewhere else? I should think probably not. Keeping a list of attending
physicians and/or list of patients as metadata redundant to content
has lots of problems.

What you likely have to do is to have an access control system that
is able to access content as security metadata.

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.