Resolution to Action 111 (https://www.w3.org/2012/ldp/track/actions/111); added BP 'Minimize server-specific constraints'.
--- a/ldp-bp/ldp-bp.html Sun Dec 29 12:30:43 2013 -0600
+++ b/ldp-bp/ldp-bp.html Mon Dec 30 08:28:37 2013 -0600
@@ -56,7 +56,7 @@
},
{
name : "Miguel Esteban Gutiérrez",
- url: "http://mayor2.dia.fi.upm.es/oeg-upm/index.php/en/phdstudents/27-mesteban",
+ url : "http://mayor2.dia.fi.upm.es/oeg-upm/index.php/en/phdstudents/27-mesteban",
company : "Ontology Engineering Group, Universidad Politécnica de Madrid",
companyURL : "http://www.oeg-upm.net/"
},
@@ -275,11 +275,12 @@
RDF Vocabulary Description Language, and gives an overview of some
deployed RDF applications. It also describes the content and
purpose of other RDF specification documents.</li>
- <li><strong>Turtle - Terse RDF Triple Language</strong> [[TURTLE]] -
- defines a textual syntax for RDF called Turtle that allows RDF
- graphs to be completely written in a compact and natural text form,
- with abbreviations for common usage patterns and datatypes. RDF
- examples used in this document are expressed in Turtle.</li>
+ <li><strong>Turtle - Terse RDF Triple Language</strong>
+ [[TURTLE]] - defines a textual syntax for RDF called Turtle that
+ allows RDF graphs to be completely written in a compact and natural
+ text form, with abbreviations for common usage patterns and
+ datatypes. RDF examples used in this document are expressed in
+ Turtle.</li>
<li><strong>Linked Data Glossary</strong> [[LD-GLOSSARY]] - a
useful glossary containing terms defined and used to describe
Linked Data, and its associated vocabularies and best practices for
@@ -906,6 +907,25 @@
the relationship.</p>
</section>
+ <section>
+ <h3>Minimize server-specific constraints</h3>
+ <p>LDPR servers should enable simple creation and modification of
+ LDPRs.</p>
+
+ <P>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.</p>
+
+ <p>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.</p>
+ </section>
+
</section>
<!-- End Best Practices Section -->