/[volute]/trunk/projects/registry/Identifiers/Identifiers.tex
ViewVC logotype

Diff of /trunk/projects/registry/Identifiers/Identifiers.tex

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 3089 by msdemlei, Thu Sep 24 13:27:55 2015 UTC revision 3090 by msdemlei, Wed Oct 7 09:58:37 2015 UTC
# Line 888  Line 888 
888  the scheme laid out below) is $$  the scheme laid out below) is $$
889  \mbox{\nolinkurl{ivo://org.gavo.dc/~?flashheros/data/ca92/f0065.mt}.}$$  \mbox{\nolinkurl{ivo://org.gavo.dc/~?flashheros/data/ca92/f0065.mt}.}$$
890    
 This specification does not exhaustively define the resolution of  
 publisher DIDs.  Instead, we recommend the following procedure, to be  
 amended as new standards are defined:  
   
 \begin{enumerate}  
 \item Obtain the Registry part of the PubDID by stripping the query and  
 fragment parts  
 \item Retrieve the corresponding resource record from a registry  
 \item If that record has a Datalink capability, dataset access options  
 can be retrieved by running the Datalink service with its \emph{ID}  
 parameter set to the PubDID.  
 \item If that record has an SSA capability, the dataset access URL  
 can be retrieved using SSAP's \emph{PUBLISHERDID} parameter.  
 \item If that record has a TAP capability implementing the ObsCore data  
 model, the dataset access URL can be retrieved by running a query  
 against ObsCore's \emph{obs\_publisher\_did} column  
 \item If that record has a \emph{served-by} relationship to other  
 record(s), each of the records mentioned in that relationship are tested  
 for for Datalink, SSA, and suitable TAP capabilities.  
 \end{enumerate}  
   
891  Existing DIDs in services implementing SSAP up to 1.1 and Obscore 1.0  Existing DIDs in services implementing SSAP up to 1.1 and Obscore 1.0
892  are not affected by these requirements and may be used until the  are not affected by these requirements and may be used until the
893  respective services are updated to newer standards.  respective services are updated to newer standards.
894    
895    Note that by this specification publishers have no obligation to ensure
896    continued access to datasets identified with PubDIDs. They are \emph{not}
897    persistent identifiers with guarantees on resolvability.  Their main
898    function is to provide globally unique identifiers for use in, e.g.,
899    federating responses from different services.
900    
901    Publishers are, however, encouraged to provide PubDID-resolving
902    services\footnote{At the time of this writing, Datalink, Obscore, and
903    SSA are IVOA recommended protocols allowing the resolution of PubDIDs
904    with various mechanisms.  SIA \citep{std:SIAP} will, according to current
905    proposed recommendations, have a PubDID-resolving facility in version
906    2.0.} as a capability of the resource referenced by the Registry part of
907    a PubDID (i.e., anything in front of the first question mark).  In that
908    way, clients can attempt to resolve stand-alone PubDIDs by querying the
909    registry for the ``embedding'' resource and seeing if it supports any
910    PubDID-resolving protocol they implement.
911    
912    
913  \subsection{Standard Identifiers}  \subsection{Standard Identifiers}
914  \label{sect:standards}  \label{sect:standards}
915    
# Line 989  Line 986 
986  and an IVOID hat only has a registry part is called a Registry  and an IVOID hat only has a registry part is called a Registry
987  reference.  reference.
988  \item More examples  \item More examples
989    \item Fixed the SSAP parameter name from PUBLISHERDID to PUBDID (as
990    required by the standard)
991  \item Editorial changes  \item Editorial changes
992  \end{itemize}  \end{itemize}
993    

Legend:
Removed from v.3089  
changed lines
  Added in v.3090

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26