- From: Tomasz Pluskiewicz <tomasz@t-code.pl>
- Date: Wed, 16 Jul 2014 20:21:14 +0200
- To: Gregg Kellogg <gregg@greggkellogg.net>
- Cc: Markus Lanthaler <markus.lanthaler@gmx.net>, "public-hydra@w3.org" <public-hydra@w3.org>
+1 On Wed, Jul 16, 2014 at 7:33 PM, Gregg Kellogg <gregg@greggkellogg.net> wrote: > On Jul 16, 2014, at 10:20 AM, Markus Lanthaler <markus.lanthaler@gmx.net> wrote: > >> Currently, it is possible to declare a property to be readonly and writeonly >> at the same time. By renaming these properties to readable/writeable it will >> become impossible >> create such inconsistencies. Thus, the proposal is thus to rename >> readonly/writeonly to readable/writeable. > > +1, and I would say that readable=false and writable=false basically says that this property is unsupported, which may be reasonable for subclasses for which such properties don't make sense. It's also similar to saying that cardinality=0. > > Gregg > >> This serves as a call for consensus on the proposed solution. Before I >> proceed with marking the issue [1] as resolved and implementing the changes >> in the spec, I would like to ask if anyone has any concerns or objections >> against this proposal. >> >> Please submit your comments by Wednesday, July 23rd. >> >> >> Thanks, >> Markus >> >> >> [1] https://github.com/HydraCG/Specifications/issues/14 >> >> >> -- >> Markus Lanthaler >> @markuslanthaler >> >> > > >
Received on Wednesday, 16 July 2014 18:22:25 UTC