From fb83a25482d9533347b9054ed377a29269cdce4a Mon Sep 17 00:00:00 2001 From: Nicholas Car Date: Sun, 20 Oct 2019 15:52:01 +1000 Subject: [PATCH 01/74] spelling, consistent altp URI --- conneg-by-ap/config.js | 2 +- conneg-by-ap/index.html | 58 +++++++++++++++++++++++------------------ 2 files changed, 33 insertions(+), 27 deletions(-) diff --git a/conneg-by-ap/config.js b/conneg-by-ap/config.js index 6709a905d..ae2b47764 100644 --- a/conneg-by-ap/config.js +++ b/conneg-by-ap/config.js @@ -1,5 +1,5 @@ var respecConfig = { - specStatus: "WD", + specStatus: "CR", shortName: "dx-prof-conneg", edDraftURI: "https://w3c.github.io/dxwg/conneg-by-ap/", previousPublishDate: "2019-04-30", diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html index ead66e98f..2afc225bd 100644 --- a/conneg-by-ap/index.html +++ b/conneg-by-ap/index.html @@ -746,7 +746,7 @@

Alternate Representations Data Model

also given in that appendix.

-
+

Order of Precedence for Implementation Profiles

A service MAY implement multiple functional profiles, including HTTP, QSA and possibly other approaches. @@ -767,12 +767,11 @@

Functional Profiles

Functional Profiles of this specification

- This section illustrates a few conformant functional profiles of this - specification's Abstract Model for different system environments. These - functional profiles are formally described in - and may be used within different environments - wishing to conform to this specification. Implementation of the profiles - illustrated here is not mandatory; any profile that conforms to the + This section illustrates a few functional profiles of this + specification's Abstract Model for different system environments. They + may be conformed to by systems operating within different environments + wishing to conform to this specification. Conforming to the profiles + illustrated here is not mandatory; conformance to any profile that conforms to the Abstract Model fulfills conformance to this specification.

@@ -802,7 +801,7 @@

Conformance to Functional Profiles

If a system wishes to show conformance to this specification, conformance to at least one functional profile of - it, such as those listed MUST be indicated. + it, such as those listed , MUST be indicated. is not an exhaustive list of functional profiles of this specification and users MAY instead make others for their environments, as described in the previous section.

@@ -1350,10 +1349,9 @@
Key naming

To conform to the "QSA Functional Profile", the QSA key _profile MUST be used to indicate a - profile token or URI and SHOULD use _mediatype to indicate a resource representation's Media + profile token or URI and the key _mediatype SHOULD be used to indicate a resource representation's Media Type.

-
The recommendation to standardise the use of _mediatype in QSA is at risk

When conforming to the profile "QSA Alternate Keywords Functional Profile", any key values acceptable within the specification of [[RFC3986]] MAY be used to indicate the desired profile. @@ -1678,14 +1676,19 @@

QSA key discovery

# QSA Alt, not a QSA Functional Profile-conformant system # The resource representations available conform to profile-x & profile-y. -# The profile-y-conformant representation is only available in XML +# The profile-x-conformant representation is available in HTML & Turtle, +# the profile-y-conformant representation is available only in XML HTTP/1.1 200 OK Link: - <http://example.org/resource/a?view=profile-x>; + <http://example.org/resource/a?view=profile-x&format=text/html>; rel="self"; type="text/html"; profile="http://otherexample.org/profile/x", + <http://example.org/resource/a?view=profile-x&format=text/turtle>; + rel="self"; + type="text/turtle"; + profile="http://otherexample.org/profile/x", <http://example.org/resource/a?view=profile-y&format=text/xml>; rel="alternate"; type="text/xml"; @@ -1707,8 +1710,8 @@

QSA key discovery

To communicate to a client what QSA key/value pair is used for list profiles when the "QSA Alternate Keywords Functional Profile" is conformed to, a server SHOULD, following the methods above for list profiles communication, indicate that a representation of the resource is available that conforms to the - Alternate Profiles Data Model described in . This is demonstrated - as an extension to in . + Alternate Profiles Data Model identified by the URI http://www.w3.org/ns/dx/conneg/altr. This is demonstrated + in which is an extension to . 

@@ -1719,31 +1722,35 @@ 
QSA key discovery

 
 HTTP/1.1 200 OK
 Link:
-  <http://example.org/resource/a?view=profile-x>;
+  <http://example.org/resource/a?view=profile-x&format=text/html>;
           rel="self";
           type="text/html";
           profile="http://otherexample.org/profile/x",
+  <http://example.org/resource/a?view=profile-x&format=text/turtle>;
+          rel="self";
+          type="text/turtle";
+          profile="http://otherexample.org/profile/x",
   <http://example.org/resource/a?view=profile-y&format=text/xml>;
           rel="alternate";
           type="text/xml";
-          profile="http://otherexample.org/profile/y",
-  <http://example.org/resource/a?view=altprofiles>;
+          profile="http://otherexample.org/profile/y"
+  <http://example.org/resource/a?view=altrep&format=application/ld+json>;
           rel="alternate";
           type="application/ld+json";
-          profile="http://www.w3.org/ns/dx/conneg/altprofiles"
+          profile="http://www.w3.org/ns/dx/conneg/altr"
 
 [default response content]

shows that for resource /resource/a there is a representation of it that conforms to the specification/profile - http://www.w3.org/ns/dx/conneg/altprofiles which is the URI identifying the Alternate Profiles - Data Model defined in . Since the example also shows the QSA - view=altprofiles can be used to formulate a request for this representation, dereferencing - http://example.org/resource/a?view=altprofiles will generate a response that also yields the - content of the request in but, since it is conformant to the - Alternate Profiles Data Model, the HTTP body of that response will also list the alternate profiles for - /resource/a as opposed to the default representation of it. + http://www.w3.org/ns/dx/conneg/altr which is the URI identifying the Alternate Profiles + Data Model defined in . +

+

The example also shows the QSA view=altrep can be used to formulate a request for a Alternate + Profiles Data Model-conformant response. Dereferencing http://example.org/resource/a?view=altrep + will therefore generate a response that also yields equivalent content to the Link header content + in rather than the default representation of /resource/a.

@@ -1924,7 +1931,6 @@

Features at Risk

From d7a4338b160736c26204c66b88140385c5817873 Mon Sep 17 00:00:00 2001 From: Nicholas Car Date: Sun, 20 Oct 2019 16:02:07 +1000 Subject: [PATCH 02/74] renaming profile appendixes --- conneg-by-ap/index.html | 71 +++++++++++++++++++++-------------------- 1 file changed, 37 insertions(+), 34 deletions(-) diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html index 2afc225bd..467fe8cb9 100644 --- a/conneg-by-ap/index.html +++ b/conneg-by-ap/index.html @@ -1953,8 +1953,8 @@

Security and Privacy

Appendices

-
-

Profiles of this specification

+
+

Profiles Vocabulary descriptions of this specification's Functional Profiles

This specification contains a number of distinct functional profiles that are identified and described in words in . This appendix presents descriptions of these functional profiles, and the relations @@ -2046,37 +2046,41 @@

Profiles of this specification

hierarchy. -
-

Demonstrating conformance to profiles

-

- With the identification of profiles of this specification given in and - their relations described using the Profiles Vocabulary [[?PROF]] in this appendix, it is possible for - resources to show conformance to the this specification or any of the profiles by using mechanisms recommended - in [[?PROF]]. PROF's recommendation is that any resource, for example <http://example.org/resource/a>, - wishing to claim conformance to a specification or a profile use the [[DCTERMS]] - - dct:conformsTo predicate like this: -

-

- <http://example.com/resource/a> dct:conformsTo <SPEC_OR_PROFILE_URI> . -

-

- The <SPEC_OR_PROFILE_URI> may be this specification's URI but, in the best case, would be - one of the profile URIs listed in since it is much clearer what is being - conformed to when the profile URIs are cited as they are narrow in scope than the specification as a whole. -

-

- 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, - that includes a dct:conformsTo predicate as [[?VOCAB-DCAT-2]], as well as [[?PROF]], suggest for - use. Conformance here is claimed to be to the QSA Alternate Keywords Functional Profile profile indicated by - the URI http://www.w3.org/ns/dx/conneg/profile/qsa-alt, as it is identified in - . -

- 
+
+
+

Demonstrating system conformance to Functional Profiles

+

+ With the identification of functional profiles of this specification given in and + their relations described using the Profiles Vocabulary [[?PROF]] in this appendix, it is possible for + resources to show conformance to the this specification or any of the profiles by using mechanisms recommended + in [[?PROF]]. PROF's recommendation is that any resource, for example <http://example.org/resource/a>, + wishing to claim conformance to a specification or a functional profile use the [[DCTERMS]] + + dct:conformsTo predicate like this: +

+

+ <http://example.com/resource/a> dct:conformsTo <SPEC_OR_PROFILE_URI> . +

+

+ The <SPEC_OR_PROFILE_URI> may be this specification's URI, https://www.w3.org/TR/dx-prof-conneg/, but in the best case, would be + one of the profile URIs listed in since it is much clearer what is being + conformed to when functional profile URIs are cited as they are narrower in scope than the specification as a whole. +

+

+ A system wishing to claim conformance to multiple conformance targets - the specification or functional profiles of it - may do so with multiple uses of dct:conformsTo. +

+

+ 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, + that includes a dct:conformsTo predicate as [[?VOCAB-DCAT-2]], as well as [[?PROF]], suggest for + use. Conformance here is claimed to be to the QSA Alternate Keywords Functional Profile profile indicated by + the URI http://www.w3.org/ns/dx/conneg/profile/qsa-alt, as it is identified in + . +

+ 
 

 CODE LISTING 2: An example Web Service claiming conformance to the QSA Alternate Keywords
 Functional Profile of this specification
@@ -2101,7 +2105,6 @@ 
Demonstrating conformance to profiles

     # Swagger UI system
     dcat:endpointDescription <http://example.com/service/v2/xx/swagger> ;
-

Alternate Representations Data Model - Details

From 3af0a5c3e431040949e5c55565303b9814c5850c Mon Sep 17 00:00:00 2001 From: Nicholas Car Date: Sun, 20 Oct 2019 21:49:17 +1000 Subject: [PATCH 03/74] updated PROF ref to 2PWD --- conneg-by-ap/config.js | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/conneg-by-ap/config.js b/conneg-by-ap/config.js index ae2b47764..9c5768fda 100644 --- a/conneg-by-ap/config.js +++ b/conneg-by-ap/config.js @@ -94,10 +94,10 @@ var respecConfig = { "Rob Atkinson", "Nicholas J. Car" ], - href: "https://www.w3.org/TR/2018/WD-dx-prof-20181218/", - title: "Profile Descriptions ontology", - date: "2018-12-18", - status: "W3C First Public Working Draft" + href: "https://www.w3.org/TR/2019/WD-dx-prof-20190402/", + title: "The Profiles Vocabulary", + date: "2019-04-02", + status: "W3C Second Public Working Draft" } } }; From 721a410ffcd8b137d81ee90c6f3237ae9ea7998c Mon Sep 17 00:00:00 2001 From: Nicholas Car Date: Sun, 20 Oct 2019 22:24:13 +1000 Subject: [PATCH 04/74] de-duplication of Functional Profile introductory text --- conneg-by-ap/index.html | 48 ++++++++++++++++------------------------- 1 file changed, 18 insertions(+), 30 deletions(-) diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html index 467fe8cb9..b9adc2721 100644 --- a/conneg-by-ap/index.html +++ b/conneg-by-ap/index.html @@ -775,8 +775,8 @@

