@erincandescent xri let you delegate to another authority at any point in the middle of the identifier
-
@erincandescent xri let you delegate to another authority at any point in the middle of the identifier
i think even with redesigning from principles i would probably start off without any mechanism for property paths, but this could be added later as an extension by creating a "path entity" which is a json object that has a property pointing to a list of path components. something like
{"to": {
"set": [
{"id": "trwnh"},
{"path": {"list": ["trwnh", "as:followers"]}}
]}}but idk if this helps
-
trwnh@mastodon.socialreplied to trwnh@mastodon.social last edited by
@erincandescent one of the things i'm leaving out here is the distinction between base-relative ids and vocab-relative ids
you could simplify a lot of this with jsonld as well, for example eliding out the set/list stuff. but the more "context" you add/require, the harder it is to undo that. i'm pretty sure that when people say they hate jsonld what they mean is that they hate that this inherent complexity is hidden from you by the context mapping
there's probably a midway point or compromise