> > Is the policy manager service used for anything 
> > other than
> > bootstrap (and unit tests :)?  (or intended to be?) 
> 
> used for - no (apart from the tests!).  intended to be - it was in Muradora,
> it's an open question as to the form of a policy management API

I see.  I think this is not really in scope for this issue, but I'm just
trying to see how this policy manager service fits into the big picture
in relation to this task.  Do we see "policies as fedora objects" as an
end or a means?  Externally, are the policy manager and future API to be
the primary focal point of policy management (and representation as
fedora objects is merely one implementation), or are policies as fedora
objects the primary focal point, with APIs and managers performing a
supporting role for manipulating the ultimately-canonical objects?   I
think my questions have been motivated by the prospect of the latter.

> I'd suggest they shouldn't be in a "fedora-system" namespace unless they are
> non-editable and somehow essential to make Fedora "work".  Are the objects
> that are currently in the fedora-system namespace editable?

Actually, yes, they are editable ... but there is also a fair bit of
hard-coded functionality that isn't!  To confuse things even more,
consider the policies that are in the "hands off" fedora-internal-use
directory.  I'm not sure which makes most sense, but I just wanted to
make note that this could be a potential point of confusion.  
To me, if policy objects are a means, I see the namespace choice as
unimportant.  If policy objects are an end, I would tend to favor
'fedora-system'.  That's just my (not very strong) opinion right now.


> I think there's a difference here between deprecating and not yet
> implemented within FeSL ;o)

Ahh, OK.  I did not know object-level policies were not implemented.  To
be honest, I've never really had to use this functionality myself.

> A question here is whether to (continue to) standardise on a datastream
> called POLICY for XACML policies, whether within existing "data" objects or
> in stand-alone policy objects, or to make that more flexible.

There may be other options too (format URI, RELS-INT, something in
extended content models), but I don't know if anything is any better
than the proposed solution.

  -Aaron


------------------------------------------------------------------------------
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
_______________________________________________
Fedora-commons-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers

Reply via email to