Post AvE5aEBCENTaGdvdTs by steve@social.technoetic.com
 (DIR) More posts by steve@social.technoetic.com
 (DIR) Post #AvDkcMvkZIMIwvsq4O by silverpill@mitra.social
       2025-06-17T12:05:44.078035Z
       
       0 likes, 0 repeats
       
       @trwnh @raucao"the identifier is foo" does not mean "the identifier MUST always be expressed using the literal sequence of characters f, o, o".It does literally mean that. Furthermore, ActivityPub requires identifiers to be dereferenceable URIs, so even in an alternative reality where "X is Y" has a different meaning, as:Public is not a valid identifier.ActivityStreams requirements don't matter because we're implementing ActivityPub, not ActivityStreams.
       
 (DIR) Post #AvE5aEBCENTaGdvdTs by steve@social.technoetic.com
       2025-06-17T13:10:52Z
       
       0 likes, 0 repeats
       
       @silverpill @trwnh @raucao I don't think this is accurate or helpful. The first sentence of the AP spec: "The ActivityPub protocol is a decentralized social networking protocol based upon the ActivityStreams 2.0 data format.". Later, "ActivityPub uses ActivityStreams for its vocabulary." AS2 is referenced many times in the spec. It definitely *does* matter in an ActivityPub context.
       
 (DIR) Post #AvE5aFGYBxLxdXRQSu by silverpill@mitra.social
       2025-06-17T16:00:34.154370Z
       
       0 likes, 0 repeats
       
       @steve @trwnh @raucao I was talking about the specific requirement in ActivityPub.ActivityStreams may matter in other cases (however, as we have seen, it is not entirely clear whether "X is Y" and "X uses Y" are normative statements).
       
 (DIR) Post #AvEHQb6XLCTLvCvK0O by trwnh@mastodon.social
       2025-06-17T16:39:10Z
       
       0 likes, 0 repeats
       
       @silverpill @steve @raucao <Note> is <as:Note> is <https://www.w3.org/ns/activitystreams#Note>, but only "Note" is consistent with compacted JSON-LD.Fundamentally, identifiers are expressed in different ways depending on context. The prefix mechanism produces compact URIs, which are still intrinsically URIs despite their lexical form not being a valid URI. If you care about referents, you need to expand them."as:Public" is canonical for object properties (type:id). Disliking this fact doesn't make it untrue.
       
 (DIR) Post #AvEHQc0XyxH8iv83JA by trwnh@mastodon.social
       2025-06-17T16:48:39Z
       
       0 likes, 0 repeats
       
       @silverpill @steve @raucao The only thing I can really suggest is dropping the use of the prefix mechanism by undefining the `as` term, then rewriting all other term definitions to not use the `as:` prefix. This might make sense since the media type nominally guarantees the meaning of certain terms, and you really shouldn't define your own custom terms in the `as:` namespace, so maybe it's okay to say that no one should ever use `as:`. Is that the resolution you'd prefer?