<?xml version="1.0" encoding="UTF-8"?><!-- generator="lyceum/0.34" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Collections considered &#8230;</title>
	<link>http://blogs.library.uq.edu.au/ms/2007/10/18/collections-considered/</link>
	<description>Library Systems Programmer</description>
	<pubDate>Mon, 23 Nov 2009 03:55:01 +0000</pubDate>
	<generator>http://lyceum.ibiblio.org/?v=0.34</generator>

	<item>
		<title>by: Christiaan Kortekaas</title>
		<link>http://blogs.library.uq.edu.au/ms/2007/10/18/collections-considered/#comment-942</link>
		<pubDate>Thu, 18 Oct 2007 07:13:33 +0000</pubDate>
		<guid>http://blogs.library.uq.edu.au/ms/2007/10/18/collections-considered/#comment-942</guid>
					<description>I think you have a good idea here Matt, but would this work work with transitive searching? Eg keeping the current option to do hierarchical auth rulesets by RELS-EXT isMemberOf. Or would this be redundant with a grand auth table view of the repository. Perhaps you could sketch up a mock of what the interface would look like. 

Take some inspiration from the Muradora policy setting tool - though I like your idea of setting the policies by search better in a way. Perhaps the auth groups could be like search keys themselves. Lots of possibilities here but the simplest will probably be the most elegant. 

I know Chi from Muradora is fairly against auth based on searches (virtual collections), though this could be due to limitations of XACML and the XACML implementation.</description>
		<content:encoded><![CDATA[<p>I think you have a good idea here Matt, but would this work work with transitive searching? Eg keeping the current option to do hierarchical auth rulesets by RELS-EXT isMemberOf. Or would this be redundant with a grand auth table view of the repository. Perhaps you could sketch up a mock of what the interface would look like. </p>
<p>Take some inspiration from the Muradora policy setting tool &#8211; though I like your idea of setting the policies by search better in a way. Perhaps the auth groups could be like search keys themselves. Lots of possibilities here but the simplest will probably be the most elegant. </p>
<p>I know Chi from Muradora is fairly against auth based on searches (virtual collections), though this could be due to limitations of XACML and the XACML implementation.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
