- From: Dan Brickley <danbri@google.com>
- Date: Mon, 20 Jun 2022 20:31:51 +0100
- To: jason@massiveimpressions.com
- Cc: "schema.org Mailing List" <public-schemaorg@w3.org>
- Message-ID: <CAK-qy=7vezdBpnSwyPBffYRbC53EAwq-WOkSXda-O8tk-dmeWw@mail.gmail.com>
My advice would be to avoid going to deep into this. Sometimes it is clear enough from context. Representing fictitiousness is a can of worms for a language a simple as schema.org / rdf. One issue is that we generally want to avoid reading too much into the semantics of something *not* being stated. This makes it easier to mix and match and slice and dice data without hidden baggage lurking everywhere. It would be inadvisable for example to assume that a Recipe description without nutrition / calories supplied is for a calorie-free meal. Similarly if "isFictitious: True" were missing, or any typing information, it would be tricky if things previously seeming to be fictitiousness became presented as non-fictitious, solely due to missing information. Dan On Sun, 19 Jun 2022, 00:23 , <jason@massiveimpressions.com> wrote: > Hello Everyone, > > > > The schema for Person is described to be applicable to: > “A person (alive, dead, undead, or fictional).” > > > > But… what Property of Person, or any other Thing for that matter, > indicates whether the Thing actually exists, is instanced in reality, has > real presence as opposed to being only entirely imaginary or fictional? > > > > Shouldn’t this be explicit, not implied by other Properties or some other > Type or Sub-type? > > > > -JP > > > > > > Jason Pelish > > Founding Partner – Marketer > > Massive Impressions Online Marketing > > Boca Raton, FL 33431 > > (561) 232-2424 > > (866) 800-3579 > https://2vu.me/m - Massive Impressions site > > https://2vu.me/C - The Click Whisperer site > > https://4boca.com – 4boca Local site > > >
Received on Monday, 20 June 2022 19:32:15 UTC