Repository navigation
Some more precise language on registry aspects. - #35
Merged
Merged
Conversation
Member
|
@msdemlei, is this meant for VOEvent-2.1? That should be already closed, how to we fit this in? |
Contributor
Author
|
On Fri, Jun 19, 2026 at 05:28:47AM -0700, Marco Molinaro wrote:
molinaro-m left a comment (ivoa-std/VOEvent#35)
@msdemlei, is this meant for VOEvent-2.1? That should be already
closed, how to we fit this in?
This *was* meant for 2.1. If it's not in there, it's not *terribly*
bad, as there is not much normative in there.
Having the two new standards keys would be nice, though. So, I'd
suggest we merge this and send the resulting StandardsRegExt record
to the RofR (it seems nobody has done so yet, at least I don't see
ivo://ivoa.net/std/voevent). As long as VOEvent doesn't say who
get's to create its standards keys, that's totally within the rules.
|
Member
|
@msdemlei this merge request lagged behind, but can now be merged since we forgot to push the VOEvent-2.1 REC to the repo. Could you give a check on the pending After that I will approve+merge and move on with doc publishing. |
In particular, we define the standards keys for the VOEvent capabilities.
msdemlei
force-pushed
the
more-registry-matters
branch
from
November 6, 2026 09:35
e087eac to
e1af121
Compare
Contributor
Author
|
Hi Marco,
On Wed, Nov 04, 2026 at 03:14:51PM -0800, Marco Molinaro wrote:
molinaro-m left a comment (ivoa-std/VOEvent#35)
@msdemlei this merge request lagged behind, but can now be merged
since we forgot to push the VOEvent-2.1 REC to the repo.
Oh, that's good luck. Because, this PR actually fixes the
discovery pattern (to what it should have been from the start), and
when I saw this I thought "oh dang, we'll need to do an erratum".
But if we can fix it like this, excellent.
Could you give a check on the pending `endorsedVersion` above?
It's 2.1 now.
|
molinaro-m
approved these changes
Nov 6, 2026
molinaro-m
left a comment
Member
There was a problem hiding this comment.
fine, thanks for fixing the version and reassuring on the content
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In particular, we define the standards keys for the VOEvent capabilities.
Sorry this has been rotting on my disk for too long.