- From: Markus Lanthaler via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Nov 2017 19:23:38 +0000
- To: public-hydra-logs@w3.org
> How much more complexity do you see in dereferencing operations? I think if client lazy loads those operations it would just force code that selects them to stay asynchronous. Clients which would load them eagerly could keep code that selects them synchronous.
Implementation complexity is just one factor. Runtime complexity/performance and failure modes are another aspect to keep in mind.
> Parsing of JSON-LD already has to happen asynchronous because of potential external @context so I think that external operations would not introduce additional complexity.
Yeah, we should probably also "restrict" that somehow for the reasons mentioned above. There are various machine clients (the Google crawler being one of them) that don't support remote contexts at all for instance.
> What we might have to address - operations shared by more than one resource. Given `"target": { "@reverse": "operation" }`
Yeah, I think this is a pretty good argument for, generally, not giving operations an IRI.
--
GitHub Notification of comment by lanthaler
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/146#issuecomment-342257081 using your GitHub account
Received on Monday, 6 November 2017 19:23:40 UTC