--- 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: <http://purl.org/dc/terms/>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix oslc_cm: <http://open-services.net/ns/cm#>.
@@ -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: <http://xmlns.com/foaf/0.1/> .
<> a foaf:PersonalProfileDocument;
@@ -941,7 +941,7 @@
foaf:mbox <mailto:timbl@w3.org>;
foaf:workplaceHomepage <http://www.w3.org/>.
]
-</pre>
+</code></pre>
<div>(see functional requirement <a>F2.1</a>)</div>
</section>
@@ -1020,7 +1020,7 @@
<http://www.w3.org/>, 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: <http://www.w3.org/ns/org#> .
@prefix owltime: <http://www.w3.org/2006/time> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@@ -1036,10 +1036,10 @@
<http://www.w3.org/> a org:FormalOrganization ;
skos:prefLabel "The World Wide Web Consortium"@en ;
skos:altLabel "W3C" .
-</pre>
+</code></pre>
</div>
<div>
-<pre class='example'>
+<pre class='example'><code>
@prefix org: <http://www.w3.org/ns/org#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@base <http://example.com/> .
@@ -1047,7 +1047,7 @@
<director> a org:Role ;
rdfs:label "Director" .
-</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><#i></code> from the retrieved description.
</p>
- <pre class='example'>
+ <pre class='example'><code>
@base <http://www.w3.org/People/Berners-Lee/card>
@prefix foaf: <http://xmlns.com/foaf/0.1/>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@@ -1071,7 +1071,7 @@
dc:title "Tim Berners-Lee's FOAF file" ;
foaf:homepage <http://www.w3.org/People/Berners-Lee/> ;
foaf:primaryTopic <#i> .
-</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 : <http://example.com/>.
@prefix sport: <http://www.bbc.co.uk/ontologies/sport/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@@ -1116,11 +1116,11 @@
sport:award <#gold_medal> .
<#gold_medal> 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 : <http://example.com/>.
@prefix sport: <http://www.bbc.co.uk/ontologies/sport/> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@@ -1134,7 +1134,7 @@
a foaf:Agent ;
foaf:name "Chris Hoy" .
] .
-</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 : <http://example.com/>.
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@@ -1152,7 +1152,7 @@
:catalog a dcat:Catalog ;
dcat:dataset :dataset/001;
dcterms:issued "2012-12-11"^^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 : <http://example.com/>.
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix cs: <http://purl.org/vocab/changeset/schema#> .
@@ -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 : <http://example.com/energy-management/>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@prefix ssn: <http://purl.oclc.org/NET/ssnx/ssn#> .
@@ -1227,7 +1227,7 @@
a :FrequencyMeasurementCapability;
ssn:hasMeasurementProperty <#property_1> .
] .
-</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 : <http://example.com/energy-management/> .
@prefix ssn: <http://purl.oclc.org/NET/ssnx/ssn#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@@ -1245,7 +1245,7 @@
<http://example.com/energy-management#property_1> :hasMeasurementPropertyValue <> .
<> a :FrequencyValue;
:hasQuantityValue "50"^^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 : <http://example.com/concept-scheme/>.
@prefix concept : <http://example.com/concept/>.
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@@ -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 : <http://example.com/snomed/>.
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .
@@ -1335,7 +1335,7 @@
:TissueSpecimenFromHeart a skos:Concept;
:conceptID "128166000";
rdfs:label "Tissue specimen from heart".
-</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: <http://purl.org/dc/elements/1.1/>.
@prefix : <http://example.org/bookshelf/>.
@prefix dcmitype: <http://purl.org/dc/dcmitype/>.
@@ -1370,7 +1370,7 @@
dcterms:abstract "This is a directory of organisations specializing in Linked Data."
cld:isLocatedAt <http://dir.w3.org>
cld:isAccessedVia <http://dir.w3.org/rdf/2012/directory/directory-list.xhtml?construct>
-</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: <http://purl.org/vocab/frbr/core#>.
@prefix dc: <http://purl.org/dc/elements/1.1/>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
@@ -1408,7 +1408,7 @@
dc:title "2 B R 0 2 B" ;
frbr:creator <#Vonnegut_Kurt>;
frbr:manifestation <ebook21279>.
-</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 : <http://example.com/people/>.
@prefix xhv: <http://www.w3.org/1999/xhtml/vocab#>.
@@ -1441,19 +1441,19 @@
foaf:mbox <mailto:alice@example.com>.
<> xhv:next <http://example.com/1234567890>.
- </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 : <http://example.com/people/>.
:bob a foaf:Person;
rdfs:label "Bob";
foaf:mbox <mailto:bob@example.com>.
- </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: <http://www.w3.org/ns/ma-ont#> .
<dataset> a ma:Collection ;
@@ -1489,7 +1489,7 @@
<dataset/image1.jpg> a ma:MediaResource ;
ma:hasFormat "image/jpeg" .
-</pre>
+</code></pre>
<div>(see functional requirement <a>F9.1</a>)</div>
</section>