This page collects specification issues as well as proposals for extensions for VOResource.

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).
  • 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).
Edit | Attach | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2016-06-08 - MarkusDemleitner
 
This site is powered by the TWiki collaboration platformCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback