Just got a note from Jason that SecPAL 1.1 is available – this is great – take a look at the codeplex site for more details – Jason/Blair and team, you’re doing great things…let’s see if the community recognize what you’ve been up to…
SecPAL v1.1 is a minor release of SecPAL that maintains compability with our first reasearch release of SecPAL. Changes for v1.1 include:
New / Upgraded Features
- We have updated the SecPAL grammar to a new and much more readable grammar. I will post a longer explanation in the coming weeks, but in short when you read a SecPAL policy conditions will now be prefaced by an “IF” statement, and constriaints will now be prefaced by a “WHERE” statement. These changes along with improved readibility of fact qualifiers should make the English representation of your policies / assertions much simpler to read. Note: This change should have no impact on existing policies, as it only affects the output of policies / tokens when you call .ToString() on them.
- The ‘CanActAs’ predicate can now be used as a conditional fact within an assertion.
- No breaking changes were made to API’s so any SecPAL dependent code that you have written should behave the same.
Just a quick note to let everyone know that we have just released a minor update to our SecPAL library. In addition to a couple of minor bug fixes there are two features which I think you are really going to like. The first is an update to our grammar – making it much clearer what conditions and constraints are. The second (which was actually a bug fix) is that our graphical proof graphs now work.
Cross Posted from Dan Fay’s Blog (http://blogs.msdn.com/dan_fay)