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

[danbri]

Targetting for publication: February 2017.

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

Implemented

• Restore material property as a superproperty of artMedium, applicable to Product, CreativeWork #1294 - improvements around 'material' (implemented).
• Stop recursion down hierarchy when node not in current layer(s) #1302 - fixed a problem with hierarchical listing not sticking to correct extension layers.
• /sameAs "Freebase" -> "Wikidata"; Change 'freebase' mention in sameAs to 'wikidata' #1162
• accessMode, accessModeSufficient, and accessibilitySummary properties for e.g. epubs - Proposal of accessMode, accessModeSufficient, and accessibilitySummary properties for e.g. epubs #1100

Site infrastructure

• Markdown bug injecting ‘klzzwxh’ into pages, need a fix and tests to ensure it stays fix #1285

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 Examples for Consortium #1539 - examples for the new Consortium Type added to pending in this release.
• Merge PR added examples for new 'identifier' property #1489 examples for the newly added identifier property.
• Merge PR Added Event to the domain of audience #1475 add Event to domain of audience
• Merge PR Fix broken links to /docs/about.html #1443 - fix a link that 404’s in the docs/schemas.html page
• Merge PR Added acknowledgement of support from Legal Entity Identifier Foundation #1416 - acknowledge the support of the Legal Entity Identifier Foundation
• Circulate to CG+SG for final review.

[gmackenz]

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]

@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 Medical/health vocabulary as an extension #492 (comment) but we will foresee some additional properties under it as suggested by @LezzaRodrigues in Medical/health vocabulary as an extension #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]

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

[danbri]

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]

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

[danbri]

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

[rtroncy]

... 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]

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]

@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.