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

Revision 42022-02-15 - 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)

Deleted:
<
<

A serverSoftware child for interface?

 
Deleted:
<
<
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.

 

Force referenceURL to be http(s)

Changed:
<
<
Various data providers get the reference URLs wrong (e.g., using plain domain names) or fail to give sensible values and are never reminded to put them in. The schema does not notice that because xs:anyURI is rather lenient (by necessity).
>
>
Various data providers get the reference URLs wrong (e.g., using plain domain names) or fail to give sensible values and are never reminded to put them in. The schema does not notice that because xs:anyURI is rather lenient (by necessity).
 
Changed:
<
<
On the other hand, the having something a browser can in all likelihood deal with appears eminently useful. While that won't prevent 404s, just forcing referenceURL to start with https?:// would go a long way to ensure useful reference URLs.
>
>
On the other hand, the having something a browser can in all likelihood deal with appears eminently useful. While that won't prevent 404s, just forcing referenceURL to start with https?:// would go a long way to ensure useful reference URLs.
 
Added:
>
>

Allow DOIs in sources

So far, we only define "bibcode" to give bibliographic sources. People can use DOIs as is, but that will only be interoperable when we say what they ought to put into format then. I'd say it should be DOI.

 
<--  
-->

Revision 32022-02-11 - MarkusDemleitner

 
META TOPICPARENT name="IvoaResReg"

VOResource 1.1 Next

Changed:
<
<
Proposed changes and additions to VOResource. Changes would go to VOResource 1.2.
>
>
Proposed changes and additions to VOResource. Changes would go to VOResource 1.2.
  (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.
Deleted:
<
<
 Possible solution:
Changed:
<
<
Add an (optional) serverSoftware child to vr:interface. Its contents
>
>
Add an (optional) serverSoftware child to vr:interface. Its contents would be a string, preferably of the form (name) (version).
Deleted:
<
<
would be a string, preferably of the form (name) (version).
  Alternative:

Just use the server: field in the HTTP responses.

Added:
>
>

Force referenceURL to be http(s)

Various data providers get the reference URLs wrong (e.g., using plain domain names) or fail to give sensible values and are never reminded to put them in. The schema does not notice that because xs:anyURI is rather lenient (by necessity).

On the other hand, the having something a browser can in all likelihood deal with appears eminently useful. While that won't prevent 404s, just forcing referenceURL to start with https?:// would go a long way to ensure useful reference URLs.

 
<--  
-->

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