ldp.html
changeset 188 8eaaca309617
parent 187 4b9d6800be9c
child 189 ccdf7eb55d7a
equal deleted inserted replaced
187:4b9d6800be9c 188:8eaaca309617
   365 	<div id="ldpr-4_1_4" class="rule">4.1.4 LDPRs SHOULD reuse existing vocabularies instead of creating
   365 	<div id="ldpr-4_1_4" class="rule">4.1.4 LDPRs SHOULD reuse existing vocabularies instead of creating
   366 		their own duplicate vocabulary terms.  In addition to this general rule, some specific cases are
   366 		their own duplicate vocabulary terms.  In addition to this general rule, some specific cases are
   367 		covered by other conformance rules.
   367 		covered by other conformance rules.
   368 	</div>
   368 	</div>
   369 	<div id="ldpr-4_1_4_1" class="rule">4.1.4.1 LDPR predicates SHOULD use standard vocabularies such as Dublin Core
   369 	<div id="ldpr-4_1_4_1" class="rule">4.1.4.1 LDPR predicates SHOULD use standard vocabularies such as Dublin Core
   370 		[[!DC-TERMS]], RDF [[!RDF-PRIMER]] and RDF Schema [[!RDF-SCHEMA]], whenever
   370 		[[!DC-TERMS]], RDF [[!RDF-CONCEPTS]] and RDF Schema [[!RDF-SCHEMA]], whenever
   371 		possible.
   371 		possible.
   372 	</div>
   372 	</div>
   373 	<div id="ldpr-4_1_5" class="rule"><del>4.1.5 LDPRs MUST use the predicate <code>rdf:type</code> to
   373 	<div id="ldpr-4_1_5" class="rule"><del>4.1.5 LDPRs MUST use the predicate <code>rdf:type</code> to
   374 		represent the concept of type. The use of non-standard type
   374 		represent the concept of type. The use of non-standard type
   375 		predicates, as well as <code>dcterms:type</code>, is
   375 		predicates, as well as <code>dcterms:type</code>, is
   437 	</div>
   437 	</div>
   438 
   438 
   439 	<div id="ldpr-4_1_13" class="rule">4.1.13 LDPR servers
   439 	<div id="ldpr-4_1_13" class="rule">4.1.13 LDPR servers
   440 		MUST NOT require LDP clients to implement inferencing in order to recognize the subset
   440 		MUST NOT require LDP clients to implement inferencing in order to recognize the subset
   441 		of content defined by LDP.  Other specifications built on top of LDP MAY require clients
   441 		of content defined by LDP.  Other specifications built on top of LDP MAY require clients
   442 		to implement inferencing.  The practical implication is that all content defined by LDP
   442 		to implement inferencing [[!RDF-CONCEPTS]].  The practical implication is that all content defined by LDP
   443 		must be explicitly represented. 
   443 		must be explicitly represented. 
   444 	</div>
   444 	</div>
   445 
   445 
   446 </section>
   446 </section>
   447 
   447 
  1265 
  1265 
  1266 	<div id="ldpc-5_2_1" class="rule">5.2.1 LDPC servers MUST also be conformant LDPR servers. A Linked Data Platform
  1266 	<div id="ldpc-5_2_1" class="rule">5.2.1 LDPC servers MUST also be conformant LDPR servers. A Linked Data Platform
  1267 		Container MUST also be a conformant Linked Data Platform Resource.
  1267 		Container MUST also be a conformant Linked Data Platform Resource.
  1268 	</div>
  1268 	</div>
  1269 	<div id="ldpc-5_2_2" class="rule">5.2.2 For an LDPC,
  1269 	<div id="ldpc-5_2_2" class="rule">5.2.2 For an LDPC,
  1270 	the same resource which is identified by its canonical URI, MAY be a member of 
  1270 	the same resource (LDPR or not) which is identified by its canonical URI, MAY be a member of 
  1271 	more than one LDPC.
  1271 	more than one LDPC.
  1272 	</div>
  1272 	</div>
  1273 	<div id="ldpc-5_2_3" class="rule">5.2.3 The state of an LDPC includes information about which
  1273 	<div id="ldpc-5_2_3" class="rule">5.2.3 The state of an LDPC includes information about which
  1274 		resources are its members. In the simplest cases, the membership subject
  1274 		resources are its members. In the simplest cases, the membership subject
  1275 		will be the LDPC resource itself, but it does not have to be. The
  1275 		will be the LDPC resource itself, but it does not have to be. The
  1920 </p>
  1920 </p>
  1921 <!--
  1921 <!--
  1922 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130701/">Third Public Working Draft</a></em></blockquote>
  1922 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130701/">Third Public Working Draft</a></em></blockquote>
  1923 -->
  1923 -->
  1924 <ul>
  1924 <ul>
       
  1925 	<li>2013-07-11 - Various editorial clean up items from editor todo list (SS)</li>
  1925 	<li>2013-07-11 - Removed closed issues that required no new spec changes: 50, 56, 16, 19, 17 (SS)</li>
  1926 	<li>2013-07-11 - Removed closed issues that required no new spec changes: 50, 56, 16, 19, 17 (SS)</li>
  1926 	<li>2013-07-11 - ISSUE-51 Added how a LDPR can show which LDPC is it in (SS)</li>
  1927 	<li>2013-07-11 - ISSUE-51 Added how a LDPR can show which LDPC is it in (SS)</li>
  1927 	<li>2013-07-10 - Removed closed issues that required no new spec changes: 18, 35, 20 (SS)</li>
  1928 	<li>2013-07-10 - Removed closed issues that required no new spec changes: 18, 35, 20 (SS)</li>
  1928 	<li>2013-07-10 - ISSUE-44 move section 4.1.7 (relationships are simple RDF links) to guidance (SS)</li>
  1929 	<li>2013-07-10 - ISSUE-44 move section 4.1.7 (relationships are simple RDF links) to guidance (SS)</li>
  1929 	<li>2013-07-10 - ISSUE-72 take 2 - added ldp:MemberSubject to handle default case (SS)</li>
  1930 	<li>2013-07-10 - ISSUE-72 take 2 - added ldp:MemberSubject to handle default case (SS)</li>
  2018 <section class='appendix informative' id="todos">
  2019 <section class='appendix informative' id="todos">
  2019 <h1>Editor Todos and Notes</h1>
  2020 <h1>Editor Todos and Notes</h1>
  2020 <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
  2021 <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
  2021 editors use.  They have no meaning in final product of a published working draft and will be removed prior to publishing.</p>
  2022 editors use.  They have no meaning in final product of a published working draft and will be removed prior to publishing.</p>
  2022 <ul>
  2023 <ul>
  2023 	<li>5.1.4 ordering example  - add example with >1 predicate, and collation sorting</li>
       
  2024 	<li>Insert some additional examples</li>
       
  2025 	<li>4.1.2: "the" subject ?= Request-URI  ... not always (hash URIs)
       
  2026 	</li>
       
  2027 	<li>4.1.5: refers to RDF *Primer* - is that intentful?
       
  2028 	</li>
       
  2029 	<li>4.1.6.1: why does it have the extra .1, to avoid renumbering?  should we divide General into subsections
       
  2030 	for vocab/client/server constraints?  Do we need to define "LDPR server"? ...think about role vs artifact.  If
       
  2031 	"an LDPR server" hosts both LDPRs and non-LDPR HTTP resources, 4.1.2 (if "the code" == LDPR server) could be
       
  2032 	read to say that in order to conform to spec it must serve up RDF for non-LDPRs.  Hits 5.2.1 too.
       
  2033 	</li>
       
  2034 	<li>4.1.7: define "explicitly"?
       
  2035 	</li>
       
  2036 	<li>4.4.1: specifically calls out 2 props; issue-11 note talks about "server-managed props" which is not defined.
       
  2037 	</li>
       
  2038 	<li>4.4.4/4.4.5 could be read to overlap/dup one another
       
  2039 	</li>
       
  2040 	<li>Deployment guide (was: 4.8 Common Properties) talks about rdfs:Range which implies inferencing.  
       
  2041 	4.1.7 spec says want to avoid putting that reqt on clients.
       
  2042 	</li>
       
  2043 	<li>5.2.1: 4.1.6.1 issue linked to this text
       
  2044 	</li>
       
  2045 	<li>5.2.2: I think we mean "resource" == any HTTP resource, not just LDPR.  If so, perhaps we should be more explicit.
       
  2046 	5.2.1 might be the place.
       
  2047 	</li>
       
  2048 	<li>5.2.3-5.2.5: don't we need to tell clients to fetch LDPC's non-member properties, introspect for these predicates,
       
  2049 	and (if either not found) supply the defaults?  that is the net effect of what's here.
       
  2050 	</li>
       
  2051 	<li>5.4.5: in light of the existence of server-managed properties, why not allow response body from create?
       
  2052 	</li>
       
  2053 	<li>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 
       
  2054  allowable write operations.  I suggest adding the statement, "An LDPR server
       
  2055  MAY require a user to be authenticated and authorized before this action is 
       
  2056  permitted." to each of those sections.', consider place to edit this in.</li>
       
  2057 	<li>(IN)Consistency issues
  2024 	<li>(IN)Consistency issues
  2058 <ul>
  2025 <ul>
  2059 	<li><a href="#ldpr-inlining" class="sectionRef"></a> + probably other sections say things like "LDP does not provide clients...".  
  2026 	<li><a href="#ldpr-inlining" class="sectionRef"></a> + probably other sections say things like "LDP does not provide clients...".  
  2060 	Should those read "LDP 1.0..." instead?
  2027 	Should those read "LDP 1.0..." instead?
  2061 	</li><a href="#ldpr-inlining" class="sectionRef"></a>
  2028 	</li><a href="#ldpr-inlining" class="sectionRef"></a>
  2073 	</li>
  2040 	</li>
  2074 	<li>using "sectionRef" instead of hardwiring
  2041 	<li>using "sectionRef" instead of hardwiring
  2075 	</li>
  2042 	</li>
  2076 	<li>using respec section labeling consistently
  2043 	<li>using respec section labeling consistently
  2077 	</li>
  2044 	</li>
  2078 	<li>
  2045 	<li>update ldpc's with all required props
  2079 	</li>
       
  2080 	<li>
       
  2081 	</li>
       
  2082 	<li>
       
  2083 	</li>
       
  2084 	<li>
       
  2085 	</li>
       
  2086 	<li>
       
  2087 	</li>
       
  2088 	<li>
       
  2089 	</li>
       
  2090 	<li>
       
  2091 	</li>
       
  2092 	<li>
       
  2093 	</li>
  2046 	</li>
  2094 </ul>
  2047 </ul>
  2095 	</li>
  2048 	</li>
  2096 </ul>
  2049 </ul>
  2097 	<div class="ldp-issue-open">
  2050 	<div class="ldp-issue-open">
  2098 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/37">ISSUE-37</a></div>
  2051 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/37">ISSUE-37</a></div>
  2099 	Additional introductory text on the LDP data and interaction model
  2052 	Additional introductory text on the LDP data and interaction model
  2100 	</div>
  2053 	</div>
  2101 </section>
  2054 </section>
       
  2055 
  2102     
  2056     
  2103   </body>
  2057   </body>
  2104 </html>
  2058 </html>