the world if as2 used hal instead of jsonld
-
the world if as2 used hal instead of jsonld compacted form
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
mostly joking but the real problem is that there is just way too much rope in as2 letting things be strings, ids, arrays, etc
a little more verbosity would have given a lot less ambiguity
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
compare this
```
{
"to": [{"id": "some-actor"}]
}
```with this
```
{
"to": "some-actor"
}
```yes the second one looks cleaner but it actually is very messy when you try to do anything with it
if you were required to do the first one, then implementations would have a LOT less to worry about
-
erincandescent@akko.erincandescent.netreplied to trwnh@mastodon.social last edited by@trwnh AS2 should have had a mandatory context with non-functional (i.e. single valued) properties forced to be arrays *change my mind*
-
erincandescent@akko.erincandescent.netreplied to erincandescent@akko.erincandescent.net last edited by@trwnh (mandatory as in *this is the one context, if you use something else you use a different media type*)
-
trwnh@mastodon.socialreplied to erincandescent@akko.erincandescent.net last edited by
@erincandescent idk if media types solve anything. profiles might? limiting to a single context certainly reduces the burden of cascading contexts. but while this might make sense for e.g. mastodon to package its own "mastodon context" and each vendor to more or less provide their own context, i think this doesn't fundamentally change the media type. at least it shouldn't.
-
erincandescent@akko.erincandescent.netreplied to trwnh@mastodon.social last edited by@trwnh it's basically a way of saying that a given graph compacted into application/activity+json should always come in one canonical form, with extensions in expanded form
-
trwnh@mastodon.socialreplied to erincandescent@akko.erincandescent.net last edited by
@erincandescent oh okay
well, "partially compacted form" and not proper expanded form, but yeah
the main thing i'm thinking though is that as2 goes too far in compacting things. i think you could get something close to the desired result if you not only add container:set to most properties, but also drop type:id from all properties
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
@erincandescent this basically takes away the assumptions and forces producers to be explicit
unfortunately i think it would necessitate an as2v2 context
-
trwnh@mastodon.socialreplied to oblomov@sociale.network last edited by
@oblomov @erincandescent not strictly, no -- it's still as2, it's just the v2 context