/[volute]/trunk/projects/vocabularies/doc/vocabularies-issues.xml
ViewVC logotype

Diff of /trunk/projects/vocabularies/doc/vocabularies-issues.xml

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

revision 60 by norman.x.gray, Sun Feb 10 22:14:45 2008 UTC revision 61 by norman.x.gray, Thu Feb 14 17:43:23 2008 UTC
# Line 103  Line 103 
103  without being final.</p>  without being final.</p>
104    
105  <div class='section-nonum' id='masterformat-1'>  <div class='section-nonum' id='masterformat-1'>
106  <p class='title'>[masterformat-1] Format of the master vocabulary</p>  <p class='title'>CLOSED: [masterformat-1] Format of the master vocabulary</p>
107    
108  <p><em>[Issue summarised here in some detail since it hasn't had much  <p><em>[Issue summarised here in some detail since it hasn't had much
109  airing on-list]</em></p>  airing on-list]</em></p>
# Line 138  Line 138 
138  <em>completely</em> technology-agnostic, and even SKOS is too hard to  <em>completely</em> technology-agnostic, and even SKOS is too hard to
139  parse, post-apocalypse]</p>  parse, post-apocalypse]</p>
140    
141  <p><strong>Provisional resolution:</strong> option (1) above – nothing  <p><strong>Provisional resolution: option (1) above – nothing
142  mandated.  Only the distribution format is to be specified (no  mandated</strong>.  Only the distribution format is to be specified (no
143  objections on the list).</p>  objections on the list).</p>
144    
145  <p>Discussion (such as it was):  <p>Discussion (such as it was):
# Line 154  Line 154 
154  </div>  </div>
155    
156  <div class='section-nonum' id='distformat-2'>  <div class='section-nonum' id='distformat-2'>
157  <p class='title'>[distformat-2] Format of the distributed vocabularies</p>  <p class='title'>CLOSED: [distformat-2] Format of the distributed vocabularies</p>
158    
159  <p>Question: in which format should vocabularies be distributed?</p>  <p>Question: in which format should vocabularies be distributed?</p>
160    
# Line 168  Line 168 
168  in a format which is parseable as RDF, but which is also regular  in a format which is parseable as RDF, but which is also regular
169  enough that it's usefully interpretable as ‘normal’ XML.</p>  enough that it's usefully interpretable as ‘normal’ XML.</p>
170    
171  <p><strong>Provisional resolution:</strong> option (1) above – distribution  <p><strong>Provisional resolution: option (1) above – distribution in
172  in any RDF serialisation.  More rationale to be added to the document.</p>  any RDF serialisation</strong>.  More rationale added to the
173    document.</p>
174    
175  <p>Discussion:  <p>Discussion:
176  <a href='http://www.ivoa.net/forum/semantics/0801/0644.htm' >2008 Jan 21</a>,  <a href='http://www.ivoa.net/forum/semantics/0801/0644.htm' >2008 Jan 21</a>,
# Line 219  Line 220 
220  </div>  </div>
221    
222  <div class='section-nonum' id='maintenance-4'>  <div class='section-nonum' id='maintenance-4'>
223  <p class='title'>[maintenance-4] Who maintains vocabularies?</p>  <p class='title'>CLOSED: [maintenance-4] Who maintains vocabularies?</p>
224    
225  <p>Question: By whom, and by what process, are vocabularies maintained?</p>  <p>Question: By whom, and by what process, are vocabularies maintained?</p>
226    
# Line 228  Line 229 
229  versions are identified, whereas this is concerned with who it is  versions are identified, whereas this is concerned with who it is
230  who manages the changes which are necessary as a vocabulary evolves.</p>  who manages the changes which are necessary as a vocabulary evolves.</p>
231    
232  <p>Possible resolution 1: the vocabularies in the standardised  <p>Option 1: the vocabularies in the standardised
233  document are regarded purely as examples, with no normative force and  document are regarded purely as examples, with no normative force and
234  no specified maintenance process.</p>  no specified maintenance process.</p>
235    
236  <p>Possible resolution 2: the document's vocabularies are normative,  <p>Option 2: the document's vocabularies are normative,
237  and the document should define a maintenance process, possibly  and the document should define a maintenance process, possibly
238  modelled on the UCD process <span class='cite' >std:ucdmaint</span>.</p>  modelled on the UCD process <span class='cite' >std:ucdmaint</span>.</p>
239    
240  <p>Possible resolution 3: the document's vocabularies are normative,  <p>Option 3: the document's vocabularies are normative,
241  but not claimed to be more than merely adequate.  They will not be  but not claimed to be more than merely adequate.  They will not be
242  developed as part of this standard's evolution, but instead be  developed as part of this standard's evolution, but instead be
243  maintained by other interest groups, either within or outwith the IVOA  maintained by other interest groups, either within or outwith the IVOA
# Line 247  Line 248 
248  maintainers to use the <code>&lt;skos:changeNote&gt;</code>  maintainers to use the <code>&lt;skos:changeNote&gt;</code>
249  mechanisms, or just rely on their good sense?</p>  mechanisms, or just rely on their good sense?</p>
250    
251    <p><strong>Provisional resolution: Option 3</strong>.  The final
252    published standard will include a number of SKOS vocabularies produced
253    as part of this process.  These will be usable and citable, and the
254    community will be encouraged to use them, but they will not be
255    maintained after the standard is complete.  Instead, the `owners' of
256    the underlying vocabularies (for example the UCD maintenance group)
257    will be encouraged to maintain the SKOS version alongside their other
258    forms.  In particular, the IVOA-T vocabulary will be developed and
259    maintained in a parallel standard to this one.</p>
260    
261  <p>Discussion:  <p>Discussion:
262  <a href='http://www.ivoa.net/forum/semantics/0801/0665.htm' >2008 Jan 31</a>  <a href='http://www.ivoa.net/forum/semantics/0801/0665.htm' >2008 Jan 31</a>,
263    <a href='http://www.ivoa.net/forum/semantics/0802/0753.htm' >2008 Feb 14</a>
264  </p>  </p>
265    
266  </div>  </div>
267    
268  <div class='section-nonum' id='vocabset-5'>  <div class='section-nonum' id='vocabset-5'>
269  <p class='title'>[vocabset-5] What vocabularies are included in the standard?</p>  <p class='title'>CLOSED: [vocabset-5] What vocabularies are included in the standard?</p>
270    
271  <p>Irrespective of the resolution to issue <span  <p>Irrespective of the resolution to issue <span
272  class='xref'>maintenance-4</span>, there will be a set of vocabularies  class='xref'>maintenance-4</span>, there will be a set of vocabularies
# Line 283  Line 295 
295  been SKOSified at all, and Rick's excellent suggestion is that these  been SKOSified at all, and Rick's excellent suggestion is that these
296  be left as homework for the VOEvent group.</p>  be left as homework for the VOEvent group.</p>
297    
298    <p><strong>Provisional resolution: include all five/six</strong>.  The
299    A&amp;A, AOIM, UCD1, IAU-93 and constellations vocabularies will be
300    finished and immediately useable (see the resolution on maintenance in
301    <a href='#maintenance-4'>[maintenance-4]</a>).  The IVOAT vocabulary
302    will be developed in a parallel process to this vocabularies standard:
303    it will be referred to, and a snapshot of it <em>may</em> be included
304    in the standard, but it will be clearly marked as a work-in-progress.</p>
305    
306  <p>Discussion:  <p>Discussion:
307  <a href='http://www.ivoa.net/forum/semantics/0801/0665.htm' >2008 Jan 31</a>,  <a href='http://www.ivoa.net/forum/semantics/0801/0665.htm' >2008 Jan 31</a>,
308  <a href='http://www.ivoa.net/forum/semantics/0802/0682.htm' >2008 Feb 4</a>,  <a href='http://www.ivoa.net/forum/semantics/0802/0682.htm' >2008 Feb 4</a>,
309  <a href='http://www.ivoa.net/forum/voevent/0802/0654.htm' >2008 Feb 4  <a href='http://www.ivoa.net/forum/voevent/0802/0654.htm' >2008 Feb 4
310  (VOEvent list)</a>,  (VOEvent list)</a>,
311  <a href='http://www.ivoa.net/forum/semantics/0802/0711.htm' >7</a>;  <a href='http://www.ivoa.net/forum/semantics/0802/0711.htm' >7</a>,
312    <a href='http://www.ivoa.net/forum/semantics/0802/0753.htm' >14</a>;
313  <a href='http://www.ivoa.net/twiki/bin/view/IVOA/VocabulariesWorkingArea'  <a href='http://www.ivoa.net/twiki/bin/view/IVOA/VocabulariesWorkingArea'
314     >wiki page</a>.     >wiki page</a>.
315  </p>  </p>
316    
317  </div>  </div>
318    
319    <div class='section-nonum' id='mappings-6'>
320    <p class='title'>[mappings-6] Inclusion of mappings in vocabularies</p>
321    
322    <p>Should mappings between vocabularies be in this standard, and if
323    so, how closely bound should they be to the vocabulary itself?</p>
324    
325    <p>The early-2008 editors draft for the SKOS standard <span
326    class='cite'>std:skosref</span> included inter-vocabulary mappings,
327    which were hitherto separate from the intra-vocabulary links in the
328    SKOS core.  The question of mappings in the SKOS standard is still
329    (early 2008) in flux.</p>
330    
331    <p>Question: how do we accomodate this uncertainty in the IVOA
332    Vocabularies standard?  And how do we advise mappings to be published?</p>
333    
334    <p>Consideration 1: The mappings spec is still in flux, and likely to
335    remain so for some time after the SKOS core document is
336    standardised</p>
337    
338    <p>Consideration 2: Norman would hope to see the situation developing
339    where there are multiple third-party mappings between vocabularies,
340    maintained by specific communities, or which describe mappings at
341    different levels of granularity, or which represent significant
342    (publication-worthy?) labour on the part of individuals, adding value
343    to the network of vocabularies.</p>
344    
345    <p>Suggested resolution: include mappings as non-normative parts of
346    this standard, published alongside, but separate from, the normative
347    SKOS versions of the vocabularies, and using whatever are the
348    then-current best mapping practices.  In this standard, and in the
349    best-practice guidelines we include, we should proscribe inter-vocabulary
350    mappings being published as part of a vocabulary.</p>
351    
352    <p>Crucially, vocabularies and the mappings between them are
353    conceptually separate entities, although they will in practice likely be
354    maintained together.</p>
355    
356    </div>
357    
358  </div>  </div>
359    
360  <div class='appendices'>  <div class='appendices'>

Legend:
Removed from v.60  
changed lines
  Added in v.61

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