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.

Sign up for GitHub

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

Jump to bottom

need to provide a mechanism for versioning #3

Open
tacaswell opened this issue Apr 1, 2016 · 2 comments
Open

need to provide a mechanism for versioning #3

tacaswell opened this issue Apr 1, 2016 · 2 comments

Comments

@tacaswell
Copy link
Contributor

Need to be able to ask for 'latest' or some specific version of the schema.
@danielballan
Copy link
Member

Seems reasonable and straightforward to do. For prioritization purposes, have we encountered a need for this yet, or is it just a generally good idea?

@tacaswell
Copy link
Contributor Author

Just generally a good idea.

I suspect some of the bulk* work is going to point out flaws in the current schema.

@danielballan danielballan mentioned this issue Jun 1, 2020
Draft
evalott100 added a commit to evalott100/event-model that referenced this issue Feb 27, 2023
@evalott100
Removed vscode and dev container, changed references to DLS with refe…
8a24bc0 
…rences to bluesky (bluesky#3)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@tacaswell @danielballan