Re: Shipping schema.org v2.1 (sdo-ganymede)

Looks good to me! Cheers, 
Peter 


     On Thursday, July 30, 2015 5:33 PM, Dan Brickley <danbri@google.com> wrote:
   

 All quiet on the Steering Group reviewing front! Please take a look, I
think we're done with vocab/example changes:

http://sdo-ganymede.appspot.com/docs/releases.html#ganymede

I believe releases.html is up to date with all commits since our last
release. It now also highlights items for which Steering Group review
is particularly solicited.

Richard Wallis and I have also been working on the hosted extensions
implementation, for which you can now see a 'rough but usable' of bib.
and auto. extensions. We could include (with "work in progress"
banner) or postpone these, but I believe we are long overdue for
pushing out our collected improvements to vocabulary and example. So
do have a look and respond here or Github if you have any concerns or
final-tweak suggestions.

Still TODO:

1.) I still plan to slim down the mainContent[OfPage] documentation
string as discussed previously. No text will be lost, it will just be
moved so it isn't dominating the top of every type definition page.

2.) Add status/warnings to bib.* and auto.* section and refine the
navigation links from 'core' pages e.g.
http://sdo-ganymede.appspot.com/Book as well as clarify how we expect
things to work with JSON-LD contexts.

Anything else? Let's aim to ship a release early next week.

Dan



On 13 July 2015 at 16:04, Dan Brickley <danbri@google.com> wrote:
> Schema.org CG,
>
> We haven't released a new version since
> http://schema.org/docs/releases.html#v2.0 2 months ago.
> Meanwhile the sdo-ganymede branch has collected a reasonable number of
> improvements which would be doing a lot more good published properly
> at http://schema.org/ rather than waiting in the queue.
>
> http://sdo-ganymede.appspot.com/docs/releases.html#ganymede has the
> list of changes currently commited to the repo for the release
> codenamed 'ganymede'. I suggest we aim to push this out early next
> week as v2.1, and continue with a fresh branch for anything we can't
> agree in the next 2-3 days.
>
> Therefore please see the issue tracker (and pull requests) for the
> many issues we have floating around and try to identify any you think
> we can squeeze into a release next week.
>
> My personal "let's fix this please" priority is to slim down the
> mainEntityOfPage documentation as it is filling each page on the site
> with too much background text. I'll work a proposal for fixing that
> via https://github.com/schemaorg/schemaorg/issues/643 asap.
>
> List of 'vocab'-labelled issues tagged for (potential) Ganymede release.
>
> https://github.com/schemaorg/schemaorg/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22sdo-ganymede+release%22+label%3A%22schema.org+vocab%22
>
> Please take a look and share your "let's fix this bit quickly first"
> wishlists asap.
>
> cheers,
>
> Dan