The CIFER API group has proposed using the 2014 ACAMP at the 2014 Technology Exchange to vote on "decision points" for moving forward. These decision points will set the overall strategy and approach for the future CIFER API work. All work afterwards could/would then focus on producing camera-ready documents that could/would become reference materials/standards.
Proposed Methodology
- To submit a proposal, list it below, along with any supporting documentation.
- Consensus is preferred for a proposal to be adopted or rejected.
- If consensus cannot be reached on a proposal then a simple majority vote is required to adopt.
- For purposes of counting votes towards consensus or majority, eligible voters are (1) members of the cifer-api mailing list AND EITHER (2a) present in the room at the time of the vote OR (2b) notify a moderator via email of their vote.
- If two conflicting proposals are adopted, the conflict must be resolved using consensus or majority as described above.
Proposals
Includes action items to be worked on if proposal is agreed to.
Topic | Submitter | Resolution |
|---|---|---|
MACE-dir should be CIFER API governing body
|
Counter-proposal:
- Repository for CIFER documents and registry: https://github.com/ciferproject/api
- Namespace for resource assignments: base url: http://ciferproject.org/ | Keith | |
A representation of CIFER API metadata in a SCIM compatible format
Jim
- Draft Core Schema | Benn | |
Registry APIs using SCIM API and CIFER schema
- Draft Registry API | Benn | |
ID Match using SCIM API and CIFER schema
- Draft ID Match API | Benn | |
Authorization/Group API using SCIM API and CIFER schema