features for VOEvent v2.0

[Rob Seaman]

Running tally as of this PM (view with fixed width font):

1) VOEvent v2.0:        (7) yes  ( ) no  (2) don't care  ( ) don't  
understand
	1a) called v1.2:(4) yes  ( ) no  (5) don't care  ( ) don't understand
2) time-series:         (5) yes  (4) no  ( ) don't care  ( ) don't  
understand
3) simple tables:       (5) yes  (3) no  (1) don't care  ( ) don't  
understand
4) orbital elements:    (6) yes  (1) no  (2) don't care  ( ) don't  
understand
	4a) ephemerides:(4) yes  (1) no  (4) don't care  ( ) don't understand
5) <reference> typing:  (3) yes  ( ) no  (5) don't care  (1) don't  
understand
6) <param> typing:      (4) yes  ( ) no  (5) don't care  ( ) don't  
understand
7) non-empty params:    (4) yes  (1) no  (3) don't care  (1) don't  
understand
	7a) references: (4) yes  (1) no  (2) don't care  (2) don't understand
	7b) descripts:  (4) yes  (1) no  (2) don't care  (2) don't understand
	7c) multi-line: (2) yes  (1) no  (3) don't care  (3) don't understand
8) physical inferences  (6) yes  ( ) no  (3) don't care  ( ) don't  
understand
9) simple STC:          (5) yes  ( ) no  (3) don't care  (1) don't  
understand
10) robust schema:      (8) yes  ( ) no  (1) don't care  ( ) don't  
understand
11) Stream template:    (4) yes  ( ) no  (4) don't care  (1) don't  
understand

Plan of attack:

1) Please stand up and be counted!  We need more responses.

2) Supporters of items with any "don't understand" tallies, should  
consider describing them in more detail.

3) This is an initial reconnaissance, not a final vote (which will  
follow the IVOA RFC process).  Let's characterize the problem space  
before debating details of any solutions we decide to explore.   
Obviously much work has already gone into issues like time-series.

Rob

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/voevent/attachments/20100407/57c96354/attachment-0001.html>