From 1db0877ab265cf9fee6dc9ecb3bab2cef89c2930 Mon Sep 17 00:00:00 2001
From: Rob Atkinson
Date: Tue, 17 Sep 2019 22:54:34 +1000
Subject: [PATCH 1/4] Added order of precedence text
---
conneg-by-ap/index.html | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html
index 0a16dd893..c4be00a37 100644
--- a/conneg-by-ap/index.html
+++ b/conneg-by-ap/index.html
@@ -840,6 +840,15 @@ Alternate Representations Data Model
also given in Functional Profiles of this specification are also given in that appendix.
+
+ Order of Precedence for Implementation Profiles
+
+ It is possible that multiple functional profiles MAY be implemented by a service, including HTTP, QSA and possibly other approaches. In such clases a client MAY specify conflicting choices via different mechanisms. The order of precedence determines which mechanism MUST be used.
+
+
+ The order of precedence is QSA over HTTP - on the basis that human agency may be used to determine URL elements whereas client software is more likely to determine header content, and header content is less visible to human agents. If other profiles of the abstract model are defined each MUST specify order of precedence.
+
+
Functional Profiles
From e1963fc4be1d237e11198a9fbef4e4c90b535dec Mon Sep 17 00:00:00 2001
From: Rob Atkinson
Date: Tue, 17 Sep 2019 23:20:21 +1000
Subject: [PATCH 2/4] updates for issues in #575
---
conneg-by-ap/index.html | 10 ++++++----
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html
index c4be00a37..08e6d3571 100644
--- a/conneg-by-ap/index.html
+++ b/conneg-by-ap/index.html
@@ -283,13 +283,13 @@ Motivation
From dbb303e60736985d22e2f7d9361d670607a8240e Mon Sep 17 00:00:00 2001
From: Rob Atkinson
Date: Tue, 17 Sep 2019 23:23:25 +1000
Subject: [PATCH 3/4] Lars requested changes
---
conneg-by-ap/index.html | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html
index 08e6d3571..e86a406c7 100644
--- a/conneg-by-ap/index.html
+++ b/conneg-by-ap/index.html
@@ -846,7 +846,9 @@ Order of Precedence for Implementation Profiles
It is possible that multiple functional profiles MAY be implemented by a service, including HTTP, QSA and possibly other approaches. In such clases a client MAY specify conflicting choices via different mechanisms. The order of precedence determines which mechanism MUST be used.
- The order of precedence is QSA over HTTP - on the basis that human agency may be used to determine URL elements whereas client software is more likely to determine header content, and header content is less visible to human agents. If other profiles of the abstract model are defined each MUST specify order of precedence.
+ The order of precedence is QSA over HTTP - on the basis that the more exactly a URI points to a resource, the more likely it is that the agent intends to request that precise resource irrespective of which HTTP headers are sent with that request.
+
+ if other profiles of the abstract model are defined each MUST specify order of precedence.
From 080d5f3e651f57bcace49e35802b044e34185ba0 Mon Sep 17 00:00:00 2001
From: aisaac
Date: Tue, 17 Sep 2019 22:09:36 +0200
Subject: [PATCH 4/4] fixing a non-closed tag in the note on IETF
---
conneg-by-ap/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/conneg-by-ap/index.html b/conneg-by-ap/index.html
index 4e9e757e9..d6638f253 100644
--- a/conneg-by-ap/index.html
+++ b/conneg-by-ap/index.html
@@ -283,7 +283,7 @@ Motivation