Meta-issue for sdo-callisto release (likely as version 3.2) #1292

Closed
danbri opened this Issue Aug 10, 2016 · 23 comments

Comments

Projects
None yet
@danbri
Contributor

danbri commented Aug 10, 2016

Targetting for publication: February 2017.

See http://webschemas.org/docs/releases.html#sdo-callisto for proposed public "release notes".

Implemented

  • #1294 - improvements around 'material' (implemented).
  • #1302 - fixed a problem with hierarchical listing not sticking to correct extension layers.
  • /sameAs "Freebase" -> "Wikidata"; #1162
  • accessMode, accessModeSufficient, and accessibilitySummary properties for e.g. epubs - #1100

Site infrastructure

Final checklist / @danbri tasks

  • double-check all changes are listed here and in releases.html as appropriate.
  • update language in doc/*.html to clarify that when we say "sponsor" we mean "founder" organizations.
  • update aboutus.html for recent changes.
  • Check that Courses, Channel, Menu, ClaimReview are properly documented.
  • Fix/change the ClaimReview example.
  • Add a structure to releases.html that clarified moves from pending to core or other hosted extensions, and that introduces 'attic' for retired ideas.
  • Check for final "low hanging fruit"
  • Fibo/Finance and guidance for hosted extension maintainance.
  • Merge PR #1539 - examples for the new Consortium Type added to pending in this release.
  • Merge PR #1489 examples for the newly added identifier property.
  • Merge PR #1475 add Event to domain of audience
  • Merge PR #1443 - fix a link that 404’s in the docs/schemas.html page
  • Merge PR #1416 - acknowledge the support of the Legal Entity Identifier Foundation
  • Circulate to CG+SG for final review.

@danbri danbri self-assigned this Aug 10, 2016

@danbri danbri referenced this issue Aug 10, 2016

Open

Meta: schema.org planning #1

14 of 20 tasks complete
@gmackenz

This comment has been minimized.

Show comment
Hide comment
@gmackenz

gmackenz Aug 18, 2016

Contributor

If possible, I'd like to add #1288 - Proposal of a Menu/menuItems schema as a possible inclusion to sdo-callisto.

Also #1004 is rather close to a final form I believe.

Contributor

gmackenz commented Aug 18, 2016

If possible, I'd like to add #1288 - Proposal of a Menu/menuItems schema as a possible inclusion to sdo-callisto.

Also #1004 is rather close to a final form I believe.

@twamarc

This comment has been minimized.

Show comment
Hide comment
@twamarc

twamarc Aug 18, 2016

Contributor

@danbri is it possible to add also the 1) #492 (comment)
and the 2)#1114
in this coming release? The 2 topics have been largely discussed and I think we have now a consensus on them:

  • (for 1) We will only extend the definition to cover both person and place as suggested @westurner in #492 (comment) but we will foresee some additional properties under it as suggested by @LezzaRodrigues in #492 (comment).

*(for 2) #1114 (comment)).

If is OK I will prepare a pull request for that.

~Marc (for ScheMed W3C WG) and health-lifesci.schema.org extension.

Contributor

twamarc commented Aug 18, 2016

@danbri is it possible to add also the 1) #492 (comment)
and the 2)#1114
in this coming release? The 2 topics have been largely discussed and I think we have now a consensus on them:

  • (for 1) We will only extend the definition to cover both person and place as suggested @westurner in #492 (comment) but we will foresee some additional properties under it as suggested by @LezzaRodrigues in #492 (comment).

*(for 2) #1114 (comment)).

If is OK I will prepare a pull request for that.

~Marc (for ScheMed W3C WG) and health-lifesci.schema.org extension.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Aug 22, 2016

Contributor

Also relevant, please note the summary @RichardWallis has been updating for tools/python/infrastructure-related (rather than vocab) issues, see #3.

Contributor

danbri commented Aug 22, 2016

Also relevant, please note the summary @RichardWallis has been updating for tools/python/infrastructure-related (rather than vocab) issues, see #3.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 2, 2017

Contributor

I've been updating docs/releases.html towards having a release candidate.

http://webschemas.org/docs/releases.html

As you can see, we have been filling the "pending" pipeline. I've started restructuring the page to have a way to show progression of successful ideas into e.g. Core section, or abandoned ideas into the "Attic". It's not ideal yet but I believe all the basic content should be there now.

Contributor

danbri commented Mar 2, 2017

I've been updating docs/releases.html towards having a release candidate.

http://webschemas.org/docs/releases.html

As you can see, we have been filling the "pending" pipeline. I've started restructuring the page to have a way to show progression of successful ideas into e.g. Core section, or abandoned ideas into the "Attic". It's not ideal yet but I believe all the basic content should be there now.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 2, 2017

Contributor

TODO: we are missing some non-vocabulary improvements, specifically Travis-CI unit testing + the structured data checker being run over our examples.

Contributor

danbri commented Mar 2, 2017

TODO: we are missing some non-vocabulary improvements, specifically Travis-CI unit testing + the structured data checker being run over our examples.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 2, 2017

Contributor

TODO: http://localhost:8080/accessMode etc. also migrate to Core.

Contributor

danbri commented Mar 2, 2017

TODO: http://localhost:8080/accessMode etc. also migrate to Core.

@rtroncy

This comment has been minimized.

Show comment
Hide comment
@rtroncy

rtroncy Mar 2, 2017

... and you want to correct in http://webschemas.org/docs/releases.html that sdo-callisto is due by
(2017-03-XX) (and not 2016)

rtroncy commented Mar 2, 2017

... and you want to correct in http://webschemas.org/docs/releases.html that sdo-callisto is due by
(2017-03-XX) (and not 2016)

@gkellogg

This comment has been minimized.

Show comment
Hide comment
@gkellogg

gkellogg Mar 2, 2017

Contributor

TODO: we are missing some non-vocabulary improvements, specifically Travis-CI unit testing + the structured data checker being run over our examples.

To be clear, we do have the unit testing, and are running code based on the linter over all examples on Travis-CI, we're just ignoring the results. The work to do is in applying the test results to the examples themselves. I've corrected most syntactic errors, what remains is semantic errors (use of obsolete terms, for example). The plan was to work away at these, and enable the Travis-CI tests to fail when an error is found. This requires some judgement call, which I was not comfortable making unilaterally.

Contributor

gkellogg commented Mar 2, 2017

TODO: we are missing some non-vocabulary improvements, specifically Travis-CI unit testing + the structured data checker being run over our examples.

To be clear, we do have the unit testing, and are running code based on the linter over all examples on Travis-CI, we're just ignoring the results. The work to do is in applying the test results to the examples themselves. I've corrected most syntactic errors, what remains is semantic errors (use of obsolete terms, for example). The plan was to work away at these, and enable the Travis-CI tests to fail when an error is found. This requires some judgement call, which I was not comfortable making unilaterally.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 3, 2017

Contributor

@gkellogg - yes, exactly. It is one thing to be checked, it is another to get the all clear. For our next release I'd love to focus on that kind of cleanup.

Contributor

danbri commented Mar 3, 2017

@gkellogg - yes, exactly. It is one thing to be checked, it is another to get the all clear. For our next release I'd love to focus on that kind of cleanup.

@danbri

This comment has been minimized.

Show comment
Hide comment
Contributor

danbri commented Mar 3, 2017

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 3, 2017

Contributor

Also needed: 2-3 sentence release summary with main highlights.

Contributor

danbri commented Mar 3, 2017

Also needed: 2-3 sentence release summary with main highlights.

@eliaskaerle

This comment has been minimized.

Show comment
Hide comment
@eliaskaerle

eliaskaerle Mar 3, 2017

Pls. consider integrating #1259 into the release. There was no further complaint or suggestion since Oct. '16.

Pls. consider integrating #1259 into the release. There was no further complaint or suggestion since Oct. '16.

@sumutcan

This comment has been minimized.

Show comment
Hide comment
@sumutcan

sumutcan Mar 3, 2017

Please consider the change about the occupancy property (#1524), I think this is one of the low hanging fruits.

sumutcan commented Mar 3, 2017

Please consider the change about the occupancy property (#1524), I think this is one of the low hanging fruits.

@NicoSki

This comment has been minimized.

Show comment
Hide comment
@NicoSki

NicoSki Mar 3, 2017

As see that the SkiResort extention is not in the newest release. Being a wintersports journalist I know that travellers are very keen on information about the number of lifts, the number of skislopes and the length of every lift or slope. Would it be possible to add that kind of information as well to schema.org?
with kind regards
Nico

NicoSki commented Mar 3, 2017

As see that the SkiResort extention is not in the newest release. Being a wintersports journalist I know that travellers are very keen on information about the number of lifts, the number of skislopes and the length of every lift or slope. Would it be possible to add that kind of information as well to schema.org?
with kind regards
Nico

@chaals

This comment has been minimized.

Show comment
Hide comment
@chaals

chaals Mar 3, 2017

Contributor

I think we should try to get this release out. I have made minor comments on the skiResort stuff, which I think would be good to get out, and I have some concerns about speakable which I should either try to fix or decide it's OK really quickly…

Contributor

chaals commented Mar 3, 2017

I think we should try to get this release out. I have made minor comments on the skiResort stuff, which I think would be good to get out, and I have some concerns about speakable which I should either try to fix or decide it's OK really quickly…

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 3, 2017

Contributor

Can you articulate the issue with speakable? It is going only into pending at this stage, i.e. "kick the tires" mode

Contributor

danbri commented Mar 3, 2017

Can you articulate the issue with speakable? It is going only into pending at this stage, i.e. "kick the tires" mode

@AymenLoukil

This comment has been minimized.

Show comment
Hide comment
@AymenLoukil

AymenLoukil Mar 3, 2017

Release details page is missing for 3.2
#1544

Release details page is missing for 3.2
#1544

@AymenLoukil

This comment has been minimized.

Show comment
Hide comment
@AymenLoukil

AymenLoukil Mar 3, 2017

@danbri Sitemap.xml added by @RichardWallis too, to mention
#1483

@danbri Sitemap.xml added by @RichardWallis too, to mention
#1483

@Dataliberate

This comment has been minimized.

Show comment
Hide comment
@Dataliberate

Dataliberate Mar 4, 2017

Contributor

Sitemap.xml is available: http://webschemas.org/docs/sitemap.xml
It won't fully reflect the recent changes, as the process to create it is only run as part of the final release process.

On the webschemas site however it is not referenced in the robots.txt file - as we don't want to facilitate crawling of this work-in-progress site.

When released on the schema.org site it will be picked up via this line in robots.txt:
Sitemap: http://schema.org/docs/sitemap.xml

Contributor

Dataliberate commented Mar 4, 2017

Sitemap.xml is available: http://webschemas.org/docs/sitemap.xml
It won't fully reflect the recent changes, as the process to create it is only run as part of the final release process.

On the webschemas site however it is not referenced in the robots.txt file - as we don't want to facilitate crawling of this work-in-progress site.

When released on the schema.org site it will be picked up via this line in robots.txt:
Sitemap: http://schema.org/docs/sitemap.xml

@chaals

This comment has been minimized.

Show comment
Hide comment
@chaals

chaals Mar 14, 2017

Contributor

The speakable sounds wrong to me, since it's sort of a summary, but for kicking its tires I can live with it - and I suspect in the end I will just think that name was poorly chosen as too tied to one of several specific use cases.

So let's publish. In particular, people are waiting on the accessibility improvements.

Contributor

chaals commented Mar 14, 2017

The speakable sounds wrong to me, since it's sort of a summary, but for kicking its tires I can live with it - and I suspect in the end I will just think that name was poorly chosen as too tied to one of several specific use cases.

So let's publish. In particular, people are waiting on the accessibility improvements.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 16, 2017

Contributor

Ok, let's do it. I'll fold in the most obvious things from above and open a new issue for a next release. It was interesting to leave it a few months collecting ideas in pending.webschemas.org but it'd be healthier to get back on a tighter release cycle again.

Contributor

danbri commented Mar 16, 2017

Ok, let's do it. I'll fold in the most obvious things from above and open a new issue for a next release. It was interesting to leave it a few months collecting ideas in pending.webschemas.org but it'd be healthier to get back on a tighter release cycle again.

@danbri

This comment has been minimized.

Show comment
Hide comment
@danbri

danbri Mar 21, 2017

Contributor

Release in progress, aimed at Thursday, DNS changes for new subdomains should be propagating now. Current release candidate is http://3-2-1.webschemas-g.appspot.com/docs/releases.html - anything from above that we didn't get to is first on the list for attention in next release.

Contributor

danbri commented Mar 21, 2017

Release in progress, aimed at Thursday, DNS changes for new subdomains should be propagating now. Current release candidate is http://3-2-1.webschemas-g.appspot.com/docs/releases.html - anything from above that we didn't get to is first on the list for attention in next release.

@danbri

This comment has been minimized.

Show comment
Hide comment
Contributor

danbri commented Mar 23, 2017

@danbri danbri closed this Mar 23, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment