Following on from Aaron's question (and speaking for myself, not having
consulted others in the Hydra team)...
I think local installations should be able to specify their own
namespaces, even for specialised objects. The Hydra Project will be
providing sample content models, sDefs and sDeps with a specified
namespace (simply to identify them as being Hydra-provided) but local
installations will be able to add others of their own design (or
effectively rename ours, if they wish, we would not wish to mandate...).
I think each institution should be able to specify their own
namespace(s) for anything that is not essential Fedora core so that it
is easy to distinguish (for instance) core, contributed and local. I
can quite see the possibility of Hydra wanting to provide sample
policies down the line called 'hydra-policy:xxxxxx' in the same way that
we currently have 'hydra-cModel:xxxx', hydra-sDef:xxxxx' etc).
___________________________________________________________________
Richard Green
Consultant to the University of Hull IT Systems Group
managing the CLIF and Hydra (Hull) Projects
http://edocs.hull.ac.uk
http://www.hull.ac.uk/clif
https://fedora-commons.org/confluence/display/hydra
-----Original Message-----
From: Aaron Birkland [mailto:[email protected]]
Sent: 11 February 2010 6:41 PM
To: Steve Bayliss
Cc: [email protected]
Subject: Re: [Fedora-commons-developers] FeSL: Make XACML policies
first-class Fedora digital objects (FCREPO-577)
> 1) XACML policies will be stored as Fedora Objects with a specified
content
> model and PID namespace
I am curious - what is the motivation for specifying a PID namespace
dedicated to policies? We don't use special namespacaces
differentiating SDeps, SDefs, or CModels - cmodels are sufficient for
that. We have used a specific namespace such as 'fedora-system' in the
past to denote core objects (such as the foundational CModels) that are
introduced into the repository upon bootstrap. I think that convention
would also be a valid approach for policies, unless I am missing
something. I am worried that prescribing a single namespace for all
policies might be unnecessarily restrictive.
> config-pdm-fedora.xml (new file):
> - content model for Policy objects
> - datastream identifier for XACML policy datastreams (POLICY)
> - PID namespace for policy objects (policy:)
Regarding the datastream identifier for XACML policies - does that refer
to 'local' policies that are specified at the object level (e.g. the
presence of a datastream matching the configured value (e.g. POLICY) in
any object means that the policy therein applies to that specific
object)
-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
*****************************************************************************************
To view the terms under which this email is distributed, please go to
http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************
------------------------------------------------------------------------------
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
