Skip to content

Comments

Add erratum for fragment identifiers per issue #610#669

Open
evanp wants to merge 1 commit intomainfrom
issue-610
Open

Add erratum for fragment identifiers per issue #610#669
evanp wants to merge 1 commit intomainfrom
issue-610

Conversation

@evanp
Copy link
Contributor

@evanp evanp commented Feb 16, 2026

Issue #610 notes that there is no defined considerations for fragment identifiers with AS2. This erratum notes the absence, and suggests an adjustment to default to JSON-LD treatment.

Issue #610 notes that there is no defined considerations for fragment identifiers with AS2. This erratum notes the absence, and suggests an adjustment to default to JSON-LD treatment.
Copy link
Member

@snarfed snarfed left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

The one thing I immediately thought of is resolution failure, eg when fetching the URL (without fragment) returns 404, or doesn't return AS2, or returns an AS2 object that doesn't contain an element with the fragment id. (These are all common on the fediverse right now.) Some examples in w3c/activitypub#367 (comment) and further down the thread.

I expect this doesn't change our resolution failure logic at all, so we probably don't need to say anything explicitly, but I figured I'd check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants