- From: Karol Szczepański via GitHub <sysbot+gh@w3.org>
- Date: Sun, 05 Nov 2017 18:57:56 +0000
- To: public-hydra-logs@w3.org
>There is no sensible term to put as hydra:property because the year doesn't necessarily have to be a >property of an Event Still i prefer a property over a raw type as it gives a context. Saying that the variable should be mapped to `xsd:string` says nothing. Saying that that variable should be mapped to `hydra:freetextQuery` sasy everyhing. The property should define the type of value (question is on how to do this - RDFS, OWL, SHACL?) and gives a hint to the client that the value should come from the user input. I was also experimenting wit custom properties for skip/take. And remember that even for a variable mapped to a property that actually exists within the `event` type, it still may be taken from somewhere else. -- GitHub Notification of comment by alien-mcl Please view or discuss this issue at https://github.com/HydraCG/Specifications/issues/145#issuecomment-341996097 using your GitHub account
Received on Sunday, 5 November 2017 18:57:58 UTC