From 126cec2ef50a063b494d187ae59edf58d896fd4c Mon Sep 17 00:00:00 2001 From: Andy Seaborne Date: Wed, 27 Nov 2024 10:24:40 +0000 Subject: [PATCH] Remove local CSS for RFC2119 --- spec/index.html | 41 ++++++++++++++++++----------------------- 1 file changed, 18 insertions(+), 23 deletions(-) diff --git a/spec/index.html b/spec/index.html index ffe7ee7..16e916c 100644 --- a/spec/index.html +++ b/spec/index.html @@ -333,10 +333,6 @@ div.exampleWrapper { margin: 4px } div.exampleHeader { font-weight: bold; margin: 4px} - - em.rfc2119 { text-transform: lowercase; - font-variant: small-caps; - font-style: normal; } @@ -362,8 +358,10 @@

Introduction

A SPARQL service description lists the features of a SPARQL service made available via the [[[SPARQL12-QUERY]]]. This document describes both a method for discovering a service description from a specific SPARQL service and an RDF schema for encoding such descriptions in RDF.

Terminology

-

When this document uses the words MUST, SHOULD and MAY, and the words appear as emphasized text, they must be interpreted as described in [[RFC2119]].

+

When this document uses the words MUST, MUST NOT, SHOULD, SHOULD NOT, + and MAY, and the words appear as emphasized text, they must be + interpreted as described in [[RFC2119]]. +

The following terms are also in use throughout this document:

SPARQL Service
@@ -376,9 +374,9 @@

Terminology

Accessing a Service Description

-

SPARQL services made available via the SPARQL Protocol SHOULD return a service description document at the service endpoint when - dereferenced using the HTTP GET operation without any query parameter strings provided. This service description MUST be made - available in an RDF serialization, MAY be embedded in (X)HTML by way of [[[RDFa-core]]], and SHOULD use content negotiation if available in other RDF representations.

+

SPARQL services made available via the SPARQL Protocol SHOULD return a service description document at the service endpoint when + dereferenced using the HTTP GET operation without any query parameter strings provided. This service description MUST be made + available in an RDF serialization, MAY be embedded in (X)HTML by way of [[[RDFa-core]]], and SHOULD use content negotiation if available in other RDF representations.

Service Description Vocabulary

@@ -654,8 +652,7 @@

sd:resultFormat

Relates an instance of sd:Service to a format that is supported for serializing query results.

URIs for commonly used serialization formats are defined by Unique URIs for File Formats. For formats that do not have an existing URI, the <http://www.w3.org/ns/formats/media_type> and <http://www.w3.org/ns/formats/preferred_suffix> properties defined in that document SHOULD be used to describe the format.

+ "http://www.w3.org/ns/formats/preferred_suffix">http://www.w3.org/ns/formats/preferred_suffix> properties defined in that document SHOULD be used to describe the format.

@@ -676,8 +673,7 @@

sd:inputFormat

"#sd-dereferencesuris">sd:DereferencesURIs below).

URIs for commonly used serialization formats are defined by Unique URIs for File Formats. For formats that do not have an existing URI, the <http://www.w3.org/ns/formats/media_type> and <http://www.w3.org/ns/formats/preferred_suffix> properties defined in that document SHOULD be used to describe the format.

+ "http://www.w3.org/ns/formats/preferred_suffix">http://www.w3.org/ns/formats/preferred_suffix> properties defined in that document SHOULD be used to describe the format.

@@ -710,8 +706,8 @@

sd:defaultGraph

sd:namedGraph

Relates an instance of sd:GraphCollection (or its subclass sd:Dataset) to the description of one of - its named graphs. The description of such a named graph MUST include the sd:name property - and MAY include the sd:graph property.

+ its named graphs. The description of such a named graph MUST include the sd:name property + and MAY include the sd:graph property.

@@ -859,8 +855,7 @@

sd:EntailmentRegime

sd:EntailmentProfile

-

An instance of sd:EntailmentProfile represents a profile of an entailment regime. An entailment profile MAY impose restrictions on what constitutes valid RDF with respect to entailment. URIs for commonly used entailment profiles are defined by An instance of sd:EntailmentProfile represents a profile of an entailment regime. An entailment profile MAY impose restrictions on what constitutes valid RDF with respect to entailment. URIs for commonly used entailment profiles are defined by Unique URIs for OWL 2 Profiles.

@@ -878,7 +873,7 @@

sd:EntailmentProfile

sd:GraphCollection

An instance of sd:GraphCollection represents a collection of zero or more named graph descriptions. Each named graph description belonging - to an sd:GraphCollection MUST be linked with the sd:GraphCollection MUST be linked with the sd:namedGraph predicate.

@@ -893,7 +888,7 @@

sd:GraphCollection

sd:Dataset

An instance of sd:Dataset represents a RDF Dataset comprised of a default graph and zero or more named graphs.

-

The default graph of an sd:Dataset MUST be linked with the The default graph of an sd:Dataset MUST be linked with the sd:defaultGraph predicate.

@@ -1043,7 +1038,7 @@

sd:RequiresDataset

sd:EmptyGraphs

sd:EmptyGraphs, when used as the object of the sd:feature property, indicates that the underlying graph store supports empty graphs. A graph store - that supports empty graphs MUST NOT remove graphs that are left empty after triples are removed from them. (See 3.1 Graph Update in SPARQL 1.2 Update.)

@@ -1199,13 +1194,13 @@

Turtle Service Description

Conformance

A SPARQL service conformant with this specification:

    -
  1. MUST return RDF content when the service endpoint URL is accessed as described in section 2 Accessing a +
  2. MUST return RDF content when the service endpoint URL is accessed as described in section 2 Accessing a Service Description.
    3. -
  3. The RDF content returned from dereferencing a service endpoint URL <service-endpoint-URL> MUST include at +
  4. The RDF content returned from dereferencing a service endpoint URL <service-endpoint-URL> MUST include at least one triple matching: 
    ?service sd:endpoint <service-endpoint-URL> .
    5. -
  5. The RDF content returned MUST make use of the vocabulary defined in this document in accordance with the usage specified in +
  6. The RDF content returned MUST make use of the vocabulary defined in this document in accordance with the usage specified in section 3 Service Description Vocabulary.