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
Release History and Planning #1
Labels
no-issue-activity
Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
status:work expected
We are likely to, or would like to, or probably should try, ... to do something in this area.
Comments
danbri
added a commit
that referenced
this issue
Dec 11, 2014
Modified property names as discussed in partners meeting, cleaned up com...
danbri
pushed a commit
that referenced
this issue
Dec 11, 2014
Tilid video game - updates from recent non-game changes
danbri
pushed a commit
that referenced
this issue
Mar 25, 2015
Sync with next iteration of sdo-gozer
vholland
pushed a commit
that referenced
this issue
May 14, 2015
Fixed json on "Top 5 covers of Bob Dylan Songs"
danbri
added
status:work expected
We are likely to, or would like to, or probably should try, ... to do something in this area.
Extension Tracking
labels
May 27, 2015
This was referenced May 27, 2015
chaals
pushed a commit
that referenced
this issue
Jun 22, 2015
chaals
pushed a commit
that referenced
this issue
Jun 22, 2015
Merge pull request #1 from rvguha/master
This was referenced Sep 7, 2015
This was referenced Sep 15, 2015
Move of fibo extension proposals (PR #1300) in to pending - A candidate for 'in between releases' release. |
Closed
hhakung
added a commit
to hhakung/schemaorg
that referenced
this issue
Aug 21, 2018
14 tasks
This issue is being tagged as Stale due to inactivity. |
github-actions
bot
added
the
no-issue-activity
Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
label
Oct 11, 2020
RichardWallis
pushed a commit
that referenced
this issue
Jan 18, 2022
alex-jansen
pushed a commit
that referenced
this issue
May 13, 2024
Adding digital link attribute to Thing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
no-issue-activity
Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
status:work expected
We are likely to, or would like to, or probably should try, ... to do something in this area.
Issue #1 tracks high-level plans for schema.org. It gives entry points for release-level issues as well as broader goals that correspond to rough milestones over the next year. In practice, these goals are pretty hit-and-miss w.r.t. people actually doing the necessary work, but they are reported here as aspirations and for discussion.
See also release history and draft next release.
Release plans
Issues Overview
We label issues by topic, workflow status. The most concrete milestone is the next upcoming release, which since April 2019 are monthly, officially on (and named for) the 1st of the month, but in practice released on the first working day following. Work in progress edits can be found on webschemas.org.
We try to avoid unlabelled issues. The most important labels and entry points are:
Historical Meeting agenda and notes
Steering Group background
Elaborating on http://schema.org/docs/about.html -
The day to day operations of Schema.org, including decisions regarding the schema, are handled by a steering group, which includes representatives of the sponsor companies and a small number of individuals who have contributed substantially to Schema.org and related standards. The steering group typically makes decisions by consensus. All members of the steering group have the same standing. The steering group is currently chaired by R.V.Guha, who does not represent his employer in this capacity. Discussions of the steering group are public, see https://groups.google.com/forum/#!forum/schema-org-sg (very rarely used; more often CC:'d threads with the W3C Community Group public list).
The text was updated successfully, but these errors were encountered: