ACTION-111: [EDITOR] Update BPs to reflect 10/21 resolution for normative changes to align vanilla/chocolate
[EDITOR] Update BPs to reflect 10/21 resolution for normative changes to align vanilla/chocolate
- State:
- closed
- Person:
- Cody Burleson
- Due on:
- November 1, 2013
- Created on:
- October 25, 2013
- Associated Product:
- Best Practices & Guidelines
- Related emails:
- Re: Question regarding Action 111 (from ashok.malhotra@oracle.com on 2013-11-26)
- Re: Question regarding Action 111 (from cody.burleson@base22.com on 2013-11-26)
- Re: Question regarding Action 111 (from sspeiche@gmail.com on 2013-11-26)
- Question regarding Action 111 (from cody.burleson@base22.com on 2013-11-25)
Related notes:
This action covers the ADDITIONS to BPs/Gs resulting from
http://www.w3.org/2013/meeting/ldp/2013-10-21#resolution_3
Action 110 covers the hits to the normative spec.
Text removed from normative spec is being commented out for now, not deleted, until it is added into BP by action 111.
John Arwe, 25 Oct 2013, 13:27:34Assigning to Cody as he is keeper of BPs
Steve Speicher, 18 Nov 2013, 14:18:24I have moved the stanza to the Best Practices and Guidelines document and it is now written there as follows:
Minimize server-specific constraints
LDPR servers SHOULD enable simple creation and modification of LDPRs.
It may be common for LDP servers to put restrictions on representations – for example, the range of rdf:type predicates, datatypes of the objects of predicates, and the number of occurrences of predicates in an LDPR, but servers should minimize such restrictions.
For some server applications, excessive constraints on modification of resources may be required. However, enforcement of more complex constraints will greatly restrict the set of clients that can modify resources. For interoperability with a wider range of clients, implementers are therefore encouraged to minimize server-specific constraints.
Display change log.