Previous meeting: #588

Agenda

• restart audio calls after summer break
• review progress on extensions
• call for proposals and prioritization

Mailed as https://groups.google.com/d/msg/schema-org-sg/3ggXE0xcWfU/NmIX8vvIEgAJ

Meeting Notes

Mailed as https://groups.google.com/d/msg/schema-org-sg/3ggXE0xcWfU/eO-Tf8QfEwAJ

Regrets from: Vicki (@vholland), Shankar (@shankarnat), Martin (@mfhepp), Steve
Attending: Alex (@ajax-als), Peter (@pmika), Guha (@rvguha), Dan (@danbri).

~25m call

Guha: we need a 6 month plan, something high level in terms of both core and extensions

Dan: Agree. The Github issues are at 200+ open issues now, even though they're labelled it is overwhelming and fine-grained. We should
perhaps extract all the vocabulary proposal issues as "noted" (linked from a meta vocabulary planning issue) and then close them to avoid
clutter.

Discussion on what should we focus on ~6 months?

No specific vocabulary proposals from Yandex, Yahoo. Dan or Vicki will circulate issue URLs for vocabulary Google are interested in
progressing in next release, mentioned some datasets-as-feeds improvements - see #688

Dan: re Schema.org in Email, Steve Macbeth has expressed interest in collaborating on a package of examples around schemas-in-email and
encourages people here to contact him directly. We can also collaborate on making sure we have more, better, and more complete
mail-oriented examples in the site.

[some discussion on whether that would be a good idea, general consensus that it would]

Dan/Peter have a rolling slow motion conversation about the out-dated old gmail mail markup - action: Dan to chase up status of that. Alex
noted that any new examples on the site should use the real/modern schema.org design not the obsoleted version, especially as Actions had
evolved.

Dan: We shipped bib: and auto: in the last release. It was technically complex / wobbly so delayed blogging about it.

Guha: It hasn't happened until it is blogged about!

Action: dan blog post announcing the v2.1 release emphasising extensions (bib, auto and process)

Some discussion of the schemed extensions proposal for health.schema.org and the history of
http://schema.org/docs/meddocs.html --- we need to provide better guidance and examples on what we expect extension authors to produce,
levels of detail etc. Guha, Dan and Richard joined a call last week with the schemed team and expressed concerns about the size of the
proposal (270+ terms). Discussion in https://lists.w3.org/Archives/Public/public-schemed/2015Aug/0010.html
and teleconf minuted in http://www.w3.org/2015/08/28-schemed-minutes.html and in their (not
our) issue tracker at twamarc/ScheMed#11 (comment)

Some discussion of using request for more examples to engage with other consumers, maybe Baidu, Pinterest, Apple, "EU community",
WIkipedia/Wikidata. Dan reported from 2 days in Wikipedia Science conference https://wikimedia.org.uk/wiki/Wikipedia_Science_Conference
that there is some awareness of schema.org, growing efforts around Wikidata, but no clear story for how these things fit together.