IVOA Identifiers Version 2 Proposed Recommendation: Request for CommentsIVOA Identifiers describes the syntax and semantics of the IVOA's special URIs. Such URIs are being used in the Registry to identify records, but IVOIDs are also used to denote datasets of all kinds, reference standards, and more. The latest version of Identifiers 2 can be found at: See also Examples of the validator. SVN revision references in the text refer to the repository at https://volute.g-vo.org/svn/trunk/projects/registry/Identifiers, where you'll also find bleeding edge versions not yet published in the repository.Reference Interoperable ImplementationsDoesn't really apply here, as no protocol is defined. However, IVOA identifers are in daily use in the Registry, and we preserve the Version 1 properties that make that work. The special form of Dataset ids has been in use in the GAVO data center for a while. We will try to have other data centers on board for TCG review and provide a reference service implementing the recommended procedure for resolving these things. The special form of standard ids has, essentially, been used for VOSI URLs and RegTAP. TAP 1.1 will probably be the first standard to fully use the patterns proposed here.Implementations ValidatorsThere is a validator for IVOIDs at http://dc.g-vo.org/ivoidval/q/val/form As a somewhat-validator for PubDIDs -- it checks whether a PubDID is globally resolvable according to the recipe in the document --, there's also http://dc.g-vo.org/ivoidval/q/didresolve/form.RFC Review Period: 2015-07-22 - 2015-09-01TCG Review Period: 2015-10-12 - 2015-11-20Comments from the IVOA Community during RFC period: 2015-07-22 - 2015-09-01In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment. Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this documentComments from MarkTaylorBasically clear, it's good to have a detailed definition of Identifiers for reference. However I have some comments:
Comments from TCG member during the TCG Review Period: 2015-10-12 - 2015-11-20!!! SECTION TO BE ADDED ONLY ONCE THE TCG REVIEW PERIOD HAS STARTED !!! WG chairs or vice chairs must read the Document, provide comments if any and formally indicate if they approve or not the Standard. IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.TCG Chair & Vice Chair ( _Matthew Graham, Pat Dowler )Applications Working Group ( _Pierre Fernique, Tom Donaldson )We approve this document. -- PierreFernique - 2015-10-31Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )It is a very good standard, exactly what's needed for DAL standards: Standard ids and Dataset ids. Minimal request on architecture diagram change (non blocking request, anyway). We approve this document. -- FrancoisBonnarel / MarcoMolinaro - 2015-11-18Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Very minor comments..
| ||||||||
Added: | ||||||||
> > | ''Thanks for catching those; I've replaced the double negation with simpler logic ("only [...] underscores, and tildes are allowed"). Fixes went in in volute rev. 3157 -- MD'' | |||||||
Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )
| ||||||||
Added: | ||||||||
> > | ''Uh.... You're (almost) right, it's 1.12 throughout; I've also fixed things in the document history in the preamble, where REC-1.12 was listed as PR-something. Fix went in in rev. 3158. Thanks. -- MD'' | |||||||
Registry Working Group ( _Markus Demleitner, Theresa Dower )I take issue with any case-sensitivity in the part of identifiers, especially given the move via the RegTAP interface to lowercase ivoids and many other columns during ingest for simpler search. I otherwise approve and am not going to hold up the document on it. -- TheresaDower - 2015-11-19 | ||||||||
Added: | ||||||||
> > | ''Trust me, I'm deeply unhappy about the rules for comparison of ivoids, but as I said we can't really back out of case-insensitive registry parts without breaking a lot of things (and scheme and authority are case-insensitive by RFC 3986 anyway), and allowing case changes in local parts in turn would make the thing very hard to deal with for data providers. So, I guess all I can say is that the world sometimes sucks. -- MD'' | |||||||
Semantics Working Group ( _Mireille Louys, Alberto Accomazzi )Education Interest Group ( _Massimo Ramella, Sudhanshu Barway )Time Domain Interest Group ( _John Swinbank, Mike Fitzpatrick )Data Curation & Preservation Interest Group ( Francoise Genova )Knowledge Discovery in Databases Interest Group ( George Djorgovski )Theory Interest Group ( _Franck Le Petit, Carlos Rodrigo )Standards and Processes Committee ( Françoise Genova )Operations ( _Tom McGlynn, Mark Taylor )Thanks for responding to our RFC comments. Ops IG is pleased to recommend acceptance (modulo one or two typos communicated offline). -- MarkTaylor and TomMcGlynn - 2015-10-28<--
|