StandardID for VOSpace Capability

[Guy Rixon]

Hi,

Dave Morris reminded me that here:

http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/VOSpaceHome#Standard_URIs

there is text that assigns different StandardIDs for registration -  
i.e. it uses the names of internal capabilities.
In that form, the standardID includes the version of the interface.

I prefer the simpler form of the standardID, without the version  
number, unless there is a pressing
need to have different capabilities for different versions. The  
interface elements distinguish the versions.

Guy

On 14 Apr 2009, at 12:35, Paul Harrison wrote:

>
> On 2009-04 -14, at 11:07, Guy Rixon wrote:
>
>> Hi,
>>
>> looking through VOSpace-1.14, I can't see any mention of how a  
>> VOSpace service is registered. In particular, the StandardID for a  
>> VOSpace capability is not given (this is the capability of the  
>> service written in the resource registry as opposed to the  
>> capability of a node written within the space itself).
>>
>> I need to write code dealing with VOSpace registrations right away.  
>> May I assume that the StandardID is ivo://ivoa.net/std/VOSpace,
>> following the usual pattern?
>>
>
> In the original VOSpace usage note draft http://www.ivoa.net/internal/IVOA/VOSpaceHome/VOSpace-Usage.odt 
>  it had been defined as ivo://net.ivoa/standard/VOSpace - however,  
> that was some time ago now and your suggestion does follow the  
> pattern of SIA etc. so I think your suggestion is fine.
>
>
> Paul.
>
> Dr. Paul Harrison
> JBCA, Manchester University
> http://www.manchester.ac.uk/jodrellbank
>
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.ivoa.net/pipermail/grid/attachments/20090414/cec18030/attachment-0003.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3006 bytes
Desc: not available
URL: <http://www.ivoa.net/pipermail/grid/attachments/20090414/cec18030/attachment-0003.bin>