create different styles to differentiate issues based on their status: open, pending, closed
authorArnaud Le Hors <lehors@us.ibm.com>
Wed, 12 Jun 2013 23:36:47 +0100
changeset 124 6f1d7304f03f
parent 123 f027d5117282
child 125 24853c53dae0
create different styles to differentiate issues based on their status: open, pending, closed
ldp.html
--- a/ldp.html	Mon Jun 10 18:29:11 2013 -0400
+++ b/ldp.html	Wed Jun 12 23:36:47 2013 +0100
@@ -84,7 +84,7 @@
     </script>
     <style type="text/css">
     	div.rule {padding-top: 1em;}
-    	div.ldp-issue {
+    	div.ldp-issue-open {
 	    	border-color: #E05252;
 			background: #FBE9E9;
 			padding: 0.5em;
@@ -94,6 +94,26 @@
 			border-left-width: .5em;
 			border-left-style: solid;
     	}
+    	div.ldp-issue-pending {
+	    	border-color: #FAF602;
+			background: #F7F6BC;
+			padding: 0.5em;
+			margin: 1em 0;
+			position: relative;
+			clear: both;
+			border-left-width: .5em;
+			border-left-style: solid;
+    	}
+    	div.ldp-issue-closed {
+	    	border-color: #009900;
+			background: #BCF7CF;
+			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;
@@ -251,7 +271,7 @@
 requests and generates HTTP responses that conform to the rules defined in sections on <a href="#linked-data-platform-resources">LDPRs</a>
 and <a href="#linked-data-platform-containers">LDPCs</a></p>.
 
-<div class="ldp-issue">
+<div class="ldp-issue-open">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/57">ISSUE-57</a></div>
 	How can a client determine that it is in communication with an LDP server?
 	</div>
@@ -334,7 +354,7 @@
 		does not require the creation of an intermediate link resource to
 		describe the relationship.
 		
-	<div class="ldp-issue">
+	<div class="ldp-issue-closed">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/44">ISSUE-44</a></div>
 	4.1.9.(now 4.1.7) is obscure or too restrictive
 	</div>
@@ -354,23 +374,23 @@
 ones) as response <code>ETag</code> header values.
 	</div>
 	
-	<div class="ldp-issue">
+	<div class="ldp-issue-closed">
 	<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-open">
 	<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-pending">
 	<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-open">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/32">ISSUE-32</a></div>
 	How can clients discover that a resource is an LDPR or LDPC, and what features are supported?
 	</div>
-		<div class="ldp-issue">
+		<div class="ldp-issue-closed">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/33">ISSUE-33</a></div>
 	Pagination for non-container resources
 	</div>
@@ -520,7 +540,7 @@
 		<a href="#ldpc-HTTP_POST">POST (to an LDPC)</a> and/or <a href="#ldpc-HTTP_PUT">PUT</a> should be used as the standard way to create new LDPRs.
 	</div>
 	
-	<div class="ldp-issue">
+	<div class="ldp-issue-pending">
 	<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>
@@ -730,7 +750,7 @@
    a o:RealEstateHolding;
    o:value 300000.</pre>
 
-<div class="ldp-issue">
+<div class="ldp-issue-open">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/58">ISSUE-58</a></div>
 	Property for asserting that complete description of members is included in LDPC representation
 	</div>
@@ -987,7 +1007,7 @@
 		any kind of resource identified by its URI, LDPR or otherwise.
 	</div>
 	
-	<div class="ldp-issue">
+	<div class="ldp-issue-open">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/51">ISSUE-51</a></div>
 	Linking from a Resource to its Containers (not the containers the resource is in)
 	</div>
@@ -1113,7 +1133,7 @@
 	    last page, predicate of <code>ldp:nextPage</code> and object being <code>rdf:nil</code>.
 	</div>
 	
-	<div class="ldp-issue">
+	<div class="ldp-issue-closed">
 	<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>	
@@ -1125,7 +1145,7 @@
 		ordinal predicate literal data types supported are those as defined
 		by SPARQL SELECT’s ORDER BY clause [[!SPARQL-QUERY]].
 		
-			<div class="ldp-issue">
+			<div class="ldp-issue-closed">
 	<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>
@@ -1144,7 +1164,7 @@
 		only when an LDPC supports that method.  This specification does not impose any
 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
 		
-	<div class="ldp-issue">
+	<div class="ldp-issue-open">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/50">ISSUE-50</a></div>
 	Intuitive Containers: better support for relative URIs
 	</div>	
@@ -1163,7 +1183,7 @@
 		the site that implements the LDPC.
 	</div>
 	
-	<div class="ldp-issue">
+	<div class="ldp-issue-closed">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/35">ISSUE-35</a></div>
 	POSTing to a container MUST yield a fresh URI
 	</div>
@@ -1191,7 +1211,7 @@
 		triples in the created resource whose subject is the created
 		resource.  
 		
-	<div class="ldp-issue">
+	<div class="ldp-issue-closed">
 	<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 using &lt;&gt;
 	</div>	
@@ -1226,7 +1246,7 @@
 		only when an LDPC supports that method.  This specification does not impose any
 		new requirement to support that method, and [[!HTTP11]] makes it optional.</p>
 		
-	<div class="ldp-issue">
+	<div class="ldp-issue-open">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/56">ISSUE-56</a></div>
 	How can clients discover LDPR PUT URLs?
 	</div>	
@@ -1455,7 +1475,7 @@
  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.</li>
 </ul>
-	<div class="ldp-issue">
+	<div class="ldp-issue-open">
 	<div class="ldp-issue-title"><a href="http://www.w3.org/2012/ldp/track/issues/37">ISSUE-37</a></div>
 	Additional introductory text on the LDP data and interaction model
 	</div>