- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Sep 2020 21:01:01 +0000
- To: public-hydra-logs@w3.org
>>Instead of fitting problem+json into hydra:Error There is not to much to do in here. The only thing that needs some thoughts is `instance`, that actually could be mapped to `hydra:object` rather than new term introduced in my last example. >>we could make an independent RDF bindings for the problem document and have Hydra import that But what would by Hydra worth if it couldn't let developers describe their APIs in most basic situations, like error handling without using other vocabularies? Hydra currently does not import any external vocabularies and we're trying hard to have hydra closed in semantics, but opened for extensions - I believe we shall keep doing it. As for what @asbjornu wrote - there are many _if_s that are vague. There is also an opposite possibility of incorporating Hydra into schema.org. This is the only vocabulary I'd consider to align to as it's a big player maintained by even bigger players. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/178#issuecomment-697970269 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 September 2020 21:01:03 UTC