Steve Bate

Thanks for the pull request. I'll review shortly.

I also ran into this issue. The `Create.perform` dereferences the `@json["object"]` into the `@object` field. However, later in `process_status_params`, the `StatusParser` is provided with the original `@json` data that still...

> However, implementation practices may differ based on practical considerations, such as the cost of lookups and the need for a tie-breaking mechanism. The temporal dimension of linked data is...

There are also widely-used terms in the AS2 namespace that are not part of the normative context (`manuallyApprovesFollowers`, `sensitive`, `HashTag`, `movedTo`). My focus, for now, is only on the normative...

> The second thing I'll ask is that I'd love to get some help from volunteers on making these changes, IF we decide to do it. I'd rather no one...

If the normative context is modified in this way, will that possibly produce empty arrays in compacted documents? If so, how is that related to the mandatory AS2 requirement that:...

> The proposed context can can produce an empty array when compacting an empty array, but so does the current context. I think we need some clarification about the non-empty...

Defining a context term as both an object reference (`@id`) and a `@value` (if that's allowed) causes issues in modeling the associated vocabulary/ontology using OWL. In OWL, a property must...

> I'm not sure that the compactArrays option existed when AS2 was specified. It is described in the version of the JSON-LD API document included in the normative AS2 references....

Based on experimentation in JSON-LD Playground it appears that turning off the `compactArrays` for compaction may also result in other undesirable side effects. The following document: ```json { "@context": ["https://www.w3.org/ns/activitystreams"],...