Difference: VOUnit11RFC (12 vs. 13)

VOUnit 1.1 Proposed Recommendation: Request for Comments

VOUnit proposes a recommended syntax for writing the string representation of unit labels.

Latest version of VOUnits can be found at:

• https://ivoa.net/documents/VOUnits/20230502/index.html

Reference Interoperable Implementations

• DaCHS 2.8. To try things out, you could run, with DaCHS installed, run python -c 'from gavo.base import unitconv;print(unitconv.computeConversionFactor("pc/yr", "m/s"))' or the like

• Unity library (canonical home page https://purl.org/nxg/dist/unity): Parsing library for the VOUnits syntax, as well as for the FITS, OGIP and CDS syntaxes. There are parser implementations in Java and C. As well, this project produces formal (yacc-style) grammars for the syntaxes it supports.

Implementations Validators

Both implementations serve as validators. In the DaCHS case, you could run python -c "from gavo import api;print(api.parseUnit('kg/(m.s**2)'))".

Comments from the IVOA Community during RFC/TCG review period: 2023-07-01 – 2023-08-15

The comments from the TCG members during the RFC/TCG review should be included in the next section.

In order to add a comment to the document, please edit this page and add your comment to the list below in the format used for the example (include your Wiki Name so that authors can contact you for further information). When the author(s) of the document have considered the comment, they will provide a response after the comment.

Additional discussion about any of the comments or responses can be conducted on the WG mailing list. However, please be sure to enter your initial comments here for full consideration in any future revisions of this document

• Sample comment by WikiName
  • Response (by WikiName)

Comments from TCG member during the RFC/TCG Review Period: 2023-07-01 – 2023-08-15

WG chairs or vice chairs must read the Document, provide comments if any (including on topics not directly linked to the Group matters) or indicate that they have no comment.

IG chairs or vice chairs are also encouraged to do the same, althought their inputs are not compulsory.

TCG Chair & Vice Chair

Applications Working Group

It looks good from our perspective. It clearly shows the variations between different syntaxes.

Data Access Layer Working Group

Changes are limited and look to be easily supported.

-- JamesDempsey 2023-11-08

Data Model Working Group

The changes seem rather minor and are well considered. I see no issues with the proposed changes.

-- MarkCresitelloDittmar - 2023-11-10

Grid & Web Services Working Group

Registry Working Group

No issue

-- RenaudSavalle - 2023-11-12

Semantics Working Group

No issue.

Data Curation & Preservation Interest Group

Education Interest Group

Knowledge Discovery Interest Group

Operations Interest Group

Radio Astronomy Interest Group

Solar System Interest Group

Nothing to add.

-- Anne Raugh - 2023-11-10

Theory Interest Group

Time Domain Interest Group

Standards and Processes Committee

TCG Vote

If you have minor comments (typos) on the last version of the document please indicate it in the Comments column of the table and post them in the TCG comments section above with the date.

<!--
* Set ALLOWTOPICRENAME = TWikiAdminGroup
-->