Caching or pre-processing the AS2 context document

[evanp]

An AS2 processor that downloads and parses the AS2 context document at https://www.w3.org/ns/activitystreams each time it is invoked will be very inefficient. The preferred method for including the context document is to pre-process it within the processor code.

Should we note this is section 2.1? Or an appendix?

[trwnh]

We should note this in Section 2.1 directly. Newer JSON-LD adjacent work actually requires that you MUST treat their contexts as already resolved:

Verifiable Credentials Data Model 2.0

• https://www.w3.org/TR/vc-data-model-2.0/#contexts
• https://www.w3.org/TR/vc-data-model-2.0/#base-context

Implementations MUST treat the base context value, located at https://www.w3.org/ns/credentials/v2, as already retrieved; the following value is the hexadecimal encoded SHA2-256 digest value of the base context file: 59955ced6697d61e03f2b2556febe5308ab16842846f5b586d7f1f7adec92734. It is possible to confirm the cryptographic digest above by running the following command from a modern Unix command interface line: curl -s https://www.w3.org/ns/credentials/v2 | openssl dgst -sha256.

Controlled Identifiers 1.0

• https://www.w3.org/TR/cid-1.0/#contexts-and-vocabularies

Implementations that perform JSON-LD processing MUST treat the following JSON-LD context URL as already resolved, where the resolved document matches the corresponding hash value below:

[evanp]

We'd probably need to take on the versioning issue. I'd lean into semantic versioning, but hard to do with the W3C's document versioning system.