...
- Not a lot has changed since the London meeting (Data Conservancy work has affected availability)
- Feedback needed in order to progress this (Aaron presenting at the conference, specifically requesting feedback)
- Series of special topics meetings to be held to make decisions
- There are big issues, need proper governance for these issues
- Key themes in progressing this are a roadmap and governance
- Development plans to be finalized at next committer face-to-face
Enhanced content models
- Most of the ECM specification has been implemented for 3.4
- The validate method has been implemented (outstanding work on RELS-INT validation)
- Items on the roadmap:
- "Clone" method (3.5 release?)
- Search engine configuration for atomistic models
- Also noted that atomistic models are problematic in general for indexing, searching, OAI-PMH
...
- We have two APIs (REST, SOAP) with two sets of code
- SOAP splits into API-A and API-M, REST does not
- Mapping SOAP directly to REST does cause issues, however we should perform a comparison and understand the differences
- The Java client should map directly to the server API
- Merging APIs should be targetted at the 4.0 release
- Consider hooking authorization to objects/datastreams rather than API methods