Additional constraints on Shape needed for allowed values: min/max values, date range, etc
agreement that this is not needed at this time, will defer until we have clear scenarios that require it
Adoption of OSLCCorePartialUpdateDRAFT and extended properties to handle efficient fetch, add, update, removal of large multi-valued properties
overall agreement on approach need to iron out a few details on how to efficiently fetch large set (paging). SteveSpeicher to investigate existing approaches.
will update current draft with this guidance
DaveJohnson to update guidance document with examples
Refine query capability that is needed from core
Agreement to defer Attachments support from 2.0
PatrickStreule is working to complete state transition writeup this week.
Copyright � by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Contributions are governed by our Terms of Use Ideas, requests, problems regarding this site? Send feedback