| [higgins-dev] Notes from Higgins Dev Call October 19 at 12pm ET |
Attended -------- - TomD, MaryR, ValeryK, PaulT, BrianC, JimS, GerryB, MikeM, DaleO Note: See action items at the end IdAS ---- - we had discussion of latest changes to higgins.owl. these include adding metadata tags, making SubjectRelationship to being ako Attribute, making the DS's CUID a non-exceptional Attribute * Paul will add explicit domains to complexMetadata and simpleMetadata Open/closed class problem - Jim how are we going to solve the "open" vs. "closed" class problem? - Paul mentioned that we'd need OWL-FULL in order to solve this elegantly; so this is still unresolved Tom - generated ontologies are OWL-FULL not OWL-DL - this is because the LDAP schemas aren't consistent - Then again these are some of the kinds of problems IdAS is trying to solve - One of the failures of LDAP is that you have a common protocol but not a lot of common schemas Jim - we need something better than getSchema() returns something more structured than just a string - to an IdAS consumer, iterating through attributes, etc. Wouldn't it be better to have the option to fetch the schema in a standard way. - e.g. each DigitalSubject definition could be read, what are the required/optional attributes; you'd find the list of all possible. Valery - will commit such a schema interface today - Jim will update the javadoc and have a look at Valery's interfaces Dale - Higgins needs to have the mechanisms we're talking about to "make sense of the world as it is" - We will get broad concensus from the LDAP community on trying to address differences in schemas - 1) Higgins needs to its best to make sense of the world as it is (inconsistent schemas, etc.) - 2) And the identity schemas effort needs to make progress on schema interop, mapping Generic Registry Code --------------------- - there was a brief discussion of the need for a reusable "registry" library that these three could build from: 1) IdAS Registry 2) Token Service (STS) Token Provider Registry 3) I-Card Registry This needs to provide an abstraction over: 1) the eclipse plug-in registry 2) the java.security extension mechanism 3) ...any future platform issues A c t i o n I t e m s ----------------------- - Valery to commit his schema interface today - Jim, Tom to review - Paul to add domain declarations to complexMetadata and simpleMetadata - Valery is working on nightly build scripts, and new download page - Mary is working on getting legal approval for Jena libraries through Eclipse - Greg is still waiting for approval of his IdAS Registry
<<attachment: winmail.dat>>