Fwd: Approaching "we think we're done" for sdo-gozer release aka schema.org v2.0: please review

Regarding previous discussions of using schema.org terms, the new release
has a stable, versioned snapshot.  I believe that this is what was missing
from the W3C normative requirements, but perhaps Ivan can confirm?



---------- Forwarded message ----------
From: Dan Brickley <danbri@google.com>
Date: Wed, May 13, 2015 at 2:28 PM
Subject: Re: Approaching "we think we're done" for sdo-gozer release aka
schema.org v2.0: please review
To: Tom Marsh <tmarsh@exchange.microsoft.com>
Cc: Peter Mika <pmika@yahoo-inc.com>, "schema.org Mailing List" <
public-schemaorg@w3.org>, Vicki Tardif Holland <vtardif@google.com>, Steve
Macbeth <Steve.Macbeth@microsoft.com>, Yuliya Tihohod <tilid@yandex-team.ru>,
Chaals from Yandex <chaals@yandex-team.ru>, Alexander Shubin <
ajax@yandex-team.ru>, St├ęphane Corlosquet <scorlosquet@gmail.com>, Martin
Hepp <mfhepp@gmail.com>, Ralph Swick <swick@w3.org>, Ramanathan Guha <
guha@google.com>, Dan Scott <dan@coffeecode.net>, Richard Wallis <

Ok, thanks everyone. The sdo-gozer branch has just gone out as a
"schema.org 2.0" release.




There are certainly a few rough edges here and there, and I hope to
push out a few more software-only fixes over the next week, but this
release represents a lot of work from many contributors and
significant progress. Coupled with the earlier cleanup in our last few
releases I think it is well worth the '2.0' name. Many thanks to
everyone who has been part of this!

The site also now includes a "versioned snapshot" URL structure - e.g.
http://schema.org/version/2.0/    The actual content of the versioned
release snapshot is generated automatically from a frozen snapshot of
the canonical RDFS-based triples representation that we use to
generate the site (available in RDFa and N-Triple RDFS downloads). The
actual content of the human-oriented document is (as you might
imagine) rather unwieldy given the size of our schemas, and we can
certainly work to improve its navigation and layout. But it gives a
clear URL that can be cited for each new release (and we can back-fill
it with old releases too). As usual, a detailed list of the schema
changes in this release is available from
schema.org/docs/releases.html#v2.0 (the /version/ link is also linked
from the table entry there).

The next big thing on our horizon is rolling out the extensions
mechanism via some specific actual extensions. Most of the
infrastructure to achieve this (for schema.org-hosted extensions) is
included in today's release. However the social and workflow side of
these extensions needs some attention too. We have a solid draft of
the bib: extension in
as well as a number of additional Automotive terms nearby which will
add even more expressivity around cars and other vehicles. In both
cases the extension work has its own W3C Community Group:
https://www.w3.org/community/schemabibex/ needs no introduction, as it
has been the home to schema.org-meets-bibliographic data discussions
for a long while. They are now joined by
https://www.w3.org/community/gao/ - the Automotive Ontology CG. This
seems a healthy structure for vocabulary collaboration at W3C, at
least as it relates to schema.org. We have this new Community Group
for schema.org, for various topic-specific groups (who may or may not
contribute terms into schema.org core and extension); and we retain
the public-vocabs list within the Semantic Web Interest Group
(http://lists.w3.org/Archives/Public/public-vocabs/) for broader
conversations about how all these things fit into a wider landscape.

Administrivia: I've merged sdo-gozer branch into 'master' (the GitHub
branch we serve the site from). The next release is named sdo-ganymede
(since the Ghostbusters thing wasn't funny any more). I've flipped the
default GitHub branch to be ganymede, and pushed a trivial update to
http://sdo-ganymede.appspot.com/ - this is where we'll start sketching
out the next release...

Thanks again all,


for schema.org

Rob Sanderson
Information Standards Advocate
Digital Library Systems and Services
Stanford, CA 94305

Received on Wednesday, 13 May 2015 21:33:43 UTC