Fixed namespaces
authorsspeiche
Mon, 10 Mar 2014 11:01:48 -0400
changeset 532 18666ca04035
parent 531 938b34f100fb
child 534 3fd2143c0765
child 537 0e863fcf76df
Fixed namespaces
ldp-paging.html
ldp-paging.ttl
--- a/ldp-paging.html	Wed Mar 05 17:02:22 2014 +0000
+++ b/ldp-paging.html	Mon Mar 10 11:01:48 2014 -0400
@@ -301,7 +301,6 @@
 	@prefix foaf:     <http://xmlns.com/foaf/0.1/>.
 	@prefix rdf:     <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
 	@prefix ldp:     <http://www.w3.org/ns/ldp#>.
-	@prefix ldp-paging:     <http://www.w3.org/ns/ldp-paging#>.
 	@prefix xsd:     &lt;http://www.w3.org/2001/XMLSchema#&gt;.</pre>
 </section>
 </section>
@@ -559,7 +558,7 @@
 
 	<section id="ldpr-pagingGET-page-type-reqd"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST
 		provide an HTTP <code>Link</code>
-		header whose target URI is <code>http://www.w3.org/ns/ldp-paging#Page</code>, and whose link relation type is <code>type</code> [[!RFC5988]]
+		header whose target URI is <code>http://www.w3.org/ns/ldp#Page</code>, and whose link relation type is <code>type</code> [[!RFC5988]]
 		in responses to <code>GET</code> requests with any <a title="Single-page resource">single-page resource</a> 
 		as the <code>Request-URI</code>.
 		This is one mechanism by which clients know that the resource is one of a sequence of pages.  
@@ -653,11 +652,11 @@
 		Since more than one value may be used to sort members, 
 		the LDPC specification allows servers to assert the ordered list
 		of sort criteria used to sort the members, using the 
-		<code>ldp-paging:containerSortCriteria</code> relation.
-		Each member of the ordered list exposes one <code>ldp-paging:containerSortCriterion</code>, 
-		consisting of a <code>ldp-paging:containerSortOrder</code>, 
-		<code>ldp-paging:containerSortPredicate</code>, and 
-		optionally a <code>ldp-paging:containerSortCollation</code>.
+		<code>ldp:containerSortCriteria</code> relation.
+		Each member of the ordered list exposes one <code>ldp:containerSortCriterion</code>, 
+		consisting of a <code>ldp:containerSortOrder</code>, 
+		<code>ldp:containerSortPredicate</code>, and 
+		optionally a <code>ldp:containerSortCollation</code>.
 	</p>
 	<p>Here is an example container described
 		previously, with representation for ordering of the assets:</p>
@@ -668,7 +667,6 @@
 # @base &lt;http://example.org/netWorth/nw1/assetContainer/&gt;
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
[email protected] ldp-paging: &lt;http://www.w3.org/ns/ldp-paging#&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
 
 &lt;&gt;
@@ -679,14 +677,14 @@
    ldp:insertedContentRelation ldp:MemberSubject.
 
 &lt;?firstPage&gt;
-   a ldp-paging:Page;
-   ldp-paging:pageOf &lt;&gt;;
-   ldp-paging:containerSortCriteria (&lt;#SortValueAscending&gt;).
+   a ldp:Page;
+   ldp:pageOf &lt;&gt;;
+   ldp:containerSortCriteria (&lt;#SortValueAscending&gt;).
 
 &lt;#SortValueAscending&gt;
-   a ldp-paging:ContainerSortCriterion;
-   ldp-paging:containerSortOrder ldp-paging:Ascending;
-   ldp-paging:containerSortPredicate o:value.
+   a ldp:ContainerSortCriterion;
+   ldp:containerSortOrder ldp:Ascending;
+   ldp:containerSortPredicate o:value.
 
 &lt;http://example.org/netWorth/nw1&gt;
    a o:NetWorth;
@@ -703,7 +701,7 @@
    o:value 300000 .
 </pre>
 		<p>
-			As you can see by the addition of the <code>ldp-paging:ContainerSortCriteria</code> 
+			As you can see by the addition of the <code>ldp:ContainerSortCriteria</code> 
 			predicate, the <code>o:value</code> predicate is used
 			to order the page members in ascending order.  It is up to the domain model
 			and server to determine the appropriate predicate to indicate the
@@ -750,9 +748,9 @@
 		represent the members of a paged LDPC in a sequential
 		order.  If the server does so, it MUST specify the order using a triple 
 		whose subject is the page URI, 
-		whose predicate is <code>ldp-paging:containerSortCriteria</code>, 
+		whose predicate is <code>ldp:containerSortCriteria</code>, 
 		and whose object is a <code>rdf:List</code> of
-		<code>ldp-paging:containerSortCriterion</code> resources.  
+		<code>ldp:containerSortCriterion</code> resources.  
 		The resulting order MUST be as defined by SPARQL <code>SELECT</code>’s <code>ORDER BY</code> clause 
 		[[!sparql11-query]].
 		Sorting criteria MUST be the same for all pages of a representation; if
@@ -766,11 +764,11 @@
 	</h2></section><!-- Was 5.3.2 / #ldpc-5_3_2 -->
 	
 	<section id="ldpc-sortliteraltype"><h2 class="normal">LDPC page representations 
-		ordered using <code>ldp-paging:containerSortCriteria</code> MUST contain, 
-		in every <code>ldp-paging:containerSortCriterion</code> list entry, 
+		ordered using <code>ldp:containerSortCriteria</code> MUST contain, 
+		in every <code>ldp:containerSortCriterion</code> list entry, 
 		a triple
 		whose subject is the sort criterion identifier, 
-		whose predicate is <code>ldp-paging:containerSortPredicate</code> 
+		whose predicate is <code>ldp:containerSortPredicate</code> 
 		and whose object is 
 		the predicate whose value is used to order members between pages (the <dfn>page-ordering values</dfn>).
 		The only literal data types whose behavior LDP constrains are those defined
@@ -780,41 +778,41 @@
 	</h2></section><!-- Was 5.3.3 / #ldpc-5_3_3 -->
 	
 	<section id="ldpc-sortorder"><h2 class="normal">LDPC page representations 
-		ordered using <code>ldp-paging:containerSortCriteria</code> MUST contain, 
-		in every <code>ldp-paging:containerSortCriterion</code> list entry, 
+		ordered using <code>ldp:containerSortCriteria</code> MUST contain, 
+		in every <code>ldp:containerSortCriterion</code> list entry, 
 		a triple
 		whose subject is the sort criterion identifier, 
-		whose predicate is <code>ldp-paging:containerSortOrder</code> 
+		whose predicate is <code>ldp:containerSortOrder</code> 
 		and whose object describes the order used.
 		LDP defines two values,
-		<code>ldp-paging:Ascending</code> and <code>ldp-paging:Descending</code>, for use
+		<code>ldp:Ascending</code> and <code>ldp:Descending</code>, for use
 		as the object of this triple.  Other values can be used, but LDP
 		assigns no meaning to them and interoperability will be limited.
 	 </h2></section><!-- Was 5.3.4 / #ldpc-5_3_4 -->
 	
 	<section id="ldpc-sortcollation"><h2 class="normal">LDPC page representations 
-		ordered using <code>ldp-paging:containerSortCriteria</code> MAY contain, 
-		in any <code>ldp-paging:containerSortCriterion</code> list entry,
+		ordered using <code>ldp:containerSortCriteria</code> MAY contain, 
+		in any <code>ldp:containerSortCriterion</code> list entry,
 		a triple
 		whose subject is the sort criterion identifier, 
-		whose predicate is <code>ldp-paging:containerSortCollation</code> 
+		whose predicate is <code>ldp:containerSortCollation</code> 
 		and whose object identifies the collation used.
 		LDP defines no values for use
 		as the object of this triple.  While it is better for interoperability to use
 		open standardized values, any value can be used.
-		When the <code>ldp-paging:containerSortCollation</code> triple is absent and the 
+		When the <code>ldp:containerSortCollation</code> triple is absent and the 
 		<a title="page-ordering values">page-ordering values</a> are strings or simple literals [[!sparql11-query]], the
 		resulting order is as defined by SPARQL SELECT’s ORDER BY clause 
 		[[!sparql11-query]] using two-argument <code>fn:compare</code>, that is, 
 		it behaves as if <code>http://www.w3.org/2005/xpath-functions/collation/codepoint</code> 
 		was the specified collation.
-		When the <code>ldp-paging:containerSortCollation</code> triple is present and the 
+		When the <code>ldp:containerSortCollation</code> triple is present and the 
 		<a title="page-ordering values">page-ordering values</a> are strings or simple literals 
 		[[!sparql11-query]], the
 		resulting order is as defined by SPARQL SELECT’s ORDER BY clause 
 		[[!sparql11-query]] using three-argument <code>fn:compare</code>, that is, the 
 		specified collation.
-		The <code>ldp-paging:containerSortCollation</code> triple MUST be omitted for comparisons
+		The <code>ldp:containerSortCollation</code> triple MUST be omitted for comparisons
 		involving <a title="page-ordering values">page-ordering values</a> for which [[!sparql11-query]] does not use collations.
 	</h2></section><!-- Was 5.3.5 / #ldpc-5_3_5 -->
 
@@ -964,6 +962,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140730/">Last Call Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-03-10 - Fixed namespaces (SS) </li>
 	<li>2014-02-18 - Split off LDP-Paging from LDP (SS) </li>
 </ul>
 <blockquote><em><a href="https://dvcs.w3.org/hg/ldpwg/raw-file/94420c5678ae/ldp.html">February 18, 2014 Editor's Draft</a></em></blockquote>
--- a/ldp-paging.ttl	Wed Mar 05 17:02:22 2014 +0000
+++ b/ldp-paging.ttl	Mon Mar 10 11:01:48 2014 -0400
@@ -5,8 +5,7 @@
 @prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
 @prefix dcterms: <http://purl.org/dc/terms/>.
 @prefix vs: <http://www.w3.org/2003/06/sw-vocab-status/ns#> .
[email protected] ldp: <http://www.w3.org/ns/ldp#>.
[email protected] : <http://www.w3.org/ns/ldp-paging#>.
[email protected] : <http://www.w3.org/ns/ldp#>.
 
 :
 	a owl:Ontology;