Volunteers for VOEvent registration?

[Dave Morris]

Hi Markus,

Line 705 of your modified VOEvent.tex file says:

   "Public VOEvent streams MUST be registered in the VO"

Based on my experience of talking to people in the community who are 
using, publishing and consuming VOEvents, this is not actually what 
people want. In fact there have been a number of informal requests to 
remove the requirement to use an IVORN as part of the event identifier 
and allow services to use their own URI schema for identifiers.

This hasn't been proposed as a change to the standard yet, mainly 
because no one has worked out the details of how an alternative scheme 
would work yet. However, given that there may be a number of VOEvent 
users who would like to make that change, I would be wary of adding more 
text to the document re-enforcing the requirement for services to be 
registered and excluding the use of non-registered services in the 
future.

VOEvent is the only IVOA standard that actually requires services to be 
registered. It is quite possible to setup and use a standards compliant 
Cone, TAP, SSA, SIA or SLAP service without having to register it. You 
just need to pass the endpoint URL to the client.

Requiring all services to be registered has in the past acted as a 
barrier to entry for people who wanted to set up a small experimental 
services.

In light of this, would you accept a slightly weaker version of the 
statement on line 705, to say that "IF a service does use an IVORN as 
part of the event identifiers, then the base IVORN SHOULD be registered, 
and the following section defines how ..."

That leaves room for others to come after and propose an alternative URI 
scheme for event identifiers if they want to.

Thanks,
-- Dave

--------
Dave Morris
Research Software Engineer
Wide Field Astronomy Unit
Institute for Astronomy
University of Edinburgh
--------

On 2020-10-07 16:13, Dave Morris wrote:
> Hi all,
> 
> You can see the changes that Markus is proposing we adopt here:
> https://github.com/ivoa-std/VOEvent/compare/master...msdemlei:registry-matters
> 
> This link shows a diff between the current standard document and the
> specific changes needed to add service registration.
> 
> Hope this helps,
> -- Dave
> 
> --------
> Dave Morris
> Research Software Engineer
> Wide Field Astronomy Unit
> Institute for Astronomy
> University of Edinburgh
> --------
> 
> On 2020-10-07 15:41, Markus Demleitner wrote:
>> Dear TDIG,
>> 
>> Since the last interop, my draft for how we could register VOEvent
>> streams (https://github.com/msdemlei/VOEvent, the registry-matters
>> branch) has been rotting for the simple reason that I couldn't find
>> anyone running a VOEvent stream volunteering for having their service
>> be the prototype and example for registration.
>> 
>> So... If you're operating an active VOEvent service, would you please
>> (off-list) contact me?  It's not much work (essentially, I'll need
>> your metadata; if you're indifferent about your ivoid, that's
>> actually all there is to it for you), but there's endless fame in
>> store: Your project will be remembered as long as people read the
>> VOEvent spec!
>> 
>>       -- Markus