Skip to content
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

Meta-issue for upcoming release, drafted as v3.8 in master branch #2272

Closed
danbri opened this issue Jun 13, 2019 · 7 comments

Comments

Projects
None yet
3 participants
@danbri
Copy link
Contributor

commented Jun 13, 2019

Tracking issue for upcoming release
Target date: 2019-07-01 (Monday 1st July 2019)
Circulate for review on or before 2019-06-17

@RichardWallis

This comment has been minimized.

Copy link
Contributor

commented Jun 13, 2019

Candidate Pull Requests:

  • #2205 Add new property conditionsOfAccess with domainIncludes CreativeWork
  • #2041 Update accessModeSufficient to expect ItemList and correct first example
  • #2247 adding properties to JobPosting to indicate when job starts
  • #2241 provides a status property for CreativeWork
  • #2267 Fixed typo in description of subjectOf
  • #2269 Removed unnecessary newlines from comments in CSV files.
  • #2273 Fixed inconsistencies in expected types for Date & Time expecting properties
@danbri

This comment has been minimized.

Copy link
Contributor Author

commented Jun 18, 2019

In addition this release will contain:

  • GTIN simplifications and modernization, as outlined in #1244 (comment)
  • Some more syntax bugfixes to our examples.
@danbri

This comment has been minimized.

Copy link
Contributor Author

commented Jun 18, 2019

@ashepherd ashepherd referenced this issue Jun 18, 2019

Open

Review Schema.org release 3.8 #20

0 of 2 tasks complete
@mkanzaki

This comment has been minimized.

Copy link

commented Jun 21, 2019

Is there any chance to proceed Archive related classes/properties to the Core? #1758 and #1759 were closed on adding them to the Pending, but it's not clear (for me) what criteria they should meet in order to advance.
Thanks.

danbri added a commit that referenced this issue Jul 3, 2019

danbri added a commit that referenced this issue Jul 3, 2019

@danbri

This comment has been minimized.

Copy link
Contributor Author

commented Jul 3, 2019

@mkanzaki this was included in v3.5 recently, see https://schema.org/docs/releases.html#v3.5 https://schema.org/docs/releases.html#g1758

I would encourage the view that these are now "in schema.org", and something that can and should be used (with care). We will make periodic reviews of Schema.org's Pending area to see which things are being used. If that use brings attention to problems or opportunities to improve the definitions, "Pending" makes it easier for us to change. We will try to make any changes respectful of existing deployments. If you know of use, please drop a note into the relevant github issue (even if it is closed).

@danbri

This comment has been minimized.

Copy link
Contributor Author

commented Jul 3, 2019

@RichardWallis

This comment has been minimized.

Copy link
Contributor

commented Jul 16, 2019

Shipped.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.