using <pre><code>..</code></pre> for multiline code in UC&R
authorsteve.battle <steve.battle@sysemia.co.uk>
Thu, 17 Oct 2013 10:14:44 +0100
changeset 383 0f8e96885093
parent 382 c7270e98c5c3
child 384 adfc713130ec
child 390 4b14b120836f
using <pre><code>..</code></pre> for multiline code in UC&R
ldp-ucr.html
--- a/ldp-ucr.html	Thu Oct 17 09:50:13 2013 +0100
+++ b/ldp-ucr.html	Thu Oct 17 10:14:44 2013 +0100
@@ -847,7 +847,7 @@
 		each issue is itself a container of attachments.
 		In the example, <code>issue1234</code> is a member of the container <code>top-level-container</code>. In turn, <code>attachment324</code> and <code>attachment251</code> are attachments within <code>issue1234</code>. Treating these as containers makes it easier to manage them as self-contained units.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt;.
 @prefix oslc_cm: &lt;http://open-services.net/ns/cm#&gt;.
@@ -862,7 +862,7 @@
 
 :attachments a oslc_cm:AttachmentList;
       oslc_cm:attachment :attachment324, :attachment251.
-</pre>
+</code></pre>
 	<div>(see functional requirement <a>F1.2</a>)</div>
 	</section>
 	<section id="s1.3">
@@ -925,7 +925,7 @@
 		created and updated as a single-unit, even though it may describe
 		ancillary resources, such as a <code>foaf:Person</code>, below.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix foaf:  &lt;http://xmlns.com/foaf/0.1/&gt; .
 
 &lt;&gt; a foaf:PersonalProfileDocument;
@@ -941,7 +941,7 @@
 		foaf:mbox &lt;mailto:[email protected]&gt;;
 		foaf:workplaceHomepage &lt;http://www.w3.org/&gt;.
 	]
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F2.1</a>)</div>
 	</section>
 	
@@ -1020,7 +1020,7 @@
 		&lt;http://www.w3.org/&gt;, that that fall under a completely different authority and
 		therefore can't be served directly from the LDP server at this location.</p>
 	<div>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix org: &lt;http://www.w3.org/ns/org#&gt; .
 @prefix owltime: &lt;http://www.w3.org/2006/time&gt; .
 @prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
@@ -1036,10 +1036,10 @@
 &lt;http://www.w3.org/&gt; a org:FormalOrganization ;
 	skos:prefLabel &quot;The World Wide Web Consortium&quot;@en ;
 	skos:altLabel &quot;W3C&quot; .
-</pre>
+</code></pre>
 </div>
 <div>
-<pre class='example'>
+<pre class='example'><code>
 @prefix org: &lt;http://www.w3.org/ns/org#&gt; .
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
 @base &lt;http://example.com/&gt; .
@@ -1047,7 +1047,7 @@
 &lt;director&gt; a org:Role ;
 	rdfs:label &quot;Director&quot; .
  
-</pre>
+</code></pre>
 </div>
 		<div>(see functional requirement <a>F3.1</a>)</div>
 	</section>
@@ -1062,7 +1062,7 @@
 		requires that the fragment part be stripped off before requesting
 		the URI from the server. The client can then read properties of the hash URI <code>&lt;#i&gt;</code> from the retrieved description.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @base &lt;http://www.w3.org/People/Berners-Lee/card&gt;
 @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
 @prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt;.
@@ -1071,7 +1071,7 @@
 	dc:title &quot;Tim Berners-Lee's FOAF file&quot; ;
 	foaf:homepage &lt;http://www.w3.org/People/Berners-Lee/&gt; ;
 	foaf:primaryTopic &lt;#i&gt; .
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F3.2</a>)</div>
 	</section>
 	</section>
@@ -1106,7 +1106,7 @@
 		of the resource would allow a user to replace the information about the
 		award without disturbing the information about the event.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix : &lt;http://example.com/&gt;.
 @prefix sport: &lt;http://www.bbc.co.uk/ontologies/sport/&gt; .
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
@@ -1116,11 +1116,11 @@
     sport:award &lt;#gold_medal&gt; .
 
 &lt;#gold_medal&gt; a sport:Award .
-</pre>
+</code></pre>
 	<p>The description can be enriched as events unfold, adding a link to
 		the winner of the gold medal by substituting the above description
 		with the following.</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix : &lt;http://example.com/&gt;.
 @prefix sport: &lt;http://www.bbc.co.uk/ontologies/sport/&gt; .
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
@@ -1134,7 +1134,7 @@
         a foaf:Agent ;
         foaf:name &quot;Chris Hoy&quot; .
     ] .
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F4.1</a>)</div>
 	</section>
 	
@@ -1144,7 +1144,7 @@
 		This relates to user story <a>Data Catalogs</a>. A catalogue is
 		described by the following RDF model, based on the Data Catalog Vocabulary [[vocab-dcat]] which provides a standard format for representing the metadata held by organizations.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix : &lt;http://example.com/&gt;.
 @prefix dcat: &lt;http://www.w3.org/ns/dcat#&gt; .
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
@@ -1152,7 +1152,7 @@
  :catalog a dcat:Catalog ;
     dcat:dataset :dataset/001;
     dcterms:issued &quot;2012-12-11&quot;^^xsd:date.
-</pre>
+</code></pre>
 	<p>
 		A catalog may contain multiple datasets, so when linking to new
 		datasets it would be simpler and preferable to selectively add
@@ -1160,7 +1160,7 @@
 		dataset. The following update would be directed to the catalogue
 		to add an additional dataset.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix : &lt;http://example.com/&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt; .
 @prefix cs: &lt;http://purl.org/vocab/changeset/schema#&gt; .
@@ -1177,7 +1177,7 @@
     rdf:predicate dcat:dataset ;
     rdf:object :dataset/002 .
   ] .
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F4.2</a>)</div>
 	</section>
 	</section>
@@ -1216,7 +1216,7 @@
 		resource below, represents a sensor described using the Semantic
 		Sensor Network [[SSN]] ontology.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix : &lt;http://example.com/energy-management/&gt;.
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
 @prefix ssn: &lt;http://purl.oclc.org/NET/ssnx/ssn#&gt; .
@@ -1227,7 +1227,7 @@
 	a :FrequencyMeasurementCapability;
 	ssn:hasMeasurementProperty &lt;#property_1&gt; .
   ] .
-</pre>
+</code></pre>
 	<p>
 		The value of the sensor changes in real-time as measurements are
 		taken. The LDP client can interrogate the resource below to
@@ -1236,7 +1236,7 @@
 		are represented disjointly (separate RDF representations) they may
 		change independently.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix : &lt;http://example.com/energy-management/&gt; .
 @prefix ssn: &lt;http://purl.oclc.org/NET/ssnx/ssn#&gt; .
 @prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
@@ -1245,7 +1245,7 @@
 &lt;http://example.com/energy-management#property_1&gt; :hasMeasurementPropertyValue &lt;&gt; .
 &lt;&gt; a :FrequencyValue;
 	:hasQuantityValue &quot;50&quot;^^xsd:float.
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F5.1</a>)</div>
 	</section>
 	</section>
@@ -1289,7 +1289,7 @@
 		description of the collection,
 		also demonstrating that the relationship between the parent and child resources may run in a seemingly counter-intuitive direction, from child to parent.
 		</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix scheme : &lt;http://example.com/concept-scheme/&gt;.
 @prefix concept : &lt;http://example.com/concept/&gt;.
 @prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt; .
@@ -1297,7 +1297,7 @@
 scheme:subject-heading a skos:ConceptScheme.
 
 concept:Outer+space+Exploration skos:inScheme scheme:subject-heading.
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F6.1</a>)</div>
 	</section>
 	
@@ -1318,7 +1318,7 @@
 		concept <code>:TissueSpecimenFromHeart</code> belongs to two parent collections as it is both a  <code>:TissueSpecimen</code> and a <code>:SpecimenFromHeart</code>.
 		This example also demonstrates how composition and aggregation support different scenarios, as the ability to have multiple parents should not be a possibility with composition.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix : &lt;http://example.com/snomed/&gt;.
 @prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt; .
 
@@ -1335,7 +1335,7 @@
 :TissueSpecimenFromHeart a skos:Concept;
 	:conceptID "128166000";
 	rdfs:label &quot;Tissue specimen from heart&quot;.
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F6.2</a>)</div>
 	</section>
 	</section>
@@ -1358,7 +1358,7 @@
 		without necessarily having to download a full listing of the items
 		within the collection.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt;.
 @prefix : &lt;http://example.org/bookshelf/&gt;.
 @prefix dcmitype: &lt;http://purl.org/dc/dcmitype/&gt;.
@@ -1370,7 +1370,7 @@
 	dcterms:abstract &quot;This is a directory of organisations specializing in Linked Data.&quot;
 	cld:isLocatedAt &lt;http://dir.w3.org&gt;
 	cld:isAccessedVia &lt;http://dir.w3.org/rdf/2012/directory/directory-list.xhtml?construct&gt;
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F7.1</a>)</div>
 	</section>
 	
@@ -1392,7 +1392,7 @@
 	<p>
 	Based on the example below, the item-level description should include as a minimum all the <code>rdfs:member</code> relationships. It need not include other properties of the collection, and it need not include additional properties of the members.
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix frbr: &lt;http://purl.org/vocab/frbr/core#&gt;.
 @prefix dc: &lt;http://purl.org/dc/elements/1.1/&gt;.
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
@@ -1408,7 +1408,7 @@
 	dc:title &quot;2 B R 0 2 B&quot; ;
 	frbr:creator &lt;#Vonnegut_Kurt&gt;;
 	frbr:manifestation &lt;ebook21279&gt;.
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F7.2</a>)</div>
 	</section>
 	</section>
@@ -1432,7 +1432,7 @@
 This leads to a very large resource description, especially if some basic information about the contacts is included as well. The size of this representation may be so large that retrieval in a single HTTP request is impractical.</p>
 
 <p>In this example the response to the first request includes a reference to the <code>next</code> resource in an ordered collection of resources. For the purposes of the example, we make use of the <code>next</code> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab/">XHTML Metainformation Vocabulary</a>. There is no presumption that the LDP specification will recommend the use of this vocabulary.</p>
-		<pre class='example'>
+		<pre class='example'><code>
 @prefix : &lt;http://example.com/people/&gt;.
 @prefix xhv: &lt;http://www.w3.org/1999/xhtml/vocab#&gt;.
 
@@ -1441,19 +1441,19 @@
    foaf:mbox &lt;mailto:[email protected]&gt;.
    
 &lt;&gt; xhv:next &lt;http://example.com/1234567890&gt;.
-		</pre>
+		</code></pre>
 		
 <p>When the client requests the resource identified by <code>next</code>, the response includes additional content that can be merged with the earlier data to construct a more complete model of the originally requested resource. It may also contain further <code>next</code> links, which may be requested in turn.</p> 
 		
 <p>The following representation is the response to the resource identified by <code>next</code>, completing the contacts list.</p>
 		
-		<pre class='example'>
+		<pre class='example'><code>
 @prefix : &lt;http://example.com/people/&gt;.
 
 :bob a foaf:Person;
    rdfs:label "Bob";
    foaf:mbox &lt;mailto:[email protected]&gt;.
-		</pre>
+		</code></pre>
 			<div>(see functional requirement <a>F8.1</a>)</div>
 		</section>
 	</section>
@@ -1481,7 +1481,7 @@
 		This example uses the Ontology for Media Resources to describe a media resource added to a
 		collection [[MEDIAONT]].
 	</p>
-	<pre class='example'>
+	<pre class='example'><code>
 @prefix ma: &lt;http://www.w3.org/ns/ma-ont#&gt; .
 
 &lt;dataset&gt; a ma:Collection ;
@@ -1489,7 +1489,7 @@
 
 &lt;dataset/image1.jpg&gt; a ma:MediaResource ;
 	ma:hasFormat &quot;image/jpeg&quot; .
-</pre>
+</code></pre>
 		<div>(see functional requirement <a>F9.1</a>)</div>
 	</section>