I’ve been thinking on how to integrate Fedora and Intralibrary with a Ruby + Dojo front end and with both repositories generating screeds of complicated XML, I knew XML wasn’t the way to go. I’m not a great fan of XML at the best of times and complicated XML, with multiple namespaces, is just a no-go for scripting languages and SAX. But this is where Java + XMLBeans excels, so I developed DRAKula, the Digital Repository Abstraction Kit, which is a set of modules that together make up a Java/Spring based REST facade for multiple digital repositories.
I’ve been working on a rails3 + dojo front end for a repository project and it’s been working fine on OS X. However, when I stuck it on linux and did bundle install this shit happens:
Installing nokogiri (188.8.131.52) with native extensions
error: ‘strdup’ undeclared (first use in this function) (more...)
When I built the SAML2  Web Browser SSO Profile into the Guanxi IdP and SP, I based the attribute release from the IdP on a specific profile. The X.500/LDAP Attribute Profile which looks like this:
However, there’s another profile out there. The SAML2 Basic Attribute Profile, which looks like this:
The word on the streets is the former is the one to use, even though it’s just bloatware. I mean, why have so much crammed in there when all you want is the name and value of the attribute? Why not just use the basic attribute profile? Turns out some SPs do use the basic attribute profile so I’m now adding support for this to the Guanxi IdP and SP.
 SAML2 Specifications
 SAML2 X.500/LDAP Attribute Profile [PDF]
 SAML2 Basic Attribute Profile [PDF]