Difference: VOResource-1_1-Next (1 vs. 2)

Revision 22019-09-11 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"

VOResource 1.1 Next

Changed:
<
<
Proposed changes and additions to VOResource. Changes would go to VOResource 1.2. this page for VOResource 1.0
>
>
Proposed changes and additions to VOResource. Changes would go to VOResource 1.2.
Added:
>
>
(this page for VOResource 1.0)

A serverSoftware child for interface?

Use cases:

  • Clients sometimes like to know which software they are talking to
  • Server software authors would like to know which versions of their software are still around.

Possible solution:

Add an (optional) serverSoftware child to vr:interface. Its contents would be a string, preferably of the form (name) (version).

Alternative:

Just use the server: field in the HTTP responses.

 
<--  
-->

Revision 12019-02-05 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"

VOResource 1.1 Next

Proposed changes and additions to VOResource. Changes would go to VOResource 1.2. this page for VOResource 1.0


<--  
-->
 
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