- From: Angelo Veltens via GitHub <sysbot+gh@w3.org>
- Date: Wed, 08 May 2019 10:56:55 +0000
- To: public-hydra-logs@w3.org
Thanks for your detailed explanation, I know understand better why you find it important. From my point of view the `rdfs:range` does not really matter, because I have clients in mind, that are "domain specific", so they are not hard-coded to a specific API, but yet hard-coded to a specific domain, i.e. set of vocabularies / terms they can handle. This means those clients would already know how to handle `schema:duration`, without additional information in either the API doc or the vocabulary itself. It appears to me, that data types would mostly be required by real generic clients that have no clue about the API domain at all. But even those could fall back to a simple textfield if nothing is defined. Of course it would be better to have an explicit range, but I am not sure if this justifies to enforce it. The more complex it is to design a Hydra API the less likely it becomes that people adopt it. -- GitHub Notification of comment by angelo-v Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/192#issuecomment-490442063 using your GitHub account
Received on Wednesday, 8 May 2019 10:56:57 UTC