Date: Thursday, July 07, 1pm EDT (-4 UTC)
- Dial-in Number: (712) 775-7035
- IRC:
Attendees
Agenda
- Design docs - consensus that these are OK? good to commit to GitHub?
- Follow up on #30 - Does API-X necessarily have to guarantee ontology resolution
- Follow up on #5 persisting data in repository. Some open questions
- Can/should/must/ API-X be able to persist objects to the repository for its own purposes?
- Can/should/must API-X be configurable to specify a particular container (or containers) to inspect for API-X-related objects (service and extension definitions, ontologies, etc)
- High level overview doc (#29)
- Other updates
- Unknown User (acoburn) and Bethany Seeger have started creating extension impls aligned with the current design draft
- These extension impls expose extension definition documents in OPTIONS body on service URI. Should this be a pattern generally supported by API-X? Required?
- Aaron Birkland has started implementing #10 and #12