[Volute] r3956 - trunk/projects/edu/edumatters

Volute commit messages volutecommits at g-vo.org
Fri Apr 21 15:31:18 CEST 2017


Author: msdemlei
Date: Fri Apr 21 15:31:18 2017
New Revision: 3956

Log:
edumatters: translation to ivoatex markup.

Modified:
   trunk/projects/edu/edumatters/Makefile
   trunk/projects/edu/edumatters/edumatters.bbl
   trunk/projects/edu/edumatters/edumatters.tex

Modified: trunk/projects/edu/edumatters/Makefile
==============================================================================
--- trunk/projects/edu/edumatters/Makefile	Fri Apr 21 11:17:13 2017	(r3955)
+++ trunk/projects/edu/edumatters/Makefile	Fri Apr 21 15:31:18 2017	(r3956)
@@ -1,129 +1,28 @@
-# Makefile to drive ivoadoc.
-#
-# To use this, you must have checked out ivoadoc as svn:externals into
-# your document directory.  Copy this Makefile into that directory and
-# edit it as necessary.
-#
-# To make this work, you need xalan and fop; on Debian systems, the following
-# should do the trick:
-#
-# sudo aptitude install xalan fop w3c-dtd-xhtml
-#
-# You most likely want the hyphenation patterns for fop (the PDF
-# formatter), too.  Presumably for licensing reasons, you have to 
-# get them manually from http://offo.sourceforge.net.  Drop them
-# into /usr/share/fop/fop-hyph.jar (that's FOPHYPH below)
-#
-# Edit your source as $(STDNAME).html; available targets then are:
-#
-# * default: format the html, expanding the magic things explained in
-#   ivoadoc/README
-# * $(STDNAME).pdf: same, but make a pdf
-# * package: package the docs, css, all pngs and whatever is in
-#   PACKAGE_EXTRAS into an aptly-named zip that expands into a
-#   nicely-named subdirectory.
-# * biblio: remake the bibliography (this is never done automatically).
-#   Unless you try the experimental includebibliography PI, you have
-#   to manually insert the result into your HTML.
-#
-# Contact for this Makefile: Markus Demleitner (gavo at ari.uni-heidelberg.de)
-#
-# Fix (and maintain, as you go on) the following set of variables:
-#
-# The base name of the files (a sensible abbreviation of your standard's 
-# title; this is case sensitive)
-STDNAME=edumatters
-# The current version
-DOCVERSION=1.0
-# YYYYMMDD of the current release
-DOCDATE=20140225
-# One of NOTE, WD, PR, REC
-PUBSTATUS=NOTE
-# Extra files that need to end up in the final package
-# (pngs are included automatically)
-PACKAGE_EXTRAS=
-
-
-# You probably want to configure your system so the following works
-# Basically, RESOLVERJAR must eventally point to a jar of apache
-# xml commons resolver, and SAXONJAR to a jar containing saxon-b
-#
-# For Debian Squeeze, you need to install the backported fop to make
-# this work.
-
-CATALOG=ivoadoc/xmlcatalog/catalog.xml
-FOPHYPH=/usr/share/fop/fop-hyph.jar
-
-JARROOT=/usr/share/java
-RESOLVERJAR=$(JARROOT)/xml-resolver.jar
-SAXONJAR=$(JARROOT)/saxonb.jar
-SAXON=java -cp $(RESOLVERJAR):$(SAXONJAR) \
-	-Dxml.catalog.files=$(CATALOG) -Dxml.catalog.verbosity=1\
-	net.sf.saxon.Transform\
-	-novw -r org.apache.xml.resolver.tools.CatalogResolver\
-	-x org.apache.xml.resolver.tools.ResolvingXMLReader\
-	-y org.apache.xml.resolver.tools.ResolvingXMLReader
-BIBTEX=bibtex
-SED=sed
-
-# TODO: make fop use our custom catalog
-FOP=FOP_HYPHENATION_PATH=$(FOPHYPH) fop -catalog
-
-HTMLSTYLE=ivoadoc/ivoarestructure.xslt
-FOSTYLE=ivoadoc/ivoa-fo.xsl
-CITEEXSTYLE=ivoadoc/extractcite.xslt
-
-# You should not need to edit anything below this line
-
-versionedName:=$(PUBSTATUS)-$(STDNAME)-$(DOCVERSION)
-ifneq "$(PUBSTATUS)" "REC"
-		versionedName:=$(versionedName)-$(subst -,,$(DOCDATE))
-endif
-
-.PHONY: package
-
-%-fmt.html: %.html $(HTMLSTYLE)
-	$(SAXON) -o $@ $< $(HTMLSTYLE) docdate=$(DOCDATE)\
-		docversion=$(DOCVERSION) pubstatus=$(PUBSTATUS) ivoname=$(STDNAME)
-
-%.fo: %-fmt.html
-	$(SAXON) -o $@ $< $(FOSTYLE) docdate=$(DOCDATE)\
-		docversion=$(DOCVERSION) pubstatus=$(PUBSTATUS) ivoname=$(STDNAME)
-
-%.pdf: %.fo
-	$(FOP) -pdf $@ -fo $<
-
-# this is for BibTex
-%.aux: %.html
-	$(SAXON) -o:$@ -xsl:$(CITEEXSTYLE) -s:$< 
-
-%.bbl: %.aux
-	$(BIBTEX) $<
-	$(SED) -f ivoadoc/detex.sed $@ > $@.tmp
-	mv $@.tmp $@
-
-default: $(STDNAME)-fmt.html
-
-cleanbbl:
-	rm -f $(STDNAME).bbl
-
-biblio: cleanbbl $(STDNAME).bbl
-
-package: $(STDNAME)-fmt.html $(STDNAME).pdf
-	rm -rf -- $(versionedName)
-	mkdir $(versionedName)
-	cp $(STDNAME)-fmt.html $(versionedName)/$(versionedName).html
-	cp $(STDNAME).pdf $(versionedName)/$(versionedName).pdf
-	mkdir $(versionedName)/ivoadoc
-	cp ivoadoc/*.css $(versionedName)/ivoadoc
-	cp *.png $(SCHEMA_FILE) $(PACKAGE_EXTRAS) $(versionedName)
-	zip -r $(versionedName).zip $(versionedName)
-	rm -rf -- $(versionedName)
-
-clean:
-	rm -f $(PUBSTATUS)-$(STDNAME)-*.html
-	rm -f $(PUBSTATUS)-$(STDNAME)-*.pdf
-	rm -f $(STDNAME).pdf
-	rm -fr $(PUBSTATUS)-$(STDNAME)*.zip
+# ivoatex Makefile.  The ivoatex/README for the targets available.
 
--include make.local
+# short name of your document (edit $DOCNAME.tex; would be like RegTAP)
+DOCNAME = edumatters
+
+# count up; you probably do not want to bother with versions <1.0
+DOCVERSION = 1.0
+
+# Publication date, ISO format; update manually for "releases"
+DOCDATE = 2017-06-04
+
+# What is it you're writing: NOTE, WD, PR, REC, PEN, or EN
+DOCTYPE = PEN
+
+# Source files for the TeX document (but the main file must always
+# be called $(DOCNAME).tex
+SOURCES = $(DOCNAME).tex m1distance-example.xml
+
+# List of pixel image files to be included in submitted package 
+FIGURES = curation.png
+
+# List of PDF figures (for vector graphics)
+VECTORFIGURES = 
+
+# Additional files to distribute (e.g., CSS, schema files, examples...)
+AUX_FILES = 
+
+include ivoatex/Makefile

Modified: trunk/projects/edu/edumatters/edumatters.bbl
==============================================================================
--- trunk/projects/edu/edumatters/edumatters.bbl	Fri Apr 21 11:17:13 2017	(r3955)
+++ trunk/projects/edu/edumatters/edumatters.bbl	Fri Apr 21 15:31:18 2017	(r3956)
@@ -1,38 +1,42 @@
-<dl xmlns='http://www.w3.org/1999/xhtml'>
+\begin{thebibliography}{xx}
 
-<dt><a name="std:RI1">[std:RI1] Kevin Benson, Ray Plante, Elizabeth Auden,
-  Matthew Graham, Gretchen Greene, Martin Hill, Tony Linde, Dave Morris, Wil
-  O'Mullane, Guy Rixon, Aurélien Stébé, and Kona Andrews, Kevin Benson and
-  Ray Plante, editors.</a></dt> <dd>
-  <a href="http://www.ivoa.net/Documents/RegistryInterface/" >IVOA registry
-  interfaces version 1.0</a>.
-  IVOA Recommendation, 2009.
-</dd>
+\harvarditem[{Benson} \harvardand\ {Plante} et~al.]{{Benson}, {Plante},
+  {Auden}, {Graham}, {Greene}, {Hill}, {Linde}, {Morris}, {O`Mullane}, {Rixon},
+  {St{\'e}b{\'e}} \harvardand\ {Andrews}}{2009}{2009ivoa.spec.1104B}
+{Benson}, K., {Plante}, R., {Auden}, E., {Graham}, M., {Greene}, G., {Hill},
+  M., {Linde}, T., {Morris}, D., {O`Mullane}, W., {Rixon}, G., {St{\'e}b{\'e}},
+  A. \harvardand\ {Andrews}, K.  \harvardyearleft 2009\harvardyearright ,
+  `{IVOA Registry Interfaces Version 1.0}', IVOA Recommendation 04 November
+  2009,  arXiv:1110.0513.
+\newline\url{http://adsabs.harvard.edu/abs/2009ivoa.spec.1104B}
 
-<dt><a name="std:REGTAP">[std:REGTAP] Markus Demleitner, Paul Harrison, Marco
-  Molinaro, Gretchen Greene, Theresa Dower, and Menelaos Perdikeas, Markus
-  Demleitner, editor.</a></dt> <dd>
-  <a href="http://www.ivoa.net/documents/RegTAP/" >IVOA registry relational
-  schema</a>.
-  IVOA Working Draft, 2013.
-</dd>
+\harvarditem[{Demleitner} \harvardand\ {Harrison} et~al.]{{Demleitner},
+  {Harrison}, {Molinaro}, {Greene}, {Dower} \harvardand\
+  {Perdikeas}}{2014}{2014ivoa.spec.1208D}
+{Demleitner}, M., {Harrison}, P., {Molinaro}, M., {Greene}, G., {Dower}, T.
+  \harvardand\ {Perdikeas}, M.  \harvardyearleft 2014\harvardyearright , `{IVOA
+  Registry Relational Schema Version 1.0}', IVOA Recommendation 08 December
+  2014,  arXiv:1510.02275.
+\newline\url{http://adsabs.harvard.edu/abs/2014ivoa.spec.1208D}
 
-<dt><a name="std:STDREGEXT">[std:STDREGEXT] Paul Harrison, Douglas Burke, Ray
-  Plante, Guy Rixon, and Dave Morris.</a></dt> <dd>
-  <a
-  href="http://www.ivoa.net/Documents/StandardsRegExt/20120508/REC-StandardsRegExt-1.0-20120508.html"
-  >StandardsRegExt: a VOResource schema extension for describing IVOA
-  standards, version 1.0</a>.
-  IVOA Recommendation, May 2012.
-</dd>
+\harvarditem[{Harrison} \harvardand\ {Burke} et~al.]{{Harrison}, {Burke},
+  {Plante}, {Rixon}, {Morris} \harvardand\ {IVOA Registry Working
+  Group}}{2012}{2012ivoa.spec.0508H}
+{Harrison}, P., {Burke}, D., {Plante}, R., {Rixon}, G., {Morris}, D.
+  \harvardand\ {IVOA Registry Working Group}  \harvardyearleft
+  2012\harvardyearright , `{StandardsRegExt: a VOResource Schema Extension for
+  Describing IVOA Standards Version 1.0}', IVOA Recommendation 08 May 2012,
+  arXiv:1402.4745.
+\newline\url{http://adsabs.harvard.edu/abs/2012ivoa.spec.0508H}
 
-<dt><a name="std:VOR">[std:VOR] Raymond Plante, Kevin Benson, Matthew Graham,
-  Gretchen Greene, Paul Harrison, Gerard Lemson, Tony Linde, Guy Rixon, and
-  Aurélien Stébé.</a></dt> <dd>
-  <a href="http://www.ivoa.net/Documents/REC/ReR/VOResource-20080222.html"
-  >VOResource: an XML encoding schema for resource metadata version
-  1.03</a>.
-  IVOA Recommendation, February 2008.
-</dd>
+\harvarditem[{Plante} \harvardand\ {Benson} et~al.]{{Plante}, {Benson},
+  {Graham}, {Greene}, {Harrison}, {Lemson}, {Linde}, {Rixon}, {St{\'e}b{\'e}}
+  \harvardand\ {IVOA Registry Working Group}}{2008}{2008ivoa.spec.0222P}
+{Plante}, R., {Benson}, K., {Graham}, M., {Greene}, G., {Harrison}, P.,
+  {Lemson}, G., {Linde}, T., {Rixon}, G., {St{\'e}b{\'e}}, A. \harvardand\
+  {IVOA Registry Working Group}  \harvardyearleft 2008\harvardyearright ,
+  `{VOResource: an XML Encoding Schema for Resource Metadata Version 1.03}',
+  IVOA Recommendation 22 February 2008,  arXiv:1110.0515.
+\newline\url{http://adsabs.harvard.edu/abs/2008ivoa.spec.0222P}
 
-</dl>
+\end{thebibliography}

Modified: trunk/projects/edu/edumatters/edumatters.tex
==============================================================================
--- trunk/projects/edu/edumatters/edumatters.tex	Fri Apr 21 11:17:13 2017	(r3955)
+++ trunk/projects/edu/edumatters/edumatters.tex	Fri Apr 21 15:31:18 2017	(r3956)
@@ -1,71 +1,29 @@
-<?xml version="1.0"?>
-<!-- $Id:$ 
-Note that this file should be xhtml with div to mark sections - see README for more information
-Paul Harrison -->
-<!DOCTYPE html
-  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "ivoadoc/xmlcatalog/xhtml1-transitional.dtd">
-<html xmlns="http://www.w3.org/1999/xhtml">
-<head>
-<title>Educational Resources in the Virtual Observatory</title>
-<meta http-equiv="content-type" content="text/html; charset=utf-8" />
-<meta name="Title" content="Educational Resources in the Virtual Observatory" />
-<meta name="author" content="Marco Molinaro" />
-<meta name="maintainedBy" content="Marco Molinaro" />
-<link href="http://www.ivoa.net/misc/ivoa_a.css" rel="stylesheet" type="text/css" />
-<link href="./ivoadoc/XMLPrint.css" rel="stylesheet" type="text/css" />
-<link href="./ivoadoc/ivoa-extras.css" rel="stylesheet" type="text/css" />
-
-<style type="text/css" xml:space="preserve">
-table.plain {
-  border-style: none;
-}
-td.even {
-  padding-top: 2px;
-  padding-bottom: 2px;
-  background: #EEEEFF;
-}
-
-.edit {
-	background-color: red;
-}
-</style>
-
-</head>
-<body>
-<div class="head">
-  <div id="titlehead" style="position:relative;height:170px;width: 500px">
-    <div id="logo" style="position:absolute;width:300px;height:169px;left: 50px;top: 0px;">
-    <img src="http://www.ivoa.net/pub/images/IVOA_wb_300.jpg" alt="IVOA logo"/></div>
-    <div id="logo-title"
-         style="position: absolute; width: 200px; height: 115px; left: 320px; top: 5px; font-size: 14pt; color: #005A9C; font-style: italic;">
-      <p style='position: absolute; left: 0px; top: 0px;'><span style='font-weight: bold;'>I</span> nternational</p>
-      <p style='position: absolute; left: 15pt; top: 25pt;'><span style='font-weight: bold;'>V</span> irtual</p>
-      <p style='position: absolute; left: 15pt; top: 50pt;'><span style='font-weight: bold;'>O</span> bservatory</p>
-      <p style='position: absolute; left: 0px; top: 75pt;'><span style='font-weight: bold;'>A</span> lliance</p>
-    </div>
-  </div>
-<h1>Educational Resources in the Virtual Observatory<br/>
-  Version <span class="docversion">0.1</span></h1>
-<h2 class="subtitle">Filled in automatically</h2>
-<dl>
-  <dt>Working Group</dt>
-  <dd><a href="http://wiki.ivoa.net/twiki/bin/view/IVOA/WebHome">Edu IG</a></dd>
-  <dt><b>This version:</b></dt>
-  <dd><a href="" class="currentlink">filled in automatically</a></dd>
-  <dt><b>Latest version:</b></dt>
-  <dd> not issued outside
-    EDU-IG</dd>
-  <dt><b>Previous version(s):</b></dt>
-  <dd> None</dd>
-    <dt><b>Author(s):</b></dt>
-  <dd>Marco Molinaro<br/>
-  Markus Demleitner<br/>
-  Massimo Ramella<br/>
-  Giulia Iafrate</dd>
-</dl>
+\documentclass{ivoa}
+\input tthdefs
+
+\usepackage{todonotes}
+\usepackage{listings}
+\lstloadlanguages{XML,sh}
+\lstset{flexiblecolumns=true,tagstyle=\ttfamily, showstringspaces=False}
+
+\ivoagroup{Edu IG}
+
+\author{Molinaro, M.}
+\author{Demleitner, M.}
+\author{Ramella, M.}
+\author{Iafrate, G.}
+
+\editor{Molinaro, M.}
+
+\previousversion{First published version}
+
+
+\title{Educational Resources in the Virtual Observatory}
+
+\begin{document}
+
+\begin{abstract}
 
-<h2>Abstract</h2>
-<p>
 The goal of this IVOA Note is to introduce and explain practices followed
 and requirements found while creating and 
 deploying astrophysical resources 
@@ -73,31 +31,14 @@
 Issues, proposed solutions and desirables are here reported to be
 possibly taken into account in future modifications of relevant
 standards.
-</p>
 
-<p>In detail, we discuss: the curation of educational resources inside or
-along with standard registries; use cases and techniques for registering
-and locating documents, tutorials and similar within the registries;
-dealing with multiple languages.</p>
-
-<h2> Status of This Document</h2>
-<p id="statusdecl">(updated automatically)</p>
-<p>This is an IVOA Note generated by discussion between Education IG and Registry WG members mainly.</p>
-<p> <em>A list of </em><span style="background: transparent"><a  href="http://www.ivoa.net/Documents/"><i>current
-  IVOA Recommendations and other technical documents</i></a></span><em > can be found at http://www.ivoa.net/Documents/.</em></p>
-<h2 class="prologue-heading-western">Acknowledgements</h2>
-<p>blah</p>
-</div>
-<h2>Contents</h2>
-<div>
-<?toc ?>
-</div>
-
-<div class="body">
-
-<div class="section">
-<h1><a id="Introduction"></a>Introduction</h1>
-<p>
+
+
+\end{abstract}
+
+
+\section{Introduction}
+
 Advances in technology and communications are creating new and exciting 
 opportunities for teachers to bring astronomy into their 
 classrooms.  As the VO makes science-grade data publicly available and
@@ -108,524 +49,584 @@
 tutorials, use cases explaining how to perform basic astrophysical research 
 using VO tools and resources, and similar exist in various formats and
 have been translated in different languages.
-</p>
 
-<p>New opportunities also come on the observational side. 
+
+New opportunities also come on the observational side. 
 There is a growing availability of remotely controlled 
 telescopes dedicated to education in many countries world-wide, from the 
-Bradford Robotic Telescope on MountTeide, Tenerife (http://www.telescope.org) 
-to the radio telescopes of the Radio Physics Lab, IUCAA, Pune 
-(http://www.ncra.tifr.res.in/rpl). In some cases, educational telescopes are 
+Bradford Robotic Telescope\footnote{\url{http://www.telescope.org}} on MountTeide, Tenerife 
+to the radio telescopes of the Radio Physics
+Lab\footnote{\url{http://www.ncra.tifr.res.in/rpl}}, IUCAA, Pune 
+. In some cases, educational telescopes are 
 linked into a network with the aim of guaranteeing the best observing conditions, 
 including deep sky observations during regular daytime school hours, and 
 the best instrument for the particular program of interest. Examples
-of these networks are iTelescope.net (http://www.itelescope.net) and EuHOU-MW 
-(http://euhou.obspm.fr/public).
-</p>
-<p>
+of these networks are
+iTelescope.net\footnote{\url{http://www.itelescope.net}} and
+EuHOU-MW\footnote{\url{http://euhou.obspm.fr/public}}.
+
+
+
 As telescopes enter classrooms more frequently, interest is growing for a 
 public archive of observations and hence for publishing and curation tools, 
 together with the basic applications needed to retrieve, display
 and analyze data. The VO already includes most of the technology needed 
 to satisfy the requests of educational observatories. In fact, since several 
 years, VO, and in particular the European project EuroVO, is devoting part 
-of its resources to education (http://wwwas.oats.inaf.it/aidawp5). It is 
+of its resources to
+education\footnote{\url{http://wwwas.oats.inaf.it/aidawp5}}. It is 
 therefore a natural decision for VO to tackle the problem of publishing 
 educational data in VO archives.
-</p>
 
-<p>Resource registration for both educational data services and documents 
+
+Resource registration for both educational data services and documents 
 is the most appropriate approach toward making educational resources 
 available within the VO.  While
 technically this may seem trivial, keeping too technical
 research services out of the the resources devoted to education will
 require some effort, that will also be needed in order to avoid contaminating 
-VO professional research with obviously inadequate material.</p>
+VO professional research with obviously inadequate material.
 
-<p>In the next section we discuss the idea of educational resources curation, then 
-<a href="#regext">Registering Texts</a> we work out the use cases and needs for
+In the next section we discuss the idea of educational resources curation, then 
+we work out the use cases and needs for
 registration of tutorials and documents. Finally, we discuss the idea of introducing language
 internationalization in the resources.
-</p>
-</div> <!-- section Introduction -->
 
-<div class="section">
-<h2><a id="curreg">A Curated Registry for Education</a></h2>
-<p>
+
+
+\section{A Curated Registry for Education}
+
+\label{sect:curreg}
+
+
 From a technical point of view the registration of educational services
 does not require extensions
-to the existing for VOResource standard (<cite>std:VOR</cite>).
+to the existing for VOResource standard \citep{2008ivoa.spec.0222P}.
 The only real need for investigating changes to what already exists is due to a
 use case's distinction between resources to be used in teaching and dissemination
 versus all the research driven resources that exist in the VO.
-</p>
-<p>
+
+
+
 For simplicity here we will distinguish these two groups of resources as
-<i>educational</i> and <i>professional</i> but without any intent of putting them
+\emph{educational}
+ and 
+\emph{professional}
+ but without any intent of putting them
 on different levels of importance.
-</p>
-<div class="section">
-  <h3><a id="eduvspro">Educational vs. Professional Resources</a></h3>
-  <p>
-  On the one side, teachers and educators may find it difficult to filter out 
-  from all VO resources those that are suitable for their tutorials and
-  examples. On the other side, educational resources should not be retrieved 
-  by a standard professional query.
-  Given that it is not a matter of data quality, but only a distinction upon 
-  the resources' scope, nevertheless this duality leads to an issue about the
-  proper way to tag resources for educational usage.
-  </p>
-  <p>
-  In the next subsection we propose a possible tagging solution, based upon 
-  the existing <i>ContentLevel</i> element of VOResource, but requiring a small change
-  to it. The subsequent subsection describes the idea of a
-  curated registry for educational resources and the reasons for it to exist.
-  </p>
-</div> <!-- subsection eduvspro -->
-
-<div class="section">
-  <h3><a id="contentlvl">ContentLevel granularity issue</a></h3>
-  <p>
-  <cite>std:VOR</cite> already has the <i>ContentLevel</i> element
-  allowing data publishers to optionally identify their resources as being 
-  suitable for one or more of the following audiences:</p>
-  <ul>
-	<li>General</li>
-	<li>Elementary Education</li>
-	<li>Middle School Education</li>
-	<li>Secondary Education</li>
-	<li>Community College</li>
-	<li>University</li>
-	<li>Research</li>
-	<li>Amateur</li>
-	<li>Informal Education</li>
-  </ul>
-  <p>This element turns out to be misused by many publishers, presumably because
-  it is not really clear what the subtle differences between the available
-  possibilities are; also, to require a fairly substantial enumeration to
-  convey "for school use" seems, in retrospect, not likely to promote
-  widespread adoption. We hence propose to simplify the content model
-  to:</p>
-  <ul>
-	<li>General</li>
-	<li>Research</li>
-	<li>Amateur</li>
-  </ul>
-  <p>We expect this to reach two goals:
-  <ul>
-    <li>to make publishers to better describe (on the average)
-    their resources</li>
-    <li>to providing a tagging solution that suits a first filtering 
-    on the resources at client level</li>
-  </ul>
-  Of course, the chance to 
-  add an <i>Educational</i> value option to this shrinked list, or even
-  substitute it to the <i>General</i> one, would be a valuable change.
-  </p>
-  <p>
-  This change in the already existing standard will require only 
-  a small effort to update already registered resources because nearly 97% of 
-  them currently have ContentLevel set to <i>research</i>, about 2% of them have
-  no ContentLevel defined at all and only the remaining have a different value
-  (or set of values) set for this element (Appendix A details better these
-  figures).
-  </p>
-  <p>Until the change in VOResource can be performed, it
-  can work as a "best practice" recommendation, possibly even at a
-  registry level, where registries can map existing <i>ContentLevel</i>s values 
-  of <i>University</i> to <i>Research</i> and
-  everything else except <i>Amateur</i> to <i>General</i>.</p>
-</div> <!-- subsection contentlvl -->
-
-<div class="section">
-  <h3><a id="edureg">Curating the Edu Registry</a></h3>
-  <p>
-  Even in the case of the simplified <i>ContentLevel</i> tagging system
-  a curated registry for educational VO resources will be useful for
-  educators in order to let their students work with a registry without having to
-  worry about confusing material or overwhelming data sizes. A good example
-  for this is the educational version of the Aladin sky atlas that has a
-  built in, curated set of resources suitable for educational level 
-  tutorials.
-  </p>
-  <p>
-  Curation will require some effort in managing and keeping up to date
-  such a registry but, most important, it is subjected to  some restrictions coming from
-  the IVOA resource registry architecture. 
-  </p>
-  <p>
-  If such a registry were a standard publishing registry
-  (<cite>std:RI1</cite>),
-  its resources would be harvested by the full registries: this means 
-  that any dedicated educational resource would end up in the full VO 
-  set of resources.  For reasons mentioned above, this is not
-  desirable.</p>
-  <p>
-  If it were to be a full registry, it will harvest itself all the existing
-  resources, and not all of them will fit, or be suitable for, the educational
-  scope the registry has to be preserved for.
-  </p>
-  <p>
-  We need a resource (the curated, in <cite>std:RI1</cite>
-  parlance, local, registry) capable of :
-  <ul>
-	<li><i>selectively</i> harvesting the existing VO resources 
-	(e.g. from a full registry);</li>
-	<li>register its own educational resources without being directly
+
+
+
+\subsection{Educational vs. Professional Resources}
+
+\label{sect:eduvspro}
+
+
+On the one side, teachers and educators may find it difficult to filter out 
+from all VO resources those that are suitable for their tutorials and
+examples. On the other side, educational resources should not be retrieved 
+by a standard professional query.
+Given that it is not a matter of data quality, but only a distinction upon 
+the resources' scope, nevertheless this duality leads to an issue about the
+proper way to tag resources for educational usage.
+  
+
+
+In the next subsection we propose a possible tagging solution, based upon 
+the existing 
+\vorent{ContentLevel}
+element of VOResource, but requiring a small change
+to it. The subsequent subsection describes the idea of a
+curated registry for educational resources and the reasons for it to exist.
+  
+
+
+\subsection{ContentLevel granularity issue}
+
+\label{sect:contentlvl}
+
+\citep{2008ivoa.spec.0222P} already has the 
+\vorent{ContentLevel}
+element
+allowing data publishers to optionally identify their resources as being 
+suitable for one or more of the following audiences:
+
+
+\begin{itemize}
+
+\item General{}
+
+\item Elementary Education{}
+
+\item Middle School Education{}
+
+\item Secondary Education{}
+
+\item Community College{}
+
+\item University{}
+
+\item Research{}
+
+\item Amateur{}
+
+\item Informal Education{}
+
+\end{itemize}
+
+This element turns out to be misused by many publishers, presumably because
+it is not really clear what the subtle differences between the available
+possibilities are; also, to require a fairly substantial enumeration to
+convey ``for school use'' seems, in retrospect, not likely to promote
+widespread adoption. We hence propose to simplify the content model
+to:
+
+
+\begin{itemize}
+
+\item General{}
+
+\item Research{}
+
+\item Amateur{}
+
+\end{itemize}
+
+We expect this to reach two goals:
+  
+\begin{itemize}
+
+\item to make publishers to better describe (on the average)
+    their resources{}
+
+\item to providing a tagging solution that suits a first filtering 
+    on the resources at client level{}
+
+\end{itemize}
+
+Of course, the chance to 
+add an 
+\emph{Educational}
+value option to this shrinked list, or even
+substitute it to the 
+\emph{General}
+one, would be a valuable change.
+  
+
+
+This change in the already existing standard will require only 
+a small effort to update already registered resources because nearly 97\% of 
+them currently have \vorent{ContentLevel} set to 
+\emph{research}, about 2\% of them have
+no \vorent{ContentLevel} defined at all and only the remaining have a different value
+(or set of values) set for this element (Appendix \ref{app:clcurrval} details better these
+figures).
+  
+
+Until the change in VOResource can be performed, it
+can work as a ``best practice'' recommendation, possibly even at a
+registry level, where registries can map existing 
+\vorent{ContentLevel} values 
+  of 
+\emph{University}
+ to 
+\emph{Research}
+ and
+  everything else except 
+\emph{Amateur}
+ to 
+\emph{General}.
+.
+
+
+\subsection{Curating the Edu Registry}
+
+\label{sect:edureg}
+
+
+Even in the case of the simplified 
+\vorent{ContentLevel}
+tagging system
+a curated registry for educational VO resources will be useful for
+educators in order to let their students work with a registry without having to
+worry about confusing material or overwhelming data sizes. A good example
+for this is the educational version of the Aladin sky atlas that has a
+built in, curated set of resources suitable for educational level 
+tutorials.
+  
+
+
+Curation will require some effort in managing and keeping up to date
+such a registry but, most important, it is subjected to  some restrictions coming from
+the IVOA resource registry architecture. 
+  
+
+
+If such a registry were a standard publishing registry
+(\citep{2009ivoa.spec.1104B}),
+its resources would be harvested by the full registries: this means 
+that any dedicated educational resource would end up in the full VO 
+set of resources.  For reasons mentioned above, this is not
+desirable.
+
+
+If it were to be a full registry, it will harvest itself all the existing
+resources, and not all of them will fit, or be suitable for, the educational
+scope the registry has to be preserved for.
+  
+
+
+We need a resource (the curated, in \citep{2009ivoa.spec.1104B}
+parlance, local, registry) capable of:
+  
+\begin{itemize}
+
+\item 
+\emph{selectively}
+ harvesting the existing VO resources 
+	(e.g. from a full registry);{}
+
+\item register its own educational resources without being directly
 	harvested by full registries (e.g. this could be done using a
 	sibling publishing registry dedicated to host those educational
-	resources that are to be harvested by the standard full registries.</li>
-  </ul>
-  This solution, also presented in Fig. 1, will not touch the existing architecture
-  while giving flexibility for the emerging educational resources to 
-  be curated.
-  </p>
-  <div class="figure" style="text-align: center;">
-    <img src="curation.png"></img>
-    <p class="figurecaption"><strong>Figure 1:</strong> Graphic illustration
+	resources that are to be harvested by the standard full registries.{}
+
+\end{itemize}
+
+This solution, also presented in Fig. 1, will not touch the existing architecture
+while giving flexibility for the emerging educational resources to 
+be curated.
+  
+
+
+\begin{figure}
+
+\includegraphics[width=0.9\textwidth]{curation.png}
+\caption{Graphic illustration
     of the connecting interfaces between full registries and the educational
-    curated one. The <i>auxiliary</i> publishing is the only automatic token
-    from the edu part.</p>  
-  </div><!-- figure -->
-</div> <!-- subsection edureg -->
-
-</div> <!-- section curreg -->
-
-<div class="section">
-<h2><a id="regext">Registering Texts</a></h2>
-<p>Educational material is not only about services – text-like material
+    curated one. The 
+\emph{auxiliary}
+ publishing is the only automatic token
+    from the edu part.}
+\label{fig:curation}
+\end{figure}
+
+\section{Registering Texts}
+
+\label{sect:regext}
+
+Educational material is not only about services – text-like material
 like tutorials, worked-out use cases, or textbook-like material are at
 least as important.  Within the VO community, there is a large body of
 educational material for a wide variety of audiences ranging from pre-school to
 researchers:
-<ul>
-<li>EURO-VO AIDA WP5 - http://wwwas.oats.inaf.it/aidawp5/eng_download.html</li>
-<li>EURO-VO Scientific Tutorials - http://www.euro-vo.org/?q=science/scientific-tutorials</li>
-<li>VAO for Education - http://virtualobservatory.org/education/</li>
-</ul>
-</p>
 
-<p>To date, such material has been collected informally by the various
+\begin{itemize}
+
+\item EURO-VO AIDA WP5 - \url{http://wwwas.oats.inaf.it/aidawp5/eng_download.html}
+
+\item EURO-VO Scientific Tutorials - \url{http://www.euro-vo.org/?q=science/scientific-tutorials}
+
+\item VAO for Education - \url{http://virtualobservatory.org/education/}
+
+\end{itemize}
+
+
+To date, such material has been collected informally by the various
 projects on plain web pages.  It is, in consequence, hard to find, with
 knowledge of it often passed on antecdotically. In order to improve upon 
 this situation, we
-propose to keep record of educational material in the registry.</p>
+propose to keep record of educational material in the registry.
 
-<p>The VO already has a registry extension for standards, which of
-course are also text-like (<cite>std:STDREGEXT</cite>).  This extension,
+The VO already has a registry extension for standards, which of
+course are also text-like (\citep{2012ivoa.spec.0508H}).  This extension,
 however, focuses on metadata important for standards – e.g.,
 vocabularies and status – that is not pertinent for educational
 material.  Conversely, it is not concerned with document language (which
 can safely be assumed to be English for standards), and it disregards
 the issue of locating formatted and source version, which for educational
 material is important.  We therefore propose a simple registry extension
-covering text-like material, dubbed DocRegExt.</p>
+covering text-like material, dubbed DocRegExt.
+
+
+\subsection{Use Cases}
+
+\label{sect:regext-usecases}
 
+The design of DocRegExt has been guided by the desire to fulfill the
+following use cases:
 
-<div class="section">
-<h3><a id="regext-usecases">Use Cases</a></h3>
 
-<p>The design of DocRegExt has been guided by the desire to fulfill the
-following use cases:</p>
+\begin{itemize}
 
-<ul>
-<li>Is there a tutorial covering discovering intermediate mass black
-holes? (Standard VOResource is sufficient)</li>
-<li>Is there a tutorial covering working with X-Ray data? (Standard
-VOResource is sufficient)</li>
-<li>Is there a tutorial dealing with Planets suitable for school use?
-(Standard VOResource is sufficient)</li>
-<li>Is there a tutorial dealing with Planets suitable for school use in
-Italian? (That requires the declaration of the document language)</li>
-<li>What are the subjects of maintained (in the sense of: probably
+\item Is there a tutorial covering discovering intermediate mass black
+holes? (Standard VOResource is sufficient){}
+
+\item Is there a tutorial covering working with X-Ray data? (Standard
+VOResource is sufficient){}
+
+\item Is there a tutorial dealing with Planets suitable for school use?
+(Standard VOResource is sufficient){}
+
+\item Is there a tutorial dealing with Planets suitable for school use in
+Italian? (That requires the declaration of the document language){}
+
+\item What are the subjects of maintained (in the sense of: probably
 working in the VO as found by the students) tutorials?
 (The active flag of standard VOResource is
 unsuitable here since even outdated resources will still be accessible;
-therefore, we introduce the maintained flag)</li>
-<li>Are there tutorials using redshifts? (This is solved by allowing
-table metadata in DocRegExt)</li>
-<li>Where can I find an editable version of tutorial ivo://auth/tut1?
+therefore, we introduce the maintained flag){}
+
+\item Are there tutorials using redshifts? (This is solved by allowing
+table metadata in DocRegExt){}
+
+\item Where can I find an editable version of tutorial ivo://auth/tut1?
 (This is solved by allowing multiple access URLs with different content
-types, which should be sufficient to allow answering the question)</li>
-<li>Are there translations of tutorial ivo://auth/tut2? (This is covered
+types, which should be sufficient to allow answering the question){}
+
+\item Are there translations of tutorial ivo://auth/tut2? (This is covered
 by the recommendations on declaring relationships between text-like
-resources)</li>
-<li>Is there material using service ivo://auth/svc1? (Again, declaring
-relationships covers this use case)</li>
-<li>Is there material about something visible tonight? (In principle,
+resources){}
+
+\item Is there material using service ivo://auth/svc1? (Again, declaring
+relationships covers this use case){}
+
+\item Is there material about something visible tonight? (In principle,
 allowing the coverage element withing DocRegExt resources would allow
 answering the question; in reality, few registries expose this
-information in useable form)</li>
-<li>I found this VO tutorial somewhere on the net ("on a mirror").  Is it
+information in useable form){}
+
+\item I found this VO tutorial somewhere on the net ("on a mirror").  Is it
 the latest version?  If not, where can I find an update? (Unless the
-title of the text changed, standard VOResource should suffice)</li>
-</ul>
+title of the text changed, standard VOResource should suffice){}
 
-<p>On the use cases of locating editable forms of such texts – which
+\end{itemize}
+
+On the use cases of locating editable forms of such texts – which
 has been found to be necessary fairly regularly – we note in passing
 that representing source-product relationships is in principle in the
 domain of provenance and thus not in scope for the registry. However, in
 the case discussed here the relation is so simple and its representation
-so useful that we propose to include it in a DocRegExt.</p>
-
-</div> <!-- section regext-usecases -->
+so useful that we propose to include it in a DocRegExt.
 
 
-<div class="section">
-<h3><a id="regext-ext">A Document Registry Extension</a></h3>
+\subsection{A Document Registry Extension}
 
-<p>To satisfy our use cases, we have designed a registry extension with
-a single definition, extending the basic <code>vr:Resource</code>
-element with three concepts to make the <code>doc:Document</code>
-resource type.</p>
+\label{sect:regext-ext}
 
-<?schemadef href="../DocRegExt-v1.0.xsd" defn="Document"?>
+To satisfy our use cases, we have designed a registry extension with
+a single definition, extending the basic \texttt{vr:Resource}
+element with three concepts to make the \texttt{doc:Document}
+resource type.
 
-<p>The full schema is given in Appendix <span
-class="xref">app:schema</span></p>
+The full schema is given in Appendix \ref{app:schema}
 
-<p>We considered  having language as an attribute of accessURL to allow
+We considered  having language as an attribute of \xmlel{accessURL} to allow
 language-specific document discovery.  We decided against this mainly
 for reasons of maintainability; the same reason is behind the
-recommendation to have both access and source URLs as landing pages.</p>
+recommendation to have both access and source URLs as landing pages.
 
-<p>Since the access URL is supposed to point to a "landing page" anyway,
+Since the access URL is supposed to point to a ``landing page'' anyway,
 it is tempting to just unify it with the standard VOResource reference
-URL. As a "human-readable document describing this resource"
-<cite>std:VOR</cite> quite conceivably could very well work as a landing
+URL. As a ``human-readable document describing this resource''
+\citep{2008ivoa.spec.0222P} quite conceivably could very well work as a landing
 page.  For many documents having identical access and reference, urls
 will certainly work fine.  However, we want to cover the cases in
 which different projects offer different translations or even versions
 of a document at different sites, which is not possible with just a
 single reference URL.  A similar reasoning is behind including source
 URIs, except that in this case we wanted to allow URIs with non-HTTP
-schemes like svn or git.</p>
+schemes like svn or git.
 
-<p>Document-typed resource records should define relations to other
-general resources (e.g. applications, services, ...) 
+Document-typed resource records should define relations to other
+general resources (e.g. applications, services, \dots) 
 they use; since an extension of the vocabulary allowed for relationship types
 in VOResource will probably not be possible in the near future,
 we suggest the relationshipType for these relations should be
-<code>related-to</code>.  If a relation <code>uses</code> becomes available
-in the future, it should be used in this situation.</p>
+\emph{related-to}.  If a relation \emph{uses} becomes available
+in the future, it should be used in this situation.
+
+\todo{do we want i18n-ed titles?}
+
+In the relational registry \citep{2014ivoa.spec.1208D}, DocRegExt is
+entirely represented in the \verb|res_details|, with details
+
 
-<p class="edit">TBD: do we want i18n-ed titles?</p>
+\begin{itemize}
 
-<p>In the relational registry <cite>std:REGTAP</cite>, DocRegExt is
-entirely represented in the <code>res_details</code>, with details</p>
-<ul>
-<li><code>/language</code> -- A language the document is available in.</li>
-<li><code>/accessURL</code> -- A URL allowing access to one or more
-renderings of the document.</li>
-<li><code>/sourceURI</code> -- A URL allowing access to an editable version of the document.</li>
-</ul>
+\item \texttt{/language} -- A language the document is available in.{}
 
-<p>Here is a (slightly abridged) example record:</p>
+\item \texttt{/accessURL} -- A URL allowing access to one or more
+renderings of the document.{}
 
-<?incxml href="../m1distance-example.xml"?>
+\item \texttt{/sourceURI} -- A URL allowing access to an editable version of the document.{}
 
-<p class="edit">TBD: should we use ISO-3166-1 two letter 
-country codes or ISO-639-2 two letter language codes?<br/>
+\end{itemize}
+Here is a (slightly abridged) example record:
+
+TBD: should we use ISO-3166-1 two letter 
+country codes or ISO-639-2 two letter language codes?\\
 MMo: I vote for 639-2. This shouldn't require changes now, 
 but it's better to clarify it in advance IMHO.
-</p>
 
-</div> <!-- subsection regext-ext -->
 
-<div class="section">
-<h3><a id="svn-repo">A versioned repository for tutorials</a></h3>
-<p>Registering text document as VO resources allows search for tutorials and other 
+\subsection{A versioned repository for tutorials}
+
+\label{sect:svn-repo}
+
+Registering text document as VO resources allows search for tutorials and other 
 materials through standard registry interfaces, but keeping 
 tutorials up to date, in their master form and also in their translated 
-versions, is another important issue to allow proficient use.<br/>
+versions, is another important issue to allow proficient use.
 A versioned repository (using subversion as the version control system) 
-has been set up at GAVO data center (
-http://svn.ari.uni-heidelberg.de/svn/edu/) and collects part of the
+has been set up at GAVO data
+center\footnote{\url{http://svn.ari.uni-heidelberg.de/svn/edu/}} 
+and collects part of the
 already existing VO tutorials with the goal of preserve them and let users 
-update and translate them in favour of the whole community.<br/>
+update and translate them in favour of the whole community.
 The repository has an internal structure that takes care for:
-<ul>
-  <li>different national languages (master language set to english)</li>
-  <li>translation vs. master language updates</li>
-  <li>licensing, in order to clarify how and whether a tutorial can be changed or re-used</li>
-  <li>additional materials used by tutorials</li>
-  <li>access roles to allow everyone to access tutorials but prevent untrusted updates or additions to it</li>
-</ul>
+
+\begin{itemize}
+
+\item different national languages (master language set to english){}
+
+\item translation vs. master language updates{}
+
+\item licensing, in order to clarify how and whether a tutorial can be changed or re-used{}
+
+\item additional materials used by tutorials{}
+
+\item access roles to allow everyone to access tutorials but prevent untrusted updates or additions to it{}
+
+\end{itemize}
+
 The repository is intended to work as a space for cooperative 
 VO tutorials development.
 
-</p>
-</div> <!-- subsection svn-repo -->
 
-</div> <!-- section regext -->
 
-<div class="section">
-<h2><a id="lang">Internationalization of VO Resources</a></h2>
-<p>
+\section{Internationalization of VO Resources}
+
+\label{sect:lang}
+
+
 The EURO-VO AIDA project WP5 produced multilingual tutorials, 
 meeting the needs for high schools and lower level 
 educational degrees in countries where English is not the native language. 
 Clearly, it would be an added value to be able to register an educational or
 document resource not only in english (as it is done currently with 
 standard VO resources) but also in other national languages.
-</p>
-<p>
+
+
+
 Here we propose discuss whether this means:
-<ul>
-  <li>changing VOResource to allow different languages in resource 
-  descriptions;</li>
-  <li>enable internazionalization in VO resources within existing
-  resources: one resource described in multiple languages</li>
-  <li>other...</li>
-</ul>
-</p>
-</div> <!-- section lang -->
-
-</div> <!-- body -->
-
-<div class="appendices">
-<div class="section">
-<h2><a id="clcurrval">ContentLevel values summary</a></h2>
-<p>
+
+\begin{itemize}
+
+\item changing VOResource to allow different languages in resource 
+  descriptions;{}
+
+\item enable internazionalization in VO resources within existing
+  resources: one resource described in multiple languages{}
+
+\item other\dots
+
+\end{itemize}
+
+
+\appendix
+
+\section{ContentLevel values summary}
+
+\label{app:clcurrval}
+
+
 This appendix reports some statistics on the usage of the ContentLevel 
-element in <cite>std:VOR</cite> as of 2014-01-30, taken from the
+element in \citep{2008ivoa.spec.0222P} as of 2014-01-30, taken from the
 GAVO RegTAP endpoint http://dc.g-vo.org/tap .
 There are 14392 useful resources (excluding authorities, standards and
 similar) that expose 26 different values as their ContentLevel.
-In the following table these values are reported in order of count.
-</p>
-<p>
-<table class="plain">
-<thead>
-<tr>
- <th>count</th> <th>content_level string</th>
-</tr>
-</thead>
-<tbody>
-<tr>
- <td>13937</td> <td>research</td>
-</tr>
-<tr>
- <td>290</td> <td> </td>
-</tr>
-<tr>
- <td>41</td> <td>university#research</td>
-</tr>
-<tr>
- <td>40</td> <td>general#university#research#amateur</td>
-</tr>
-<tr>
- <td>24</td> <td>university</td>
-</tr>
-<tr>
- <td>14</td> <td>university#research#amateur</td>
-</tr>
-<tr>
- <td>7</td> <td>general</td>
-</tr>
-<tr>
- <td>5</td> <td>research#general</td>
-</tr>
-<tr>
- <td>4</td> <td>general#research</td>
-</tr>
-<tr>
- <td>3</td> <td>secondary education#community college#university#research#amateur</td>
-</tr>
-<tr>
- <td>3</td> <td>research#university#community college</td>
-</tr>
-<tr>
- <td>3</td> <td>elementary education#middle school education#secondary education</td>
-</tr>
-<tr>
- <td>3</td> <td>general#university#research</td>
-</tr>
-<tr>
- <td>2</td> <td>research#university</td>
-</tr>
-<tr>
- <td>2</td> <td>research#amateur#university#community college</td>
-</tr>
-<tr>
- <td>2</td> <td>general#informal education</td>
-</tr>
-<tr>
- <td>2</td> <td>general#elementary education#middle school education#secondary education#community college#university#research#amateur#informal education</td>
-</tr>
-<tr>
- <td>1</td> <td>university#community college#research</td>
-</tr>
-<tr>
- <td>1</td> <td>general#university#research#amateur#informal education</td>
-</tr>
-<tr>
- <td>1</td> <td>elementary education#middle school education#secondary education#community college#university#research</td>
-</tr>
-<tr>
- <td>1</td> <td>general#secondary education#university#research</td>
-</tr>
-<tr>
- <td>1</td> <td>university#research#general#informal education</td>
-</tr>
-<tr>
- <td>1</td> <td>research#university#amateur</td>
-</tr>
-<tr>
- <td>1</td> <td>elementary education#middle school education#secondary education#community college#university#research#amateur</td>
-</tr>
-<tr>
- <td>1</td> <td>elementary education#middle school education#secondary education#community college#university#research#amateur#informal education</td>
-</tr>
-<tr>
- <td>1</td> <td>university#research#amateur#informal education</td>
-</tr>
-<tr>
- <td>1</td> <td>general#university#research#informal education</td>
-</tr>
-</tbody>
-</table>
-</p>
-<p>
+In table \ref{tab:cldist} these values are reported in order of count.
+
+
+
+\begin{table}
+\begin{tabular}{lp{12cm}}
+\sptablerule
+\textbf{count}&
+\textbf{content\_level string}\\
+\sptablerule
+13937&research\\
+290&\\
+41&university research\\
+40&general university research amateur\\
+24&university\\
+14&university research amateur\\
+7&general\\
+5&research general\\
+4&general research\\
+3&secondary education community college university research amateur\\
+3&research university community college\\
+3&elementary education middle school education secondary education\\
+3&general university research\\
+2&research university\\
+2&research amateur university community college\\
+2&general informal education\\
+2&general elementary education middle school education secondary education community college university research amateur informal education\\
+1&university community college research\\
+1&general university research amateur informal education\\
+1&elementary education middle school education secondary education community college university research\\
+1&general secondary education university research\\
+1&university research general informal education\\
+1&research university amateur\\
+1&elementary education middle school education secondary education community college university research amateur\\
+1&elementary education middle school education secondary education community college university research amateur informal education\\
+1&university research amateur informal education\\
+1&general university research informal education\\
+\end{tabular}
+\caption{Empirical distribution of \vorent{ContentLevel}s declared by VO
+resources.}
+\label{tab:cldist}
+\end{table}
+
+
+
 This table can be easily updated from the same endpoint (or an analogue 
 one) using the following ADQL query:
-<pre>
+
+\begin{verbatim}
 SELECT 
   count(*) as cnt, content_level
 FROM 
   rr.resource
 WHERE
-  res_type != 'vstd:servicestandard' and 
-  res_type != 'vg:authority' and 
-  res_type != 'vstd:standard' and 
-  res_type != 'va:application' and
-  res_type != 'vr:organization'
+  res_type not in ('vstd:servicestandard',
+    'vg:authority',
+    'vstd:standard',
+    'va:application',
+    'vr:organization')
 GROUP BY content_level
 ORDER BY cnt DESC
-</pre>
-The table shows that only about 1% of the ContentLevel values use 
-something different and more complex than <i>research</i>, when 
-the element is not empty. Morever, of this 1% (165 resources), 
-61 include the <i>general</i> value (roughly 37% of them), 
-29 (17%) state that are devoted to some <i>education</i> level only,
-while 148 (90%) state that are also devoted to some <i>education</i> level (up to <i>university</i>).
-</p>
-</div> <!-- end clcurrval-->
-
-<div class="section">
-<h2><a id="app:schema">The proposed DocRegExt Schema</a></h2>
-<?incxml href="../DocRegExt-v1.0.xsd"?>
-
-</div> <!-- app:schema -->
-</div> <!-- end appendices -->
-
-<div class="section-nonum">
-<h2><a id="references"/><span class="secnum"/>References</h2>
-
-<?bibliography ivoadoc/refs?>
-
-</div> <!-- section references -->
-
-<hr/>
-</body>
-</html>
+\end{verbatim}
+
+The table shows that only about 1\% of the ContentLevel values use 
+something different and more complex than 
+\emph{research}, when 
+the element is not empty. Morever, of this 1\% (165 resources), 
+61 include the \emph{general} value (roughly 37\% of them), 
+29 (17\%) state that are devoted to some 
+\emph{education} level only,
+while 148 (90\%) state that are also devoted to some 
+\emph{education} level (up to 
+\emph{university}).
+
+
+\section{The proposed DocRegExt Schema}
+
+\label{app:schema}
+
+\lstinputlisting[language=XML]{DocRegExt-v1.0.xsd}
+
+\bibliography{ivoatex/ivoabib,ivoatex/docrepo}
+
+\end{document}


More information about the Volutecommits mailing list