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

Should the version history of the schema.org JSON-LD context file be archived? #1101

Closed
danbri opened this issue Apr 14, 2016 · 4 comments
Closed
Assignees
Labels
Administrivia Project-internal tasks that most parties can happily ignore site tools + python code Infrastructural issues around schema.org site. Most can ignore this! standards + organizations Relationships, liaison, mappings between our work and standards elsewhere type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc

Comments

@danbri
Copy link
Contributor

danbri commented Apr 14, 2016

/cc @betehess

@akuckartz
Copy link

akuckartz commented Apr 14, 2016

If possible with only a small amount of effort: yes.

@danbri
Copy link
Contributor Author

danbri commented Apr 14, 2016

Since the site is essentially static, this would add another step to the release process https://github.com/schemaorg/schemaorg/blob/sdo-deimos/RELEASING.TXT ...

@danbri danbri added site tools + python code Infrastructural issues around schema.org site. Most can ignore this! standards + organizations Relationships, liaison, mappings between our work and standards elsewhere type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc Administrivia Project-internal tasks that most parties can happily ignore labels Apr 15, 2016
@danbri danbri self-assigned this Apr 15, 2016
@danbri
Copy link
Contributor Author

danbri commented Aug 19, 2016

@RichardWallis has automated much of RELEASING.TXT in scripts/buildreleasefiles.sh

Richard - could you add the JSON-LD context to this too?

@danbri
Copy link
Contributor Author

danbri commented Jul 17, 2020

Thanks @RichardWallis - this was fixed. Closing!

# In schemaorg/data/releases/

master└─ $ ls -1v */*context*
3.5/schemaorgcontext.jsonld
3.6/schemaorgcontext.jsonld
3.7/schemaorgcontext.jsonld
3.8/schemaorgcontext.jsonld
3.9/schemaorgcontext.jsonld
4.0/schemaorgcontext.jsonld
5.0/schemaorgcontext.jsonld
6.0/schemaorgcontext.jsonld
7.0/schemaorgcontext.jsonld
7.01/schemaorgcontext.jsonld
7.02/schemaorgcontext.jsonld
7.03/schemaorgcontext.jsonld
7.04/schemaorgcontext.jsonld
8.0/schemaorgcontext.jsonld
9.0/schemaorgcontext.jsonld

@danbri danbri closed this as completed Jul 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Administrivia Project-internal tasks that most parties can happily ignore site tools + python code Infrastructural issues around schema.org site. Most can ignore this! standards + organizations Relationships, liaison, mappings between our work and standards elsewhere type:cleanup + clarity Addresses wording fixes, ambiguities, confusion, bad examples etc
Projects
None yet
Development

No branches or pull requests

2 participants