W3C home > Mailing lists > Public > public-schemaorg@w3.org > June 2017

How well recognized / parsed / handled are composite types?

From: Christopher Allan Webber <cwebber@dustycloud.org>
Date: Thu, 29 Jun 2017 14:16:53 -0500
To: public-schemaorg@w3.org
Message-ID: <87shii8uze.fsf@dustycloud.org>
Hi there,

I'm doing some data modeling for a client that would like to ensure that
their content is discoverable via Google / Bing / etc.  We're using
schema.org everywhere we can, but there are some custom terms.  Say we
have a Person object posted in a context like:

  {"@context": {"schema": "https://schema.org/",
                "customfoo": "https://foo.example/ns#"}
   "@type": ["schema:Person", "customfoo:Citizen"],
   "schema:name": "Gertrude McBell",
   ...}

This should technically be valid data modeling as far as I can tell, and
it should also convey that this Person is also a "Citizen" under their
custom vocabulary.  (This is not the actual vocabulary we're using, I'm
just making up an example.)  Composite types are allowed in the linked
data world in general... but whether they are recognized by common
systems is another thing.

Google / Bing / etc probably have no idea what a Citizen is here, even
though it is important to our data, and that's fine.  But will they
still be able to recognize the presence of Person with the type as an
array?

If not, maybe we should stick to just a singular type, as schema:Person.

Thanks in advance!
 - Christopher Allan Webber
Received on Thursday, 29 June 2017 19:18:18 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 June 2017 19:18:19 UTC