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..
Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )
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
Semantics Working Group ( _Mireille Louys, Alberto Accomazzi ) | ||||||||
Added: | ||||||||
> > | Just a few remarks , but the document is very clear and I approve the final repository version (2015, Oct 12) .
p17. octohorpe(the # symbol). would help to prevent people to have to look for the meaning of this word, while it is used so often in hyperlinks. P17. potential interoperability issue as explained in Gray, 2012: could we summarize in just 3 sentences what was the point ? the reference was a Note. 4.2 : Standard identifiers would not it be clearer to say 'Identifiers for IVOA standards', as a special case of what is being defined in this specification?. This RFC page (top) points to examples of real resources on the GAVO portal. This is very helpful to play with real examples. However I feel uncomfortable to see IVORN used in some places on this page , while the IVOA Identifiers mentions in 1.1 Definitions (page 5) : 'we now deprecate the term IVORN '. Any chance to update the vocabulary for this example page? -- MireilleLouys - 2015-11-25 | |||||||
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<--
|
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..
| ||||||||
Changed: | ||||||||
< < | ''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 )
| ||||||||
Changed: | ||||||||
< < | ''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 | ||||||||
Changed: | ||||||||
< < | ||||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ''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<--
|
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<--
|
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..
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )
Registry Working Group ( _Markus Demleitner, Theresa Dower ) | ||||||||
Added: | ||||||||
> > | 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 | |||||||
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<--
|
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 ) | ||||||||
Added: | ||||||||
> > | 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-18 | |||||||
Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Very minor comments..
Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )
Registry Working Group ( _Markus Demleitner, Theresa Dower )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<--
|
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 )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel ) | ||||||||
Added: | ||||||||
> > | Very minor comments..
| |||||||
Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )
Registry Working Group ( _Markus Demleitner, Theresa Dower )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<--
|
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:
| ||||||||
Changed: | ||||||||
< < | Comments from TCG member during the TCG Review Period: 2015-10-12 - 2015-10-20 | |||||||
> > | 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 )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )
Registry Working Group ( _Markus Demleitner, Theresa Dower )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<--
|
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-10-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 ) | ||||||||
Added: | ||||||||
> > | We approve this document. -- PierreFernique - 2015-10-31 | |||||||
Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )
| ||||||||
Deleted: | ||||||||
< < | ||||||||
I approve this document. -- BrianMajor - 2015-10-30
Registry Working Group ( _Markus Demleitner, Theresa Dower )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<--
|
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-10-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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni ) | ||||||||
Added: | ||||||||
> > |
| |||||||
Registry Working Group ( _Markus Demleitner, Theresa Dower )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 ) | ||||||||
Changed: | ||||||||
< < | Thanks for responding to our RFC comments. Ops IG is pleased to recommend acceptance (modulo one or two typos communicated offline). | |||||||
> > | 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
<--
|
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-10-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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 ) | ||||||||
Changed: | ||||||||
< < | Operations ( _Tom McGlynn, Mark Taylor ) | |||||||
> > | Operations ( _Tom McGlynn, Mark Taylor ) | |||||||
Added: | ||||||||
> > | 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 | |||||||
<--
|
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. | ||||||||
Changed: | ||||||||
< < | Latest version of Identifiers 2 can be found at: | |||||||
> > | 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-10-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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
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. 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 | ||||||||
Changed: | ||||||||
< < | As a somewhat-validator for PubDIDs -- it checks whether a PubDID is globally | |||||||
> > | 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. | |||||||
Deleted: | ||||||||
< < | 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-01 | ||||||||
Changed: | ||||||||
< < | TCG Review Period: TCG_start_date - TCG_end_date | |||||||
> > | TCG Review Period: 2015-10-12 - 2015-11-20 | |||||||
Comments 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:
| ||||||||
Changed: | ||||||||
< < | Comments from TCG member during the TCG Review Period: TCG_start_date - TCG_end_date | |||||||
> > | Comments from TCG member during the TCG Review Period: 2015-10-12 - 2015-10-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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
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. 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 | ||||||||
Added: | ||||||||
> > | 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: TCG_start_date - TCG_end_dateComments 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:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
Note that if % is not one of the unreserved characters, then the first MUST NOT is redundant.
Comments from TCG member during the TCG Review Period: TCG_start_date - TCG_end_date!!! 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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
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. 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/formRFC Review Period: 2015-07-22 - 2015-09-01TCG Review Period: TCG_start_date - TCG_end_dateComments 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:
| ||||||||
Changed: | ||||||||
< < | * The trouble is that I really want to avoid copying the grammar from RFC 3986, partly because it's fairly long, partly because I don't want to have to update Identifiers when they change/fix things, partly because there are plenty of implementations of RFC 3986 out there and people shouldn't need to check them from compliance. The document says "The rules from RFC 3986 are assumed throughout" in the "Usage of ABNF" section, which, true, lies in the "oh, boring boilerplate text" section of the document. Where would you have expected this statement? -- MD | |||||||
> > | * The trouble is that I really want to avoid copying the grammar from RFC 3986, partly because it's fairly long, partly because I don't want to have to update Identifiers when they change/fix things, partly because there are plenty of implementations of RFC 3986 out there and people shouldn't need to check them from compliance. The document says "The rules from RFC 3986 are assumed throughout" in the "Usage of ABNF" section, which, true, lies in the "oh, boring boilerplate text" section of the document. Where would you have expected this statement? -- MD | |||||||
While this is a relatively straightforward standard, I think it could be even clearer if there were examples given throughout the document and not just in 2.1. This is true of almost all IVOA standards. In particular I believe there should be labeled examples of both legal and illegal usage where at least one example is given for each class of violation and where we give legal examples for both normal usage and to illustrate the limits of valid code. E.g., Close 2.3.2 Authority with: Examples: Legal: nasa.heasarc n_1a.alph0.02 123.sub [Can start with a number] Illegal: a2 Not three characters .mydata.xxx Does not start with alphnumeric character _mydata.xxx Does not start with alphanumeric [if _ is not considered such I'd put this in because in some systems you can start with an _ when you cannot with a number] data%20.space Includes percent encoded character data^2.info Includes reserved character | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Note that if % is not one of the unreserved characters, then the first MUST NOT is redundant. | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
If there are additional rules in RFC 3986 that could be broken then those violations should be illustrated too. Typo: third example in 2.1 where there is a space between .org/ and the following ? | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
-- TomMcGlynn - 2015-09-14
Comments from TCG member during the TCG Review Period: TCG_start_date - TCG_end_date!!! 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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
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. Latest version of Identifiers 2 can be found at: See also Examples of the validator. | ||||||||
Added: | ||||||||
> > | 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/formRFC Review Period: 2015-07-22 - 2015-09-01TCG Review Period: TCG_start_date - TCG_end_dateComments 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: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
Plus a few spellings and typos:
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Added: | ||||||||
> > |
| |||||||
-- MarkTaylor - 2015-08-20 I'm not clear the the term <unreserved> is defined anywhere in the document. Presumably it refers to some range of characters defined somewhere (in RFC 3986 perhaps?) but that's not stated. I'd suggest the unreserved characters be defined explicitly here rather than requiring the user to find yet another document. | ||||||||
Added: | ||||||||
> > | * The trouble is that I really want to avoid copying the grammar from RFC 3986, partly because it's fairly long, partly because I don't want to have to update Identifiers when they change/fix things, partly because there are plenty of implementations of RFC 3986 out there and people shouldn't need to check them from compliance. The document says "The rules from RFC 3986 are assumed throughout" in the "Usage of ABNF" section, which, true, lies in the "oh, boring boilerplate text" section of the document. Where would you have expected this statement? -- MD | |||||||
While this is a relatively straightforward standard, I think it could be even clearer if there were examples given throughout the document and not just in 2.1. This is true of almost all IVOA standards. In particular I believe there should be labeled examples of both legal and illegal usage where at least one example is given for each class of violation and where we give legal examples for both normal usage and to illustrate the limits of valid code. E.g., Close 2.3.2 Authority with: | ||||||||
Changed: | ||||||||
< < | Examples: | |||||||
> > | Examples: | |||||||
Changed: | ||||||||
< < | Legal: nasa.heasarc | |||||||
> > | Legal: nasa.heasarc | |||||||
Changed: | ||||||||
< < | n_1a.alph0.02 | |||||||
> > | n_1a.alph0.02 | |||||||
Changed: | ||||||||
< < | 123.sub [Can start with a number] | |||||||
> > | 123.sub [Can start with a number] | |||||||
Changed: | ||||||||
< < | Illegal: a2 Not three characters | |||||||
> > | Illegal: a2 Not three characters | |||||||
Changed: | ||||||||
< < | .mydata.xxx Does not start with alphnumeric character | |||||||
> > | .mydata.xxx Does not start with alphnumeric character | |||||||
Changed: | ||||||||
< < | _mydata.xxx Does not start with alphanumeric [if _ is not considered such I'd put this in because in some systems you can start with an _ when you cannot with a number] | |||||||
> > | _mydata.xxx Does not start with alphanumeric [if _ is not considered such I'd put this in because in some systems you can start with an _ when you cannot with a number] | |||||||
Changed: | ||||||||
< < | data%20.space Includes percent encoded character | |||||||
> > | data%20.space Includes percent encoded character | |||||||
Changed: | ||||||||
< < | data^2.info Includes reserved character | |||||||
> > | data^2.info Includes reserved character | |||||||
Added: | ||||||||
> > |
| |||||||
Note that if % is not one of the unreserved characters, then the first MUST NOT is redundant. | ||||||||
Added: | ||||||||
> > |
| |||||||
If there are additional rules in RFC 3986 that could be broken then those violations should be illustrated too. Typo: third example in 2.1 where there is a space between .org/ and the following ? | ||||||||
Added: | ||||||||
> > |
| |||||||
-- TomMcGlynn - 2015-09-14
Comments from TCG member during the TCG Review Period: TCG_start_date - TCG_end_date!!! 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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
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. Latest version of Identifiers 2 can be found at: | ||||||||
Deleted: | ||||||||
< < | ||||||||
See also Examples of the validator.
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. | ||||||||
Changed: | ||||||||
< < | 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 | |||||||
> > | 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. | |||||||
Deleted: | ||||||||
< < | 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/formRFC Review Period: 2015-07-22 - 2015-09-01TCG Review Period: TCG_start_date - TCG_end_dateComments 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 MarkTaylor | ||||||||
Changed: | ||||||||
< < | Basically clear, it's good to have a detailed definition of Identifiers for reference. However I have some comments: | |||||||
> > | Basically clear, it's good to have a detailed definition of Identifiers for reference. However I have some comments: | |||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
Plus a few spellings and typos: | ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
Deleted: | ||||||||
< < | ||||||||
-- MarkTaylor - 2015-08-20 | ||||||||
Added: | ||||||||
> > | I'm not clear the the term <unreserved> is defined anywhere in the document. Presumably it refers to some range of characters defined somewhere (in RFC 3986 perhaps?) but that's not stated. I'd suggest the unreserved characters be defined explicitly here rather than requiring the user to find yet another document. While this is a relatively straightforward standard, I think it could be even clearer if there were examples given throughout the document and not just in 2.1. This is true of almost all IVOA standards. In particular I believe there should be labeled examples of both legal and illegal usage where at least one example is given for each class of violation and where we give legal examples for both normal usage and to illustrate the limits of valid code. E.g., Close 2.3.2 Authority with: Examples: Legal: nasa.heasarc n_1a.alph0.02 123.sub [Can start with a number] Illegal: a2 Not three characters .mydata.xxx Does not start with alphnumeric character _mydata.xxx Does not start with alphanumeric [if _ is not considered such I'd put this in because in some systems you can start with an _ when you cannot with a number] data%20.space Includes percent encoded character data^2.info Includes reserved character Note that if % is not one of the unreserved characters, then the first MUST NOT is redundant. If there are additional rules in RFC 3986 that could be broken then those violations should be illustrated too. Typo: third example in 2.1 where there is a space between .org/ and the following ? -- TomMcGlynn - 2015-09-14 | |||||||
Comments from TCG member during the TCG Review Period: TCG_start_date - TCG_end_date!!! 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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
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. Latest version of Identifiers 2 can be found at: See also Examples of the validator.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/formRFC Review Period: 2015-07-22 - 2015-09-01TCG Review Period: TCG_start_date - TCG_end_dateComments 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 document | ||||||||
Added: | ||||||||
> > |
Comments 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: TCG_start_date - TCG_end_date!!! 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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
IVOA Identifiers Version 2 Proposed Recommendation: Request for Comments | ||||||||
Changed: | ||||||||
< < | IVOA Identifiers describes the syntax and semantics of the IVOA's special URIs. | |||||||
> > | IVOA 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. | |||||||
Deleted: | ||||||||
< < | 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. | |||||||
Deleted: | ||||||||
< < | ||||||||
Latest version of Identifiers 2 can be found at: | ||||||||
Added: | ||||||||
> > | See also Examples of the validator. | |||||||
Reference Interoperable Implementations | ||||||||
Changed: | ||||||||
< < | Doesn't really apply here, as no protocol is defined. However, IVOA identifers | |||||||
> > | Doesn'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. | |||||||
Deleted: | ||||||||
< < | are in daily use in the Registry, and we preserve the Version 1 properties that make that work. | |||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | 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 | |||||||
Added: | ||||||||
> > | these things. | |||||||
Changed: | ||||||||
< < | The special form of standard ids has, essentially, been used for VOSI | |||||||
> > | 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. | |||||||
Deleted: | ||||||||
< < | 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/formRFC Review Period: 2015-07-22 - 2015-09-01TCG Review Period: TCG_start_date - TCG_end_date | ||||||||
Changed: | ||||||||
< < | Comments from the IVOA Community during RFC period: 2015-07-22 - 2015-09-01 | |||||||
> > | Comments from the IVOA Community during RFC period: 2015-07-22 - 2015-09-01 | |||||||
In 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 document
Comments from TCG member during the TCG Review Period: TCG_start_date - TCG_end_date!!! 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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|
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. Latest version of Identifiers 2 can be found at: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. 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/formRFC Review Period: 2015-07-22 - 2015-09-01TCG Review Period: TCG_start_date - TCG_end_dateComments 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 TCG member during the TCG Review Period: TCG_start_date - TCG_end_date!!! 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 )Data Access Layer Working Group ( François Bonnarel, Marco Molinaro )Data Model Working Group ( _Mark Cresitello-Dittmar, Laurent Michel )Grid & Web Services Working Group ( Brian Major, Giuliano Taffoni )Registry Working Group ( _Markus Demleitner, Theresa Dower )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 )<--
|