- From: elf Pavlik via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Nov 2017 03:58:36 +0000
- To: public-hydra-logs@w3.org
> The former means all clients would become slightly more complex as they would need to dereference operations.
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. 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.
What we might have to address - operations shared by more than one resource. Given `"target": { "@reverse": "operation" }`, multiple resources referencing the same operation could result in that operation 'having multiple targets'.
--
GitHub Notification of comment by elf-pavlik
Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/146#issuecomment-342040604 using your GitHub account
Received on Monday, 6 November 2017 03:58:42 UTC