From d5737bc24625a75ce9085538f2c29def7425f9b2 Mon Sep 17 00:00:00 2001 From: Evan Prodromou Date: Fri, 19 Sep 2025 12:35:46 -0400 Subject: [PATCH] Issue #648: overly specific reason for not using relative URLs Issue #648 points out that the reason listed in Section 2.2 for not using relative URLs is incomplete and inexact. This erratum replaces the term "JSON parser implementations" with the more general and accurate "consumers", which is used elsewhere in the document. --- ERRATA.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ERRATA.md b/ERRATA.md index f5140a8..450f5f9 100644 --- a/ERRATA.md +++ b/ERRATA.md @@ -4,7 +4,7 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a ## Activity Streams - - None yet reported. + - Section 2.2 "IRIs and URLs" says that publishers SHOULD NOT generate AS2 documents with relative IRI and URL references because JSON parser implementations may not conserve the base context to resolve relative references. This is overly specific; there are other types of implementations that may also fail to conserve the base context. One correction is to simply remove the reference to JSON parsers and replace it with "consumers": "Relative IRI (and URL) references SHOULD NOT be used within an Activity Streams 2.0 document due to the fact that many consumers are not capable of reliably preserving the base context necessary to properly resolve relative references." ## Activity Vocabulary @@ -147,4 +147,4 @@ This document includes errata for the [Activity Streams](https://www.w3.org/TR/a } } } -``` \ No newline at end of file +```