>>>> Maybe it's worth of considering a default value predicate for mappings? >>>That seems like a good idea! >> Just thinking: >> - hydra:hasDefaultValue >> - hydra:defaultValue >> - hydra:default >> - hydra:fallbackValue >> - hydra:fallback >> >> I'd also think about a "null" or "nothing" value. Unfortunately, rdf:nil >> cannot be used here but actually it's function is what we might seek. >Both SHACL and schema:PropertyValueSpecification allow to specify a default value. I also think it is necessary. But we are getting ahead of Markus' agenda... Ahh, SHACL again. Indeed it’s up to Markus’ agenda, but I fall more and more into a conclusion that we should drop some of hydra’s own creations and stick that vocabulary. I’ve got few agruments to support this but let’s wait for Markus to start that desciussion. Karol
Received on Sunday, 1 November 2015 13:56:40 UTC