<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi,<div><br></div><div>Dave Morris reminded me that here:</div><div><br></div><div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); "><a href="http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/VOSpaceHome#Standard_URIs">http://www.ivoa.net/cgi-bin/twiki/bin/view/IVOA/VOSpaceHome#Standard_URIs</a></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); ">there is text that assigns different StandardIDs for registration - i.e. it uses the names of internal capabilities.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); ">In that form, the standardID includes the version of the interface.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); ">I prefer the simpler form of the standardID, without the version number, unless there is a pressing</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); ">need to have different capabilities for different versions. The interface elements distinguish the versions.</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); "><br></div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); ">Guy</div><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; font: normal normal normal 12px/normal Helvetica; color: rgb(11, 21, 232); "><br></div><div><div>On 14 Apr 2009, at 12:35, Paul Harrison wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div><br>On 2009-04 -14, at 11:07, Guy Rixon wrote:<br><br><blockquote type="cite">Hi,<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">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).<br></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">I need to write code dealing with VOSpace registrations right away. May I assume that the StandardID is ivo://ivoa.net/std/VOSpace,<br></blockquote><blockquote type="cite">following the usual pattern?<br></blockquote><blockquote type="cite"><br></blockquote><br>In the original VOSpace usage note draft <a href="http://www.ivoa.net/internal/IVOA/VOSpaceHome/VOSpace-Usage.odt">http://www.ivoa.net/internal/IVOA/VOSpaceHome/VOSpace-Usage.odt</a> 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.<br><br><br>Paul.<br><br>Dr. Paul Harrison<br>JBCA, Manchester University<br><a href="http://www.manchester.ac.uk/jodrellbank">http://www.manchester.ac.uk/jodrellbank</a><br><br><br></div></blockquote></div><br></div></body></html>