- From: Dan Brickley <danbri@google.com>
- Date: Sat, 16 Jun 2018 21:24:44 +0200
- To: Thad Guidry <thadguidry@gmail.com>
- Cc: Russell Pruitt <russell.pruitt@gmail.com>, "schema.org Mailing List" <public-schemaorg@w3.org>
- Message-ID: <CAK-qy=5S5+VC7k0vnLY9EyQhh=yEQoZ91nj7KV_GGT2aNnP5NA@mail.gmail.com>
Regarding case studies... We have historically minimized any details relating to specific search engine or similar products/features. It is important to remain clear that collaboration on such products has always been out of scope for the Schema.org founders and project. What we could do is offer a link to the main documentation URL for any large scale users. Meanwhile at Google, some case studies were recently posted: https://developers.google.com/search/case-studies/ I've just got off a flight so will keep other remarks brief, but given the concerns raised in some messages I did want to respond. The project has always been grounded in a focus on large scale *usage* of the schemas. This does not necessarily mean big companies, e.g. it can be opensource, Wikipedia/Wikidata etc. This focus is not a twisting of the original intent but foundational to why Schema.org has seen successes that eluded us in previous efforts around RDF, Linked Data, Semantic Web and so on. I would encourage folk here to consider putting some energy into building things that use this data in interesting and creative ways. Regarding Google's validation tooling, it is primarily a tool to help publishers understand markup patterns that are associated with tangible Google functionality. Sometimes we try out ideas before proposing them for wider consensus, because implementation experience helps in getting things right. The relatively recent extension mechanisms at Schema.org, particularly the Pending area and the editorial drafting site (webschemas.org) are efforts we've made in the Schema.org project to support a development mode that is informed by deployment experience. I'll repeat my suggestion that technologists here explore the ShEx and SHACL languages as possible platforms for expressing validation patterns in a more interoperable form. If you do so, please report back to this list. Dan On Sat, 16 Jun 2018, 18:46 Thad Guidry, <thadguidry@gmail.com> wrote: > Some good links for *case studies* do really need to be added onto #9 > Q: Why should I add markup? What will I get out of it? How will the data > be used? > > in our FAQ https://schema.org/docs/faq.html#9 > > Russell, Find those case studies and we can add the links to that Question > I'm sure. > > -Thad >
Received on Saturday, 16 June 2018 19:25:21 UTC