@[email protected] @[email protected] keep in mind we’re talking about as:context
and not @context
Co-Founder (NodeBB) | Husband 🤷♂️ and Dad 🙉 to three | Rock Climber 🧗♂️ | Foodie 🥙 | Conductor 🎵 | Saxophonist 🎷
✅ Small teams craft better code.
🗨️ Federating NodeBB (in-progress) with funding NLNet ♥️🇪🇺
@[email protected] @[email protected] keep in mind we’re talking about as:context
and not @context
@[email protected] just added an open floor item for tomorrow’s WG meeting to discuss Harvard’s Applied Social Media Lab (https://asml.cyber.harvard.edu/)
Looking forward to it!
@[email protected] Thanks for sharing this. I’m confused by these two sentences:
Collection type SHOULD be
Context
. …Add.target
MUST be a partial representation of the collection. Thus, if type of the collection isContext
, anyAdd
activity modifying that collection can be identified byAdd.target.type
.
My context collection is of type OrderedCollection
. I don’t believe Context
is one of the AS2 core types.
I don’t see any reference to collection type
being Context
in @[email protected]’s original document.
@[email protected] @[email protected] Right, it gets a little confusing when implementors inherit
context
from the objects they’re replying to (or maybe the root node?), but that’s exactly what 7888 tries to codify/demystify.But Akkoma’s use of
context
seems to be in line with 7888 (in that it’s pointing back to the resolvable context provided by NodeBB).