Skip to content

Add description VO-DML tools #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
pahjbo wants to merge 2 commits into
base: 20-update-vo-dml-standard-document
Choose a base branch
from
Draft

Add description VO-DML tools #80

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
503c383
brief initial description VO-DML tools
pahjbo Jul 3, 2025
a7cc00b
note that VO-DML tools do define a consistent set of model serializat…
pahjbo Oct 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 18 additions & 3 deletions doc/std/VO-DML.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2771,6 +2771,12 @@ value must be an [ivoa:real.](#real)

# Procedure for defining data models in the IVOA

## VO-DML Tools

In addition to this standard that defines VO-DML there is some tooling ("VO-DML tools")
to assist with the definition and validation of models created in VO-DML. This tooling is maintained
in the IVOA GitHub project and is described in detail in its [on-line documentation](https://ivoa.github.io/vo-dml/). It is recommended that the VO-DML tools are used to aid in creating new data models.

## IVOA-standardized data models

A data model specified in VO-DML can be endorsed by the IVOA to become a
Expand All @@ -2789,7 +2795,7 @@ artifacts:

- The data model itself, written in VO-DML/XML, which MUST conform to
the VO-DML schema[^39] and the rules in the VO-DML Schematron
file[^40].
file[^40].

- A detailed documentation in HTML format containing human-readable
definitions for all elements of the data model, formatted in HTML
Expand Down Expand Up @@ -3313,7 +3319,11 @@ mappings aim to be as close to 1-1 as possible, providing so called
*faithful* representations of the model. Developing standards for
mappings to languages like these could greatly simplify a modeling
process, as one need only define the conceptual model itself and use
automated procedures to derive the serialization formats.
automated procedures to derive the serialization formats.
The VO-DML tooling does define one such set of self-consistent
concrete mappings. These mappings could be adopted as the definitive
mappings in a separate IVOA standard.


XSD

Expand Down Expand Up @@ -3678,6 +3688,10 @@ standard -->

## Change log {#change-log .unnumbered}

**Version 1.1 WD**

* Added references to VO-DML Tools.

**Version 20161222**

- Added this changelog
Expand Down Expand Up @@ -3845,7 +3859,8 @@ standard -->

[^39]: http://www.ivoa.net/xml/VODML/vo-dml-v1.xsd

[^40]: <http://www.ivoa.net/xml/VODML/vo-dml-v1.sch.xml>
[^40]: The schematron validation rules are explained more fully in the
[validation section of the VO-DML Tools guide](https://ivoa.github.io/vo-dml/modelling/Validation/)

[^41]: E.g. see
<http://en.wikibooks.org/wiki/Java_Persistence/Inheritance>
Expand Down