Functional Profiles of this specification

Abstract Model fulfills conformance to this specification.

- This document provides functional profiles for two environments: HTTP and human browser (Query String - Arguments). For the human browser environment, two functional profiles are presented to demonstrate different modes of use. + This specification provides functional profiles of it for two environments: HTTP and human browser (Query String + Arguments) as well as a single action functional profile relevant to multiple environments. For the human browser environment, two functional profiles are presented to demonstrate different modes of use. Further functional profiles of this specification MAY be implemented either for other environments and or even for constrained scenarios within these environments, and implementers are encouraged create additional profiles conforming to this specification. @@ -787,26 +787,14 @@

Functional Profiles of this specification

this document or may develop other functional profiles that conform to the abstract model. Conformance to one of the profiles provided here guarantees conformance to the abstract model, but conformance can be - achieved with other functional profiles. Implementers of Content + achieved with other functional profiles too. Implementers of Content Negotiation by Profile need not ensure systems conform to multiple - functional profiles of this specification, they need only conform to the + functional profiles of this specification: they need only conform to the functional profile(s) relevant to their environment.

-
-
-

Conformance to Functional Profiles

-

- This specification defines several functional profiles to which systems may conform. - These functional profiles are identified by URIs and given in the table below. -

-

- If a system wishes to show conformance to this specification, conformance to at least one functional profile of - it, such as those listed , MUST be indicated. - is not an exhaustive list of functional profiles of this specification and users MAY instead make others - for their environments, as described in the previous section. -

