- From: Karol Szczepański <karol.szczepanski@gmail.com>
- Date: Sun, 14 Feb 2016 22:08:57 +0100
- To: "Tomasz Pluskiewicz" <tomasz@t-code.pl>, <public-hydra@w3.org>
Hi Tom >Next, I think we need a way to instruct the client what is valid input for >a property. >There has been a number of related discussions and there is issue 82 [2]. >We definitely need a way to tell the client what the server expects as >parameter input. >Some ideas include datatype restrictions (eg. datatype, numeric ranges, >string maximum length), enumerations of a set of values or values retrieved >from external resources (think autocomplete input). >Cardinality also applies here. Such mechanism would have to be applicable >not only to template parameters but also SupportedProperties as suggested >in issue 82. I think this issue was raised several times as indeed the current spec doesn't say what client MUST understand. Currently we need to use either pure RDFS/OWL descriptions (i.e. ranges and domains for properties), but this isn't very convenient way and requires client to have a reasoner onboard. There is also no consensus whether we shall use any other dictionary (SHACL appeared here several times). In general I agree with you that these decisions should take place some time in future as I struggle to address these issues in my projects. Regards
Received on Sunday, 14 February 2016 21:09:26 UTC