- From: Markus Lanthaler <markus.lanthaler@gmx.net>
- Date: Fri, 1 Nov 2013 15:41:46 +0100
- To: <public-hydra@w3.org>
Hi all, We currently have two properties in the Hydra vocabulary which I'm not entirely happy with yet: hydra:readonly and hydra:writeonly. I think more and more that renaming them to hydra:readable and hydra:writeable would make them easier to work with. This is ISSUE-14 [1] The reason why I gave them this name in the first place was because I thought that it is only necessary to explicitly set them if a property is either readonly or writeonly but that's not entirely true due to the open world assumption Hydra is based on. If it's not set, you can't assume it is set to false. You have to accept that you don't know what value it has. The advantage of renaming them would be that the inconsistency which is cause if something is marked as both read- and writeonly would be eliminated and programming against them would become easier. Apart from introducing a breaking change (which is still quite cheap at this point in time) I don't see any downside of the change but maybe I miss something. What do you guys think? Cheers, Markus [1] https://github.com/HydraCG/Specifications/issues/14 -- Markus Lanthaler @markuslanthaler
Received on Friday, 1 November 2013 14:42:19 UTC