Specification is ready for some real proof-reading, please pitch in
Review the RESOLVED issues on the issues page, did we resolve your issues to your satisfaction?
Review the Partial Update proposal and give feedback on the mailing list
Current open issues
OSLC Defined resources
21. OPEN No need for NLS string, any string should able to be an NLS string
22. OPEN Jim Conallen questions Core's stance on "discard unknown property values" saying that we cannot expect a domain to "define all possible types of file resources it is allowed to version?"
Response: No change, opaque resources should be created via special creation factory
Service Provider
25. OPEN Use dc:publisher in stead of dc:contributor here
Response: yes, fix this
Query
22. OPEN Proposal to defier oslc.from, oslc.offset, etc.
Response: pending Steve's use cases
Resource Shapes
19. OPEN Resource Shape value-types wrong, don't match those in defined resources section
Response: fix this
20. OPEN Default property value should be same type as property value itself
Response: fix this
21. OPEN allowedValues needs work, should be resource or inline
Response: fix problems but don't add min/max
JSON
4. OPEN Can we remove namespace definitions since we have them in service provider?
Turtle
1. OPEN Need Turtle representation rules, probably just a paragraph
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