From patrick.dowler at nrc-cnrc.gc.ca Fri Nov 18 11:27:17 2011 From: patrick.dowler at nrc-cnrc.gc.ca (Patrick Dowler) Date: Fri, 18 Nov 2011 11:27:17 -0800 Subject: WG Review period for TAPRegExt-1.0 Message-ID: <201111181127.17811.patrick.dowler@nrc-cnrc.gc.ca> Note: cross-posted to registry list; please respond to DAL list only. I would like to start the (informal) WG review of the TAPRegExt now so that I can begin the RFC in January. The latest WD is here: http://www.ivoa.net/Documents/TAPRegExt/ The current XML schema file is available from here: http://code.google.com/p/volute/source/browse/#svn%2Ftrunk%2Fprojects%2Fregistry%2FTAPRegExt Note: As of 2011-11-18 there is one bug in the schema file (r1609). This should be fixed asap; just look for a later revision number. PS-If/when people implement some portion of this in the VOSI-capabilities resource of their TAP service, please let me know (base service url would be good) as I need a list of "implementations". Thnx. -- Patrick Dowler Tel/T?l: (250) 363-0044 Canadian Astronomy Data Centre National Research Council Canada 5071 West Saanich Road Victoria, BC V9E 2M7 Centre canadien de donnees astronomiques Conseil national de recherches Canada 5071, chemin West Saanich Victoria (C.-B.) V9E 2M7 From m.b.taylor at bristol.ac.uk Fri Nov 25 07:38:43 2011 From: m.b.taylor at bristol.ac.uk (Mark Taylor) Date: Fri, 25 Nov 2011 15:38:43 +0000 (GMT) Subject: taplint goes ObsTAP Message-ID: Hi ObsTAP enthusiasts, following encouragement from Pat, I have added ObsTAP validation features to taplint, the STILTS-based TAP service validator tool. As well as all the previous tests, for TAP services which claim to implement ObsCoreDM, taplint now checks that all the required ObsCore columns are in place, that all the column metadata for the required and optional columns matches what's written in the ObsCore spec, and does a few additional tests on the data in those columns. I won't make a public release of STILTS specially for this, but you can find the pre-release jar file at: ftp://andromeda.star.bris.ac.uk/pub/star/stilts/pre/ Documentation (minus mention of the OBS stage, which is what does the new ObsTAP stuff) can be found at: http://www.star.bristol.ac.uk/~mbt/stilts/sun256/taplint.html Run it like this: java -jar stilts.jar tapurl=... or if you just want ObsTAP tests: java -jar stilts.jar tapurl=... stages='TMS CAP OBS' There may be errors in the validator; if you believe that it's claiming an error where you don't think there is one (or vice versa) please let me know. Any questions etc you know where I live. Mark -- Mark Taylor Astronomical Programmer Physics, Bristol University, UK m.b.taylor at bris.ac.uk +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/ From m.b.taylor at bristol.ac.uk Tue Nov 29 10:44:23 2011 From: m.b.taylor at bristol.ac.uk (Mark Taylor) Date: Tue, 29 Nov 2011 18:44:23 +0000 (GMT) Subject: WG Review period for TAPRegExt-1.0 In-Reply-To: <201111181127.17811.patrick.dowler@nrc-cnrc.gc.ca> References: <201111181127.17811.patrick.dowler@nrc-cnrc.gc.ca> Message-ID: Pat, Markus et al. On Fri, 18 Nov 2011, Patrick Dowler wrote: > I would like to start the (informal) WG review of the TAPRegExt now so that I > can begin the RFC in January. > > The latest WD is here: > > http://www.ivoa.net/Documents/TAPRegExt/ I'm mostly happy with the current draft. I have one or two comments and corrections. Sec 2.3, discussion of language features: ----------------------------------------- Where the features-adqlgeo key is defined its IVORN is quoted wrong, it says: ivo://ivoa.net/TAPRegExt#features-adqlgeo when it should say: ivo://ivoa.net/std/TAPRegExt#features-adqlgeo (compare with the features-udf key above). Having noticed this I did a 'grep ivo://ivoa.net/TAPRegExt *' in the volute projects/registry/TAPRegExt dir and found quite a few matches. I think most of them don't find their way into the built document, but I don't understand the build well enough to work out if there's a good reason they are in those files. Maybe Markus could do a similar grep and make sure the std-less IVORN is not getting used anywhere. In the same section, the features-adqlgeo key has an example element but the features-udf key does not. Probably the example isn't essential, since examples of both feature types appear in Appendix B, but it would make sense to have it consistent? Especially since the UDF example is more complicated than the Geom one. Appendix B (Example document): ----------------------------- ADQL version ivo-id is incorrect: 2.0 should read 2.0 The non-standard uploadMethods listed here, while not incorrect, may be a bit confusing. How about removing the "ivo://ivoa.org/tap/uploadmethods#"* entries. Other than that, the document looks good to go to me. > PS-If/when people implement some portion of this in the VOSI-capabilities > resource of their TAP service, please let me know (base service url would be > good) as I need a list of "implementations". Thnx. The most recent version of the taplint TAP service validator in STILTS performs fairly comprehensive validation of Capabilities documents which implement TAPRegExt. Validation tools are required or at least encouraged alongside implementations by the IVOA Document Standards, so you should mention this as well (it's a kind of implementation in any case). taplint refs: http://www.star.bristol.ac.uk/~mbt/stilts/sun256/taplint.html (docs) ftp://andromeda.star.bris.ac.uk/pub/star/stilts/pre/ (download) Note it's possible to use it standalone to validate a TAPRegExt document which is not deployed in a TAP service as well, though this is not documented or obvious - I can explain how if anyone wants to know. Mark -- Mark Taylor Astronomical Programmer Physics, Bristol University, UK m.b.taylor at bris.ac.uk +44-117-928-8776 http://www.star.bris.ac.uk/~mbt/