W3C home > Mailing lists > Public > public-schemaorg@w3.org > April 2015

Re: Github issue tracker - wrapping up for sdo-gozer release

From: Dan Brickley <danbri@google.com>
Date: Tue, 28 Apr 2015 15:45:16 +0100
Message-ID: <CAK-qy=573t9y2KuJF0W8xPPQf4WqSqa8Bjr=gwDCk-4WPqaTxw@mail.gmail.com>
To: "schema.org Mailing List" <public-schemaorg@w3.org>, Vicki Tardif Holland <vtardif@google.com>, Ramanathan Guha <guha@google.com>, Peter Mika <pmika@yahoo-inc.com>, Chaals from Yandex <chaals@yandex-team.ru>, Tom Marsh <tmarsh@exchange.microsoft.com>, Yuliya Tihohod <tilid@yandex-team.ru>, Alexander Shubin <ajax@yandex-team.ru>
Quick update. We still have a good number of these issues open. I am
working on the Python side of things until I get it in a more
respectable state. All works in progress on extension handling (and
some JSON-LD things) have been merged in from the sdo-scripts branch
into sdo-gozer yesterday, and sdo-gozer.appspot.com and
webschemas.appspot.com (aka webschemas.org) test sites updated to
match recent commits. Any glitches should only be around the
extensions implementation.
Vicki will update us on #417 asap (i.e. the proposal to fix some
regrettable naming choices). I've recorded in
https://github.com/schemaorg/schemaorg/issues/429 everything that I
believe v1 of the extensions implementation ought to do (and mostly
does). Also one new issue that came in via public-vocabs,
https://github.com/schemaorg/schemaorg/issues/456 ("numberOfEmployees
should be applicable to Organization"). Although this is a late
arrival I propose we address it in gozer release as it seems
uncontroversial and in line with the spirit of polish and integration.
If anyone has concerns/objections please note that in the Github


On 22 April 2015 at 21:54, Dan Brickley <danbri@google.com> wrote:
> A quick update.
> We continue to play whack-a-mole [1] with the issue list.  We are
> making good cleanup progress but I believe hopes for a release early
> next week are over-optimistic.
> 1. The recipe-related issue #165 was prematurely closed by me last
> week. Stephane reminded us of some further flaws, and I've just
> committed (and pushed a test build) of the new re-resolution of that
> issue. https://github.com/schemaorg/schemaorg/issues/165 (some
> discussion continues...)
> http://sdo-gozer.appspot.com/docs/releases.html#sdo-gozer now says
> "Fix to #165: Renamed ingredients to recipeIngredient, improved the
> description, and added ItemList as a possible value for
> recipeInstructions."
> 2. Vicki and I discussed today the RsvpAction/ReplyAction/AskAction vs
> Question/Answer situation -
> https://github.com/schemaorg/schemaorg/issues/300 . It is messier than
> we first suspected, and needs some cleanup. This is one of those areas
> in which we have Action-based and non-action based vocabulary
> addressing the same problem space, compounded by poor examples and the
> larger need for more clarity around UserInteraction vs Comment+Action.
> 3. Peter Mika and I will meet up tomorrow in London and spend some
> time on this stuff.
> 4. The BibExtend Community Group mailing list is super busy as they
> work towards a first cut at a Bibliographic extension, see
> https://lists.w3.org/Archives/Public/public-schemabibex/2015Apr/0057.html
> ... including very natural questions about scope, e.g. whether/when to
> include 'archives', and how to engage archivists if so.
> In summary I think our initial hopes around a release early next week
> may be over ambitious but a solid release candidate for final review
> on that timescale ought to be feasible if we keep moving...
> See below for how-to-help links,
> Dan
> [1] https://www.youtube.com/watch?v=K-jaOfIHGko
> On 21 April 2015 at 21:56, Dan Brickley <danbri@google.com> wrote:
>> Checking https://lists.w3.org/Archives/Public/public-schemaorg it is
>> clear that most of the activities towards our next schema.org release
>> are (as planned!) happening over in Github and the Community Group
>> list discussion here so far has focussed on other topics. So I thought
>> I ought to send a quick update here (as well as a reminder that a
>> Github.com account is very useful for participating more fully in
>> discussions).
>> The next release is code-named sdo-gozer ("sdo" stands for
>> schema.org). We use these (Ghostbusters-inspired) names for Git(hub)
>> work-in-progress branches and for test versions of the site published
>> on appspot.com.
>> For info, https://github.com/schemaorg/schemaorg/issues/418 is a
>> meta-bug with a l reasonable annotated listing of gozer-related
>> issues. See also Vicki's doc about possible renamings of terms that
>> have very generic or confusing names,
>> https://github.com/schemaorg/schemaorg/issues/417 (the specific list
>> there was intended a conversation starter).
>> The build of the site visible on sdo-gozer.appspot.com is based on the
>> work-in-progress sdo-gozer branch within Github, i.e. this will become
>> the candidate next release soon. A good entry point is the draft new
>> version of the /docs/releases.html page, i.e.
>> http://sdo-gozer.appspot.com/docs/releases.html#sdo-gozer
>> You can filter Github by milestone and label. At this time filtering
>> on Gozer release and 'schema.org vocab' provides a useful status
>> report:
>> https://github.com/schemaorg/schemaorg/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22sdo-gozer+release%22+label%3A%22schema.org+vocab%22
>> This currently reveals 24 open issues, which need analysis, agreement
>> and closure (or postponing to a future release). Do please take a look
>> at the discussions and jump in with any observations and proposals
>> that you think can help progress things. While there are also some
>> software fixes in progress (sdo-scripts branch), we are optimistic
>> that this next release can be wrapped up within days rather than
>> weeks. If comments in Github can be made in the spirit of resolving
>> (or resolving to postpone) issues rather than opening, broadening or
>> prolonging discussion that would be super helpful!
>> cheers,
>> Dan
Received on Tuesday, 28 April 2015 14:45:44 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 28 April 2015 14:45:45 UTC