From f164e62f16fdd7add27f973656e0cc3ef1d01000 Mon Sep 17 00:00:00 2001 From: YoucTagh Date: Tue, 19 Sep 2023 13:25:29 +0200 Subject: [PATCH 1/3] Address parts of issue #45 --- connegp/config.js | 13 +++++++------ connegp/index.html | 20 ++++++++++---------- 2 files changed, 17 insertions(+), 16 deletions(-) diff --git a/connegp/config.js b/connegp/config.js index 9717a64..aefd77b 100644 --- a/connegp/config.js +++ b/connegp/config.js @@ -49,9 +49,9 @@ var respecConfig = { "J. Kunze", "R. Rodgers" ], - href: "https://tools.ietf.org/id/draft-kunze-ark-15.txt", + href: "https://datatracker.ietf.org/doc/draft-kunze-ark/37/", title: "The ARK Identifier Scheme" , - date: "2008-05-22", + date: "2023-04-25", status: "Internet-Draft" }, "PROF-GUIDANCE": { @@ -69,11 +69,12 @@ var respecConfig = { "PROF-IETF": { authors: [ "L. Svensson", - "R. Verborgh" + "R. Verborgh", + "H. Van de Sompel" ], - href: "https://profilenegotiation.github.io/I-D-Profile-Negotiation/I-D-Profile-Negotiation", - title: "Indicating and Negotiating Profiles in HTTP", - date: " 2019-07-11", + href: "https://datatracker.ietf.org/doc/draft-svensson-profiled-representations/01/", + title: "Indicating, Discovering, Negotiating, and Writing Profiled Representations", + date: " 2021-03-09", status: "IETF Internet Draft" } } diff --git a/connegp/index.html b/connegp/index.html index 5e16cdd..519d0a8 100644 --- a/connegp/index.html +++ b/connegp/index.html @@ -26,7 +26,7 @@

Overview of DXWG documents on profiles

@@ -1714,7 +1714,7 @@

QSA key discovery

While the Link header in above communicates all the information that a list profiles request does, it is not visible directly in a web browser. shows a requests/response pair that include equivalent Link header and HTTP body information listing profiles, the - latter of which is visible in a browser but a client formulating this request is dependent on a it knowing + latter of which is visible in a browser but a client formulating this request is dependent on it knowing that the QSA key/value pair _profile=alt is used to trigger this response as opposed to the server's default resource representation.

@@ -2239,36 +2239,36 @@

Profiles Vocabulary descriptions of this specification's Functional Profiles prof:isProfileOf <https://www.w3.org/TR/dx-connegp/> ; rdfs:label "HTTP Headers Functional Profile" ; rdfs:comment "For conformance with the functional profile of Content Negotiation by - Profile presented in § 7.1 Hypertext Transfer Protocol Headers."@en ; + Profile presented in § 7.2 Hypertext Transfer Protocol Headers."@en ; skos:scopeNote "To be used if a resource conforms to the HTTP Headers functional profile"@en . cnpr:qsa a prof:Profile ; prof:isProfileOf cnpr:qsa-alt ; rdfs:label "QSA Functional Profile"@en ; rdfs:comment "For conformance with the functional profile of Content Negotiation by - Profile presented in § 7.2 URL Query String Arguments."@en ; + Profile presented in § 7.3 URL Query String Arguments."@en ; skos:scopeNote "To be used if a resource conforms to the QSA Functional Profile using the Query String Arguments _profile and _mediatype as per the - recommendations in § 7.2 URL Query String Arguments."@en . + recommendations in § 7.3 URL Query String Arguments."@en . cnpr:qsa-alt a prof:Profile ; prof:isProfileOf <https://www.w3.org/TR/dx-connegp/> ; rdfs:label "QSA Alternate Keywords Functional Profile" ; rdfs:comment "For conformance with the functional profile of Content Negotiation by - Profile presented in § 7.2 URL Query String Arguments."@en ; + Profile presented in § 7.3 URL Query String Arguments."@en ; skos:scopeNote "To be used if a resource conforms to the QSA Functional Profile but uses alternate keywords for the Query String Arguments _profile and - _mediatype, as allowed by the recommendations in § 7.2 URL Query + _mediatype, as allowed by the recommendations in § 7.3 URL Query String Arguments."@en . cnpr:rrd a prof:Profile ; prof:isProfileOf <https://www.w3.org/TR/dx-connegp/> ; rdfs:label "Resource Representation Description Profile"@en ; - rdfs:comment "For conformance with Content Negotiation by Profile § 6.2.2 get + rdfs:comment "For conformance with Content Negotiation by Profile § 6.3.2 get resource by profile."@en ; skos:scopeNote "To be used if a resource representation is able to indicate which profile(s) it conforms to, in its appropriate functional profile, - as per the abstract specification in § 6.2.2 get resource by + as per the abstract specification in § 6.3.2 get resource by profile."@en .
@@ -2307,7 +2307,7 @@

Demonstrating system conformance to Functional Profiles

The code in Code Listing 2 shows an imaginary Web Service documented using [[?VOCAB-DCAT-2]] and borrowing parts from its examples, such as - Example 49. + Example 48. Included is the predicate dct:conformsTo used as per [[?VOCAB-DCAT-2]] & [[?DX-PROF]]. Conformance here is claimed to the QSA Alternate Keywords Functional Profile profile which is indicated by the URI http://www.w3.org/ns/dx/connegp/profile/qsa-alt, identified as per From 2286e015429bf46bc8f60238f831c9be9938311f Mon Sep 17 00:00:00 2001 From: YoucTagh Date: Wed, 27 Sep 2023 16:34:10 +0200 Subject: [PATCH 2/3] change RFC 7231 with 9110 --- connegp/index.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/connegp/index.html b/connegp/index.html index 519d0a8..8a36fa3 100644 --- a/connegp/index.html +++ b/connegp/index.html @@ -237,7 +237,7 @@

Related Work