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

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

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

revision 5154 by msdemlei, Fri Sep 28 10:05:15 2018 UTC revision 5155 by msdemlei, Mon Oct 1 13:24:31 2018 UTC
# Line 113  Line 113 
113  schema include the namespaces prefix \xmlel{vr} as in  schema include the namespaces prefix \xmlel{vr} as in
114  \xmlel{vr:Resource} (a type defined in the VOResource schema; the  \xmlel{vr:Resource} (a type defined in the VOResource schema; the
115  recommended namespace prefix for VODataService as per Registry  recommended namespace prefix for VODataService as per Registry
116  Interfaces 1.1 \citep{todo:RI1.1}, sect.~2.2, is \xmlel{vs}.  Interfaces 1.1 \citep{2018ivoa.spec.0723D}, sect.~2.2, is \xmlel{vs}.
117    
118  \section{Introduction}  \section{Introduction}
119    
# Line 237  Line 237 
237    
238  The namespace associated with VODataService extensions is  The namespace associated with VODataService extensions is
239  $$\mbox{\texttt{http://www.ivoa.net/xml/VODataService/v1.1}}.$$  $$\mbox{\texttt{http://www.ivoa.net/xml/VODataService/v1.1}}.$$
240  Just like the namespace URI for the VOResource schema, the  As required by the IVOA schema versioning policies
241  VODataService namespace URI can be interpreted as a URL.  Resolving it  \citep{2018ivoa.spec.0529H}, this namespace is identical to the one
242  will return the XML Schema document  associated with version 1.1 of this document.  It is regrettable that a
243  that defines the VODataService schema.\todo{explain constant ns vs.  misleading minor version is present in the namespace URI, but dropping
244  v1.1}  it would break existing software for creating and processing
245    VODataService instance documents.  Hence, the namespace URI ending in
246    \verb|1.1| is also used for versions 1.2, 1.3, and so forth of the
247    schema.
248    
249    Resolving the VODataService namespace URI will redirect to a schema
250    document having the actual version number (for the schema associated
251    with this document version, this will end in VODataService-1.2.xsd).
252    Following the schema versioning policies, the minor version will be
253    declared in the \xmlel{version} attribute of this file's root element.
254    This information should not in general be used in production software;
255    all versions with the above schema URI are compatible with each
256    other in the sense defined in the IVOA schema versioning policies.
257    
258    The versioning policies in version 1.0 posit a requirement that instance
259    documents declare the minor version of the schema used to produce them
260    in the root element of elements coming from a schema.  VODataService has
261    no global elements, and hence there is no place for such a declaration,
262    nor is it needed.
263    
264    
265  Authors of VOResource instance documents may choose to  Authors of VOResource instance documents may choose to
# Line 260  Line 277 
277    
278    
279  \begin{admonition}{Note}  \begin{admonition}{Note}
280  The IVOA Registry Interface standard \citep{todo:RI1.1}  The IVOA Registry Interface standard \citep{2018ivoa.spec.0723D}
281         actually \emph{requires} that the VOResource records it         actually \emph{requires} that the VOResource records it
282         shares with other registries provide location URLs via         shares with other registries provide location URLs via
283         \xmlel{xsi:schemaLocation} for the VOResource schema and         \xmlel{xsi:schemaLocation} for the VOResource schema and
# Line 269  Line 286 
286  \end{admonition}  \end{admonition}
287    
288    
289  The prefix, \xmlel{vs}, is used by convention as the prefix  The canonical prefix for VODataService is \xmlel{vs}; this means, in
290  defined for the VODataService schema; however, instance documents may  particular, that in non-XML contexts (e.g., relational mappings
291  use any prefix.  In applications where common use of prefixes is  like RegTAP) global VODataService elements \emph{must} be qualified with
292  recommended (such as with the Registry Interfaces specification),  vs:.  The Registry Interfaces standard \citep{2018ivoa.spec.0723D} also
293  use of the \xmlel{vs} prefix is recommended.  strongly recommends using the canonical prefixes in XML documents.
294    
295  Note also that in this document, the \xmlel{vr} prefix is used to  Note also that in this document, the \xmlel{vr} prefix is used to
296  label, as shorthand, a type or element name that is defined in the  label, as shorthand, a type or element name that is defined in the
297  VOResource schema, as in \xmlel{vr:Resource}.  VOResource schema, as in \xmlel{vr:Resource}.
# Line 283  Line 301 
301    
302  As recommend by the VOResource standard, the  As recommend by the VOResource standard, the
303  VODataService schema sets \xmlel{element\-Form\-Default} to \emph{unqualified}.  VODataService schema sets \xmlel{element\-Form\-Default} to \emph{unqualified}.
304  This means that it is not necessary to qualify element names defined  This means that element names defined
305  in this schema with a namespace prefix (as there are no global  in this schema may not be used with a namespace prefix.
306  elements defined).  The only place it is usually needed is as a  The only place the namespace prefix must be used is the
307  qualifier to a VODataService type name given as the value of an  type names given as the value of an
308  \xmlel{xsi:type} attribute.    \xmlel{xsi:type} attribute.  
309    
310    

Legend:
Removed from v.5154  
changed lines
  Added in v.5155

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