Time Domain Interest Group

Simple Time Series• Note posted to IVOA in Madrid

– http://www.ivoa.net/Documents/Notes/SimpleTimeSeries/

• Want to use this as implementation of Endorsed Note process– Some docs may need an IVOA endorsement, but not full REC overhead

• Document Process:– Draft Endorsed Note – Equivalent of a Working Draft

• Published at the discretion of the WG/TCG

– Proposed Endorsed Note • Mature enough for TCG Review• Goes to 4-week RFC for public comment

– Endorsed Note• Has been accepted by the TCG• Available in Document Repository

• Issues– Current IVOA Document Standards v1.3 draft suggests these can only come from a

WG or TCG

VOEventRegExt

1) Referring to existing Registry material• Issues:– Repeating or condensing materials from other

standards can be confusing• Suggestion: – Simply reference the REC

VOEventRegExt

2) Identifier Syntax ivo://authori.ty/service/id#local_event.id

to ivo://authori.ty/service/id?local_event.id

Issues:• Requires a new version of the spec• Breaks existing community codeSuggestions:• Avoid issue in RegExt• Describe only how to resolve a stream, not the ivorn• Defer to the VOEvent spec the ivorn meaning

VOEventRegExt

3) Re-using vs:tableSetIssues:• Definition of Group/Param adds complexity to RegTAP for

something similar to vs:tableSetSuggestions:• Map VOEvent data model to vs:tableSet• Less work for TDIG and Registry, immediately discoverable

VOEventRegExt

4) Less TypesIssues:• Is the difference between DataStream and DataServices

important for discoverability?Suggestions:• Drop DataStream and derive VOEventStream directly from

CatalogService• DataDictionary moves to vs:tableSet

VOEventRegExt

5) accessControl -> securityModelsecurityURL in capability

Suggestions:• Interface/securityModel@standardId• Move everything to ‘interface’

VOEventRegExt

6) Do away with VOEventServer

Suggestions:• Simpler to let capabilities sit on the VOEventStream if we

don’t expect many streams per server

7) Add RegTAP support

8) Misc comments

VOEvent Transport Protocol

• No change since Madrid• Comments promised but not delivered (me)• Quick comments on the mailing list, then on

to RFC?• Implementations:– Comet broker– GCN

Community Engagement

• Hotwired IV meeting, – May 12-15, Santa Barbara, CA

• What should the IVOA presence / message be at this meeting?

• Can we followup with the groups from Heidelberg?