- From: ☮ elf Pavlik ☮ <perpetual-tripper@wwelves.org>
- Date: Sat, 20 Sep 2014 15:21:22 +0200
- To: "public-vocabs@w3.org" <public-vocabs@w3.org>
Hi,
I see various use cases where I would like to state *NotApplicable*
{
"@context": "http://schema.org",
"@id": "http://wwelves.org/perpetual-tripper",
"@type": "Person",
"nationality": "NotApplicable",
"taxID": "NotApplicable",
"vatID": "NotApplicable"
}
To my understanding by simply omitting those properties I live it open
for reasoning - "Maybe he has nationality, taxID and vatID but just
doesn't publish it". Creating schema:NotApplicable or something in this
line would provide way to make such statements *explicit*. Since we
don't talk about boolean values here schema:False doesn't look to me
like something that fits.
Following https://github.com/rvguha/schemaorg/issues/120
"Explore adding link to Role into per type, per property navigation
boilerplate"
Having such NotApplicable allowed on all properties would make a lot of
sense to me. I could also see possibility of having one more generic
type for that and making NotApplicable one of its sub types.
All feedback appreciated!
Received on Saturday, 20 September 2014 13:23:38 UTC