Difference: VOResourceNext (1 vs. 6)

Revision 62019-02-05 - MarkusDemleitner

 
META TOPICPARENT name="RegistryWorkingGroup"
Changed:
<
<
This page collects specification issues as well as proposals for extensions for VOResource.
>
>
Note: This was an early prototype for the -Next pages and hence didn't have a version number in it yet. This page is superseded by VOResource-1_1-Next.
 
Added:
>
>
This page collects specification issues as well as proposals for extensions for VOResource 1.0.
 Work on the document itself is done in volute, http://volute.g-vo.org/svn/trunk/projects/registry/VOResource

Following the guidelines to report and accept Errata to IVOA standards here you'll only find listed the proposed features and discussion for subsequents revisions of the this specification.

Errata tracking for VOResource 1.1 can be found at the VOResourceOneDotOneErrata page.

Specification Problems

As of: VOResource 1.1 (Rec)

  • There is a discrepancy in some IVOA documents that causes XSD validation failures. Standards documents give examples of ivo-id's that include a '#' but VOResource-v1.0.xsd or
VOResource-v1.1.xsd do not allow it, for example:
http://ivoa.net/documents/SimpleDALRegExt/20170530/REC-SimpleDALRegExt-1.1.html: ivo://ivoa.net/std/SIA#query???2.0

http://www.ivoa.net/documents/RegTAP/20180731/PR-RegTAP-1.1-20180731.html : <dataModel ivo-id="ivo://ivoa.net/std/RegTAP#1.1">Registry 1.1</dataModel>

Suggested Extensions

  • There should be an indication of the "size" of a resource. This would normally be the number of rows present in the underlying database table (this should probably be dealt with in VODataService).
  • We should probably have a place for ORCIDs
    • Addressed by 1.1 IWD (altIdentifier on authors)
  • There should be a standard way to reference individual capabilities (use case: someone wants to say: "I used this TAP service to generate this data"; referencing the whole record may not be good enough if there are other capabilities like, say, Datalink or SIA on that same service, or there's TAP capabilities of different versions in there).
Added:
>
>
* This has been shelved for now since there was not sufficient community interest to develop and test solutions.
 
<--  
-->

Revision 52018-12-04 - TheresaDower

 
META TOPICPARENT name="RegistryWorkingGroup"
This page collects specification issues as well as proposals for extensions for VOResource.
Changed:
<
<
There is an internal working draft for VOResource. Work is being done in volute, http://volute.g-vo.org/svn/trunk/projects/registry/VOResource
>
>
Work on the document itself is done in volute, http://volute.g-vo.org/svn/trunk/projects/registry/VOResource
 
Added:
>
>
Following the guidelines to report and accept Errata to IVOA standards here you'll only find listed the proposed features and discussion for subsequents revisions of the this specification.

Errata tracking for VOResource 1.1 can be found at the VOResourceOneDotOneErrata page.

 

Specification Problems

Added:
>
>

As of: VOResource 1.1 (Rec)

  • There is a discrepancy in some IVOA documents that causes XSD validation failures. Standards documents give examples of ivo-id's that include a '#' but VOResource-v1.0.xsd or
VOResource-v1.1.xsd do not allow it, for example:
http://ivoa.net/documents/SimpleDALRegExt/20170530/REC-SimpleDALRegExt-1.1.html: ivo://ivoa.net/std/SIA#query???2.0

http://www.ivoa.net/documents/RegTAP/20180731/PR-RegTAP-1.1-20180731.html : <dataModel ivo-id="ivo://ivoa.net/std/RegTAP#1.1">Registry 1.1</dataModel>

 

Suggested Extensions

  • There should be an indication of the "size" of a resource. This would normally be the number of rows present in the underlying database table (this should probably be dealt with in VODataService).
  • We should probably have a place for ORCIDs
    • Addressed by 1.1 IWD (altIdentifier on authors)
  • There should be a standard way to reference individual capabilities (use case: someone wants to say: "I used this TAP service to generate this data"; referencing the whole record may not be good enough if there are other capabilities like, say, Datalink or SIA on that same service, or there's TAP capabilities of different versions in there).
<--  
-->

Revision 42016-06-08 - MarkusDemleitner

 
META TOPICPARENT name="RegistryWorkingGroup"
Changed:
<
<
This page collects specification issues as well as proposals for extensions for VOResource. No new version of the document is scheduled right now.
>
>
This page collects specification issues as well as proposals for extensions for VOResource.
 
Added:
>
>
There is an internal working draft for VOResource. Work is being done in volute, http://volute.g-vo.org/svn/trunk/projects/registry/VOResource
 

Specification Problems

Suggested Extensions

  • There should be an indication of the "size" of a resource. This would normally be the number of rows present in the underlying database table (this should probably be dealt with in VODataService).
Changed:
<
<
  • We should probably have a place for ORCIDs
>
>
  • We should probably have a place for ORCIDs
Added:
>
>
    • Addressed by 1.1 IWD (altIdentifier on authors)
 
  • There should be a standard way to reference individual capabilities (use case: someone wants to say: "I used this TAP service to generate this data"; referencing the whole record may not be good enough if there are other capabilities like, say, Datalink or SIA on that same service, or there's TAP capabilities of different versions in there).
<--  
-->

Revision 32015-06-12 - MarkusDemleitner

 
META TOPICPARENT name="RegistryWorkingGroup"
This page collects specification issues as well as proposals for extensions for VOResource. No new version of the document is scheduled right now.

Specification Problems

Suggested Extensions

  • There should be an indication of the "size" of a resource. This would normally be the number of rows present in the underlying database table (this should probably be dealt with in VODataService).
  • We should probably have a place for ORCIDs
Changed:
<
<

Revision 22015-02-24 - MarkusDemleitner

 
META TOPICPARENT name="RegistryWorkingGroup"
This page collects specification issues as well as proposals for extensions for VOResource. No new version of the document is scheduled right now.

Specification Problems

Suggested Extensions

Changed:
<
<
There should be an indication of the "size" of a resource. This would normally be the number of rows present in the underlying database table (this should probably be dealt with in VODataService).
>
>
  • There should be an indication of the "size" of a resource. This would normally be the number of rows present in the underlying database table (this should probably be dealt with in VODataService).
Added:
>
>
  • We should probably have a place for ORCIDs
 
<--  
-->

Revision 12015-02-13 - MarkusDemleitner

 
META TOPICPARENT name="RegistryWorkingGroup"
This page collects specification issues as well as proposals for extensions for VOResource. No new version of the document is scheduled right now.

Specification Problems

Suggested Extensions

There should be an indication of the "size" of a resource. This would normally be the number of rows present in the underlying database table (this should probably be dealt with in VODataService).


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback