--- /dev/null Thu Jan 01 00:00:00 1970 +0000
+++ b/ldp-diff-20130304.html Mon Mar 04 14:00:57 2013 -0500
@@ -0,0 +1,10600 @@
+<!DOCTYPE html>
+<html>
+ <head>
+ <title>Linked Data Platform 1.0</title>
+ <meta http-equiv='Content-Type' content='text/html;charset=utf-8'/>
+ <!--
+ === NOTA BENE ===
+ For the three scripts below, if your spec resides on dev.w3 you can check them
+ out in the same tree and use relative links so that they'll work offline,
+ -->
+ <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script>
+ <script class='remove'>
+ var respecConfig = {
+ // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
+ specStatus: "ED",
+
+ // the specification's short name, as in http://www.w3.org/TR/short-name/
+ shortName: "ldp",
+ // TODO: Confirm short name
+
+ // if your specification has a subtitle that goes below the main
+ // formal title, define it here
+ // subtitle : "an excellent document",
+
+ // if you wish the publication date to be other than today, set this
+ // publishDate: "2009-08-06",
+
+ // if the specification's copyright date is a range of years, specify
+ // the start date here:
+ // copyrightStart: "2005"
+
+ // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
+ // and its maturity status
+ previousPublishDate: "2012-10-25",
+ previousMaturity: "FPWD",
+ previousURI: "http://www.w3.org/TR/2012/WD-ldp-20121025/",
+
+ // if there a publicly available Editor's Draft, this is the link
+ edDraftURI: "http://www.w3.org/2012/ldp/hg/ldp.html",
+
+ // if this is a LCWD, uncomment and set the end of its review period
+ // lcEnd: "2009-08-05",
+
+ // if you want to have extra CSS, append them to this list
+ // it is recommended that the respec.css stylesheet be kept
+ //extraCSS: ["https://dvcs.w3.org/hg/ldpwg/css/respec.css"],
+
+ // editors, add as many as you like
+ // only "name" is required
+ editors: [
+ { name: "Steve Speicher", url: "http://stevespeicher.blogspot.com",
+ company: "IBM Corporation", companyURL: "http://ibm.com/" },
+ { name: "John Arwe", url: "https://www.ibm.com/developerworks/mydeveloperworks/groups/service/html/allcommunities?userid=120000CAW7",
+ company: "IBM Corporation", companyURL: "http://ibm.com/" },
+ ],
+
+ // authors, add as many as you like.
+ // This is optional, uncomment if you have authors as well as editors.
+ // only "name" is required. Same format as editors.
+
+ //authors: [
+ // { name: "Your Name", url: "http://example.org/",
+ // company: "Your Company", companyURL: "http://example.com/" },
+ //],
+
+ // name of the WG
+ wg: "Linked Data Platform Working Group",
+
+ // URI of the public WG page
+ wgURI: "http://www.w3.org/2012/ldp",
+
+ // name (without the @w3c.org) of the public mailing to which comments are due
+ wgPublicList: "public-ldp-wg",
+
+ // URI of the patent status for this WG, for Rec-track documents
+ // !!!! IMPORTANT !!!!
+ // This is important for Rec-track documents, do not copy a patent URI from a random
+ // document unless you know what you're doing. If in doubt ask your friendly neighbourhood
+ // Team Contact.
+ wgPatentURI: "http://www.w3.org/2004/01/pp-impl/55082/status",
+ doRDFa: "1.1",
+ };
+ </script>
+ <style type="text/css">
+ div.rule {padding-top: 1em;}
+ div.ldp-issue {
+ border-color: #E05252;
+ background: #FBE9E9;
+ padding: 0.5em;
+ margin: 1em 0;
+ position: relative;
+ clear: both;
+ border-left-width: .5em;
+ border-left-style: solid;
+ }
+ div.ldp-issue-title {
+ color: #E05252;
+ padding-right: 1em;
+ min-width: 7.5em;
+ }
+ </style>
+ <style type="text/css" media="all">
+ code {
+ font-weight:bold;
+ }
+ /* ReSpec uses color ff4500 for code elements, which does not print well on some black & white printers
+ and is a little hard to read for some folks even on-line. */
+ </style>
+<style type='text/css'>
+.diff-old-a {
+ font-size: smaller;
+ color: red;
+}
+
+.diff-new { background-color: yellow; }
+.diff-chg { background-color: lime; }
+.diff-new:before,
+.diff-new:after
+ { content: "\2191" }
+.diff-chg:before, .diff-chg:after
+ { content: "\2195" }
+.diff-old { text-decoration: line-through; background-color: #FBB; }
+.diff-old:before,
+.diff-old:after
+ { content: "\2193" }
+:focus { border: thin red solid}
+</style>
+ </head>
+<body>
+<del class="diff-old">Linked
+Data
+Platform
+1.0
+W3C
+Working
+Draft
+25
+October
+2012
+This
+version:
+http://www.w3.org/TR/2012/WD-ldp-20121025/
+Latest
+version:
+http://www.w3.org/TR/ldp/
+Editors:
+Steve
+Speicher
+,
+IBM
+Corporation
+Michael
+Hausenblas
+,
+DERI,
+NUI
+Galway
+Copyright
+©
+2012
+W3C
+®
+(
+MIT
+,
+ERCIM
+,
+Keio
+),
+All
+Rights
+Reserved.
+W3C
+liability
+,
+trademark
+and
+document
+use
+rules
+apply.
+Abstract
+</del>
+<section id='abstract'>
+A
+set
+of
+best
+practices
+and
+simple
+approach
+for
+a
+read-write
+Linked
+Data
+architecture,
+based
+on
+HTTP
+access
+to
+web
+resources
+that
+describe
+their
+state
+using
+<del class="diff-old">RDF.
+Status
+of
+This
+Document
+This
+section
+describes
+the
+status
+of
+this
+document
+at
+the
+time
+of
+its
+publication.
+Other
+documents
+may
+supersede
+this
+document.
+A
+list
+of
+current
+W3C
+publications
+and
+the
+latest
+revision
+of
+this
+technical
+report
+can
+be
+found
+in
+the
+W3C
+technical
+reports
+index
+at
+http://www.w3.org/TR/.
+This
+First
+Public
+Working
+Draft
+was
+published
+by
+the
+Linked
+Data
+Platform
+Working
+Group
+.
+This
+document
+builds
+on
+a
+W3C
+Member
+Submission
+.
+All
+known
+issues
+are
+documented
+inline
+as
+well
+as
+in
+the
+LDP
+WG
+Issue
+Tracker
+.
+If
+you
+wish
+to
+make
+comments
+regarding
+this
+document,
+please
+send
+them
+to
+public-ldp@w3.org
+(
+subscribe
+,
+archives
+).
+All
+feedback
+is
+welcome.
+Publication
+as
+a
+Working
+Draft
+does
+not
+imply
+endorsement
+by
+</del>
+the
+<del class="diff-old">W3C
+Membership.
+This
+is
+a
+draft
+document
+and
+may
+be
+updated,
+replaced
+or
+obsoleted
+by
+other
+documents
+at
+any
+time.
+It
+is
+inappropriate
+to
+cite
+this
+document
+as
+other
+than
+work
+in
+progress.
+This
+document
+was
+produced
+by
+a
+group
+operating
+under
+the
+5
+February
+2004
+W3C
+Patent
+Policy
+.
+W3C
+maintains
+a
+public
+list
+of
+any
+patent
+disclosures
+made
+in
+connection
+with
+the
+deliverables
+of
+the
+group;
+that
+page
+also
+includes
+instructions
+for
+disclosing
+a
+patent.
+An
+individual
+who
+has
+actual
+knowledge
+of
+a
+patent
+which
+the
+individual
+believes
+contains
+Essential
+Claim(s)
+must
+disclose
+the
+information
+in
+accordance
+with
+section
+6
+of
+the
+W3C
+</del>
+<abbr title="Resource Description Framework">
+<ins class="diff-chg">RDF
+</ins>
+</abbr>
+<del class="diff-old">Patent
+Policy
+.
+Table
+of
+Contents
+1.
+Introduction
+2.
+Terminology
+2.1
+Conventions
+Used
+in
+This
+Document
+3.
+Conformance
+4.
+Linked
+Data
+Platform
+Resource
+4.1
+General
+4.2
+HTTP
+GET
+4.3
+HTTP
+POST
+4.4
+HTTP
+PUT
+4.5
+HTTP
+DELETE
+4.6
+HTTP
+HEAD
+4.7
+HTTP
+PATCH
+4.8
+Common
+Properties
+5.
+Linked
+Data
+Platform
+Container
+5.1
+Informative
+5.2
+General
+5.3
+HTTP
+GET
+5.4
+HTTP
+POST
+5.5
+HTTP
+PUT
+5.6
+HTTP
+DELETE
+5.7
+HTTP
+HEAD
+5.8
+HTTP
+PATCH
+A.
+Acknowledgements
+B.
+Change
+History
+C.
+Editor
+Todos
+and
+Notes
+D.
+References
+D.1
+Normative
+references
+D.2
+Informative
+references
+1.
+</del>
+<ins class="diff-chg">data
+model.
+</ins></section><section><h1 id="intro">
+Introduction
+</h1>
+<p>
+This
+document
+describes
+the
+use
+of
+HTTP
+for
+accessing,
+updating,
+creating
+and
+deleting
+resources
+from
+servers
+that
+expose
+their
+resources
+as
+Linked
+Data.
+<del class="diff-old">It
+</del>
+<ins class="diff-chg"> It
+</ins>
+provides
+some
+new
+rules
+as
+well
+as
+clarifications
+and
+extensions
+of
+the
+four
+rules
+of
+Linked
+Data
+<del class="diff-old">[
+LINKED-DATA
+]
+</del>
+<ins class="diff-chg">[[LINKED-DATA]]:
+</ins>
+</p>
+<p>
+1.
+Use
+URIs
+as
+names
+for
+things
+</p>
+<p>
+2.
+Use
+HTTP
+URIs
+so
+that
+people
+can
+look
+up
+those
+names
+</p>
+<p>
+3.
+When
+someone
+looks
+up
+a
+URI,
+provide
+useful
+information,
+using
+the
+standards
+(RDF*,
+<del class="diff-old">SPARQL)
+</del>
+<abbr title="SPARQL Protocol and RDF Query Language">
+<ins class="diff-chg">SPARQL
+</ins></abbr><ins class="diff-chg">
+)
+</ins>
+</p>
+<p>
+4.
+Include
+links
+to
+other
+URIs.
+so
+that
+they
+can
+discover
+more
+things
+</p>
+<p>
+The
+best
+practices
+and
+anti-patterns
+covered
+in
+this
+document
+are:
+</p>
+<ul>
+<li>
+<p>
+<em>
+Resources
+</em>
+-
+a
+summary
+of
+the
+HTTP
+and
+RDF
+standard
+techniques
+and
+best
+practices
+that
+you
+should
+use,
+and
+anti-patterns
+you
+should
+avoid,
+when
+constructing
+clients
+and
+servers
+that
+read
+and
+write
+linked
+data.
+</p>
+</li>
+<li>
+<p>
+<em>
+Containers
+</em>
+-
+defines
+resources
+that
+allow
+new
+resources
+to
+be
+created
+using
+HTTP
+POST
+and
+existing
+resources
+to
+be
+found
+using
+HTTP
+<del class="diff-old">GET.
+</del>
+<ins class="diff-chg">GET.
+</ins>
+</p>
+</li>
+</ul>
+<p>
+Additionally,
+it
+is
+the
+intention
+of
+this
+document
+to
+enable
+additional
+rules
+and
+layered
+groupings
+of
+rules,
+such
+as
+additional
+specifications.
+<del class="diff-old">The
+</del>
+<ins class="diff-chg"> The
+</ins>
+scope
+is
+intentionally
+narrow
+to
+provide
+a
+set
+of
+key
+rules
+for
+reading
+and
+writing
+Linked
+Data
+that
+most,
+if
+not
+all,
+other
+specifications
+will
+depend
+on
+and
+implementations
+will
+support.
+</p>
+<del class="diff-old">2.
+</del>
+</section>
+<section>
+<h1 id="terms">
+Terminology
+</h1>
+<p>
+Terminology
+is
+based
+on
+<del class="diff-old">W3C
+'s
+</del>
+<ins class="diff-chg">W3C's
+</ins>
+Architecture
+of
+the
+World
+Wide
+Web
+<del class="diff-old">[
+WEBARCH
+]
+</del>
+<ins class="diff-chg">[[WEBARCH]]
+</ins>
+and
+Hyper-text
+Transfer
+Protocol
+<del class="diff-old">[
+HTTP11
+]
+</del>
+<ins class="diff-chg">[[HTTP11]].
+</ins>
+</p>
+<dl class="glossary">
+<dt>
+Link
+</dt>
+<dd>
+A
+relationship
+between
+two
+resources
+when
+one
+resource
+(representation)
+refers
+to
+the
+other
+resource
+by
+means
+of
+a
+<del class="diff-old">URI.[
+</del>
+<ins class="diff-chg">URI
+[[WEBARCH]].
+</ins><p>
+<del class="diff-old">WEBARCH
+</del>
+</p>
+<del class="diff-old">]
+</del>
+</dd>
+<dt>
+Linked
+Data
+</dt>
+<dd>
+As
+defined
+by
+Tim
+<del class="diff-old">Berners-Lee.
+[
+</del>
+<ins class="diff-chg">Berners-Lee
+[[LINKED-DATA]].
+</ins><p>
+<del class="diff-old">LINKED-DATA
+</del>
+</p>
+<del class="diff-old">]
+</del>
+</dd>
+<dt>
+<dfn>
+Linked
+Data
+Platform
+Resource
+<del class="diff-old">(LDPR)
+</del>
+</dfn>
+<ins class="diff-chg">(
+</ins><dfn><abbr title="Linked Data Platform Resource"><ins class="diff-chg">
+LDPR
+</ins></abbr></dfn><ins class="diff-chg">
+)
+</ins>
+</dt>
+<dd>
+HTTP
+resource
+that
+conforms
+to
+the
+simple
+lifecycle
+patterns
+and
+conventions
+in
+<del class="diff-old">this
+document.
+</del>
+<ins class="diff-chg">the
+</ins><a href="#ldpr"><ins class="diff-chg">
+LDPRs
+</ins></a><ins class="diff-chg">
+section.
+</ins><p></p>
+</dd>
+<dt>
+<dfn>
+Linked
+Data
+Platform
+Container
+<del class="diff-old">(LDPC)
+</del>
+</dfn>
+<ins class="diff-chg">(
+</ins><dfn><abbr title="Linked Data Platform Container"><ins class="diff-chg">
+LDPC
+</ins></abbr></dfn><ins class="diff-chg">
+)
+</ins>
+</dt>
+<dd>
+<del class="diff-old">LDP
+resource
+</del>
+<ins class="diff-chg">LDPR
+</ins>
+that
+also
+conforms
+to
+<a href="#ldpc">
+additional
+patterns
+and
+conventions
+<del class="diff-old">in
+this
+document
+</del>
+</a>
+for
+managing
+membership.
+<p>
+</p>
+</dd>
+<dt>
+Client
+</dt>
+<dd>
+A
+program
+that
+establishes
+connections
+for
+the
+purpose
+of
+sending
+<del class="diff-old">requests.
+[
+</del>
+<ins class="diff-chg">requests
+[[HTTP11]].
+</ins><p>
+<del class="diff-old">HTTP11
+</del>
+</p>
+<del class="diff-old">]
+</del>
+</dd>
+<dt>
+Server
+</dt>
+<dd>
+An
+application
+program
+that
+accepts
+connections
+in
+order
+to
+service
+requests
+by
+sending
+back
+responses.
+<p>
+Any
+given
+program
+may
+be
+capable
+of
+being
+both
+a
+client
+and
+a
+server;
+our
+use
+of
+these
+terms
+refers
+only
+to
+the
+role
+being
+performed
+by
+the
+program
+for
+a
+particular
+connection,
+rather
+than
+to
+the
+program's
+capabilities
+in
+general.
+Likewise,
+any
+server
+may
+act
+as
+an
+origin
+server,
+proxy,
+gateway,
+or
+tunnel,
+switching
+behavior
+based
+on
+the
+nature
+of
+each
+<del class="diff-old">request.
+[
+HTTP11
+</del>
+<ins class="diff-chg">request
+[[HTTP11]].
+</ins></p>
+<del class="diff-old">]
+</del>
+</dd>
+<dt>
+<del class="diff-old">ISSUE-8
+</del>
+<dfn>
+<ins class="diff-chg">Membership
+triples
+</ins></dfn>
+<del class="diff-old">CLOSED
+Better
+</del>
+</dt>
+<dd>
+<ins class="diff-chg">A
+set
+of
+triples
+in
+an
+LDPC's
+state
+that
+lists
+its
+members.
+The
+membership
+triples
+of
+a
+container
+all
+have
+the
+same
+subject
+and
+predicate,
+and
+the
+objects
+of
+the
+membership
+triples
+</ins>
+define
+<del class="diff-old">or
+just
+not
+use
+</del>
+the
+<del class="diff-old">"Basic
+profile"
+terminology
+</del>
+<ins class="diff-chg">container's
+members.
+</ins><p>
+<del class="diff-old">2.1
+</del>
+</p>
+</dd>
+<dt>
+<dfn>
+<ins class="diff-chg">Membership
+subject
+</ins></dfn></dt><dd><ins class="diff-chg">
+The
+subject
+of
+all
+an
+LDPC's
+</ins><a title="Membership triples"><ins class="diff-chg">
+membership
+triples
+</ins></a>.<p></p></dd><dt><dfn><ins class="diff-chg">
+Membership
+predicate
+</ins></dfn></dt><dd><ins class="diff-chg">
+The
+predicate
+of
+all
+an
+LDPC's
+</ins><a title="Membership triples"><ins class="diff-chg">
+membership
+triples
+</ins></a>.<p></p></dd></dl><section><h2 id="conventions">
+Conventions
+Used
+in
+This
+Document
+</h2>
+<p>
+Sample
+resource
+representations
+are
+provided
+in
+<code>
+text/turtle
+</code>
+format
+<del class="diff-old">[
+TURTLE
+].
+</del>
+<ins class="diff-chg">[[TURTLE]].
+</ins>
+</p>
+<p>
+Commonly
+used
+namespace
+prefixes:
+</p>
+<del class="diff-old"> @prefix dcterms: <http://purl.org/dc/terms/>.
+ @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
+ @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
+ @prefix ldp: <http://www.w3.org/ns/ldp#>.
+</del>
+ <pre style="word-wrap: break-word; white-space: pre-wrap;">
+<ins class="diff-chg"> @prefix dcterms: <http://purl.org/dc/terms/>.
+ @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
+ @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
+ @prefix ldp: <http://www.w3.org/ns/ldp#>.
+</ins>
+@prefix
+xsd:
+<del class="diff-old"><http://www.w3.org/2001/XMLSchema#>.
+</del>
+<ins class="diff-chg">
+ <http://www.w3.org/2001/XMLSchema#>.
+</ins>
+</pre>
+<del class="diff-old">3.
+Conformance
+</del>
+</section>
+</section>
+<section id='conformance'>
+<p>
+<del class="diff-old">As
+well
+as
+</del>
+<ins class="diff-chg">The
+status
+of
+the
+</ins>
+sections
+<del class="diff-old">marked
+</del>
+<ins class="diff-chg">of
+Linked
+Data
+Platform
+1.0
+(this
+document)
+is
+</ins>
+as
+<del class="diff-old">non-normative,
+all
+authoring
+guidelines,
+diagrams,
+examples,
+</del>
+<ins class="diff-chg">follows:
+</ins></p><ul><li><ins class="diff-chg">
+1.
+Introduction:
+</ins><b><ins class="diff-chg">
+informative
+</ins></b></li><li><ins class="diff-chg">
+2.
+Terminology:
+</ins><b><ins class="diff-chg">
+informative
+</ins></b></li><li><ins class="diff-chg">
+3.
+Conformance:
+</ins><b><ins class="diff-chg">
+normative
+</ins></b></li><li><ins class="diff-chg">
+4.
+Linked
+Data
+Platform
+Resources:
+</ins><b><ins class="diff-chg">
+normative
+</ins></b></li><li><ins class="diff-chg">
+5.
+Linked
+Data
+Platform
+Containers:
+</ins><b><ins class="diff-chg">
+normative
+</ins></b></li><li><ins class="diff-chg">
+A.
+Acknowledgements:
+</ins><b><ins class="diff-chg">
+normative
+</ins></b></li><li><ins class="diff-chg">
+B.
+Change
+History:
+</ins><b><ins class="diff-chg">
+normative
+</ins></b></li><li><ins class="diff-chg">
+D.1
+Normative
+references:
+</ins><b><ins class="diff-chg">
+normative
+</ins></b></li><li><ins class="diff-chg">
+D.2
+Informative
+references:
+</ins><b><ins class="diff-chg">
+informative
+</ins></b></li></ul><p><ins class="diff-chg">
+A
+conforming
+</ins><b><ins class="diff-chg">
+LDP
+Server
+</ins></b><ins class="diff-chg">
+is
+an
+application
+program
+that
+processes
+HTTP
+requests
+</ins>
+and
+<del class="diff-old">notes
+in
+this
+specification
+are
+non-normative.
+Everything
+else
+</del>
+<ins class="diff-chg">generates
+HTTP
+responses
+that
+conform
+to
+the
+rules
+defined
+</ins>
+in
+<del class="diff-old">this
+specification
+is
+normative.
+</del>
+<ins class="diff-chg">sections
+on
+</ins><a href="#linked-data-platform-resources"><ins class="diff-chg">
+LDPRs
+</ins></a><ins class="diff-chg">
+and
+</ins><a href="#linked-data-platform-containers"><ins class="diff-chg">
+LDPCs
+</ins></a>
+</p>
+<p>
+<del class="diff-old">The
+key
+words
+must
+,
+must
+not
+,
+required
+,
+should
+,
+should
+not
+,
+recommended
+,
+may
+,
+</del>
+<ins class="diff-chg">A
+conforming
+</ins><b><ins class="diff-chg">
+LDP
+Client
+</ins></b><ins class="diff-chg">
+is
+an
+application
+program
+that
+generates
+HTTP
+requests
+</ins>
+and
+<del class="diff-old">optional
+in
+this
+specification
+are
+</del>
+<ins class="diff-chg">processes
+HTTP
+responses
+that
+conform
+</ins>
+to
+<del class="diff-old">be
+interpreted
+as
+described
+</del>
+<ins class="diff-chg">the
+rules
+defined
+</ins>
+in
+<del class="diff-old">[
+RFC2119
+</del>
+<ins class="diff-chg">sections
+on
+</ins><a href="#linked-data-platform-resources"><ins class="diff-chg">
+LDPRs
+</ins></a><ins class="diff-chg">
+and
+</ins><a href="#linked-data-platform-containers"><ins class="diff-chg">
+LDPCs
+</ins>
+</a>
+<del class="diff-old">].
+</del>
+</p>
+<del class="diff-old">4.
+</del>
+</section>
+<section>
+<h1 id="ldpr">
+Linked
+Data
+Platform
+<del class="diff-old">Resource
+</del>
+<ins class="diff-chg">Resources
+</ins></h1>
+<p>
+Linked
+Data
+Platform
+Resources
+<del class="diff-old">(LDPRs)
+</del>
+<ins class="diff-chg">(
+</ins><dfn><abbr title="Linked Data Platform Resources"><ins class="diff-chg">
+LDPRs
+</ins></abbr></dfn><ins class="diff-chg">
+)
+</ins>
+are
+HTTP
+resources
+that
+conform
+to
+the
+simple
+patterns
+and
+conventions
+in
+this
+section.
+HTTP
+requests
+to
+access,
+modify,
+create
+or
+delete
+LDPRs
+are
+accepted
+and
+processed
+by
+LDPR
+servers.
+Most
+LDPRs
+are
+domain-specific
+resources
+that
+contain
+data
+for
+an
+entity
+in
+some
+domain,
+which
+could
+be
+commercial,
+governmental,
+scientific,
+religious,
+or
+other.
+</p>
+<p>
+Some
+of
+the
+rules
+defined
+in
+this
+document
+provide
+clarification
+and
+refinement
+of
+the
+base
+Linked
+Data
+rules
+<del class="diff-old">[
+LINKED-DATA
+],
+</del>
+<ins class="diff-chg">[[LINKED-DATA]];
+</ins>
+others
+address
+additional
+needs.
+</p>
+<p>
+The
+rules
+for
+Linked
+Data
+Platform
+Resources
+address
+basic
+questions
+such
+as:
+</p>
+<ul>
+<li>
+What
+resource
+formats
+should
+be
+used?
+</li>
+<li>
+<del class="diff-old">What
+literal
+value
+types
+should
+be
+used?
+Are
+there
+some
+typical
+vocabularies
+that
+should
+be
+reused?
+</del>
+How
+is
+optimistic
+collision
+detection
+handled
+for
+updates?
+</li>
+<li>
+What
+should
+client
+expectations
+be
+for
+changes
+to
+linked-to
+resources,
+such
+as
+type
+changes?
+</li>
+<li>
+What
+can
+servers
+do
+to
+ease
+the
+burden
+of
+constraints
+for
+resource
+creation?
+</li>
+</ul>
+<p>
+<ins class="diff-new">Additional
+informative
+guidance
+is
+available
+on
+the
+</ins><a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide" class="external " title="Deployment Guide" rel="nofollow"><ins class="diff-new">
+working
+group's
+wiki
+</ins></a><ins class="diff-new">
+that
+addresses
+deployment
+questions
+such
+as:
+</ins></p><ul><li><ins class="diff-new">
+What
+literal
+value
+types
+should
+be
+used?
+</ins></li><li><ins class="diff-new">
+Are
+there
+some
+typical
+vocabularies
+that
+should
+be
+reused?
+</ins></li></ul><p>
+The
+following
+sections
+define
+the
+rules
+and
+guidelines
+for
+use
+of
+LDPRs.
+</p>
+<del class="diff-old">4.1
+</del>
+<section>
+<h2 id="ldpr-general">
+General
+</h2>
+<div id="ldpr-4_1_1" class="rule">
+4.1.1
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+at
+least
+be
+HTTP/1.1
+conformant
+servers
+<del class="diff-old">[
+HTTP11
+].
+</del>
+<ins class="diff-chg">[[!HTTP11]].
+</ins>
+</div>
+<div id="ldpr-4_1_2" class="rule">
+4.1.2
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+provide
+an
+RDF
+representation
+for
+LDPRs.
+The
+<del class="diff-old">subject
+</del>
+<ins class="diff-chg">HTTP
+Request-URI
+of
+the
+LDPR
+</ins>
+is
+typically
+the
+<del class="diff-old">LDPR
+itself.
+</del>
+<ins class="diff-chg">subject
+of
+most
+triples
+in
+the
+response.
+</ins>
+</div>
+<div id="ldpr-4_1_3" class="rule">
+4.1.3
+LDPR
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+host
+a
+mixture
+of
+LDPRs
+and
+non-LDPRs.
+For
+example,
+it
+is
+common
+for
+LDPR
+servers
+to
+need
+to
+host
+binary
+or
+text
+resources
+that
+do
+not
+have
+useful
+RDF
+representations.
+</div>
+<div id="ldpr-4_1_4" class="rule">
+4.1.4
+Clients
+can
+access
+a
+LDPR
+using
+multiple
+URLs,
+for
+example
+when
+DNS
+aliasing
+is
+used.
+A
+LDPR
+server
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+respond
+to
+each
+of
+those
+requests
+using
+a
+single
+consistent
+URL,
+a
+canonical
+URL,
+for
+the
+LDPR
+which
+may
+be
+found
+in
+the
+response's
+Location
+header
+and
+potentially
+also
+in
+the
+representation
+of
+the
+LDPR.
+Clients
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+use
+<del class="diff-old">that
+</del>
+<ins class="diff-chg">the
+</ins>
+canonical
+URL
+<ins class="diff-new">as
+an
+LDPR's
+identity;
+for
+example,
+when
+determining
+if
+two
+URLs
+refer
+</ins>
+to
+<del class="diff-old">identify
+</del>
+the
+<del class="diff-old">LDPR.
+4.1.5
+LDPR
+predicates
+should
+use
+standard
+vocabularies
+such
+as
+Dublin
+Core
+[
+DC-TERMS
+],
+RDF
+[
+RDF-PRIMER
+]
+and
+RDF
+Schema
+[
+</del>
+<ins class="diff-chg">same
+resource
+clients
+need
+to
+compare
+the
+canonical
+URLs
+not
+the
+URLs
+used
+to
+access
+the
+resources.
+</ins><div class="ldp-issue"><div class="ldp-issue-title">
+<del class="diff-old">RDF-SCHEMA
+</del>
+<a href="http://www.w3.org/2012/ldp/track/issues/49">
+<ins class="diff-chg">ISSUE-49
+</ins>
+</a>
+<del class="diff-old">],
+whenever
+possible.
+</del>
+</div>
+<ins class="diff-chg">Canonical
+URL
+-
+how
+to
+communicate
+its
+value
+to
+clients
+</ins></div></div><div id="ldpr-4_1_5" class="rule"><ins class="diff-chg">
+4.1.5
+</ins>
+LDPRs
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+reuse
+existing
+vocabularies
+instead
+of
+creating
+their
+own
+duplicate
+vocabulary
+terms.
+<ins class="diff-new">In
+addition
+to
+this
+general
+rule,
+some
+specific
+cases
+are
+covered
+by
+other
+conformance
+rules.
+</ins>
+</div>
+<del class="diff-old">4.1.6
+</del>
+<div id="ldpr-4_1_5_1" class="rule">
+<ins class="diff-chg">4.1.5.1
+</ins>
+LDPR
+predicates
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+use
+<del class="diff-old">well-known
+RDF
+</del>
+<ins class="diff-chg">standard
+</ins>
+vocabularies
+<ins class="diff-new">such
+</ins>
+as
+<del class="diff-old">defined
+in
+section
+4.8
+Common
+Properties
+wherever
+a
+predicate’s
+meaning
+matches
+one
+of
+them.
+</del>
+<ins class="diff-chg">Dublin
+Core
+[[!DC-TERMS]],
+RDF
+[[!RDF-PRIMER]]
+and
+RDF
+Schema
+[[!RDF-SCHEMA]],
+whenever
+possible.
+</ins>
+</div>
+<del class="diff-old">4.1.6.1
+</del>
+<div id="ldpr-4_1_6" class="rule">
+<ins class="diff-chg">4.1.6
+</ins>
+LDPRs
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+use
+the
+predicate
+<code>
+rdf:type
+</code>
+to
+represent
+the
+concept
+of
+type.
+The
+use
+of
+non-standard
+type
+predicates,
+as
+well
+as
+<code>
+dcterms:type
+</code>,
+is
+<del class="diff-old">discouraged.
+[
+DC-RDF
+]
+</del>
+<ins class="diff-chg">discouraged,
+as
+it
+is
+not
+recommended
+by
+the
+Dublin
+Core
+Metadata
+Initiative
+for
+use
+with
+RDF
+resources
+[[!DC-RDF]].
+</ins>
+</div>
+<div id="ldpr-4_1_7" class="rule">
+4.1.7
+LDPR
+representations
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+have
+at
+least
+one
+<code>
+rdf:type
+</code>
+set
+explicitly.
+<del class="diff-old">This
+</del>
+<ins class="diff-chg"> This
+</ins>
+makes
+the
+representations
+much
+more
+useful
+to
+client
+applications
+that
+don’t
+support
+inferencing.
+</div>
+<div id="ldpr-4_1_8" class="rule">
+4.1.8
+Predicate
+URIs
+used
+in
+LDPR
+representations
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+be
+HTTP
+URLs.
+<del class="diff-old">These
+</del>
+<ins class="diff-chg"> These
+</ins>
+predicate
+URIs
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+identify
+LDPRs
+whose
+representations
+are
+retrievable.
+LDPR
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+provide
+an
+RDF
+Schema
+<del class="diff-old">[
+RDF-SCHEMA
+]
+</del>
+<ins class="diff-chg">[[!RDF-SCHEMA]]
+</ins>
+representation
+of
+these
+predicates.
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/9">
+ISSUE-9
+</a>
+</div>
+Should
+properties
+used
+in
+LDPR
+representations
+be
+LDPRs?
+</div>
+</div>
+<div id="ldpr-4_1_9" class="rule">
+4.1.9
+<del class="diff-old">LDPR
+representations
+must
+use
+only
+the
+following
+standard
+datatypes.
+RDF
+does
+not
+by
+itself
+define
+datatypes
+to
+be
+used
+for
+literal
+property
+values,
+therefore
+a
+set
+of
+standard
+datatypes
+based
+on
+[
+XMLSCHEMA11-2
+]
+and
+[
+RDF-PRIMER
+]
+are
+to
+be
+used:
+URI
+Description
+http://www.w3.org/2001/XMLSchema#boolean
+Boolean
+type
+as
+specified
+by
+XSD
+Boolean
+http://www.w3.org/2001/XMLSchema#date
+Date
+type
+as
+specified
+by
+XSD
+date
+http://www.w3.org/2001/XMLSchema#dateTime
+Date
+and
+Time
+type
+as
+specified
+by
+XSD
+dateTime
+http://www.w3.org/2001/XMLSchema#decimal
+Decimal
+number
+type
+as
+specified
+by
+XSD
+Decimal
+http://www.w3.org/2001/XMLSchema#double
+Double
+floating-point
+number
+type
+as
+specified
+by
+XSD
+Double
+http://www.w3.org/2001/XMLSchema#float
+Floating-point
+number
+type
+as
+specified
+by
+XSD
+Float
+http://www.w3.org/2001/XMLSchema#integer
+Integer
+number
+type
+as
+specified
+by
+XSD
+Integer
+http://www.w3.org/2001/XMLSchema#string
+String
+type
+as
+specified
+by
+XSD
+String
+http://www.w3.org/1999/02/22-rdf-syntax-ns#XMLLiteral
+Literal
+XML
+value
+as
+specified
+by
+RDF
+ISSUE-6
+Should
+LDBP
+say
+that
+any
+kind
+of
+user-defined
+simple
+data
+type
+is
+disallowed?
+4.1.10
+</del>
+LDPRs
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+use
+at
+least
+one
+RDF
+triple
+to
+represent
+a
+link
+(relationship)
+to
+another
+resource.
+In
+other
+words,
+having
+the
+source
+resource’s
+URI
+as
+the
+subject
+and
+the
+target
+resource’s
+URI
+as
+the
+object
+of
+the
+triple
+<del class="diff-old">represent
+</del>
+<ins class="diff-chg">representing
+</ins>
+the
+link
+(relationship)
+is
+enough
+and
+does
+not
+require
+the
+creation
+of
+an
+intermediate
+link
+resource
+to
+describe
+the
+relationship.
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/44">
+<ins class="diff-new">ISSUE-44
+</ins></a>
+</div>
+<del class="diff-old">4.1.11
+</del>
+<ins class="diff-chg">4.1.9.
+is
+obscure
+or
+too
+restrictive
+</ins></div></div><div id="ldpr-4_1_10" class="rule"><ins class="diff-chg">
+4.1.10
+</ins>
+LDPR
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+support
+<del class="diff-old">additional
+</del>
+standard
+<del class="diff-old">representations.
+</del>
+<ins class="diff-chg">representations
+beyond
+those
+necessary
+to
+conform
+to
+this
+specification.
+</ins>
+These
+could
+be
+other
+RDF
+formats,
+like
+N3
+or
+NTriples,
+but
+non-RDF
+formats
+like
+HTML
+<del class="diff-old">[
+HTML401
+]
+</del>
+<ins class="diff-chg">[[!HTML401]]
+</ins>
+and
+JSON
+<del class="diff-old">[
+RFC4627
+]
+</del>
+<ins class="diff-chg">[[!RFC4627]]
+</ins>
+would
+be
+likely
+be
+common.
+<del class="diff-old">ISSUE-22
+Need
+to
+normatively
+reference
+and
+recommend
+JSON-LD
+</del>
+</div>
+<del class="diff-old">4.1.12
+</del>
+<div id="ldpr-4_1_11" class="rule">
+<ins class="diff-chg">4.1.11
+</ins>
+LDPRs
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+be
+created,
+updated
+and
+deleted
+using
+methods
+not
+defined
+in
+this
+document,
+for
+example
+through
+application-specific
+means,
+SPARQL
+UPDATE,
+etc.
+<del class="diff-old">[
+SPARQL-UPDATE
+]
+</del>
+<ins class="diff-chg">[[!SPARQL-UPDATE]],
+as
+long
+as
+those
+methods
+do
+not
+conflict
+with
+this
+specification's
+normative
+requirements.
+</ins>
+</div>
+<del class="diff-old">4.1.13
+LDPR
+</del>
+<div id="ldpr-4_1_12" class="rule">
+<ins class="diff-chg">4.1.12
+BPR
+</ins>
+server
+responses
+<del class="diff-old">must
+contain
+accurate
+</del>
+<ins class="diff-chg">MUST
+use
+entity
+tags
+(either
+weak
+or
+strong
+ones)
+as
+</ins>
+response
+<code>
+ETag
+</code>
+header
+values.
+<del class="diff-old">ISSUE-10
+Include
+clarifications
+and
+guidance
+around
+ETags
+ISSUE-2
+Do
+LDPR
+versions
+get
+managed
+in
+a
+systematic,
+discoverable
+way?
+</del>
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/15">
+ISSUE-15
+</a>
+</div>
+sharing
+binary
+resources
+and
+metadata
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/16">
+ISSUE-16
+</a>
+</div>
+Redirection
+of
+non-information
+resources
+to
+LDPRs
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/19">
+ISSUE-19
+</a>
+</div>
+Adressing
+more
+error
+cases
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/32">
+<ins class="diff-new">ISSUE-32
+</ins></a>
+</div>
+<ins class="diff-chg">How
+can
+clients
+discover
+that
+a
+resource
+is
+an
+LDPR
+or
+LDPC,
+and
+what
+features
+are
+supported?
+</ins></div><div class="ldp-issue"><div class="ldp-issue-title">
+<del class="diff-old">4.2
+</del>
+<a href="http://www.w3.org/2012/ldp/track/issues/33">
+<ins class="diff-chg">ISSUE-33
+</ins></a></div><ins class="diff-chg">
+Pagination
+for
+non-container
+resources
+</ins></div><div id="ldpr-4_1_13" class="rule"><ins class="diff-chg">
+4.1.13
+LDPR
+servers
+SHOULD
+enable
+simple
+creation
+and
+modification
+of
+LDPRs.
+It
+is
+common
+for
+LDPR
+servers
+to
+put
+restrictions
+on
+representations
+–
+for
+example,
+the
+range
+of
+</ins><code><ins class="diff-chg">
+rdf:type
+</ins></code><ins class="diff-chg">
+predicates,
+datatypes
+of
+the
+objects
+of
+predicates,
+and
+the
+number
+of
+occurrences
+of
+predicates
+in
+an
+LDPR,
+but
+servers
+SHOULD
+minimize
+those
+restrictions.
+ Enforcement
+of
+more
+complex
+constraints
+will
+greatly
+restrict
+the
+set
+of
+clients
+that
+can
+modify
+resources.
+For
+some
+server
+applications,
+excessive
+constraints
+on
+modification
+of
+resources
+may
+be
+required.
+</ins></div></section><section><h2 id="ldpr-HTTP_GET">
+HTTP
+GET
+</h2>
+<div id="ldpr-4_2_1" class="rule">
+4.2.1
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+support
+the
+HTTP
+GET
+Method
+for
+LDPRs.
+</div>
+<div id="ldpr-4_2_2" class="rule">
+4.2.2
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+provide
+<del class="diff-old">an
+</del>
+<ins class="diff-chg">a
+</ins>
+<code>
+text/turtle
+</code>
+representation
+of
+the
+requested
+<del class="diff-old">LDPR.[
+TURTLE
+]
+</del>
+<ins class="diff-chg">LDPR
+[[!TURTLE]].
+</ins>
+</div>
+<div id="ldpr-4_2_3" class="rule">
+4.2.3
+LDPR
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">MAY
+</ins>
+provide
+<del class="diff-old">a
+application/rdf+xml
+representation
+</del>
+<ins class="diff-chg">representations
+</ins>
+of
+the
+requested
+<del class="diff-old">LDPR.[
+RDF-SYNTAX
+]
+ISSUE-23
+Remove
+application/rdf+xml
+as
+</del>
+<ins class="diff-chg">LDPR
+beyond
+those
+necessary
+to
+conform
+to
+this
+specification,
+using
+standard
+HTTP
+content
+negotiation.
+If
+the
+client
+does
+not
+indicate
+</ins>
+a
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">preference,
+</ins><code><ins class="diff-chg">
+text/turtle
+</ins></code><ins class="diff-chg">
+MUST
+be
+returned.
+</ins>
+</div>
+<div id="ldpr-4_2_4" class="rule">
+4.2.4
+In
+the
+absence
+of
+special
+knowledge
+of
+the
+application
+or
+domain,
+LDPR
+clients
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+assume
+that
+any
+LDPR
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">can
+</ins>
+have
+multiple
+values
+for
+<code>
+rdf:type
+</code>.
+</div>
+<div id="ldpr-4_2_5" class="rule">
+4.2.5
+In
+the
+absence
+of
+special
+knowledge
+of
+the
+application
+or
+domain,
+LDPR
+clients
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+assume
+that
+the
+<code>
+rdf:type
+</code>
+values
+of
+a
+given
+LDPR
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">can
+</ins>
+change
+over
+time.
+</div>
+<del class="diff-old">4.3
+</del>
+</section>
+<section>
+<h2 id="ldpr-HTTP_POST">
+HTTP
+POST
+</h2>
+<p>
+<del class="diff-old">There
+are
+</del>
+<ins class="diff-chg">This
+specification
+adds
+</ins>
+no
+<del class="diff-old">additional
+</del>
+<ins class="diff-chg">new
+</ins>
+requirements
+on
+HTTP
+POST
+for
+LDPRs.
+</p>
+<del class="diff-old">4.4
+</del>
+</section>
+<section>
+<h2 id="ldpr-HTTP_PUT">
+HTTP
+PUT
+</h2>
+<p>
+<ins class="diff-chg">This
+specification
+imposes
+the
+following
+new
+requirements
+on
+HTTP
+PUT
+for
+LDPRs
+only
+when
+the
+LDPR
+supports
+that
+method.
+This
+specification
+does
+not
+impose
+any
+new
+requirement
+to
+support
+that
+method,
+and
+[[!HTTP11]]
+makes
+it
+optional.
+</ins></p><div id="ldpr-4_4_1" class="rule">
+4.4.1
+If
+HTTP
+PUT
+is
+performed
+on
+an
+existing
+resource,
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+replace
+the
+entire
+persistent
+state
+of
+the
+identified
+resource
+with
+the
+entity
+representation
+in
+the
+body
+of
+the
+request.
+<del class="diff-old">The
+only
+recognized
+exception
+are
+the
+</del>
+<ins class="diff-chg">BPR
+servers
+MAY
+ignore
+server
+managed
+</ins>
+properties
+<ins class="diff-new">such
+as
+</ins>
+<code>
+dcterms:modified
+</code>
+and
+<code>
+dcterms:creator
+</code>
+<del class="diff-old">that
+</del>
+<ins class="diff-chg">if
+they
+</ins>
+are
+<del class="diff-old">never
+</del>
+<ins class="diff-chg">not
+</ins>
+under
+client
+<del class="diff-old">control
+-
+LDPR
+servers
+must
+ignore
+any
+values
+of
+these
+properties
+that
+are
+provided
+by
+the
+client.
+</del>
+<ins class="diff-chg">control.
+</ins>
+Any
+LDPR
+servers
+that
+wish
+to
+support
+a
+more
+sophisticated
+merge
+of
+data
+provided
+by
+the
+client
+with
+existing
+state
+stored
+on
+the
+server
+for
+a
+resource
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+use
+HTTP
+PATCH,
+not
+HTTP
+PUT.
+<del class="diff-old">ISSUE-11
+</del>
+</div>
+<del class="diff-old">Do
+we
+need
+to
+define
+server-managed
+properties
+or
+do
+we
+leave
+them
+to
+applications?
+</del>
+<div id="ldpr-4_4_2" class="rule">
+4.4.2
+LDPR
+clients
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+use
+the
+HTTP
+<code>
+If-Match
+</code>
+header
+and
+HTTP
+<code>
+ETags
+</code>
+to
+ensure
+it
+isn’t
+modifying
+a
+resource
+that
+has
+changed
+since
+the
+client
+last
+retrieved
+its
+representation.
+LDPR
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+require
+the
+HTTP
+<code>
+If-Match
+</code>
+header
+and
+HTTP
+<code>
+ETags
+</code>
+to
+detect
+collisions.
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+respond
+with
+status
+code
+412
+(Condition
+Failed)
+if
+<code>
+ETag
+</code>
+s
+fail
+to
+match
+if
+there
+are
+no
+other
+errors
+with
+the
+<del class="diff-old">request.
+[
+HTTP11
+]
+</del>
+<ins class="diff-chg">request
+[[!HTTP11]].
+</ins>
+</div>
+<div id="ldpr-4_4_3" class="rule">
+4.4.3
+LDPR
+clients
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+always
+assume
+that
+the
+set
+of
+predicates
+for
+a
+resource
+of
+a
+particular
+type
+at
+an
+arbitrary
+server
+is
+<del class="diff-old">open
+</del>
+<ins class="diff-chg">open,
+</ins>
+in
+the
+sense
+that
+different
+resources
+of
+the
+same
+type
+may
+not
+all
+have
+the
+same
+set
+of
+predicates
+in
+<del class="diff-old">its
+</del>
+<ins class="diff-chg">their
+</ins>
+triples,
+and
+the
+set
+of
+predicates
+that
+are
+used
+in
+the
+state
+of
+<del class="diff-old">a
+</del>
+<ins class="diff-chg">any
+one
+</ins>
+resource
+is
+not
+limited
+to
+any
+pre-defined
+set.
+</div>
+<div id="ldpr-4_4_4" class="rule">
+4.4.4
+LDPR
+clients
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+assume
+that
+a
+LDPR
+server
+could
+discard
+triples
+whose
+predicates
+the
+server
+does
+not
+recognize
+or
+otherwise
+chooses
+not
+to
+persist.
+In
+other
+words,
+LDPR
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+restrict
+themselves
+to
+a
+known
+set
+of
+predicates,
+but
+LDPR
+clients
+<del class="diff-old">must
+not
+</del>
+<ins class="diff-chg">MUST
+NOT
+</ins>
+restrict
+themselves
+to
+a
+known
+set
+of
+predicates
+when
+their
+intent
+is
+to
+perform
+a
+later
+HTTP
+PUT
+to
+update
+the
+resource.
+</div>
+<div id="ldpr-4_4_5" class="rule">
+4.4.5
+A
+LDPR
+client
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+preserve
+all
+triples
+retrieved
+using
+HTTP
+GET
+that
+it
+doesn’t
+change
+whether
+it
+understands
+the
+predicates
+or
+not,
+when
+its
+intent
+is
+to
+perform
+an
+update
+using
+HTTP
+PUT.
+<del class="diff-old">The
+</del>
+<ins class="diff-chg"> The
+</ins>
+use
+of
+HTTP
+PATCH
+instead
+of
+HTTP
+PUT
+for
+update
+avoids
+this
+burden
+for
+clients
+<del class="diff-old">[
+RFC5789
+].
+</del>
+<ins class="diff-chg">[[RFC5789]].
+</ins>
+</div>
+<div id="ldpr-4_4_6" class="rule">
+4.4.6
+LDPR
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+choose
+to
+allow
+the
+creation
+of
+new
+resources
+using
+HTTP
+PUT.
+</div>
+<div id="ldpr-4_4_7" class="rule">
+4.4.7
+LDPR
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+allow
+clients
+to
+update
+resources
+without
+requiring
+detailed
+knowledge
+of
+server-specific
+constraints.
+<del class="diff-old">It
+</del>
+<ins class="diff-chg">
+This
+</ins>
+is
+<del class="diff-old">common
+for
+LDPR
+servers
+to
+put
+restrictions
+on
+representations
+–
+for
+example,
+the
+range
+of
+rdf:type
+,
+datatypes
+of
+predicates
+and
+number
+of
+occurrences
+</del>
+<ins class="diff-chg">a
+consequence
+</ins>
+of
+<del class="diff-old">predicates
+in
+triples,
+but
+servers
+should
+minimize
+those
+restrictions.
+In
+other
+words,
+LDPR
+servers
+need
+</del>
+<ins class="diff-chg">the
+requirement
+</ins>
+to
+<a href="#ldpr-4_1_13">
+enable
+simple
+<ins class="diff-new">creation
+and
+</ins>
+modification
+</a>
+of
+<del class="diff-old">LDPRs.
+Enforcement
+of
+more
+complex
+constraints
+will
+greatly
+restrict
+</del>
+<ins class="diff-chg">LPDRs.
+</ins></div></section><section><h2 id="ldpr-HTTP_DELETE"><ins class="diff-chg">
+HTTP
+DELETE
+</ins></h2><p><ins class="diff-chg">
+This
+specification
+imposes
+</ins>
+the
+<del class="diff-old">types
+of
+clients
+that
+can
+modify
+resources.
+For
+some
+server
+applications,
+excessive
+constraints
+</del>
+<ins class="diff-chg">following
+new
+requirements
+</ins>
+on
+<del class="diff-old">modification
+of
+resources
+may
+be
+required.
+4.5
+</del>
+HTTP
+DELETE
+<ins class="diff-chg">for
+LDPRs
+only
+when
+the
+LDPR
+supports
+that
+method.
+This
+specification
+does
+not
+impose
+any
+new
+requirement
+to
+support
+that
+method,
+and
+[[!HTTP11]]
+makes
+it
+optional.
+</ins></p><div id="ldpr-4_5_1" class="rule">
+4.5.1
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+remove
+the
+resource
+identified
+by
+the
+Request-URI.
+After
+a
+successful
+HTTP
+DELETE,
+a
+subsequent
+HTTP
+GET
+on
+the
+same
+Request-URI
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+result
+in
+a
+404
+(Not
+found)
+or
+410
+(Gone)
+status
+<del class="diff-old">code,
+until
+another
+resource
+is
+created
+or
+associated
+with
+the
+same
+Request-URI.
+</del>
+<ins class="diff-chg">code.
+Clients
+SHOULD
+note
+that
+servers
+MAY
+reuse
+a
+URI
+under
+some
+circumstances.
+</ins>
+</div>
+<div id="ldpr-4_5_2" class="rule">
+4.5.2
+LDPR
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+alter
+the
+state
+of
+other
+resources
+as
+a
+result
+of
+an
+HTTP
+DELETE
+request.
+For
+example,
+it
+is
+acceptable
+for
+the
+server
+to
+remove
+triples
+from
+other
+resources
+whose
+subject
+or
+object
+is
+the
+deleted
+resource.
+It
+is
+also
+acceptable
+and
+common
+for
+LDPR
+servers
+to
+not
+do
+this
+–
+behavior
+is
+server
+application
+specific.
+</div>
+<del class="diff-old">ISSUE-24
+Should
+DELETED
+resources
+remain
+deleted?
+4.6
+</del>
+</section>
+<section>
+<h2 id="ldpr-HTTP_HEAD">
+HTTP
+HEAD
+</h2>
+<div id="ldpr-4_6_1" class="rule">
+4.6.1
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+support
+the
+HTTP
+HEAD
+method.
+</div>
+<div id="ldpr-4_6_2" class="rule">
+4.6.2
+LDPR
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+indicate
+their
+support
+for
+HTTP
+Methods
+by
+responding
+to
+a
+HTTP
+HEAD
+request
+on
+the
+LDPR’s
+URL
+with
+the
+HTTP
+Method
+tokens
+in
+the
+HTTP
+response
+header
+“
+<code>
+Allow
+</code>
+”.
+</div>
+<del class="diff-old">4.7
+</del>
+</section>
+<section>
+<h2 id="ldpr-HTTP_PATCH">
+HTTP
+PATCH
+</h2>
+<p>
+<ins class="diff-chg">This
+specification
+imposes
+the
+following
+new
+requirements
+on
+HTTP
+PATCH
+for
+LDPRs
+only
+when
+the
+LDPR
+supports
+that
+method.
+This
+specification
+does
+not
+impose
+any
+new
+requirement
+to
+support
+that
+method,
+and
+[[!HTTP11]]
+makes
+it
+optional.
+</ins></p><div id="ldpr-4_7_1" class="rule">
+4.7.1
+LDPR
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+implement
+HTTP
+PATCH
+to
+allow
+modifications,
+especially
+partial
+replacement,
+of
+their
+<del class="diff-old">resources.
+[
+RFC5789
+]
+</del>
+<ins class="diff-chg">resources
+[[!RFC5789]].
+</ins>
+No
+minimal
+set
+of
+patch
+document
+formats
+is
+mandated
+by
+this
+document.
+</div>
+<div id="ldpr-4_7_2" class="rule">
+4.7.2
+LDPR
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+allow
+clients
+to
+update
+resources
+without
+requiring
+detailed
+knowledge
+of
+server-specific
+constraints.
+<del class="diff-old">It
+</del>
+<ins class="diff-chg">
+This
+</ins>
+is
+<del class="diff-old">common
+for
+LDPR
+servers
+to
+put
+restrictions
+on
+representations
+–
+for
+example,
+the
+range
+of
+rdf:type
+,
+datatypes
+of
+predicates
+and
+number
+of
+occurrences
+of
+predicates
+in
+triples
+–
+but
+server
+enforcement
+</del>
+<ins class="diff-chg">a
+consequence
+</ins>
+of
+<del class="diff-old">detailed,
+domain-specific
+constraints
+will
+greatly
+restrict
+</del>
+the
+<del class="diff-old">types
+</del>
+<ins class="diff-chg">requirement
+to
+</ins><a href="#ldpr-4_1_13"><ins class="diff-chg">
+enable
+simple
+creation
+and
+modification
+</ins></a>
+of
+<del class="diff-old">clients
+who
+can
+update
+resources.
+</del>
+<ins class="diff-chg">LPDRs.
+</ins>
+</div>
+<del class="diff-old">ISSUE-12
+</del>
+<div id="ldpr-4_7_3" class="rule">
+<ins class="diff-chg">4.7.3
+LDPR
+servers
+SHOULD
+NOT
+allow
+clients
+to
+create
+new
+resources
+using
+PATCH.
+</ins><a href="#ldpr-5_4"><ins class="diff-chg">
+POST
+(to
+a
+LDPC)
+</ins>
+</a>
+<del class="diff-old">Can
+HTTP
+PATCH
+</del>
+<ins class="diff-chg">and/or
+</ins><a href="#ldpr-4_4"><ins class="diff-chg">
+PUT
+</ins></a><ins class="diff-chg">
+should
+</ins>
+be
+used
+<del class="diff-old">for
+resource
+creation?
+</del>
+<ins class="diff-chg">as
+the
+standard
+way
+to
+create
+new
+LDPRs.
+</ins>
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/17">
+ISSUE-17
+</a>
+</div>
+changesets
+as
+a
+recommended
+PATCH
+format
+</div>
+<del class="diff-old">4.8
+Common
+Properties
+This
+section
+summarizes
+some
+well-known
+RDF
+vocabularies
+that
+must
+be
+used
+in
+Linked
+Data
+Platform
+Resources
+wherever
+a
+resource
+needs
+to
+use
+a
+predicate
+whose
+meaning
+matches
+one
+of
+these.
+For
+example,
+if
+a
+BP
+resource
+has
+a
+description
+,
+and
+the
+application
+semantic
+of
+that
+description
+is
+compatible
+with
+dcterms:description
+,
+then
+dcterms:description
+must
+be
+used.
+If
+needed,
+additional
+application-specific
+predicates
+may
+be
+used.
+A
+specification
+for
+a
+domain
+that
+is
+based
+on
+BP
+may
+require
+one
+or
+more
+of
+these
+properties
+for
+a
+particular
+resource
+type.
+The
+Range
+column
+in
+the
+tables
+below
+identify
+the
+recommended
+rdfs:range
+for
+the
+properties.
+4.8.1
+From
+Dublin
+Core
+URI:
+http://purl.org/dc/terms/
+Property
+Range/DataType
+Comment
+dcterms:contributor
+dcterms:Agent
+dcterms:creator
+dcterms:Agent
+dcterms:created
+xsd:dateTime
+dcterms:description
+</del>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<del class="diff-old">rdf:XMLLiteral
+</del>
+<a href="http://www.w3.org/2012/ldp/track/issues/27">
+<ins class="diff-chg">ISSUE-27
+</ins></a>
+<del class="diff-old">Descriptive
+text
+about
+</del>
+</div>
+<ins class="diff-chg">Should
+</ins>
+the
+<del class="diff-old">resource
+represented
+</del>
+<ins class="diff-chg">PATCH
+method
+be
+used,
+</ins>
+as
+<del class="diff-old">rich
+text
+in
+XHTML
+format.
+should
+include
+only
+content
+that
+is
+valid
+and
+suitable
+inside
+an
+XHTML
+<div>
+element.
+dcterms:identifier
+rdfs:Literal
+dcterms:modified
+xsd:dateTime
+dcterms:relation
+rdfs:Resource
+The
+HTTP
+URI
+of
+a
+related
+resource.
+This
+is
+the
+predicate
+to
+use
+when
+you
+don't
+know
+what
+else
+</del>
+<ins class="diff-chg">opposed
+</ins>
+to
+<del class="diff-old">use.
+If
+you
+know
+more
+specifically
+what
+sort
+of
+relationship
+it
+is,
+use
+</del>
+<ins class="diff-chg">POST
+with
+</ins>
+a
+<del class="diff-old">more
+specific
+predicate.
+dcterms:subject
+rdfs:Resource
+dcterms:title
+rdf:XMLLiteral
+A
+name
+</del>
+given
+<del class="diff-old">to
+the
+resource.
+Represented
+as
+rich
+text
+in
+XHTML
+format.
+should
+include
+only
+content
+that
+is
+valid
+inside
+an
+XHTML
+<span>
+element.
+The
+predicate
+dcterms:type
+should
+not
+be
+used,
+instead
+use
+rdf:type
+.
+[
+DC-RDF
+].
+4.8.2
+From
+RDF
+URI:
+http://www.w3.org/1999/02/22-rdf-syntax-ns#
+Property
+Range
+Comment
+rdf:type
+rdfs:Class
+The
+type
+or
+types
+of
+the
+resource
+4.8.3
+From
+RDF
+Schema
+URI:
+http://www.w3.org/2000/01/rdf-schema#
+Property
+Range
+Comment
+rdfs:member
+rdfs:Resource
+rdfs:label
+rdfs:Literal
+Only
+use
+this
+in
+vocabulary
+documents,
+to
+define
+the
+name
+of
+the
+vocabulary
+term.
+</del>
+<ins class="diff-chg">mime
+type?
+</ins>
+</div>
+<del class="diff-old">5.
+</del>
+</section>
+</section>
+<section>
+<h1 id="ldpc">
+Linked
+Data
+Platform
+<del class="diff-old">Container
+5.1
+</del>
+<ins class="diff-chg">Containers
+</ins></h1><section class="informative"><h2 id="ldpc-informative">
+Informative
+<del class="diff-old">This
+section
+is
+non-normative.
+</del>
+</h2>
+<p>
+Many
+HTTP
+applications
+and
+sites
+have
+organizing
+concepts
+that
+partition
+the
+overall
+space
+of
+resources
+into
+smaller
+containers.
+Blog
+posts
+are
+grouped
+into
+blogs,
+wiki
+pages
+are
+grouped
+into
+wikis,
+and
+products
+are
+grouped
+into
+catalogs.
+Each
+resource
+created
+in
+the
+application
+or
+site
+is
+created
+within
+an
+instance
+of
+one
+of
+these
+container-like
+entities,
+and
+users
+can
+list
+the
+existing
+artifacts
+within
+one.
+Containers
+answer
+some
+basic
+questions,
+which
+are:
+</p>
+<ol>
+<li>
+To
+which
+URLs
+can
+I
+POST
+to
+create
+new
+resources?
+</li>
+<li>
+Where
+can
+I
+GET
+a
+list
+of
+existing
+resources?
+</li>
+<li>
+How
+is
+the
+order
+of
+the
+container
+entries
+expressed?
+</li>
+<li>
+How
+do
+I
+get
+information
+about
+the
+members
+along
+with
+the
+container?
+</li>
+<li>
+How
+do
+I
+GET
+the
+entries
+of
+a
+large
+container
+broken
+up
+into
+pages?
+</li>
+<li>
+How
+can
+I
+ensure
+the
+resource
+data
+is
+easy
+to
+query?
+</li>
+</ol>
+<p>
+This
+document
+defines
+the
+representation
+and
+behavior
+of
+containers
+that
+address
+these
+issues.
+The
+set
+of
+members
+of
+a
+container
+is
+defined
+by
+a
+set
+of
+triples
+in
+its
+representation
+(and
+state)
+called
+the
+membership
+triples.
+The
+membership
+triples
+of
+a
+container
+all
+have
+the
+same
+subject
+and
+predicate
+–
+the
+objects
+of
+the
+membership
+triples
+define
+the
+members
+of
+the
+container.
+The
+subject
+of
+the
+membership
+triples
+is
+called
+the
+membership
+subject
+and
+the
+predicate
+is
+called
+the
+membership
+predicate.
+In
+the
+simplest
+cases,
+the
+membership
+subject
+will
+be
+the
+LDPC
+resource
+itself,
+but
+it
+does
+not
+have
+to
+be.
+The
+membership
+predicate
+is
+also
+variable
+and
+will
+often
+be
+a
+predicate
+from
+the
+server
+application
+vocabulary
+or
+the
+<code>
+rdfs:member
+</code>
+predicate.
+</p>
+<p>
+This
+document
+includes
+a
+set
+of
+guidelines
+for
+using
+POST
+to
+create
+new
+resources
+and
+add
+them
+to
+the
+list
+of
+members
+of
+a
+container.
+This
+document
+also
+explains
+how
+to
+include
+information
+about
+each
+member
+in
+the
+container’s
+own
+representation
+and
+how
+to
+paginate
+the
+container
+representation
+if
+it
+gets
+too
+big.
+</p>
+<p>
+The
+<ins class="diff-new">model
+for
+containers
+follow
+that
+of
+two
+distinct
+types:
+composition
+and
+aggregation.
+Due
+to
+composition
+constraints,
+the
+lifespan
+of
+the
+member
+resource
+must
+match
+that
+of
+its
+container
+and
+it
+a
+member
+resource
+can
+not
+be
+a
+member
+of
+more
+than
+one
+container.
+For
+both
+types
+of
+containers,
+members
+are
+only
+added
+by
+using
+POST,
+which
+both
+creates
+the
+resource
+and
+inserts
+a
+membership
+triple.
+A
+request
+to
+delete
+a
+composite
+container
+that
+has
+members,
+will
+result
+in
+all
+the
+members
+and
+the
+container
+itself
+will
+be
+deleted.
+A
+member
+resource
+is
+removed
+from
+a
+composite
+container
+by
+deleting
+the
+resource
+directly,
+which
+removes
+the
+membership
+triple
+from
+the
+container.
+</ins></p><p><ins class="diff-new">
+The
+</ins>
+following
+illustrates
+a
+very
+simple
+container
+with
+only
+three
+members
+and
+some
+information
+about
+the
+container
+(the
+fact
+that
+it
+is
+a
+container
+and
+a
+brief
+title):
+</p>
+<del class="diff-old"># The following is the representation of
+# http://example.org/container1
+</del>
+<pre class="example"># The following is the representation of
+<ins class="diff-chg"># http://example.org/container1/
+</ins>
+@prefix dcterms: <http://purl.org/dc/terms/>.
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
+@prefix ldp: <http://www.w3.org/ns/ldp#>.
+<del class="diff-old"><http://example.org/container1>
+ a ldp:Container;
+ dcterms:title "A very simple container";
+ rdfs:member
+ <http://example.org/container1/member1>,
+ <http://example.org/container1/member2>,
+<http://example.org/container1/member3>.
+</del>
+<ins class="diff-chg"><>
+ a ldp:Container;
+ dcterms:title "A very simple container";
+
+rdfs:member
+<member1>,
+<member2>,
+<member3>.
+</ins>
+</pre>
+<p>
+This
+example
+is
+very
+straightforward
+-
+the
+membership
+predicate
+is
+<code>
+rdfs:member
+</code>
+and
+the
+membership
+subject
+is
+the
+container
+itself.
+A
+POST
+to
+this
+container
+will
+create
+a
+new
+resource
+and
+add
+it
+to
+the
+list
+of
+members
+by
+adding
+a
+new
+membership
+triple
+to
+the
+container.
+</p>
+<p>
+Sometimes
+it
+is
+useful
+to
+use
+a
+subject
+other
+than
+the
+container
+itself
+as
+the
+membership
+subject
+and
+to
+use
+a
+predicate
+other
+than
+<code>
+rdfs:member
+</code>
+as
+the
+membership
+predicate,
+as
+illustrated
+below.
+</p>
+<del class="diff-old"># The following is the representation of
+# http://example.org/netWorth/nw1/assetContainer
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
+</del>
+<pre class="example" id="ldpc-ex-membership-subj">
+<ins class="diff-chg"># The following is the representation of
+# http://example.org/netWorth/nw1/assetContainer/
+</ins>
+@prefix ldp: <http://www.w3.org/ns/ldp#>.
+@prefix o: <http://example.org/ontology/>.
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer>
+ a ldp:Container;
+</del>
+<ins class="diff-chg"><>
+ a ldp:Container;
+</ins>
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+<del class="diff-old"> ldp:membershipPredicate o:asset.
+</del>
+<ins class="diff-chg"> ldp:membershipPredicate o:asset.
+</ins>
+<http://example.org/netWorth/nw1>
+<del class="diff-old"> a o:NetWorth;
+ o:asset
+ <http://example.org/netWorth/nw1/assetContainer/a1>,
+<http://example.org/netWorth/nw1/assetContainer/a2>.
+</del>
+<ins class="diff-chg"> a o:NetWorth;
+o:asset
+<a1>,
+<a2>.
+</ins>
+</pre>
+<p>
+The
+essential
+structure
+of
+the
+container
+is
+the
+same,
+but
+in
+this
+example,
+the
+membership
+subject
+is
+not
+the
+container
+itself
+–
+it
+is
+a
+separate
+net
+worth
+resource.
+The
+membership
+predicate
+is
+<code>
+o:asset
+</code>
+–
+a
+predicate
+from
+the
+domain
+model.
+A
+POST
+to
+this
+container
+will
+create
+a
+new
+asset
+and
+add
+it
+to
+the
+list
+of
+members
+by
+adding
+a
+new
+membership
+triple
+to
+the
+container.
+You
+might
+wonder
+why
+we
+didn’t
+just
+make
+<code>
+http://example.org/netWorth/nw1
+</code>
+a
+container
+and
+POST
+the
+new
+asset
+directly
+there.
+That
+would
+be
+a
+fine
+design
+if
+<code>
+http://example.org/netWorth/nw1
+</code>
+had
+only
+assets,
+but
+if
+it
+has
+separate
+predicates
+for
+assets
+and
+liabilities,
+that
+design
+will
+not
+work
+because
+it
+is
+unspecified
+to
+which
+predicate
+the
+POST
+should
+add
+a
+membership
+triple.
+Having
+separate
+<code>
+<del class="diff-old">http://example.org/netWorth/nw1/assetContainer
+</del>
+<ins class="diff-chg">http://example.org/netWorth/nw1/assetContainer/
+</ins>
+</code>
+and
+<code>
+<del class="diff-old">http://example.org/netWorth/nw1/liabilityContainer
+</del>
+<ins class="diff-chg">http://example.org/netWorth/nw1/liabilityContainer/
+</ins>
+</code>
+container
+resources
+allows
+both
+assets
+and
+liabilities
+to
+be
+created.
+</p>
+<p>
+In
+this
+example,
+clients
+cannot
+simply
+guess
+which
+resource
+is
+the
+membership
+subject
+and
+which
+predicate
+is
+the
+membership
+predicate,
+so
+the
+example
+includes
+this
+information
+in
+triples
+whose
+subject
+is
+the
+LDPC
+resource
+itself.
+</p>
+<div id="ldpc-member_data" class="rule">
+5.1.1
+Container
+Member
+Information
+</div>
+<em>
+This
+section
+is
+non-normative
+</em>
+<p>
+In
+many
+–
+perhaps
+most
+–
+applications
+involving
+containers,
+it
+is
+desirable
+for
+the
+client
+to
+be
+able
+to
+get
+information
+about
+each
+container
+member
+without
+having
+to
+do
+a
+GET
+on
+each
+one.
+LDPC
+allows
+servers
+to
+include
+this
+information
+directly
+in
+the
+representation
+of
+the
+container.
+The
+server
+decides
+the
+amount
+of
+data
+about
+each
+member
+that
+is
+provided.
+Some
+common
+strategies
+include
+providing
+a
+fixed
+number
+of
+standard
+properties,
+or
+providing
+the
+entire
+RDF
+representation
+of
+each
+member
+resource,
+or
+providing
+nothing.
+The
+server
+application
+domain
+and
+its
+use-cases
+will
+determine
+how
+much
+information
+is
+required.
+</p>
+<p>
+Continuing
+on
+from
+the
+net
+worth
+example,
+there
+will
+be
+additional
+triples
+for
+the
+member
+resources
+(assets)
+in
+the
+representation:
+</p>
+<del class="diff-old"># The following is the representation of
+# http://example.org/netWorth/nw1/assetContainer
+</del>
+<pre class="example"># The following is the representation of
+<ins class="diff-chg"># http://example.org/netWorth/nw1/assetContainer/
+</ins>
+@prefix dcterms: <http://purl.org/dc/terms/>.
+<del class="diff-old">@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
+</del>
+@prefix ldp: <http://www.w3.org/ns/ldp#>.
+@prefix o: <http://example.org/ontology/>.
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer>
+</del>
+<ins class="diff-chg"><>
+</ins>
+ a ldp:Container;
+<del class="diff-old"> dcterms:title "The assets of JohnZSmith";
+</del>
+<ins class="diff-chg"> dcterms:title "The assets of JohnZSmith";
+</ins>
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+ ldp:membershipPredicate o:asset.
+<http://example.org/netWorth/nw1>
+<del class="diff-old"> a o:NetWorth;
+ o:asset
+ <http://example.org/netWorth/nw1/assetContainer/a1>,
+ <http://example.org/netWorth/nw1/assetContainer/a3>,
+ <http://example.org/netWorth/nw1/assetContainer/a2>.
+</del>
+<ins class="diff-chg"> a o:NetWorth;
+ o:asset <a1>, <a3>, <a2>.
+</ins>
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer/a1>
+ a o:Stock;
+ o:value 10000.
+<http://example.org/netWorth/nw1/assetContainer/a2>
+ a o:Bond;
+ o:value 20000.
+<http://example.org/netWorth/nw1/assetContainer/a3>
+ a o:RealEstateHolding;
+o:value
+</del>
+<ins class="diff-chg"><a1>
+ a o:Stock;
+ o:value 10000.
+<a2>
+ a o:Bond;
+ o:value 20000.
+<a3>
+ a o:RealEstateHolding;
+
+ o:value
+</ins>
+300000.
+</pre>
+<del class="diff-old">5.1.2
+Retrieving
+</del>
+<div id="ldpc-get_non-member_props" class="rule">
+<ins class="diff-chg">5.1.2 Retrieving
+</ins>
+Only
+Non-member
+Properties
+</div>
+<em>
+This
+section
+is
+non-normative
+</em>
+<p>
+The
+representation
+of
+a
+container
+that
+has
+many
+members
+will
+be
+large.
+There
+are
+several
+important
+cases
+where
+clients
+need
+to
+access
+only
+the
+non-member
+properties
+of
+the
+container.
+Since
+retrieving
+the
+whole
+container
+representation
+to
+get
+this
+information
+may
+be
+onerous
+for
+clients
+and
+cause
+unnecessary
+overhead
+on
+servers,
+it
+is
+desired
+to
+define
+a
+way
+to
+retrieve
+only
+the
+non-member
+property
+values.
+Defining
+for
+each
+LDPC
+a
+corresponding
+resource,
+called
+the
+“non-member
+resource”,
+whose
+state
+is
+a
+subset
+of
+the
+state
+of
+the
+container,
+does
+this.
+</p>
+<p>
+The
+example
+listed
+here
+only
+show
+a
+simple
+case
+where
+only
+a
+few
+simple
+non-member
+properties
+are
+retrieved.
+In
+real
+world
+situations
+more
+complex
+cases
+are
+likely,
+such
+as
+those
+that
+add
+other
+predicates
+to
+containers,
+for
+example
+providing
+validation
+information
+and
+associating
+SPARQL
+endpoints.
+<del class="diff-old">[
+SPARQL-QUERY
+]
+</del>
+<ins class="diff-chg">[[SPARQL-QUERY]]
+</ins>
+</p>
+<p>
+Here
+is
+an
+example
+requesting
+the
+non-member
+properties
+of
+a
+container
+identified
+by
+the
+URL
+<code>
+<del class="diff-old">http://example.org/container1
+</del>
+<ins class="diff-chg">http://example.org/container1/
+</ins>
+</code>
+and
+adding
+the
+query
+string
+<code>
+?non-member-properties
+</code>
+:
+</p>
+<p>
+Request:
+</p>
+<del class="diff-old">GET /container1?non-member-properties HTTP/1.1
+</del>
+<pre class="example">GET /container1?non-member-properties HTTP/1.1
+Host: example.org
+<del class="diff-old">Accept:
+text/turtle;
+charset=UTF-8
+</del>
+<ins class="diff-chg">Accept: text/turtle; charset=UTF-8
+</ins>
+</pre>
+<p>
+Response:
+</p>
+<del class="diff-old">HTTP/1.1 200 OK
+Content-Type: text/turtle; chartset=UTF-8
+ETag: "_87e52ce291112"
+</del>
+<pre class="example">HTTP/1.1 200 OK
+<ins class="diff-chg">Content-Type: text/turtle; charset=UTF-8
+ETag: "_87e52ce291112"
+</ins>
+Content-Length: 325
+@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
+@prefix dcterms: <http://purl.org/dc/terms/>.
+@prefix ldp: <http://www.w3.org/ns/ldp#>.
+<del class="diff-old"><http://example.org/container1>
+</del>
+<ins class="diff-chg"><http://example.org/container1/>
+</ins>
+ a ldp:Container;
+<del class="diff-old"> dcterms:title "A Linked Data Platform Container of Acme Resources";
+ ldp:membershipPredicate rdfs:member;
+</del>
+<ins class="diff-chg"> dcterms:title "A Linked Data Platform Container of Acme Resources";
+ ldp:membershipPredicate rdfs:member;
+</ins>
+dcterms:publisher
+<http://acme.com/>.
+</pre>
+<div id="ldpc-paging" class="rule">
+5.1.3
+Paging
+</div>
+<em>
+This
+section
+is
+non-normative
+</em>
+<p>
+It
+sometimes
+happens
+that
+a
+container
+is
+too
+large
+to
+reasonably
+transmit
+its
+representation
+in
+a
+single
+HTTP
+response.
+This
+will
+be
+especially
+true
+if
+the
+container
+representation
+includes
+many
+triples
+from
+the
+representations
+of
+its
+members.
+A
+client
+may
+anticipate
+that
+a
+container
+will
+be
+too
+large
+-
+for
+example,
+a
+client
+tool
+that
+accesses
+defects
+may
+assume
+that
+an
+individual
+defect
+will
+usually
+be
+of
+sufficiently
+constrained
+size
+that
+it
+makes
+sense
+to
+request
+all
+of
+it
+at
+once,
+but
+that
+the
+container
+of
+all
+the
+defects
+ever
+created
+will
+typically
+be
+too
+big.
+Alternatively,
+a
+server
+may
+recognize
+that
+a
+container
+that
+has
+been
+requested
+is
+too
+big
+to
+return
+in
+a
+single
+message.
+</p>
+<p>
+To
+address
+this
+problem,
+LDPCs
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">should
+</ins>
+support
+a
+technique
+called
+Paging.
+<del class="diff-old">Paging
+</del>
+<ins class="diff-chg"> Paging
+</ins>
+can
+be
+achieved
+with
+a
+simple
+RDF
+pattern.
+For
+each
+container
+resource,
+<code>
+<containerURL>
+</code>,
+we
+define
+a
+new
+resource
+<code>
+<containerURL>?firstPage
+</code>.
+The
+triples
+in
+the
+representation
+of
+<code>
+<containerURL>?firstPage
+</code>
+are
+a
+subset
+of
+the
+triples
+in
+<code>
+<containerURL>
+</code>
+-
+same
+subject,
+predicate
+and
+object.
+</p>
+<p>
+LDPC
+servers
+may
+respond
+to
+requests
+for
+a
+container
+by
+redirecting
+the
+client
+to
+the
+first
+page
+resource
+–
+using
+a
+303
+“See
+Other”
+redirect
+to
+the
+actual
+URL
+for
+the
+page
+resource.
+</p>
+<p>
+Continuing
+on
+from
+the
+member
+information
+from
+the
+JohnZSmith
+net
+worth
+example,
+we’ll
+split
+the
+response
+across
+two
+pages.
+<del class="diff-old">The
+</del>
+<ins class="diff-chg"> The
+</ins>
+client
+requests
+the
+first
+page
+as
+<code>
+<del class="diff-old">http://example.org/netWorth/nw1/assetContainer?firstPage
+</del>
+<ins class="diff-chg">http://example.org/netWorth/nw1/assetContainer/?firstPage
+</ins>
+</code>:
+</p>
+<del class="diff-old"># The following is the representation of
+# http://example.org/netWorth/nw1/assetContainer?firstPage
+</del>
+<pre class="example"># The following is the representation of
+<ins class="diff-chg"># http://example.org/netWorth/nw1/assetContainer/?firstPage
+</ins>
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
+@prefix dcterms: <http://purl.org/dc/terms/>.
+@prefix ldp: <http://www.w3.org/ns/ldp#>.
+@prefix o: <http://example.org/ontology/>.
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer>
+</del>
+<ins class="diff-chg"><http://example.org/netWorth/nw1/assetContainer/>
+</ins>
+ a ldp:Container;
+<del class="diff-old"> dcterms:title "The assets of JohnZSmith";
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+ ldp:membershipPredicate o:asset.
+</del>
+<ins class="diff-chg"> dcterms:title "The assets of JohnZSmith";
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+ ldp:membershipPredicate o:asset.
+</ins>
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer?firstPage>
+</del>
+<ins class="diff-chg"><http://example.org/netWorth/nw1/assetContainer/?firstPage>
+</ins>
+ a ldp:Page;
+<del class="diff-old"> ldp:pageOf <http://example.org/netWorth/nw1/assetContainer>;
+ ldp:nextPage <http://example.org/netWorth/nw1/assetContainer?p=2>.
+</del>
+<ins class="diff-chg"> ldp:pageOf <http://example.org/netWorth/nw1/assetContainer/>;
+ ldp:nextPage <http://example.org/netWorth/nw1/assetContainer/?p=2>.
+</ins>
+
+<http://example.org/netWorth/nw1>
+<del class="diff-old"> a o:NetWorth;
+</del>
+<ins class="diff-chg"> a o:NetWorth;
+</ins>
+ o:asset
+ <http://example.org/netWorth/nw1/assetContainer/a1>,
+ <http://example.org/netWorth/nw1/assetContainer/a4>,
+ <http://example.org/netWorth/nw1/assetContainer/a3>,
+ <http://example.org/netWorth/nw1/assetContainer/a2>.
+<http://example.org/netWorth/nw1/assetContainer/a1>
+<del class="diff-old"> a o:Stock;
+ o:value 100.00.
+</del>
+<ins class="diff-chg"> a o:Stock;
+ o:value 100.00.
+</ins>
+<http://example.org/netWorth/nw1/assetContainer/a2>
+<del class="diff-old"> a o:Cash;
+ o:value 50.00.
+</del>
+<ins class="diff-chg"> a o:Cash;
+ o:value 50.00.
+</ins>
+#
+server
+initially
+supplied
+no
+data
+for
+a3
+and
+a4
+in
+this
+response
+</pre>
+<p>
+The
+following
+example
+is
+the
+result
+of
+retrieving
+the
+representation
+for
+the
+next
+page:
+</p>
+<del class="diff-old"># The following is the representation of
+# http://example.org/netWorth/nw1/assetContainer?p=2
+</del>
+<pre class="example"># The following is the representation of
+<ins class="diff-chg"># http://example.org/netWorth/nw1/assetContainer/?p=2
+</ins>
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
+@prefix dcterms: <http://purl.org/dc/terms/>.
+@prefix ldp: <http://www.w3.org/ns/ldp#>.
+@prefix o: <http://example.org/ontology/>.
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer>
+</del>
+<ins class="diff-chg"><http://example.org/netWorth/nw1/assetContainer/>
+</ins>
+ a ldp:Container;
+<del class="diff-old"> dcterms:title "The assets of JohnZSmith";
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+ ldp:membershipPredicate o:asset.
+</del>
+<ins class="diff-chg"> dcterms:title "The assets of JohnZSmith";
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+ ldp:membershipPredicate o:asset.
+</ins>
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer?p=2>
+ a ldp:Page;
+ ldp:pageOf <http://example.org/netWorth/nw1/assetContainer>;
+ ldp:nextPage rdf:nil.
+</del>
+<ins class="diff-chg"><http://example.org/netWorth/nw1/assetContainer/?p=2>
+ a ldp:Page;
+ ldp:pageOf <http://example.org/netWorth/nw1/assetContainer/>;
+ ldp:nextPage rdf:nil.
+</ins>
+<http://example.org/netWorth/nw1>
+<del class="diff-old"> a o:NetWorth;
+</del>
+<ins class="diff-chg"> a o:NetWorth;
+</ins>
+ o:asset
+ <http://example.org/netWorth/nw1/assetContainer/a5>.
+<http://example.org/netWorth/nw1/assetContainer/a5>
+ a o:Stock;
+<del class="diff-old"> dcterms:title "Big Co.";
+</del>
+<ins class="diff-chg"> dcterms:title "Big Co.";
+</ins>
+o:value
+200.02.
+</pre>
+<p>
+In
+this
+example,
+there
+is
+only
+one
+member
+in
+the
+container
+in
+the
+final
+page.
+<del class="diff-old">To
+</del>
+<ins class="diff-chg"> To
+</ins>
+indicate
+this
+is
+the
+last
+page,
+a
+value
+of
+<code>
+rdf:nil
+</code>
+is
+used
+for
+the
+<code>
+ldp:nextPage
+</code>
+predicate
+of
+the
+page
+resource.
+</p>
+<p>
+LDPC
+guarantees
+that
+any
+and
+all
+the
+triples
+about
+the
+members
+will
+be
+on
+the
+same
+page
+as
+the
+membership
+triple
+for
+the
+member.
+</p>
+<div id="ldpc-ordering" class="rule">
+5.1.4
+Ordering
+</div>
+<em>
+This
+section
+is
+non-normative
+</em>
+<p>
+There
+are
+many
+cases
+where
+an
+ordering
+of
+the
+members
+of
+the
+container
+is
+important.
+LDPC
+does
+not
+provide
+any
+particular
+support
+for
+server
+ordering
+of
+members
+in
+containers,
+because
+any
+client
+can
+order
+the
+members
+in
+any
+way
+it
+chooses
+based
+on
+the
+value
+of
+any
+available
+property
+of
+the
+members.
+In
+the
+example
+below,
+the
+value
+of
+the
+<code>
+o:value
+</code>
+predicate
+is
+present
+for
+each
+member,
+so
+the
+client
+can
+easily
+order
+the
+members
+according
+to
+the
+value
+of
+that
+property.
+In
+this
+way,
+LDPC
+avoids
+the
+use
+of
+RDF
+constructs
+like
+Seq
+and
+List
+for
+expressing
+order.
+</p>
+<p>
+Order
+only
+becomes
+important
+for
+LDPC
+servers
+when
+containers
+are
+paginated.
+If
+the
+server
+does
+not
+respect
+ordering
+when
+constructing
+pages,
+the
+client
+is
+forced
+to
+retrieve
+all
+pages
+before
+sorting
+the
+members,
+which
+would
+defeat
+the
+purpose
+of
+pagination.
+In
+cases
+where
+ordering
+is
+important,
+a
+LDPC
+server
+exposes
+all
+the
+members
+on
+a
+page
+with
+a
+higher
+sort
+order
+than
+all
+members
+on
+the
+previous
+page
+and
+lower
+sort
+order
+than
+all
+the
+members
+on
+the
+next
+page.
+The
+LDPC
+specification
+provides
+a
+predicate
+-
+<code>
+ldp:containerSortPredicates
+</code>
+-
+that
+the
+server
+may
+use
+to
+communicate
+to
+the
+client
+which
+predicates
+were
+used
+for
+page
+ordering.
+Multiple
+predicate
+values
+may
+have
+been
+used
+for
+sorting,
+so
+the
+value
+of
+this
+predicate
+is
+an
+ordered
+list.
+</p>
+<p>
+Here
+is
+an
+example
+container
+described
+previously,
+with
+representation
+for
+ordering
+of
+the
+assets:
+</p>
+<del class="diff-old"># The following is the ordered representation of
+# http://example.org/netWorth/nw1/assetContainer
+@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
+</del>
+<pre class="example"># The following is the ordered representation of
+<ins class="diff-chg"># http://example.org/netWorth/nw1/assetContainer/
+</ins>
+@prefix dcterms: <http://purl.org/dc/terms/>.
+@prefix ldp: <http://www.w3.org/ns/ldp#>.
+@prefix o: <http://example.org/ontology/>.
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer>
+ a ldp:Container;
+ dcterms:title "The assets of JohnZSmith";
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+ ldp:membershipPredicate o:asset.
+</del>
+<ins class="diff-chg"><>
+ a ldp:Container;
+ dcterms:title "The assets of JohnZSmith";
+ ldp:membershipSubject <http://example.org/netWorth/nw1>;
+ ldp:membershipPredicate o:asset.
+</ins>
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer?firstPage>
+</del>
+<ins class="diff-chg"><?firstPage>
+</ins>
+ a ldp:Page;
+<del class="diff-old"> ldp:pageOf <http://example.org/netWorth/nw1/assetContainer>;
+</del>
+<ins class="diff-chg"> ldp:pageOf <>;
+</ins>
+ ldp:containerSortPredicates (o:value).
+<http://example.org/netWorth/nw1>
+<del class="diff-old"> a o:NetWorth;
+ o:asset
+ <http://example.org/netWorth/nw1/assetContainer/a1>,
+ <http://example.org/netWorth/nw1/assetContainer/a3>,
+ <http://example.org/netWorth/nw1/assetContainer/a2>.
+</del>
+<ins class="diff-chg"> a o:NetWorth;
+ o:asset <a1>, <a3>, <a2>.
+</ins>
+<del class="diff-old"><http://example.org/netWorth/nw1/assetContainer/a1>
+ a o:Stock;
+ o:value 100.00.
+<http://example.org/netWorth/nw1/assetContainer/a2>
+ a o:Cash;
+ o:value 50.00.
+<http://example.org/netWorth/nw1/assetContainer/a3>
+ a o:RealEstateHolding;
+o:value
+</del>
+<ins class="diff-chg"><a1>
+ a o:Stock;
+ o:value 100.00.
+<a2>
+ a o:Cash;
+ o:value 50.00.
+<a3>
+ a o:RealEstateHolding;
+
+ o:value
+</ins>
+300000.
+</pre>
+<p>
+As
+you
+can
+see
+by
+the
+addition
+of
+the
+<code>
+ldp:containerSortPredicates
+</code>
+predicate,
+the
+<code>
+o:value
+</code>
+predicate
+is
+used
+to
+define
+the
+ordering
+of
+the
+results.
+<del class="diff-old">It
+</del>
+<ins class="diff-chg"> It
+</ins>
+is
+up
+to
+the
+domain
+model
+and
+server
+to
+determine
+the
+appropriate
+predicate
+to
+indicate
+the
+resource’s
+order
+within
+a
+page,
+and
+up
+to
+the
+client
+receiving
+this
+representation
+to
+use
+that
+order
+in
+whatever
+way
+is
+appropriate,
+for
+example
+to
+sort
+the
+data
+prior
+to
+presentation
+on
+a
+user
+interface.
+</p>
+<del class="diff-old">5.2
+</del>
+</section>
+<section>
+<h2 id="ldpc-general">
+General
+</h2>
+<p>
+<ins class="diff-new">The
+Linked
+Data
+Platform
+does
+not
+define
+how
+clients
+discover
+</ins><dfn>
+<del class="diff-old">This
+section
+is
+non-normative.
+</del>
+<abbr title="Linked Data Platform Containers">
+<ins class="diff-chg">LDPCs
+</ins></abbr>
+</dfn>.
+</p>
+<div id="ldpc-5_2_1" class="rule">
+5.2.1
+LDPC
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+also
+be
+conformant
+LDPR
+servers.
+A
+Linked
+Data
+Platform
+Container
+<del class="diff-old">is
+a
+resource
+that
+is
+</del>
+<ins class="diff-chg">MUST
+also
+be
+</ins>
+a
+<ins class="diff-new">conformant
+</ins>
+Linked
+Data
+Platform
+Resource.
+</div>
+<div id="ldpc-5_2_2" class="rule">
+5.2.2
+The
+same
+<del class="diff-old">resource
+may
+</del>
+<ins class="diff-chg">resource,
+identified
+by
+its
+canonical
+URI,
+MUST
+</ins>
+be
+a
+member
+of
+<del class="diff-old">multiple
+LDPCs.
+This
+happens
+commonly
+if
+one
+container
+is
+</del>
+<ins class="diff-chg">only
+</ins>
+a
+<del class="diff-old">view
+onto
+</del>
+<ins class="diff-chg">single
+LDPC.
+The
+same
+resource
+can
+not
+be
+</ins>
+a
+<del class="diff-old">larger
+container.
+</del>
+<ins class="diff-chg">member
+of
+mutliple
+LDPCs.
+</ins>
+</div>
+<div id="ldpc-5_2_3" class="rule">
+5.2.3
+The
+<del class="diff-old">representation
+</del>
+<ins class="diff-chg">state
+</ins>
+of
+a
+LDPC
+includes
+information
+about
+which
+resources
+are
+its
+members.
+<del class="diff-old">The
+set
+of
+members
+of
+a
+container
+is
+a
+set
+of
+triples
+in
+its
+representation
+(and
+state)
+called
+the
+membership
+triples.
+The
+membership
+triples
+of
+a
+container
+all
+have
+the
+same
+subject
+and
+predicate
+–
+the
+objects
+of
+the
+membership
+triples
+define
+the
+members
+of
+the
+container.
+The
+subject
+of
+the
+membership
+triples
+is
+called
+the
+membership
+subject
+and
+the
+predicate
+is
+called
+the
+membership
+predicate.
+</del>
+In
+the
+simplest
+cases,
+the
+membership
+subject
+will
+be
+the
+LDPC
+resource
+itself,
+but
+it
+does
+not
+have
+to
+be.
+The
+membership
+predicate
+is
+also
+variable
+and
+will
+often
+be
+a
+predicate
+from
+the
+server
+application
+vocabulary.
+If
+there
+is
+no
+obvious
+predicate
+from
+the
+server
+application
+vocabulary
+to
+use,
+LDPC
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+use
+the
+<code>
+rdfs:member
+</code>
+predicate.
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/21">
+ISSUE-21
+</a>
+</div>
+container
+affordances
+</div>
+</div>
+<div id="ldpc-5_2_4" class="rule">
+5.2.4
+A
+LDPC
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+contain
+one
+triple
+<del class="diff-old">for
+</del>
+<ins class="diff-chg">containing
+</ins>
+the
+<code>
+ldp:membershipSubject
+</code>
+predicate
+<del class="diff-old">that
+indicates
+the
+subject
+of
+</del>
+<ins class="diff-chg">when
+</ins>
+the
+membership
+<del class="diff-old">triples
+when
+container
+</del>
+subject
+is
+not
+the
+LDPC
+itself.
+<ins class="diff-new">This
+triple's
+object
+provides
+clients
+with
+the
+LDPC's
+membership
+subject
+URI.
+</ins>
+</div>
+<div id="ldpc-5_2_5" class="rule">
+5.2.5
+A
+LDPC
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+contain
+one
+triple
+<del class="diff-old">for
+</del>
+<ins class="diff-chg">containing
+</ins>
+the
+<code>
+ldp:membershipPredicate
+</code>
+predicate
+<del class="diff-old">that
+indicates
+the
+predicate
+of
+the
+membership
+triple
+</del>
+when
+the
+container
+predicate
+is
+not
+<code>
+rdfs:member
+</code>.
+<ins class="diff-new">This
+triple's
+object
+provides
+clients
+with
+the
+LDPC's
+membership
+predicate
+URI.
+</ins>
+</div>
+<div id="ldpc-5_2_6" class="rule">
+5.2.6
+The
+representation
+of
+a
+LDPC
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+include
+an
+arbitrary
+number
+of
+additional
+triples
+whose
+subjects
+are
+the
+members
+of
+the
+container,
+or
+that
+are
+from
+the
+representations
+of
+the
+members
+(if
+they
+have
+RDF
+representations).
+This
+allows
+a
+LDPC
+server
+to
+provide
+clients
+with
+information
+about
+the
+members
+without
+the
+client
+having
+to
+do
+a
+GET
+on
+each
+member
+individually.
+<del class="diff-old">See
+</del>
+<ins class="diff-chg"> See
+</ins>
+section
+<a href="#ldpc-member_data">
+5.1.1
+Container
+Member
+Information
+</a>
+for
+additional
+details.
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/13">
+ISSUE-13
+</a>
+</div>
+Include
+clarifications
+about
+LDPC
+representations
+that
+include
+member
+triples
+</div>
+</div>
+<div id="ldpc-5_2_7" class="rule">
+5.2.7
+The
+representation
+of
+a
+LDPC
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+have
+<code>
+rdf:type
+</code>
+of
+<code>
+ldp:Container
+</code>,
+but
+it
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+have
+additional
+<code>
+rdf:type
+</code>
+s.
+</div>
+<div id="ldpc-5_2_8" class="rule">
+5.2.8
+LDPCs
+<del class="diff-old">should
+not
+</del>
+<ins class="diff-chg">SHOULD
+NOT
+</ins>
+use
+RDF
+container
+types
+<code>
+rdf:Bag
+</code>,
+<code>
+rdf:Seq
+</code>
+<del class="diff-old">and
+</del>
+<ins class="diff-chg">or
+</ins>
+<code>
+rdf:List
+</code>.
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<del class="diff-old">ISSUE-3
+</del>
+<a href="http://www.w3.org/2012/ldp/track/issues/38">
+<ins class="diff-chg">ISSUE-38
+</ins>
+</a>
+</div>
+<del class="diff-old">Do
+LDPC
+versions
+get
+managed
+in
+a
+systematic,
+discoverable
+way?
+</del>
+<ins class="diff-chg">filtered
+representations
+and
+inlining
+</ins>
+</div>
+<del class="diff-old">5.3
+</del>
+</section>
+<section>
+<h2 id="ldpc-HTTP_GET">
+HTTP
+GET
+</h2>
+<div id="ldpc-5_3_1" class="rule">
+5.3.1
+The
+representation
+of
+a
+LDPC
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+contain
+a
+set
+of
+triples
+with
+a
+consistent
+subject
+and
+predicate
+whose
+objects
+indicate
+members
+of
+the
+container.
+The
+subject
+of
+the
+triples
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+be
+the
+container
+itself
+or
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+be
+another
+resource
+(as
+in
+the
+<a href="#ldpc-ex-membership-subj">
+example
+<del class="diff-old">above).
+See
+</del>
+</a>
+<ins class="diff-chg">).
+ See
+</ins>
+also
+<a href="#ldpc-5_2_3">
+5.2.3
+</a>.
+</div>
+<div id="ldpc-5_3_2" class="rule">
+5.3.2
+LDPC
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+support
+requests
+for
+information
+about
+a
+known
+LDPC
+without
+retrieving
+a
+full
+representation
+including
+all
+of
+its
+members,
+by
+the
+existence
+of
+the
+token
+<del class="diff-old">"
+</del>
+<ins class="diff-chg">"
+</ins>
+<code>
+non-member-properties
+</code>
+<del class="diff-old">"
+</del>
+<ins class="diff-chg">"
+</ins>
+on
+the
+query
+component
+of
+the
+LDPC
+URL.
+<del class="diff-old">For
+</del>
+<ins class="diff-chg"> For
+</ins>
+example,
+if
+there
+is
+a
+LDPC
+URL
+<code>
+<containerURL>,
+</code>
+the
+URL
+to
+request
+the
+non-membership
+properties
+would
+be
+<code>
+<containerURL>?non-member-properties
+</code>.
+<del class="diff-old">See
+</del>
+<ins class="diff-chg"> See
+</ins>
+section
+<a href="#ldpc-get_non_member_props">
+5.1.2
+Retrieving
+Non-member
+Properties
+</a>
+for
+additional
+details.
+A
+LDPC
+server
+that
+does
+not
+support
+a
+request
+to
+retrieve
+non-member
+resource
+properties
+via
+a
+Request-URI
+of
+“
+<code>
+<containerURL>?non-member-properties
+</code>
+”,
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+return
+a
+HTTP
+status
+code
+404
+(Not
+Found).
+<ins class="diff-new">A
+LDPC
+server
+that
+supports
+a
+request
+to
+retrieve
+non-member
+resource
+properties
+via
+a
+different
+Request-URI
+than
+“
+</ins><code><ins class="diff-new">
+<containerURL>?non-member-properties
+</ins></code><ins class="diff-new">
+”,
+MUST
+return
+a
+HTTP
+Redirection
+3xx
+status
+code
+such
+as
+301
+(Moved
+Permanently)
+or
+302
+(Found).
+</ins>
+</div>
+<div id="ldpc-5_3_3" class="rule">
+5.3.3
+A
+LDPC
+server
+that
+does
+not
+support
+a
+request
+to
+retrieve
+the
+first
+page
+resource
+representation
+<del class="diff-old">via
+</del>
+<ins class="diff-chg">from
+</ins>
+a
+known
+LDPC
+<del class="diff-old">as
+</del>
+<ins class="diff-chg">whose
+URL
+is
+</ins>
+“
+<code>
+<containerURL>
+</code>
+<del class="diff-old">”,
+</del>
+<ins class="diff-chg">”
+by
+using
+</ins>
+the
+Request-URI
+<del class="diff-old">of
+</del>
+“
+<code>
+<containerURL>?firstPage
+</code>
+”,
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+return
+a
+HTTP
+status
+code
+404
+(Not
+Found).
+<ins class="diff-new">A
+LDPC
+server
+that
+supports
+that
+request
+using
+a
+different
+Request-URI
+than
+“
+</ins><code><ins class="diff-new">
+<containerURL>?firstPage
+</ins></code><ins class="diff-new">
+”,
+MUST
+return
+a
+HTTP
+Redirection
+3xx
+status
+code
+such
+as
+301
+(Moved
+Permanently)
+or
+302
+(Found).
+</ins>
+</div>
+<div id="ldpc-5_3_4" class="rule">
+5.3.4
+LDPC
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+support
+requests
+for
+splitting
+large
+LDPCs
+into
+pages
+indicated
+by
+a
+client
+supplying
+the
+token
+“
+<code>
+firstPage
+</code>
+”
+on
+the
+query
+component
+of
+the
+LDPC
+URL.
+For
+example,
+if
+there
+is
+a
+LDPC
+URL
+<code>
+<containerURL>
+</code>,
+the
+URL
+to
+request
+the
+first
+page
+would
+be
+<code>
+<containerURL>?firstPage
+</code>.
+The
+representation
+for
+any
+page,
+including
+the
+first,
+will
+include
+the
+URL
+for
+the
+next
+<del class="diff-old">page.
+See
+</del>
+<ins class="diff-chg">page. See
+</ins>
+section
+<a href="#ldpc-paging">
+5.1.3
+titled
+“Paging”
+</a>
+for
+additional
+details.
+</div>
+<div id="ldpc-5_3_5" class="rule">
+5.3.5
+LDPC
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+split
+the
+response
+representation
+of
+a
+LDPC
+regardless
+of
+what
+the
+client
+requested
+(such
+as
+when
+a
+client
+omits
+a
+“
+<code>
+firstPage
+</code>
+”
+query
+component
+of
+a
+request
+URL).
+This
+is
+also
+known
+as
+server-initiated
+paging.
+See
+section
+<a href="#ldpc-paging">
+5.1.3
+Paging
+</a>
+for
+additional
+details.
+</div>
+<div id="ldpc-5_3_5_1" class="rule">
+5.3.5.1
+LDPC
+servers
+that
+initiate
+paging
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+respond
+to
+requests
+for
+a
+LDPC
+by
+redirecting
+the
+client
+to
+the
+page
+resource
+–
+using
+a
+303
+“See
+Other”
+redirect
+to
+the
+actual
+URL
+for
+the
+page
+resource.
+</div>
+<div id="ldpc-5_3_6" class="rule">
+5.3.6
+LDPC
+servers
+that
+support
+paging
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+include
+in
+the
+page
+representation
+a
+representation
+for
+the
+LDPC,
+such
+that:
+</div>
+<div id="ldpc-5_3_6_1" class="rule">
+5.3.6.1
+The
+page
+resource
+representation
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+have
+one
+triple
+to
+indicate
+its
+type,
+whose
+subject
+is
+the
+URL
+of
+the
+page,
+whose
+predicate
+is
+<code>
+rdf:type
+</code>
+and
+object
+is
+<code>
+ldp:Page;
+</code>
+it
+also
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+have
+1
+triple
+to
+indicate
+the
+container
+it
+is
+paging,
+whose
+<del class="diff-old">subject
+</del>
+<ins class="diff-chg"> subject
+</ins>
+is
+the
+URL
+of
+the
+page,
+predicate
+is
+<code>
+ldp:pageOf,
+</code>
+and
+object
+is
+the
+URL
+of
+the
+LDPC.
+</div>
+<div id="ldpc-5_3_6_2" class="rule">
+5.3.6.2
+The
+page
+resource
+representation
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+have
+one
+triple
+with
+the
+subject
+of
+the
+page,
+predicate
+of
+<code>
+ldp:nextPage
+</code>
+and
+object
+being
+the
+URL
+for
+the
+subsequent
+page.
+</div>
+<div id="ldpc-5_3_6_3" class="rule">
+5.3.6.3
+The
+last
+page
+resource
+representation
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+have
+one
+triple
+with
+the
+subject
+of
+the
+last
+page,
+predicate
+of
+<code>
+ldp:nextPage
+</code>
+and
+object
+being
+<code>
+rdf:nil
+</code>.
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/18">
+ISSUE-18
+</a>
+</div>
+container
+membership
+and
+robust
+pagination
+</div>
+<div id="ldpc-5_3_7" class="rule">
+5.3.7
+LDPC
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+represent
+the
+members
+of
+a
+paged
+LDPC
+in
+a
+sequential
+order.
+<del class="diff-old">The
+</del>
+<ins class="diff-chg"> The
+</ins>
+order
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+be
+specified
+using
+the
+<code>
+ldp:containerSortPredicates
+</code>
+predicate
+whose
+subject
+is
+that
+of
+the
+page
+and
+object
+is
+a
+list
+of
+LDPC
+ordinal
+predicates.
+<del class="diff-old">The
+</del>
+<ins class="diff-chg"> The
+</ins>
+default
+ordering
+is
+ascending.
+The
+only
+ordinal
+predicate
+literal
+data
+types
+supported
+are
+those
+as
+defined
+by
+SPARQL
+SELECT’s
+ORDER
+BY
+clause
+<del class="diff-old">[
+SPARQL-QUERY
+].
+</del>
+<ins class="diff-chg">[[!SPARQL-QUERY]].
+</ins>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/14">
+ISSUE-14
+</a>
+</div>
+Include
+clarifications
+about
+ordering
+in
+LDPC
+representations
+</div>
+</div>
+<div id="ldpc-5_3_7_1" class="rule">
+5.3.7.1
+The
+object
+of
+<code>
+ldp:containerSortPredicates
+<del class="diff-old">’,
+</del>
+</code>,
+the
+predicate
+used
+to
+indicate
+ordering,
+<del class="diff-old">must
+not
+</del>
+<ins class="diff-chg">MUST NOT
+</ins>
+change
+between
+subsequent
+pages.
+If
+it
+does,
+ordering
+among
+members
+of
+a
+container
+across
+pages
+is
+undefined.
+See
+section
+<a href="#ldpc-ordering">
+5.1.4
+Ordering
+</a>
+for
+additional
+details.
+</div>
+</section>
+<section>
+<h2 id="ldpc-HTTP_POST">
+<ins class="diff-new">HTTP
+POST
+</ins></h2>
+<p>
+<del class="diff-old">The
+Linked
+Data
+Platform
+</del>
+<ins class="diff-chg">This
+specification
+imposes
+the
+following
+new
+requirements
+on
+HTTP
+POST
+for
+LDPCs
+only
+when
+an
+LDPC
+supports
+that
+method.
+This
+specification
+</ins>
+does
+not
+<del class="diff-old">define
+how
+clients
+discover
+LDPCs.
+</del>
+<ins class="diff-chg">impose
+any
+new
+requirement
+to
+support
+that
+method,
+and
+[[!HTTP11]]
+makes
+it
+optional.
+</ins>
+</p>
+<del class="diff-old">5.4
+HTTP
+POST
+</del>
+<div id="ldpc-5_4_1" class="rule">
+5.4.1
+LDPC
+clients
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+create
+<ins class="diff-new">member
+</ins>
+resources
+by
+submitting
+a
+representation
+as
+the
+entity
+body
+of
+the
+HTTP
+POST
+to
+a
+known
+LDPC.
+LDPC
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+respond
+with
+status
+code
+201
+(Created)
+and
+the
+<code>
+Location
+</code>
+header
+set
+to
+the
+new
+resource’s
+URL.
+</div>
+<div id="ldpc-5_4_2" class="rule">
+5.4.2
+After
+a
+successful
+HTTP
+POST
+request
+to
+a
+LDPC,
+the
+new
+resource
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+appear
+as
+a
+member
+of
+the
+LDPC
+until
+the
+new
+resource
+is
+deleted
+or
+removed
+by
+other
+methods.
+A
+LDPC
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+also
+contain
+resources
+that
+were
+added
+through
+other
+means
+-
+for
+example
+through
+the
+user
+interface
+of
+the
+site
+that
+implements
+the
+LDPC.
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/35">
+<ins class="diff-chg">ISSUE-35
+</ins></a></div><ins class="diff-chg">
+POSTing
+to
+a
+container
+MUST
+yield
+a
+fresh
+URI
+</ins></div><div id="ldpc-5_4_3" class="rule">
+5.4.3
+LDPC
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+accept
+an
+HTTP
+POST
+of
+non-RDF
+representations
+for
+creation
+of
+any
+kind
+of
+resource,
+for
+example
+binary
+resources.
+</div>
+<div id="ldpc-5_4_4" class="rule">
+5.4.4
+For
+servers
+that
+support
+create,
+LDPC
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+create
+a
+LDPR
+from
+a
+RDF
+representation
+in
+the
+request
+entity
+body.
+<ins class="diff-new">The
+LDPR
+could
+also
+be
+a
+LDPC,
+therefore
+servers
+may
+allow
+the
+creations
+of
+LDPCs
+within
+a
+LDPC.
+</ins>
+</div>
+<div id="ldpc-5_4_5" class="rule">
+5.4.5
+LDPC
+servers
+<del class="diff-old">should
+not
+</del>
+<ins class="diff-chg">SHOULD
+NOT
+</ins>
+include
+the
+representation
+of
+the
+created
+resource
+in
+the
+entity
+body
+of
+a
+201
+(Created)
+response.
+In
+other
+words,
+clients
+should
+not
+expect
+any
+representation
+in
+the
+response
+entity
+body
+on
+a
+201
+(Created)
+response.
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/39">
+<ins class="diff-chg">ISSUE-39
+</ins></a></div><ins class="diff-chg">
+HTTP
+status
+codes
+used
+for
+creation
+</ins></div><div id="ldpc-5_4_6" class="rule">
+5.4.6
+<del class="diff-old">For
+LDPCs,
+</del>
+<ins class="diff-chg">LDPC
+</ins>
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+accept
+a
+request
+entity
+body
+with
+a
+<del class="diff-old">content
+type
+</del>
+<ins class="diff-chg">request
+header
+of
+</ins><code><ins class="diff-chg">
+Content-Type
+</ins></code><ins class="diff-chg">
+with
+value
+</ins>
+of
+<code>
+text/turtle
+</code>
+<del class="diff-old">[
+TURTLE
+].
+</del>
+<ins class="diff-chg">[[!TURTLE]].
+</ins>
+</div>
+<div id="ldpc-5_4_7" class="rule">
+5.4.7
+<del class="diff-old">For
+LDPCs,
+LDPR
+</del>
+<ins class="diff-chg">LDPC
+</ins>
+servers
+<del class="diff-old">should
+accept
+a
+</del>
+<ins class="diff-chg">SHOULD
+use
+the
+</ins><code><ins class="diff-chg">
+Content-Type
+</ins></code>
+request
+<del class="diff-old">with
+</del>
+<ins class="diff-chg">header
+to
+determine
+the
+representation
+format
+when
+the
+request
+has
+</ins>
+an
+entity
+<del class="diff-old">body
+</del>
+<ins class="diff-chg">body.
+When
+the
+header
+is
+absent,
+LDPC
+servers
+MAY
+infer
+the
+</ins>
+content
+type
+<del class="diff-old">of
+application/rdf+xml
+[
+RDF-SYNTAX
+].
+</del>
+<ins class="diff-chg">by
+inspecting
+the
+entity
+body
+contents
+[[!HTTP11]].
+</ins>
+</div>
+<div id="ldpc-5_4_8" class="rule">
+5.4.8
+<del class="diff-old">For
+</del>
+<ins class="diff-chg">In
+</ins>
+RDF
+representations,
+LDPC
+servers
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+interpret
+the
+null
+relative
+URI
+for
+the
+subject
+of
+triples
+in
+the
+LDPR
+representation
+in
+the
+request
+entity
+body
+as
+referring
+to
+the
+entity
+in
+the
+request
+body.
+Commonly,
+that
+entity
+is
+the
+model
+for
+the
+“to
+be
+created”
+LDPR,
+so
+triples
+whose
+subject
+is
+the
+null
+relative
+URI
+will
+usually
+result
+in
+triples
+in
+the
+created
+resource
+whose
+subject
+is
+the
+created
+resource.
+<ins class="diff-new">
+</ins>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/20">
+ISSUE-20
+</a>
+</div>
+Identifying
+and
+naming
+POSTed
+resources
+</div>
+</div>
+<div id="ldpc-5_4_9" class="rule">
+5.4.9
+LDPC
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+assign
+the
+subject
+URI
+for
+the
+resource
+to
+be
+created
+using
+server
+application
+specific
+rules.
+</div>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/43">
+<ins class="diff-chg">ISSUE-43
+</ins></a></div><ins class="diff-chg">
+hint
+at
+naming
+a
+resource
+on
+creation
+</ins></div><div id="ldpc-5_4_10" class="rule">
+5.4.10
+LDPC
+servers
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+allow
+clients
+to
+create
+new
+resources
+without
+requiring
+detailed
+knowledge
+of
+application-specific
+constraints.
+<del class="diff-old">Some
+LDPC
+servers
+put
+restrictions
+on
+representations
+–
+for
+example,
+the
+range
+of
+rdf:type
+,
+datatypes
+of
+predicates
+and
+number
+of
+occurrences
+of
+predicates
+in
+triples
+-
+but
+server
+enforcement
+</del>
+<ins class="diff-chg">This
+is
+a
+consequence
+</ins>
+of
+<del class="diff-old">detailed,
+domain-specific
+constraints
+will
+greatly
+restrict
+</del>
+the
+<del class="diff-old">types
+of
+clients
+that
+can
+create
+resources
+</del>
+<ins class="diff-chg">requirement
+to
+</ins><a href="#ldpr-4_1_13"><ins class="diff-chg">
+enable
+simple
+creation
+</ins>
+and
+<del class="diff-old">therefore
+discouraged.
+</del>
+<ins class="diff-chg">modification
+</ins></a><ins class="diff-chg">
+of
+LPDRs.
+</ins>
+</div>
+<del class="diff-old">5.5
+</del>
+</section>
+<section>
+<h2 id="ldpc-HTTP_PUT">
+HTTP
+PUT
+</h2>
+<p>
+<ins class="diff-chg">This
+specification
+imposes
+the
+following
+new
+requirements
+on
+HTTP
+PUT
+for
+LDPCs
+only
+when
+an
+LDPC
+supports
+that
+method.
+This
+specification
+does
+not
+impose
+any
+new
+requirement
+to
+support
+that
+method,
+and
+[[!HTTP11]]
+makes
+it
+optional.
+</ins></p><div id="ldpc-5_5_1" class="rule">
+5.5.1
+LDPC
+servers
+<del class="diff-old">should
+not
+</del>
+<ins class="diff-chg">SHOULD
+NOT
+</ins>
+allow
+HTTP
+PUT
+to
+update
+a
+LDPC’s
+<del class="diff-old">members
+and
+</del>
+<ins class="diff-chg">members;
+</ins>
+if
+the
+server
+receives
+such
+a
+request,
+it
+<del class="diff-old">should
+</del>
+<ins class="diff-chg">SHOULD
+</ins>
+respond
+with
+a
+409
+(Conflict)
+status
+code.
+</div>
+<div id="ldpc-5_5_2" class="rule">
+5.5.2
+LDPC
+servers
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+allow
+updating
+LDPC
+non-membership
+properties
+using
+HTTP
+PUT
+on
+<code>
+<containerURL>?non-member-properties
+</code>,
+which
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MAY
+</ins>
+exclude
+<del class="diff-old">server
+managed
+</del>
+<ins class="diff-chg">server-managed
+</ins>
+properties
+such
+as
+<code>
+ldp:membershipSubject
+</code>
+and
+<code>
+ldp:membershipPredicate
+</code>.
+</div>
+<del class="diff-old">5.6
+</del>
+</section>
+<section>
+<h2 id="ldpc-HTTP_DELETE">
+HTTP
+DELETE
+</h2>
+<p>
+<ins class="diff-chg">This
+specification
+imposes
+the
+following
+new
+requirements
+on
+HTTP
+DELETE
+for
+LDPRs
+only
+when
+a
+LDPC
+supports
+that
+method.
+This
+specification
+does
+not
+impose
+any
+new
+requirement
+to
+support
+that
+method,
+and
+[[!HTTP11]]
+makes
+it
+optional.
+</ins></p><div id="ldpc-5_6_1" class="rule">
+5.6.1
+<del class="diff-old">If
+</del>
+<ins class="diff-chg">When
+</ins>
+a
+LDPC
+<ins class="diff-new">member
+resource
+originally
+created
+by
+the
+LDPC
+(for
+example,
+one
+referenced
+by
+a
+membership
+triple)
+is
+deleted,
+and
+the
+LDPC
+</ins>
+server
+<del class="diff-old">supports
+deletion
+</del>
+<ins class="diff-chg">is
+aware
+</ins>
+of
+the
+<del class="diff-old">LDPC,
+</del>
+<ins class="diff-chg">member's
+deletion
+(for
+example,
+the
+member
+is
+managed
+by
+</ins>
+the
+<ins class="diff-new">same
+server),
+the
+LDPC
+</ins>
+server
+<del class="diff-old">may
+</del>
+<ins class="diff-chg">MUST
+also
+remove
+it
+from
+the
+LDPC
+by
+removing
+the
+corresponding
+membership
+triple.
+</ins></div><div id="ldpc-5_6_2" class="rule"><ins class="diff-chg">
+5.6.2
+When
+the
+LDPC
+includes
+an
+</ins><code><ins class="diff-chg">
+rdf:type
+</ins></code><ins class="diff-chg">
+predicate
+with
+an
+object
+of
+</ins><code><ins class="diff-chg">
+ldp:AggregateContainer
+</ins></code>,<ins class="diff-chg">
+the
+server
+MAY
+</ins>
+also
+delete
+the
+resources
+that
+are
+referenced
+as
+its
+contents.
+<ins class="diff-new">The
+LDPC
+membership
+triple
+MUST
+also
+be
+updated
+as
+defined
+by
+</ins><a href="#ldpc-5_6_1"><ins class="diff-new">
+5.6.1
+</ins></a><ins class="diff-new">
+above.
+</ins>
+</div>
+<del class="diff-old">5.6.2
+</del>
+<div id="ldpc-5_6_3" class="rule">
+<ins class="diff-chg">5.6.3
+</ins>
+When
+<del class="diff-old">a
+resource
+that
+is
+contained
+in
+a
+</del>
+<ins class="diff-chg">the
+</ins>
+LDPC
+<del class="diff-old">(for
+example
+referenced
+by
+a
+membership
+triple)
+is
+deleted,
+</del>
+<ins class="diff-chg">includes
+an
+</ins><code><ins class="diff-chg">
+rdf:type
+</ins></code><ins class="diff-chg">
+predicate
+with
+an
+object
+of
+</ins><code><ins class="diff-chg">
+ldp:CompositeContainer
+</ins></code>,
+the
+server
+<del class="diff-old">must
+</del>
+<ins class="diff-chg">MUST
+</ins>
+also
+<del class="diff-old">remove
+it
+from
+</del>
+<ins class="diff-chg">delete
+</ins>
+the
+<del class="diff-old">LDPC
+</del>
+<ins class="diff-chg">resources
+</ins>
+that
+<del class="diff-old">was
+used
+to
+create
+it
+and
+should
+remove
+it
+</del>
+<ins class="diff-chg">are
+referenced
+as
+its
+contents.
+The
+LDPC
+membership
+triple
+MUST
+also
+be
+updated
+as
+defined
+by
+</ins><a href="#ldpc-5_6_1"><ins class="diff-chg">
+5.6.1
+</ins></a><ins class="diff-chg">
+above.
+</ins></div><div class="ldp-issue"><div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/28"><ins class="diff-chg">
+ISSUE-28
+</ins></a></div><ins class="diff-chg">
+transaction/rollback
+when
+deleting
+resources
+</ins>
+from
+<del class="diff-old">any
+other
+containers
+that
+reference
+it
+</del>
+<ins class="diff-chg">a
+LDPC.
+note
+also
+</ins>
+that
+<ins class="diff-new">5.6.2's
+reminder
+about
+5.6.1
+is
+only
+sensible
+if
+there
+is
+no
+transactional
+behavior
+in
+</ins>
+the
+<del class="diff-old">server
+manages
+and
+persists.
+</del>
+<ins class="diff-chg">recursive
+delete.
+in
+the
+case
+where
+the
+only
+observable
+results
+are
+all/nothing,
+the
+reminder's
+effect
+is
+unobservable.
+</ins>
+</div>
+<del class="diff-old">5.7
+</del>
+</section>
+<section>
+<h2 id="ldpc-HTTP_HEAD">
+HTTP
+HEAD
+</h2>
+<p>
+There
+are
+no
+additional
+requirements
+on
+HTTP
+HEAD.
+</p>
+<del class="diff-old">5.8
+</del>
+</section>
+<section>
+<h2 id="ldpc-HTTP_PATCH">
+HTTP
+PATCH
+</h2>
+<p>
+<ins class="diff-chg">This
+specification
+imposes
+the
+following
+new
+requirements
+on
+HTTP
+PATCH
+for
+LDPCs
+only
+when
+a
+LDPC
+supports
+that
+method.
+This
+specification
+does
+not
+impose
+any
+new
+requirement
+to
+support
+that
+method,
+and
+[[!HTTP11]]
+makes
+it
+optional.
+</ins></p><div id="ldpc-5_8_1" class="rule">
+5.8.1
+LDPC
+servers
+are
+<del class="diff-old">recommended
+</del>
+<ins class="diff-chg">RECOMMENDED
+</ins>
+to
+support
+HTTP
+PATCH
+as
+the
+preferred
+method
+for
+updating
+LDPC
+non-membership
+properties.
+</div>
+</section>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/7">
+ISSUE-7
+</a>
+</div>
+What
+operations
+are
+<del class="diff-old">permittered
+</del>
+<ins class="diff-chg">permitted
+</ins>
+on
+containers
+and
+how
+do
+they
+get
+invoked?
+</div>
+</section>
+<section class='appendix informative'>
+<h2>
+<del class="diff-old">A.
+</del>
+Acknowledgements
+</h2>
+<del class="diff-old">This
+section
+is
+non-normative.
+</del>
+<p>
+The
+following
+people
+have
+been
+instrumental
+in
+providing
+thoughts,
+feedback,
+reviews,
+<ins class="diff-new">content,
+</ins>
+criticism
+and
+input
+in
+the
+creation
+of
+this
+specification:
+</p>
+<p style="margin-left: 3em;">
+<ins class="diff-chg">Arnaud
+le
+Hors,
+Erik
+Wilde,
+Tim
+Berners-Lee,
+Steve
+Battle,
+Olivier
+Berger,
+Alexandre
+Bertails,
+Richard
+Cyganiak,
+Raúl
+García
+Castro,
+Sandro
+Hawke,
+Kingsley
+Idehen,
+Yves
+Lafon,
+Antonis
+Loizou,
+Ashok
+Malhota,
+Roger
+Menday,
+Nandana
+Mihindukulasooriya,
+Kevin
+Page,
+Eric
+Prud'hommeaux,
+Andy
+Seaborne,
+Henry
+Story,
+Ted
+Thibodeau,
+Bart
+van
+Leeuwen,
+Ruben
+Verborgh,
+David
+Wood,
+</ins>
+Martin
+P.
+Nally
+<del class="diff-old">John
+Arwe
+Arnaud
+le
+Hors
+B.
+</del>
+</p>
+</section>
+<section class='appendix informative' id="history">
+<h1>
+Change
+History
+</h1>
+<blockquote>
+<em>
+<del class="diff-old">This
+section
+is
+non-normative.
+</del>
+<ins class="diff-chg">First
+Public
+Working
+Draft
+</ins>
+</em>
+</blockquote>
+<ul>
+<li>
+<del class="diff-old">2012-09-18
+</del>
+<ins class="diff-chg">2013-03-04
+</ins>
+-
+<del class="diff-old">Initial
+ReSpec'ing
+</del>
+<ins class="diff-chg">Comments
+received
+from
+David
+Wood:
+abstract,
+paging
+informative
+(part
+1)
+(SS)
+</ins></li><li><ins class="diff-chg">
+2013-03-04
+-
+ISSUE-36
+-
+Added
+informative
+text
+regarding
+creationg
+</ins>
+of
+<del class="diff-old">Member
+Submission
+</del>
+<ins class="diff-chg">containers
+in
+5.4.4
+(SS)
+</ins></li><li><ins class="diff-chg">
+2013-03-04
+</ins>
+-
+<del class="diff-old">Linked
+Data
+Basic
+Profile
+1.0
+</del>
+<ins class="diff-chg">ISSUE-12
+-
+Added
+section
+4.7.3
+not
+to
+allow
+PATCH
+for
+create
+</ins>
+(SS)
+</li>
+<li>
+<del class="diff-old">2012-09-18
+</del>
+<ins class="diff-chg">2013-03-03
+</ins>
+-
+<del class="diff-old">Fixed
+up
+some
+links
+and
+worked
+</del>
+<ins class="diff-chg">Adjustments
+to
+language
+about
+different
+container
+behavior
+(SS)
+</ins></li><li><ins class="diff-chg">
+2013-03-02
+-
+Adding
+trailing
+'/'
+</ins>
+on
+<del class="diff-old">references,
+work
+left
+</del>
+<ins class="diff-chg">Container
+URLs
+</ins>
+to
+<del class="diff-old">do.
+</del>
+<ins class="diff-chg">help
+with
+readability
+based
+on
+WG
+suggestion
+</ins>
+(SS)
+</li>
+<li>
+<del class="diff-old">2012-09-19
+</del>
+<ins class="diff-chg">2013-02-26
+</ins>
+-
+<del class="diff-old">Repairing
+references
+</del>
+<ins class="diff-chg">Updated
+Acknowledgements
+section
+(SS)
+</ins></li><li><ins class="diff-chg">
+2013-02-25
+-
+ISSUE-29
+-
+Use
+relative
+URIs
+in
+examples
+(SS)
+</ins></li><li><ins class="diff-chg">
+2013-02-25
+-
+ISSUE-31
+-
+Added
+a
+more
+complete
+conformance
+section,
+motived
+by
+SPARQL
+1.1
+(SS)
+</ins></li><li><ins class="diff-chg">
+2013-02-25
+-
+Updating
+some
+simple
+formatting,
+reorganizing
+open
+issues
+</ins>
+and
+<del class="diff-old">forward
+reference
+to
+biblio.js
+updates
+</del>
+<ins class="diff-chg">todos.
+</ins>
+(SS)
+</li>
+<li>
+<del class="diff-old">2012-09-19
+</del>
+<ins class="diff-chg">2013-02-15
+-
+ISSUE-34
+-
+Aggregration:
+5.6.1
+and
+5.6.2
+updated
+for
+review.
+(JA)
+</ins></li><li><ins class="diff-chg">
+2013-02-13
+-
+ISSUE-42
+-
+4.8
+Common
+Properties
+moved
+to
+</ins><a href="http://www.w3.org/2012/ldp/wiki/Deployment_Guide#Re-use_established_linked_data_vocabularies_instead_of_.28re-.29inventing_duplicates"><ins class="diff-chg">
+Deploment
+Guide
+</ins></a><ins class="diff-chg">
+(JA)
+</ins></li><li><ins class="diff-chg">
+2013-02-12
+</ins>
+-
+Fixed
+<del class="diff-old">rdfs:label
+range
+</del>
+<ins class="diff-chg">up
+previous
+publication
+links
+(SS)
+</ins></li><li><ins class="diff-chg">
+2013-02-12
+-
+ISSUE-10
+-
+4.1.12
+</ins>
+to
+be
+<del class="diff-old">rdfs:Literal
+</del>
+<ins class="diff-chg">MUST
+use
+entity
+tags
+(either
+weak
+or
+strong
+ones)
+</ins>
+(SS)
+</li>
+<li>
+<del class="diff-old">2012-09-19
+</del>
+<ins class="diff-chg">2013-02-12
+</ins>
+-
+<del class="diff-old">ISSUE-1
+Define
+Turtle
+as
+</del>
+<ins class="diff-chg">ISSUE-11
+-
+4.4.1
+Relaxed
+</ins>
+the
+<del class="diff-old">required
+serialization
+format
+for
+LDP
+</del>
+<ins class="diff-chg">MUST
+ignore
+dc:modified/creator
+to
+MAY
+</ins>
+(SS)
+</li>
+<li>
+<del class="diff-old">2012-09-20
+</del>
+<ins class="diff-chg">2013-01-16
+</ins>
+-
+<del class="diff-old">Sent
+pull
+request
+re
+LINKED-DATA
+and
+added
+suggestion
+for
+ldp
+namespace
+</del>
+<ins class="diff-chg">ISSUE-25
+Updated
+introduction.
+5.2.2
+changed
+to
+MUST
+NOT
+be
+in
+multiple
+containers.
+Flipped
+5.6.1/2
+as
+first
+rule
+leads
+to
+2nd.
+5.6.2(was
+.1)
+Delete
+LDPC
+MUST
+also
+delete
+members.
+</ins>
+(SS)
+</li>
+<li>
+<del class="diff-old">2012-10-14
+</del>
+<ins class="diff-chg">2013-01-16
+</ins>
+-
+Added
+<del class="diff-old">open
+ISSUES
+</del>
+<ins class="diff-chg">new
+issues
+ranging
+from
+26-43.
+Removed
+closed/deferred
+issues:
+2
+&
+3
+(SS)
+</ins></li><li><ins class="diff-chg">
+2012-12-28
+-
+Fixed
+Typos.
+Separated
+some
+compound
+rules
+like
+4.1.5.
+Rewording
+for
+clarity:
+4.1.10,
+Text
+being
+repeated
+in
+several
+places
+centralized
+</ins>
+and
+<del class="diff-old">formating
+</del>
+<ins class="diff-chg">cross-linked.
+Made
+printed
+code
+output
+easier
+</ins>
+to
+<del class="diff-old">prep
+for
+public
+working
+draft
+</del>
+<ins class="diff-chg">read
+on
+black
+&
+white
+printers.
+Exposed
+terms
+defined
+in-line
+under
+LDPC
+as
+Terminology
+(tentatively).
+Removed
+non-normative
+qualifer
+from
+section
+5.2.
+Added
+"several"
+editors'
+to-dos.(JA)
+</ins></li><li><ins class="diff-chg">
+2012-11-05
+-
+minor
+rewording
+from
+ISSUE-24
+</ins></li><li><ins class="diff-chg">
+2012-11-03
+-
+ISSUE-22,
+ISSUE-23:
+changed
+sections
+4.2.3
+and
+5.4.7.
+Removed
+closed
+issues.
+</ins>
+(SS)
+</li>
+<li>
+<ins class="diff-new">2012-11-03
+-
+ISSUE-24
+Delete
+the
+phrase
+in
+4.5.1
+that
+nays
+"until
+...Request
+URI"
+and
+adding
+a
+sentence,
+"Clients
+should
+note
+that
+servers
+may
+reuse
+a
+Request-URI
+under
+some
+circumstances."
+</ins></li><li><ins class="diff-new">
+2012-11-03
+-
+ISSUE-6
+Removed
+section
+4.1.9.
+Shifted
+up
+sections
+.10
+through
+.13.
+</ins></li><li><ins class="diff-new">
+2012-11-01
+-
+Fixed
+minor
+typo
+and
+added
+some
+notes
+(SS)
+</ins></li></ul><blockquote><em><ins class="diff-new">
+Submission
+</ins></em></blockquote><ul><li>
+2012-10-15
+-
+ISSUE-8
+Changed
+references
+from
+LDBP
+to
+LDP,
+removed
+definition
+for
+<del class="diff-old">"profile"
+</del>
+<ins class="diff-chg">"profile"
+</ins>
+and
+new
+namespace
+(SS)
+</li>
+<li>
+2012-10-15
+-
+Included
+additional
+open
+ISSUES
+from
+Oct
+15
+WG
+meeting:
+22,
+23,
+24
+(SS)
+</li>
+<li>
+<ins class="diff-new">2012-10-14
+-
+Added
+open
+ISSUES
+and
+formating
+to
+prep
+for
+public
+working
+draft
+(SS)
+</ins></li><li><ins class="diff-new">
+2012-09-20
+-
+Sent
+pull
+request
+re
+LINKED-DATA
+and
+added
+suggestion
+for
+</ins><code><ins class="diff-new">
+ldp
+</ins></code><ins class="diff-new">
+namespace
+(SS)
+</ins></li><li><ins class="diff-new">
+2012-09-19
+-
+Repairing
+references
+and
+forward
+reference
+to
+biblio.js
+updates
+(SS)
+</ins></li><li><ins class="diff-new">
+2012-09-19
+-
+Fixed
+rdfs:label
+range
+to
+be
+rdfs:Literal
+(SS)
+</ins></li><li><ins class="diff-new">
+2012-09-19
+-
+ISSUE-1
+Define
+Turtle
+as
+the
+required
+serialization
+format
+for
+LDP
+(SS)
+</ins></li><li><ins class="diff-new">
+2012-09-18
+-
+Initial
+ReSpec'ing
+of
+</ins><a href="http://www.w3.org/Submission/ldbp/"><ins class="diff-new">
+Member
+Submission
+-
+Linked
+Data
+Basic
+Profile
+1.0
+</ins></a><ins class="diff-new">
+(SS)
+</ins></li><li><ins class="diff-new">
+2012-09-18
+-
+Fixed
+up
+some
+links
+and
+worked
+on
+references,
+work
+left
+to
+do.
+(SS)
+</ins></li>
+</ul>
+<del class="diff-old">C.
+</del>
+</section>
+<section class='appendix informative' id="todos">
+<h1>
+Editor
+Todos
+and
+Notes
+<del class="diff-old">This
+section
+is
+non-normative.
+</del>
+</h1>
+<p>
+Other
+than
+LDP
+<a href="http://www.w3.org/2012/ldp/track/actions">
+open
+actions
+</a>
+and
+<a href="http://www.w3.org/2012/ldp/track/issues">
+issues
+</a>,
+included
+here
+are
+transient
+tasks
+and
+notes
+editors
+use.
+They
+have
+not
+meaning
+in
+final
+product
+of
+a
+published
+working
+draft
+and
+will
+be
+removed
+prior
+to
+publishing.
+</p>
+<ul>
+<li>
+<del class="diff-old">None
+</del>
+<ins class="diff-chg">Insert
+some
+additional
+examples
+</ins></li><li><ins class="diff-chg">
+4.1.2:
+"the"
+subject
+?=
+Request-URI
+...
+not
+always
+(hash
+URIs)
+</ins></li><li><ins class="diff-chg">
+4.1.5:
+refers
+to
+RDF
+*Primer*
+-
+is
+that
+intentful?
+</ins></li><li><ins class="diff-chg">
+4.1.6.1:
+why
+does
+it
+have
+the
+extra
+.1,
+to
+avoid
+renumbering?
+should
+we
+divide
+General
+into
+subsections
+for
+vocab/client/server
+constraints?
+Do
+we
+need
+to
+define
+"LDPR
+server"?
+...think
+about
+role
+vs
+artifact.
+If
+"an
+LDPR
+server"
+hosts
+both
+LDPRs
+and
+non-LDPR
+HTTP
+resources,
+4.1.2
+(if
+"the
+code"
+==
+LDPR
+server)
+could
+be
+read
+to
+say
+that
+in
+order
+to
+conform
+to
+spec
+it
+must
+serve
+up
+RDF
+for
+non-LDPRs.
+Hits
+5.2.1
+too.
+</ins></li><li><ins class="diff-chg">
+4.1.7:
+define
+"explicitly"?
+</ins></li><li><ins class="diff-chg">
+4.4.1:
+specifically
+calls
+out
+2
+props;
+issue-11
+note
+talks
+about
+"server-managed
+props"
+which
+is
+not
+defined.
+</ins></li><li><ins class="diff-chg">
+4.4.4/4.4.5
+could
+be
+read
+to
+overlap/dup
+one
+another
+</ins></li><li><ins class="diff-chg">
+Deployment
+guide
+(was:
+4.8
+Common
+Properties)
+talks
+about
+rdfs:Range
+which
+implies
+inferencing.
+4.1.7
+spec
+says
+want
+to
+avoid
+putting
+that
+reqt
+on
+clients.
+</ins></li><li><ins class="diff-chg">
+5.2.1:
+4.1.6.1
+issue
+linked
+to
+this
+text
+</ins></li><li><ins class="diff-chg">
+5.2.2:
+I
+think
+we
+mean
+"resource"
+==
+any
+HTTP
+resource,
+not
+just
+LDPR.
+If
+so,
+perhaps
+we
+should
+be
+more
+explicit.
+5.2.1
+might
+be
+the
+place.
+</ins></li><li><ins class="diff-chg">
+5.2.3-5.2.5:
+don't
+we
+need
+to
+tell
+clients
+to
+fetch
+LDPC's
+non-member
+properties,
+introspect
+for
+these
+predicates,
+and
+(if
+either
+not
+found)
+supply
+the
+defaults?
+that
+is
+the
+net
+effect
+of
+what's
+here.
+</ins></li><li><ins class="diff-chg">
+5.4.5:
+in
+light
+of
+the
+existence
+of
+server-managed
+properties,
+why
+not
+allow
+response
+body
+from
+create?
+</ins></li><li><ins class="diff-chg">
+Per
+David
+Wood,
+'Sections
+4.4.1,
+4.5.1,
+4.7.1,
+5.4.1,
+5.6.1
+and
+5.8.1
+all
+relate
+to
+allowable
+write
+operations.
+I
+suggest
+adding
+the
+statement,
+"An
+LDPR
+server
+MAY
+require
+a
+user
+to
+be
+authenticated
+and
+authorized
+before
+this
+action
+is
+permitted."
+to
+each
+of
+those
+sections.',
+consider
+place
+to
+edit
+this
+in.
+</ins>
+</li>
+</ul>
+<div class="ldp-issue">
+<div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/37">
+<ins class="diff-new">ISSUE-37
+</ins></a></div><ins class="diff-new">
+Additional
+introductory
+text
+on
+the
+LDP
+data
+and
+interaction
+model
+</ins></div><div class="ldp-issue"><div class="ldp-issue-title">
+<a href="http://www.w3.org/2012/ldp/track/issues/5">
+ISSUE-5
+</a>
+</div>
+Add
+a
+section
+explaining
+how
+<del class="diff-old">LDBP
+</del>
+<ins class="diff-chg">LDP
+</ins>
+is
+related
+to
+Graph
+Store
+Protocol
+</div>
+<del class="diff-old">D.
+References
+D.1
+Normative
+references
+[DC-RDF]
+M.
+Nilsson;
+et
+al.
+Expressing
+Dublin
+Core
+metadata
+using
+the
+Resource
+Description
+Framework
+(RDF).
+14
+January
+2008.
+DCMI
+Recommendation.
+URL:
+http://dublincore.org/documents/2008/01/14/dc-rdf/
+[DC-TERMS]
+Dublin
+Core
+Metadata
+Initiative.
+Dublin
+Core
+Metadata
+Initiative
+Terms,
+version
+1.1.
+11
+October
+2010.
+DCMI
+Recommendation.
+URL:
+http://dublincore.org/documents/2010/10/11/dcmi-terms/
+.
+[HTML401]
+David
+Raggett;
+Ian
+Jacobs;
+Arnaud
+Le
+Hors.
+HTML
+4.01
+Specification.
+24
+December
+1999.
+W3C
+Recommendation.
+URL:
+http://www.w3.org/TR/1999/REC-html401-19991224
+[HTTP11]
+R.
+Fielding;
+et
+al.
+Hypertext
+Transfer
+Protocol
+-
+HTTP/1.1.
+June
+1999.
+Internet
+RFC
+2616.
+URL:
+http://www.ietf.org/rfc/rfc2616.txt
+[RDF-PRIMER]
+Frank
+Manola;
+Eric
+Miller.
+RDF
+Primer.
+10
+February
+2004.
+W3C
+Recommendation.
+URL:
+http://www.w3.org/TR/2004/REC-rdf-primer-20040210/
+[RDF-SCHEMA]
+Dan
+Brickley;
+Ramanathan
+V.
+Guha.
+RDF
+Vocabulary
+Description
+Language
+1.0:
+RDF
+Schema.
+10
+February
+2004.
+W3C
+Recommendation.
+URL:
+http://www.w3.org/TR/2004/REC-rdf-schema-20040210
+[RDF-SYNTAX]
+Ora
+Lassila;
+Ralph
+R.
+Swick.
+Resource
+Description
+Framework
+(RDF)
+Model
+and
+Syntax
+Specification.
+22
+February
+1999.
+W3C
+Recommendation.
+URL:
+http://www.w3.org/TR/1999/REC-rdf-syntax-19990222
+[RFC2119]
+S.
+Bradner.
+Key
+words
+for
+use
+in
+RFCs
+to
+Indicate
+Requirement
+Levels.
+March
+1997.
+Internet
+RFC
+2119.
+URL:
+http://www.ietf.org/rfc/rfc2119.txt
+[RFC4627]
+D.
+Crockford.
+The
+application/json
+Media
+Type
+for
+JavaScript
+Object
+Notation
+(JSON)
+July
+2006.
+Internet
+RFC
+4627.
+URL:
+http://www.ietf.org/rfc/rfc4627.txt
+[RFC5789]
+L
+Dusseault,
+J.
+Snell.
+PATCH
+Method
+for
+HTTP.
+March
+2010.
+Internet
+Proposed
+Standard
+RFC
+5789.
+URL:
+http://tools.ietf.org/html/rfc5789
+[SPARQL-QUERY]
+E.
+Prud'hommeaux,
+A.
+Seaborne.
+SPARQL
+Query
+Language
+for
+RDF.
+W3C
+Recommendation.
+15
+January
+2008.
+URL:
+http://www.w3.org/TR/2008/REC-rdf-sparql-query-20080115/
+[SPARQL-UPDATE]
+S.
+Schenk,
+P.
+Gearon.
+SPARQL
+1.1
+Update.
+W3C
+Working
+Draft.
+26
+January
+2010.
+URL:
+http://www.w3.org/TR/2010/WD-sparql11-update-20100126/
+[TURTLE]
+David
+Beckett,
+Tim
+Berners-Lee.
+Turtle:
+Terse
+RDF
+Triple
+Language.
+January
+2008.
+W3C
+Team
+Submission.
+URL:
+http://www.w3.org/TeamSubmission/turtle/
+[XMLSCHEMA11-2]
+Henry
+S.
+Thompson;
+et
+al.
+W3C
+XML
+Schema
+Definition
+Language
+(XSD)
+1.1
+Part
+2:
+Datatypes.
+5
+April
+2012.
+W3C
+Recommendation
+URL:
+http://www.w3.org/TR/2012/REC-xmlschema11-2-20120405/
+D.2
+Informative
+references
+[LINKED-DATA]
+Tim
+Berners-Lee.
+Linked
+Data.
+18
+June
+2009.
+Design
+Issue.
+(Work
+in
+progress.)
+URL:
+http://www.w3.org/DesignIssues/LinkedData.html
+[WEBARCH]
+Norman
+Walsh;
+Ian
+Jacobs.
+Architecture
+of
+the
+World
+Wide
+Web,
+Volume
+One.
+15
+December
+2004.
+W3C
+Recommendation.
+URL:
+http://www.w3.org/TR/2004/REC-webarch-20041215/
+</del>
+</section>
+</body>
+</html>
+