-
Notifications
You must be signed in to change notification settings - Fork 851
Meta-issue for sdo-deimos release (eventually named as version 3.0) #911
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The examples for LRMI are ready, we'ld love to see them in the next release (see pull request #902 , sorry no issue raised) |
LRMI examples would be great - let's do that |
Would it be possible to also add the following:
|
Added moving the current auto & bib extensions from pre-final preview release to a released state. |
(@mfhepp notes in IM chat that he has also checked off the 'early access fixes' above, which means we're good to go there) |
OK it's time we started pulling this together as a release. Questions... How ready are we with hotels? How close to some kind of consensus around dayOfWeek and opening hour improvements? What status updates for the bib.schema.org and auto.schema.org hosted extensions would be appropriate, and where/how shall we link the recently published GS1 external extension? As a release http://sdo-deimos.appspot.com/docs/releases.html is quite slim. We should also collect up a few "low hanging fruit" bugfixes and simple improvements if there are any obvious quick-fix candidates. /cc @scor @mfhepp @vholland @chaals @pmika @shankarnat @rvguha |
Extensions
|
Scanning through the current set of PRs I believe the following are also good candidates for this release:
|
I think two of my old PRs might be candidates for "quick fixes and easy wins", as they only fix example markup and got reviews:
I guess #909 (" |
Thanks @unor - those look useful, sorry we didn't get to them sooner! |
Skimming through, I have a couple of (seemingly) uncontroversial pull requests that I would like to get in.
|
Some more easy/uncontroversial PRs:
|
I wonder when could be the right time to properly discuss the event series and related features:
|
Event series may also be interesting wrt the Courses discussion nearby, where there is a need to distinguish the "course in the abstract" from a particular occurrence of it. The model feels a little different in that "lecture 5" in a sequence could occur eg 3 times in one year, but it is related somehow. |
+1 for Event Series as useful for Courses. 'Educational course is defined as "some sequence of events and/or creative works which aims to build the knowledge, competence or ability of learners".' |
http://schema.org/workFeatured could help bridge educational events to On Mon, 29 Feb 2016, 11:17 Phil Barker notifications@github.com wrote:
|
Ok @danbri, so since we didn't make it for sdo-gozer (v2.0), what aspects we should work out to get support for event series shipped into sdo-deimos (v2.3)? |
@wikier re event series, could you take a look at the Courses discussions? They are currently struggling with the problem of describing a course in the abstract versus a course as a specific sequence of actual events. @philbarker probably has the best pointers but see the mailing list for one entry point. |
I am working through the lists above. I would also like to fix #143 finally. |
I've just #880 - added http://sdo-deimos.appspot.com/disambiguatingDescription - I think the Wikipedia usecase is compelling, but review welcomed. |
http://webschemas.org/docs/releases.html is up to date with all changes in sdo-deimos repo. Summarizing issues suggested in this thread... # Fixed / merged / done
For pending.schema.org on-ramp
Still in progress
|
I have also just merged two piece of infrastructural work from @RichardWallis
Thanks @RichardWallis :) (he's now taking a look at #990) |
http://webschemas.org/docs/releases.html is now up to date with the repository so far. There are still some todos. Expecting FIBO and Hotels related pull requests from @RichardWallis and @mfhepp imminently. I am still doing QA on the gigantic medical changes, and I want to see what incremental progress we can mine from the various opening hours discussions. But do please take a look, we're nearly there... |
Days of week / opening hours fixes are in. I'll circulate this for review as a release candidate. |
Release candidate is for review. Thanks everyone for getting us this far :) https://lists.w3.org/Archives/Public/public-schemaorg/2016Apr/0053.html |
@trypuz notes that "There is some error „404 Not Found” on http://webschemas.org/version/3.0/". This is true - the process for generating a full release is quite involved (see details at https://github.com/schemaorg/schemaorg/blob/sdo-deimos/RELEASING.TXT) so normally this happens only at final publication. I should make that more clear in the candidate release version of releases.html - thanks! |
+1 for shipping. |
As commented in #923 (comment), I think that If the steering committee wants to go ahead, that's fine, I do not want my comment to be a blocker. |
Perhaps you meant to write "do not", @betehess? |
@danbri yes, I realized my mistake right after clicking the "Comment" button. I actually wanted to emphasize the "do not" to make it clear, but my brain had a hiccup :-) I had already updated my comment in the GitHub UI. I do think more thinking should go into |
Re PublicHolidays I've filed #1139 but I'm coming at this from the view that we have already effectively had PublicHolidays for ~4 years. If we're going to add http://schema.org/Monday etc now we ought to provide a migration path for people using all the previous longer URLs for DayOfWeek. What I'd suggest (for after this release) is that it would be good to have some collaboration on a simple unit testing structure for openingHours information, to encourage interoperable implementation. e.g. input to the test could be...
The output would be a boolean, whether the date/time is considered 'open' vs 'closed'. |
I had not realized it was already there! I agree with the rationale of keeping it. Let's discuss about what to do with it in the next release. |
Related resources (not necessarily up to date ;-):
Martin martin hepp http://www.heppnetz.de
|
Ok via #1139 I think we're ok now with PublicHolidays for the release. |
Ok release time. I'm about to work through the (rough) notes in https://github.com/schemaorg/schemaorg/blob/sdo-deimos/RELEASING.TXT ... essentially creating the derived per-release files that we snapshot. The DNS entries for new subdomains (pending.schema.org, health-lifesci.schema.org) should be mostly propagated already. |
Link to #propaz works, and links to each property work. Note that each per-property section may mention others and those links sometimes fail. Markdown is pre-processed though. For v3.0 release. See #911.
# v3.0 releasing
|
Ok this is mostly published but we have an issue with AppEngine: the new subdomains for pending, meta and health-lifesci are not routing correctly to the appengine app. I will leave the new version published, despite this. It will mean a few people find links that don't yet work. I hope to get this fixed asap. |
I've set things in motion for the subdomain URL mapping issue to be fixed (short version: we're using a special version of AppEngine with hidden complexities). This could take anything from 24h until early next week, so I have for now rolled back the site to the state of things on 2015-11-05. Apologies for the gracelessness! /cc @RichardWallis |
Subdomain issue is fixed and the site is (largely) published, however there is also a problem with caching of old content - sometimes it is serving v2.2 version of pages (at least homepage and docs/schema.html). I have initiated a cache flush which might take 48h. Apologies for the clumsy release engineering... See also https://lists.w3.org/Archives/Public/public-schemaorg/2016May/0042.html |
Closing. #1212 is proposed for release as version 3.1, and should address the various glitches from 3.0. |
This issue tracks release planning for schema.org's release codenamed sdo-deimos.
It is likely to be released as v2.3 in late 2015 or early 2016. It was released as v3.0 in May 2016.Early Access fixes
The following changes are proposed for immediate "early access" publication on the schema.org site. Such changes will be considered part of the eventual following release, for versioning/snapshot purposes. They will be published as soon as they get OK'd by the schema.org steering group.
Fix for 500 error codes - #899 - in #901
SG signoffs:
Fix for needless complex JSON-LD periodicals example - #904 in dbs@8ecbfe0
Main content of release
(discussion invited, here or in email )
(checkmarks indicate a rough consensus design is implemented for final review)
Proposals for this release include:
The text was updated successfully, but these errors were encountered: