Specs have references to themselves.

[gkellogg]

For example, there’s a reference to [JSON-LD11], which shouldn’t be there. This is due to some change in ReSpec.

[gkellogg]

See https://github.com/w3c/respec/issues/2363; ReSpec should be filtering them out.

[gkellogg]

There are also problems with data-cite where the citation is a self-reference. For example in the last WD, the definition for context references "The Context" section which is not a relative URL, but a link back to the ED with ReSpec query parameters used for publishing.

Unless something can be done in ReSpec, we may need to surround such spans in terms.html with something that can cause them to be removed, or use an alternative text.

[gkellogg]

@marcoscaceres, it doesn't seem that xref is a solution for this. It isn't wrong, but seems odd for a bibliographic section to have an entry for itself.

I might imagine that if in JSON-LD11, a reference to [[JSON-LD11]] might be a direct reference to the document itself, rather than to a bibliographic section. We could eliminate the [[JSON-LD11]] in the spec through post-processing, but we'd still have those that come from data-cite="JSON-LD11#..." that would create entries.

[gkellogg]

Fixed in 989b53b, w3c/json-ld-framing@88110d9, and w3c/json-ld-api@e1e989c.