- From: Ruben Verborgh via GitHub <sysbot+gh@w3.org>
- Date: Sun, 02 Jul 2017 00:54:55 +0000
- To: public-hydra-logs@w3.org
> In my opinion, it would be a big win if Hydra could describe the most common API use cases without requiring other vocabularies. This doesn't really matter with the right JSON-LD context: the properties manifest as simple strings, regardless of their origin (as hinted at by @elf-pavlik). It would be bad practice if every vocabulary reinvented existing concepts over and over. > Using VoID, OWL, and even RDFs increase the perceived complexity for newcomers Newcomers will not even see that for the reason above. > @RubenVerborgh in case you had chance to take a closer look at Solid maybe you have some insights on those two optins. I'm indeed working with the Solid team at MIT this summer, but haven't looked at collections yet. I'll try to figure this out! -- GitHub Notification of comment by RubenVerborgh Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/126#issuecomment-312464072 using your GitHub account
Received on Sunday, 2 July 2017 00:55:01 UTC