Evan Prodromou

I definitely prefer using `attachment`, since it is more explicit and much easier to parse than working with HTML content and checking `rel=` values. I might suggest using an `Object`-derived...

Welp, 9 years later, I want to re-open this! I have been working on just this problem -- having the inverse property of `result`. I'd like to revisit the topic...

So, we have constraints from JSON-LD on the use of nulls: https://www.w3.org/TR/json-ld11/#null I think the place where we've gotten stuck in the past is using a `null` value in `id`...

There is a lot of text about null in the [Serialization](https://www.w3.org/TR/activitystreams-core/#syntaxconventions) section: > When serialized, absent properties are represented by either (a) setting the property value to null, or (b)...

Another option brought up by @trwnh is defining an AS2-specific "known to be nonexistent" value, like "rdf:Nil".

I just reread the notes. I actually think this is pretty interesting, and wouldn't mind including it in a next version, especially since it doesn't have much impact. I agree...

@steve-bate do you have a good example of when it would be useful to know that an object is an AS2 "actor" but not one of the 5 predefined types,...

This is an interesting conversation. I think it makes sense to continue it. I agree that relative URLs don't really work in a world where Activity Streams documents are flowing...

Is the fix here to change the ambiguous phrase "base context" to be more specific, like "`@base` statement in the `@context` section"?

I think the best next step is to simply remove the word "JSON" to make it clear that many implementations cannot or do not handle relative URLs. > Relative IRI...