Skip to main content
Jump to: navigation, search

Difference between revisions of "IdAS ToDo"

Line 18: Line 18:
| Implement [ ISingleValuedProperty] || 3 || 0.9 || || done
| Implement [ ISingleValuedProperty] || 3 || 0.9 || || done
| Build toolkit classes to assist CP writers || 5 || || ||
| Build toolkit classes to assist CP writers || 5 || 0.9 || || done
| Switch static Strings to static URIs where appropriate || 1 ||  || ||
| Switch static Strings to static URIs where appropriate || 1 ||  || ||

Revision as of 12:39, 24 May 2007

Also see bug list

Work Item Days Est. Milestone Bug(s) Status
Update main wiki page 2 0.8 done
Revert to Java 1.4 3 0.8 171293 done
Versioning on jar name 1 0.8 done
Update operation refactoring. See IdAS Update Proposals 8 0.8 167978 163428 163429 171290 171296 171297 done
Metadata: a) can put on attr vals and complex sub vals in OWL. when a complex val comes from somewhere else -- can't attach metadata to sub-elements. can't put on attr in OWL -- need to figure out how to do this as other systems can do it. b) Do we need metadata on IContext? It could be used to represent supported features. Need applyUpdates to context. Consider moving applyUpdates to IContext. c) Do we need metadata on model interfaces? We already have it in the owl at the outer layer (imported ontologies, last modified time, versionInfo, priorVersion, incompatibleWith,...). Other things (comment, display name, etc). Do we add these as metadata or as getters? 10 0.9 done
Re-package IdAS: A) API. Interfaces for Consumers only. B) SPI. Interfaces for CP writers (IContextFactory) C) Service (Registry, cross-context processes). D) Common (auth materials). E) Toolkit (common code for CP writers) 4 0.9 done
Implement ISingleValuedProperty 3 0.9 done
Build toolkit classes to assist CP writers 5 0.9 done
Switch static Strings to static URIs where appropriate 1
Registry refactoring See IdAS Registries Proposal 2B, IdAS Registries Proposal (obsolete), and IdAS Registry and Configuration (obsolete) 10 0.9 175630 163366
Context pooling (possibly needed for performance reasons) 10
Define Description Language for IdAS 5
Invent string format for IFilter 4 171328
Change to use JAAS-like callback. Get rid of 'getOpenPolicy' (subsumed by callback handlers and interactions) 6 164048
Put matching rules in Model (Schema) 4
Metadata refactoring: Allow subsets of metadata to be fetched. ( Does IHasMetadata.createMetadata also effectively call addMetadata? 3
API Extensibility. Consider using a Controls-like model
Alignment with IGF 15
Define IdAS interfaces for C++ 8
Define IdAS interfaces for C# 8
Implement IdAS interfaces for C++ 13
Implement IdAS interfaces for C# 13
Schema: Add method(s) which return the schema as a stream, DOM document, or other iterable object. ( 3 160412
Allow filters in other methods 2
IContext.verifySubjectAttributes doesn't leave a way to verify that a DS representing a group contains a specific member in its member value. 3
IContext::getSubjectSchema(), IContext::setSubjectSchema() 4 171295
Collisions: Determine what to do when importing data and collisions occur. Does import override, add to , or error when a DS exists? ( 171298
Document the special "uniqueIdentifier" attribute 1 171300
Does export/import only export/import Digital Subjects, or the entire Context (Metadata, Schema, DS, Relationships)? ( 1 171301
Export/Import Filter Format: Define the format ( 4 171301
Export/Import data representation format. Document what this would look like and how, given the string one could understand what the format is. Is there a registry? ( 5 171301
Relationships refactoring. How are two compared for equality? Does IHasRelationships.createRelationship also add? 4 171304
Need guidance on schema for groups (should they use subjectRelationship?) need a way to start building out higgins schema profiles
Need guidance on how to do Dynamic Groups
Password updates: Need extra info (challenge). Attributes need expire, reset, validation policy
Support for asynch operations. A way to poll (ticket) or be notified of done.
Ability to set state of subjects (suspended, active, etc)
Access Control and Audit
Need a way to ask IdAS for a context which can do X, Y, and Z rather than making people enumerate contexts, look at supported schema, supported service levels, etc.
In asking for a context, would like to be able to cause multiple candidates to be joined into one, also if no candidates exist, but by combining two one could be virtualized -- do that.
Web Services access: need wsdl. need idas client which can be configured to be local or remote (remote using WS* to an idas remote) so, need idas client and idas server.

Back to the top