- The namespace prefix for the functional profiles used in , the table below, is: + The functional profiles of this specification provided here are listed in . + The namespace prefix for them is:

  • cnpr → http://www.w3.org/ns/dx/conneg/profile/
    • @@ -1276,7 +1264,7 @@

    QSA Functional Profile description

    the QSA functional profile is fully specified here. Two forms of this QSA approach are presented: the first is the fixed keyword "QSA Functional Profile" and the second is the "QSA Alternate Keywords Functional Profile" according to which servers may implement any keywords they choose. These various functional profiles are - all identified in . + all identified in .

    Conformance of a system to any one, or perhaps multiple, of these functional profiles may be demonstrated as per @@ -1345,7 +1333,7 @@
    Key naming
    profiles are the "QSA Functional Profile" and "QSA Alternate Keywords Functional Profile" with the former being a profile of the latter. This is due to the former containing more stringent conformance rules ("narrower" rules) about how to achieve this specification's required functionality. - These functional profiles are identified and defined in . + These functional profiles are identified and defined in .

    To conform to the "QSA Functional Profile", the QSA key _profile MUST be used to indicate a @@ -1856,7 +1844,7 @@

    Changes since previous draft

  • : slight wording change
  • Status of this Document: slight changes to listing of other docs
  • : small changes to wording
    • -
  • : addition of
    • +
  • : addition of
  • : addition of a 3rd paragraph describing relation of this work to existing systems
  • : updated ref to IETF doc since it's changed, aligned examples with other section's examples, minor wording changes, removed closed issues
  • : replaced the "Context" subsection with 3 subsections: intro text, Background, Profile Identification but with essentially the same content, removal of closed issues, addition of 3 new examples (now 4, 5 & 6 with 7 being an updated version of the old 4), addition of a note & text about redirection
    • @@ -1957,7 +1945,7 @@

    Appendices

    Profiles Vocabulary descriptions of this specification's Functional Profiles

    This specification contains a number of distinct functional profiles that are identified and described in words in - . This appendix presents descriptions of these functional profiles, and the relations + . This appendix presents descriptions of these functional profiles, and the relations between them, according to the Profiles Vocabulary [[?PROF]].

    @@ -1986,7 +1974,7 @@

    Profiles Vocabulary descriptions of this specification's Functional Profiles class="codelisting nohighlight" aria-busy="false" aria-live="polite" title="Description of this specification and its profiles according to PROF">
    -CODE LISTING 1: Description of this specification and its profiles, as listed in +CODE LISTING 1: Description of this specification and its profiles, as listed in using the Profiles Vocabulary.
    @prefix dct: <http://purl.org/dc/terms/> . @@ -2050,9 +2038,9 @@

    Profiles Vocabulary descriptions of this specification's Functional Profiles

    Demonstrating system conformance to Functional Profiles

    - With the identification of functional profiles of this specification given in and + With the identification of functional profiles of this specification given in and their relations described using the Profiles Vocabulary [[?PROF]] in this appendix, it is possible for - resources to show conformance to the this specification or any of the profiles by using mechanisms recommended + systems to show conformance to the this specification or any of the profiles by using mechanisms recommended in [[?PROF]]. PROF's recommendation is that any resource, for example <http://example.org/resource/a>, wishing to claim conformance to a specification or a functional profile use the [[DCTERMS]] @@ -2063,26 +2051,26 @@

    Demonstrating system conformance to Functional Profiles

    The <SPEC_OR_PROFILE_URI> may be this specification's URI, https://www.w3.org/TR/dx-prof-conneg/, but in the best case, would be - one of the profile URIs listed in since it is much clearer what is being + one of the profile URIs listed in since it is much clearer what is being conformed to when functional profile URIs are cited as they are narrower in scope than the specification as a whole.

    A system wishing to claim conformance to multiple conformance targets - the specification or functional profiles of it - may do so with multiple uses of dct:conformsTo.

    - The code in Code Listing 2 shows an imaginary Web Service documented using + 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, that includes a dct:conformsTo predicate as [[?VOCAB-DCAT-2]], as well as [[?PROF]], suggest for use. Conformance here is claimed to be to the QSA Alternate Keywords Functional Profile profile indicated by the URI http://www.w3.org/ns/dx/conneg/profile/qsa-alt, as it is identified in - . + .

    - 
     
    
