Thanks to all who attended the webcast on ArisID this morning!  It’s always great to talk about this stuff and share ideas!

A copy of the presentation can be obtained here.

Also, as promised, here is a video of the Sonic Records ArisID demonstration.  You can view it online here.  Or, you can download the full-size video here (24MB).

Phil

Re-post from independentIdentity.blogspot.com…

From Liberty Alliance:

ArisID, the first open source software implementing Liberty Identity Governance Framework (IGF) components, provides enterprise developers and system architects with a library for building enterprise-grade identity-enabled applications using multiple identity protocols, and lays the groundwork for allowing enterprises to manage and audit the identity requirements of business applications based on declarative IGF policy specifications. This webcast will provide participants with an overview of the ArisID API, discuss benefits for developers and enterprises, and review the project roadmap. Developers will understand how to begin using ArisID to build IGF-based applications and the identity community and vendors will gain insight into how the open source ArisID API and information providers help fulfill multi-protocol identity management requirements.

Registration

For those of you who have been following my blog, you’ll know I have been talking for sometime about IGF and the need for a declarative identity API in order to making identity services more relevant to developers. Here’s your chance to see more about what I’ve been talking about all this time.

Phil

The meeting was held on Wednesday 23-May-07 in a very nice conference facility in the same Georgetown University building that houses Chad’s office. We got started at 10:00AM.

We covered a lot of ground. Topics included OpenID bootstrap, OpenSAML XML Tooling, Conor Cahill’s ID-WSF client, and code generation. It was maintained that the SAML bootstrap is top and first priority, but that the requirements for OpenID bootstrapping would be very much the same as far as the ID-WSF Client is concerned.

XML TOOLING NOTE

OpenSAML’s XML Tooling creates a complete object graph based on the element structure of the XML. Unmarshalling and Marshalling are used to go from DOM based XML to Java Objects and back. The design technique that is used by OpenSAML is to break down every single element into a set of classes/objects that handle the various details of each. This can get extremely detailed. Take this XML:

<house>
  <floors>
    <floor name=”basement”>
      <room squarefeet=”40″ doors=”" windows=”" type=”bathroom” />
      <room squarefeet=”120″ doors=”" windows=”" type=”closet” />
    </floor>
    <floor name=”first floor”>
      <room squarefeet=”40″ doors=”" windows=”" type=”bathroom” />
      <room squarefeet=”120″ doors=”" windows=”" type=”kitchen” />
    </floor>
  </floors>
</house>

The code above would be supported by 5 classes for each of the following elements: house, floors, floor, and room. For example, you might take “House” and create:

HouseXMLObject.java (The object created for the element “house”)
HouseXMLObjectBuilder.java (builds the XMLObject)
HouseXMLObjectValidator.java (any validation done here)
HouseXMLObjectUnmarshaller.java (DOM element “house” to java object)
HouseXMLObjectMarshaller.java (facilitates java object to DOM element)

Each of these is registered in a config document which will identify the role that each class plays to the underlying xml tooling engine. One concern the development group had was that this level of detail might not be great for performance. Chad agreed that we might look into not building classes for some subelements.

The full notes are posted here on the wiki:
May 23rd Washington Face to Face Notes

Riggs National Bank, Georgetown
by techrose

As anyone on the developer list already knows we’re planning a face to face meeting in Georgetown this Wednesday the 23rd. We’ll be meeting at 10am and ending around 4pm. I will post an update to the list soon with any more info that I have.

Thanks to Chad we have an excellent meeting room:

Room 2005 (Second floor in Suite 2000), 3300 Whitehaven St., NW, Washington, DC 20007

Chad says: “If you’re taking a cab from somewhere be sure to mention the Northwest part of the 3300 Whitehaven St. or you’ll end up on the other side of the navy observatory. If you’re coming in via train or plane you might consider taking the metro to Dupont and taking a cab from there (it’s cheaper).”

Lunch will be catered, coffee and snacks will be available all day.

Contact me with any questions: asa dot openliberty (at) zenn dot net