-CODE LISTING 2: An example Web Service claiming conformance to the QSA Alternate Keywords
+CODE LISTING 2: An example Web Service claiming conformance to the QSA Alternate Keywords
 Functional Profile of this specification
 
    
 <http://example.com/service/xx>

From 763ffe56aee064a91d910d4271e834b3c62bf97f Mon Sep 17 00:00:00 2001
From: Nicholas Car 
Date: Mon, 21 Oct 2019 01:53:27 +1000
Subject: [PATCH 05/74] Back to ED

---
 conneg-by-ap/config.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/conneg-by-ap/config.js b/conneg-by-ap/config.js
index 9c5768fda..768b31863 100644
--- a/conneg-by-ap/config.js
+++ b/conneg-by-ap/config.js
@@ -1,5 +1,5 @@
 var respecConfig = {
-    specStatus: "CR",
+    specStatus: "ED",
     shortName: "dx-prof-conneg",
     edDraftURI: "https://w3c.github.io/dxwg/conneg-by-ap/",
     previousPublishDate: "2019-04-30",

From 86e890ae9efb3c94ed67821812d2bb40b191250b Mon Sep 17 00:00:00 2001
From: Nicholas Car 
Date: Thu, 24 Oct 2019 13:06:15 +1000
Subject: [PATCH 06/74] addressing 3 x Karen's edits

---
 conneg-by-ap/index.html | 41 +++++++++++++++++++++++------------------
 1 file changed, 23 insertions(+), 18 deletions(-)

diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html
index b9adc2721..69cb981d2 100644
--- a/conneg-by-ap/index.html
+++ b/conneg-by-ap/index.html
@@ -547,7 +547,7 @@ 
    list profiles
    
 HTTP/1.1 200 OK
 Content-Type: application/json
 Content-Profile: <http://www.w3.org/ns/dx/conneg/profile/qsa>
-# This Link header indicates representations ar available that conform to Profile X
+# This Link header indicates representations are available that conform to Profile X
 # & Y and that the Profile X-conformant representations are available in HTML
 # & XML Media Types.
 Link:
@@ -775,8 +775,12 @@ 
    Functional Profiles of this specification
    
         Abstract Model fulfills conformance to this specification.
       
    
       
    
-        This specification provides functional profiles of it for two environments: HTTP and human browser (Query String
-        Arguments) as well as a single action functional profile relevant to multiple environments. For the human browser environment, two functional profiles are presented to demonstrate different modes of use.
+        This specification provides functional profiles of the abstract model for two environments: HTTP and human browser (Query String
+        Arguments) as well as a functional profile that specifies a single action - confirming which profile(s) a server response conforms to -
+        that is relevant to multiple environments, such as the HTTP and human browser environments.
+      
    
+      
    
+        For the human browser environment, two functional profiles are presented to demonstrate different modes of use.
         Further functional profiles of this specification MAY be implemented either for other environments and or even for
         constrained scenarios within these environments, and implementers are encouraged create additional profiles conforming to this
         specification.
@@ -787,9 +791,9 @@ 
    Functional Profiles of this specification
    
         this document or may develop other functional profiles that conform to
         the abstract model. Conformance to one of the profiles provided here
         guarantees conformance to the abstract model, but conformance can be
-        achieved with other functional profiles too. Implementers of Content
+        achieved with other functional profiles also. Implementers of Content
         Negotiation by Profile need not ensure systems conform to multiple
-        functional profiles of this specification: they need only conform to the
+        functional profiles of this specification; they need only conform to the
         functional profile(s) relevant to their environment.
       
    
       
    
@@ -2040,30 +2044,31 @@ 
    Demonstrating system conformance to Functional Profiles
    
       
    
         With the identification of functional profiles of this specification given in  and
         their relations described using the Profiles Vocabulary [[?PROF]] in this appendix, it is possible for
-        systems to show conformance to the this specification or any of the profiles by using mechanisms recommended
-        in [[?PROF]]. PROF's recommendation is that any resource, for example <http://example.org/resource/a>,
-        wishing to claim conformance to a specification or a functional profile use the [[DCTERMS]]
-        
-          dct:conformsTo predicate like this:
+        systems to show conformance to this specification or any functional profile of it using [[?PROF]] mechanisms.
+        This is done using the [[DCTERMS]] predicate dct:conformsTo
+        so that, for example, a system identified with the URI <http://example.org/system/a> claiming to
+        conform to a specification or functional profile identified by URI <SPEC_OR_PROFILE_URI> would do so like this:
       
    
       
    
-        <http://example.com/resource/a> dct:conformsTo <SPEC_OR_PROFILE_URI> .
+        <http://example.com/system/a> dct:conformsTo <SPEC_OR_PROFILE_URI> .
       
    
       
    
         The <SPEC_OR_PROFILE_URI> may be this specification's URI, https://www.w3.org/TR/dx-prof-conneg/, but in the best case, would be
-        one of the profile URIs listed in  since it is much clearer what is being
-        conformed to when functional profile URIs are cited as they are narrower in scope than the specification as a whole.
+        one of the profile URIs listed in  or another functional profile's URI,
+        since it is much clearer what is being conformed to when functional profile URIs are cited as they are narrower
+        in scope than the specification as a whole.
       
    
       
    
-        A system wishing to claim conformance to multiple conformance targets - the specification or functional profiles of it - may do so with multiple uses of dct:conformsTo.
+        A system wishing to claim conformance to multiple conformance targets - the specification or
+        functional profiles of it - may do so with multiple uses of dct:conformsTo.
       
    
       
    
         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,
-        that includes a dct:conformsTo predicate as [[?VOCAB-DCAT-2]], as well as [[?PROF]], suggest for
-        use. Conformance here is claimed to be to the QSA Alternate Keywords Functional Profile profile indicated by
-        the URI http://www.w3.org/ns/dx/conneg/profile/qsa-alt, as it is identified in
+        Example 49.
+        Included is the predicate dct:conformsTo used as per [[?VOCAB-DCAT-2]] & [[?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/conneg/profile/qsa-alt, identified as per
         .
       
    
       
    Date: Tue, 5 Nov 2019 00:01:11 +0000
Subject: [PATCH 07/74] previous affiliation

---
 dcat-implementation-report/config.js | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/dcat-implementation-report/config.js b/dcat-implementation-report/config.js
index cf3c2eb34..0aead210b 100644
--- a/dcat-implementation-report/config.js
+++ b/dcat-implementation-report/config.js
@@ -20,11 +20,12 @@ var respecConfig = {
     companyURL: "https://www.csiro.au/",
     w3cid: 1796
   },{
-    name:       "Alejandra Gonzalez Beltran",
+    name:       "Alejandra Gonzalez-Beltran",
     orcid:      "0000-0003-3499-8262",
     company:    "Scientific Computing Department, Science and Technology Facilities Council, UK",
     url: "https://www.scd.stfc.ac.uk/Pages/Alejandra-Gonzalez-Beltran.aspx",
     companyURL: "https://stfc.ukri.org/",
+    note: "Previously at the University of Oxford"
     w3cid: 61587
   },{
     name:       "Andrea Perego",

From 5049bb4610defa570e9a20173e9a759a4e0b79d4 Mon Sep 17 00:00:00 2001
From: Nicholas Car 
Date: Tue, 5 Nov 2019 10:12:33 +1000
Subject: [PATCH 08/74] ConnegP implementation report stub

---
 connegp-implementation-report/config.js       |  90 +++++++++++++
 .../extra.css                                 |   0
 connegp-implementation-report/index.html      | 126 ++++++++++++++++++
 3 files changed, 216 insertions(+)
 create mode 100644 connegp-implementation-report/config.js
 rename {conneg-by-ap => connegp-implementation-report}/extra.css (100%)
 create mode 100644 connegp-implementation-report/index.html

diff --git a/connegp-implementation-report/config.js b/connegp-implementation-report/config.js
new file mode 100644
index 000000000..d8e1c57cb
--- /dev/null
+++ b/connegp-implementation-report/config.js
@@ -0,0 +1,90 @@
+var respecConfig = {
+    specStatus: "base",
+    shortName: "dx-prof-conneg-implementation-report",
+    edDraftURI: "https://w3c.github.io/dxwg/conneg-implementation-report",
+    previousPublishDate: "2019-04-30",
+    previousMaturity: "PWD",
+    prevRecURI: "https://www.w3.org/TR/2019/WD-dx-prof-conneg-20190430/",
+    testSuiteURI: "https://github.com/w3c/conneg-prof-testing",
+    implementationReportURI: "https://github.com/w3c/conneg-prof-testing",
+    canonicalURI: "TR",
+    editors: [{
+        name:       "Lars G. Svensson",
+        company:    "Invited Expert and before at Deutsche Nationalbibliothek",
+        companyURL: "http://www.dnb.de/",
+	    orcid:      "0000-0002-8714-9718",
+        w3cid:      44603
+      },
+      {
+        name:       "Rob Atkinson",
+        company:    "Metalinkage, Open Geospatial Consortium",
+        companyURL: "http://www.opengeospatial.org/",
+        orcid:      "0000-0002-7878-2693"
+      },
+      {
+        name:       "Nicholas J. Car",
+        mailto:     "nicholas.car@surroundaustralia.com",
+        company:    "SURROUND Australia Pty Ltd and before at CSIRO",
+        companyURL: "https://surroundaustralia.com",
+        orcid:      "0000-0002-8742-7730",
+        w3cid:      70131
+    }],
+    wg: "Dataset Exchange Working Group",
+    wgURI: "https://www.w3.org/2017/dxwg/",
+    processVersion: 2019,
+    localBiblio: {
+        "ARK" : {
+           editors: [
+               "J. Kunze",
+               "R. Rodgers"
+            ],
+            href: "https://tools.ietf.org/id/draft-kunze-ark-15.txt",
+            title: "The ARK Identifier Scheme" ,
+            date: "2008-05-22",
+            status: "Internet-Draft"
+        },
+        "PROF-CONNEG": {
+            editors: [
+                "Lars G. Svensson",
+                "Rob Atkinson",
+                "Nicholas J. Car"
+            ],
+            href: "https://www.w3.org/TR/2018/WD-dx-prof-conneg-20181218/",
+            title: "Content Negotiation by Profile",
+            date: " 2018-12-18",
+            status: "W3C First Public Working Draft"
+        },
+        "PROF-GUIDANCE": {
+            editors: [
+                "Rob Atkinson",
+                "Karen Coyle",
+                "Antoine Isaac",
+                "Nicholas J. Car"
+            ],
+            href: "https://w3c.github.io/dxwg/profiles/",
+            title: "Profile Guidance",
+            date: " 2019-04-24",
+            status: "W3C Editor's Draft"
+        },
+        "PROF-IETF": {
+            authors: [
+                "L. Svensson",
+                "R. Verborgh"
+            ],
+            href: "https://profilenegotiation.github.io/I-D-Profile-Negotiation/I-D-Profile-Negotiation",
+            title: "Indicating and Negotiating Profiles in HTTP",
+            date: " 2019-07-11",
+            status: "IETF Internet Draft"
+        },
+        "PROF": {
+            editors: [
+                "Rob Atkinson",
+                "Nicholas J. Car"
+            ],
+            href: "https://www.w3.org/TR/2018/WD-dx-prof-20181218/",
+            title: "Profile Descriptions ontology",
+            date: "2018-12-18",
+            status: "W3C First Public Working Draft"
+        }
+    }
+};
diff --git a/conneg-by-ap/extra.css b/connegp-implementation-report/extra.css
similarity index 100%
rename from conneg-by-ap/extra.css
rename to connegp-implementation-report/extra.css
diff --git a/connegp-implementation-report/index.html b/connegp-implementation-report/index.html
new file mode 100644
index 000000000..700efb28f
--- /dev/null
+++ b/connegp-implementation-report/index.html
@@ -0,0 +1,126 @@
+
+
+  
+    
+    Conneg by P Implementation Report
+    
+    
+    
+    
+  
+  
+    
    
+      
    
+      This document reports implementations of the Content Negotiation by Profile Candidate Recommendation [[PROF-CONNEG]].
    
+    
    
+    
    
+    
    
+      
    Introduction
    
+      
    
+        Content Negotiation by Profile describes how Internet clients may negotiate for content provided by servers based on data profiles to which the content conforms.
+      
    
+      
    
+        
    Methodology
    
+        
    We followed the steps described below to collect evidence for the revisions proposed in [[PROF-CONNEG]]:
    
+        
      
+          
    1. 
+            Identified the Functional Profiles of [[PROF-CONNEG]] that describe how to implement the specification in specific environments
+            
        
+              
      • As originally published, the specification has four Functional Profiles however new ones created by users can be added at any time
        • 
+              
      • New Functional Profiles will be listed here with implementations as they become known
        • 
+            
      
+          
      2. 
+          
    2. 
+            Per Functional Profile, listed the individual normative instructions per function or data model
+          
      3. 
+          
    3. 
+            Tabulated the Functional Profiles implementations claim to implement
+          
      4. 
+          
    4. 
+            Per Functional Profile implemented, tabulated the individual normative instructions implemented
+          
      5. 
+        
    
+      
    
+      
+    
    
+    
    
+      
    Implementation Evidence
    
+      
    
+        
    Functional Profiles Identified
    
+        
    The namespace prefixes for the functional profiles used in Table 1 below, are: 
    
+        
      
+          
    • cnpr → http://www.w3.org/ns/dx/conneg/profile/
+          
      • 
+        
    
+        
+          
+          
+            
+              
+              
+              
+            
+          
+          
+            
+              
+              
+              
+            
+            
+              
+              
+              
+            
+            
+              
+              
+              
+            
+            
+              
+              
+              
+            
+          
+        
    Table 1: Known Functional Profiles of Content Negotiation by Profile Identified
    URINameDescription
    cnpr:httpHTTP Headers Functional ProfileFor systems operating with the HTTP [[RFC7230]] protocols
    cnpr:qsaQSA Functional ProfileFor systems negotiating for content with the use of URI [[RFC3986]] Query String Arguments and using the _profile argument key and _profile=all key/value pair
    cnpr:qsa-altQSA Alternate Keywords Functional ProfileFor systems negotiating for content with the use of URI [[RFC3986]] Query String Arguments and using key values of their choice
    cnpr:rrdResource Representation DescriptionFor systems wanting to indicate that they are able to indicate which profile(s) responses returned conform to
    
+      
    
+
+      
    
+        
    Normative Instructions per Functional Profile
    
+      
    
+
+      
    
+        
    Functional Profiles Implemented
    
+      
    
+
+      
    
+        
    Normative Instructions per Functional Profile Implemented
    
+      
    
+    
    
+
+    
    
+      
    General analysis
    
+    
    
+
+    
    
+      
    Acknowledgements
    
+      
    
+        The editors gratefully acknowledge the contributions made to gathering evidence for [[PROF-CONNEG]] and reviewing
+        this report by all members of the
+        working group, especially Annette Greiner.
+      
    
+    
    
+
+  
+

From 7d0deb056a3beb2953462a3c3bab68379c3fd3d9 Mon Sep 17 00:00:00 2001
From: David Browning <33936348+davebrowning@users.noreply.github.com>
Date: Tue, 5 Nov 2019 17:44:56 +0100
Subject: [PATCH 09/74] Fix CR shows correct ...

...previous version
---
 dcat/config.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dcat/config.js b/dcat/config.js
index ccbce6033..0dd8d3cb5 100644
--- a/dcat/config.js
+++ b/dcat/config.js
@@ -9,8 +9,8 @@ var respecConfig = {
     prevRecShortname: "vocab-dcat",
     canonicalURI: "TR",
     prevRecURI:           "https://www.w3.org/TR/2014/REC-vocab-dcat-20140116/",    
-    previousPublishDate:  "2019-05-28",
-    previousMaturity:     "WD",
+    previousPublishDate:  "2019-10-03",
+    previousMaturity:     "CR",
 //    previousURI:          "https://www.w3.org/TR/2019/WD-vocab-dcat-2-20190528/",
     edDraftURI:           "https://w3c.github.io/dxwg/dcat/",
 //    issueBase:            "https://github.com/w3c/dxwg/issues/", -- Not needed when github used

From b7ea0ff2aa044eb7695a39e578006ad03d44c9e0 Mon Sep 17 00:00:00 2001
From: Simon Cox 
Date: Wed, 6 Nov 2019 07:15:04 +1100
Subject: [PATCH 10/74] Add .md suffix

---
 dcat/{dcat-tr-to-pr => dcat-tr-to-pr.md} | 0
 1 file changed, 0 insertions(+), 0 deletions(-)
 rename dcat/{dcat-tr-to-pr => dcat-tr-to-pr.md} (100%)

diff --git a/dcat/dcat-tr-to-pr b/dcat/dcat-tr-to-pr.md
similarity index 100%
rename from dcat/dcat-tr-to-pr
rename to dcat/dcat-tr-to-pr.md

From f31d869badf64205bbd23be44c84ebc610d3a104 Mon Sep 17 00:00:00 2001
From: Nicholas Car 
Date: Wed, 6 Nov 2019 07:28:50 +1000
Subject: [PATCH 11/74] renaming conneg-by-ap to connegp top-level dir

---
 README.md                                     |  2 +-
 {conneg-by-ap => connegp}/altr.svg            |  0
 {conneg-by-ap => connegp}/altr.ttl            |  0
 {conneg-by-ap => connegp}/config.js           |  0
 connegp/extra.css                             | 32 +++++++++++++++++++
 {conneg-by-ap => connegp}/index.html          |  0
 .../profiles-hierarchy.svg                    |  0
 {conneg-by-ap => connegp}/profiles.ttl        |  0
 8 files changed, 33 insertions(+), 1 deletion(-)
 rename {conneg-by-ap => connegp}/altr.svg (100%)
 rename {conneg-by-ap => connegp}/altr.ttl (100%)
 rename {conneg-by-ap => connegp}/config.js (100%)
 create mode 100644 connegp/extra.css
 rename {conneg-by-ap => connegp}/index.html (100%)
 rename {conneg-by-ap => connegp}/profiles-hierarchy.svg (100%)
 rename {conneg-by-ap => connegp}/profiles.ttl (100%)

diff --git a/README.md b/README.md
index e2d048e63..49cc4af21 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,7 @@
 - [The Profiles Vocabulary (Editors' Draft)](https://w3c.github.io/dxwg/prof/)
   - [The Profiles Vocabulary Second Public Working Draft](https://www.w3.org/TR/2019/WD-dx-prof-20190402/)
   - [The Profiles Vocabulary First Public Working Draft](https://www.w3.org/TR/2018/WD-dx-prof-20181218/)
-- [Content Negotiation by Profile (Editors' Draft)](https://w3c.github.io/dxwg/conneg-by-ap/)
+- [Content Negotiation by Profile (Editors' Draft)](https://w3c.github.io/dxwg/connegp/)
   - [Content Negotiation by Profile Second Public Working Draft](https://www.w3.org/TR/2019/WD-dx-prof-conneg-20190430/)
   - [Content Negotiation by Profile First Public Working Draft](https://www.w3.org/TR/2018/WD-dx-prof-conneg-20181218/)
 
diff --git a/conneg-by-ap/altr.svg b/connegp/altr.svg
similarity index 100%
rename from conneg-by-ap/altr.svg
rename to connegp/altr.svg
diff --git a/conneg-by-ap/altr.ttl b/connegp/altr.ttl
similarity index 100%
rename from conneg-by-ap/altr.ttl
rename to connegp/altr.ttl
diff --git a/conneg-by-ap/config.js b/connegp/config.js
similarity index 100%
rename from conneg-by-ap/config.js
rename to connegp/config.js
diff --git a/connegp/extra.css b/connegp/extra.css
new file mode 100644
index 000000000..71dc7d4ae
--- /dev/null
+++ b/connegp/extra.css
@@ -0,0 +1,32 @@
+table {
+    width: 100%;
+    border-collapse: collapse;
+}
+
+th {
+    background-color: #f2f2f2;
+}
+
+th, td {
+    border: 1px solid #ddd;
+}
+
+th, td {
+    padding: 10px;
+    text-align: left;
+}
+
+.codelisting {
+    padding:0 5px 5px 5px;
+    background-color: #eee;
+    border-left: solid 0.5em #999;
+}
+
+.codelisting-title {
+    font-family: sans-serif;
+    font-size: medium;
+    line-height: 1.5;
+    text-transform: none;
+    color: #666;
+    margin-top: -1em;
+}
diff --git a/conneg-by-ap/index.html b/connegp/index.html
similarity index 100%
rename from conneg-by-ap/index.html
rename to connegp/index.html
diff --git a/conneg-by-ap/profiles-hierarchy.svg b/connegp/profiles-hierarchy.svg
similarity index 100%
rename from conneg-by-ap/profiles-hierarchy.svg
rename to connegp/profiles-hierarchy.svg
diff --git a/conneg-by-ap/profiles.ttl b/connegp/profiles.ttl
similarity index 100%
rename from conneg-by-ap/profiles.ttl
rename to connegp/profiles.ttl

From 54e560efb78d8b2b098eb04a332a1879b7c99225 Mon Sep 17 00:00:00 2001
From: Nicholas Car 
Date: Wed, 6 Nov 2019 07:29:24 +1000
Subject: [PATCH 12/74] removing redundant folder

---
 conneg-by-ap/extra.css | 32 --------------------------------
 1 file changed, 32 deletions(-)
 delete mode 100644 conneg-by-ap/extra.css

diff --git a/conneg-by-ap/extra.css b/conneg-by-ap/extra.css
deleted file mode 100644
index 71dc7d4ae..000000000
--- a/conneg-by-ap/extra.css
+++ /dev/null
@@ -1,32 +0,0 @@
-table {
-    width: 100%;
-    border-collapse: collapse;
-}
-
-th {
-    background-color: #f2f2f2;
-}
-
-th, td {
-    border: 1px solid #ddd;
-}
-
-th, td {
-    padding: 10px;
-    text-align: left;
-}
-
-.codelisting {
-    padding:0 5px 5px 5px;
-    background-color: #eee;
-    border-left: solid 0.5em #999;
-}
-
-.codelisting-title {
-    font-family: sans-serif;
-    font-size: medium;
-    line-height: 1.5;
-    text-transform: none;
-    color: #666;
-    margin-top: -1em;
-}

From 74cf75b9dba4c93309c1922cb023060c0d466e1c Mon Sep 17 00:00:00 2001
From: Nicholas Car 
Date: Wed, 6 Nov 2019 07:31:57 +1000
Subject: [PATCH 13/74] addressing #issuecomment-549792703 as requested

---
 connegp/index.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/connegp/index.html b/connegp/index.html
index 69cb981d2..fddc3d140 100644
--- a/connegp/index.html
+++ b/connegp/index.html
@@ -776,8 +776,8 @@ 
    Functional Profiles of this specification
    
       
    
       
    
         This specification provides functional profiles of the abstract model for two environments: HTTP and human browser (Query String
-        Arguments) as well as a functional profile that specifies a single action - confirming which profile(s) a server response conforms to -
-        that is relevant to multiple environments, such as the HTTP and human browser environments.
+        Arguments). It also provides a functional profile that has the single function to respond with which profile(s)
+        a server response conforms to, and which can be used in multiple environments.
       
    
       
    
         For the human browser environment, two functional profiles are presented to demonstrate different modes of use.

From e61a7d3ef5d398a2c985f0b0faa704360dd0295a Mon Sep 17 00:00:00 2001
From: Nicholas Car 
Date: Wed, 6 Nov 2019 07:39:19 +1000
Subject: [PATCH 14/74] updating refs to specref tokens

---
 connegp-implementation-report/config.js  | 21 ---------------------
 connegp-implementation-report/index.html | 10 +++++-----
 2 files changed, 5 insertions(+), 26 deletions(-)

diff --git a/connegp-implementation-report/config.js b/connegp-implementation-report/config.js
index d8e1c57cb..f69c88223 100644
--- a/connegp-implementation-report/config.js
+++ b/connegp-implementation-report/config.js
@@ -43,17 +43,6 @@ var respecConfig = {
             date: "2008-05-22",
             status: "Internet-Draft"
         },
-        "PROF-CONNEG": {
-            editors: [
-                "Lars G. Svensson",
-                "Rob Atkinson",
-                "Nicholas J. Car"
-            ],
-            href: "https://www.w3.org/TR/2018/WD-dx-prof-conneg-20181218/",
-            title: "Content Negotiation by Profile",
-            date: " 2018-12-18",
-            status: "W3C First Public Working Draft"
-        },
         "PROF-GUIDANCE": {
             editors: [
                 "Rob Atkinson",
@@ -75,16 +64,6 @@ var respecConfig = {
             title: "Indicating and Negotiating Profiles in HTTP",
             date: " 2019-07-11",
             status: "IETF Internet Draft"
-        },
-        "PROF": {
-            editors: [
-                "Rob Atkinson",
-                "Nicholas J. Car"
-            ],
-            href: "https://www.w3.org/TR/2018/WD-dx-prof-20181218/",
-            title: "Profile Descriptions ontology",
-            date: "2018-12-18",
-            status: "W3C First Public Working Draft"
         }
     }
 };
diff --git a/connegp-implementation-report/index.html b/connegp-implementation-report/index.html
index 700efb28f..5bf8997fe 100644
--- a/connegp-implementation-report/index.html
+++ b/connegp-implementation-report/index.html
@@ -2,7 +2,7 @@
 
   
     
-    Conneg by P Implementation Report
+    Content Negotiation by Profile Implementation Report