MOC11RFC < IVOA

---+ MOC 1.1 Proposed Recommendation: Request for Comments

<span style="background-color: transparent;">%TOC{depth="2"}%</span>

---

---++ Summary

Latest Draft: <span style="text-decoration: underline;">[[http://www.ivoa.net/documents/MOC/][MOC 1.1]]</span> (Proposed Recommendation)

<span style="background-color: transparent;">The substantive differences between version 1.1 of MOC and the preceding version 1.0 are:</span>

<div title="Page 30">

   * <span style="background-color: transparent;">The String MOC serialization was moved from an informative section </span><span style="background-color: transparent;">(suggested syntax) to the normative section.</span>
   * <span style="background-color: transparent;">A MOCORDER convention for String MOC and JSON MOC was added.</span>
</div>
---++ 
---++ Reference Interoperable Implementations

(Indicate here the links to at least two Reference Interoperable Implementations)

   * [[https://github.com/cds-astro/mocpy][MOCPy &gt;=0.5.6]]
   * [[https://aladin.u-strasbg.fr/java/nph-aladin.pl?frame=downloading#Proto][Aladin (&gt;v10.126)]]: read/write ASCII MOC (select ASCII format when exporting MOC - see snapshot below) + new script command dedicated to ASCII MOC (ex: draw MOC 3/1,2,3 4/56-67)
   * The relational registry at http://dc.g-vo.org/tap parses the ASCII MOCs in Registry records into the rr.stc_spatial table (consumer)
   * DaCHS since version 1.1 produces ASCII MOCs when serialising MOC-values database columns.
   * The [[http://starlink.eao.hawaii.edu/devdocs/sun211.htx/sun211ss141.html][Moc]] class within the [[http://starlink.eao.hawaii.edu/devdocs/sun211.htx/sun211.html][AST]]/[[http://timj.github.io/starlink-pyast/pyast.html][PyAST]] WCS library now supports reading and writing ASCII and JSON MOCs in addition to FITS.
To see non-trivial examples for ASCII MOCs coming out of a database, run something like

<pre>select top 100 * from rr.stc_spatial
where 1=contains(point(10, 10), coverage)
and 0=contains(point(20, 20), coverage)
</pre>

on http://dc.g-vo.org/tap.

---++ 
---++ Implementations Validators

   * This validator is written in Python. It check for valid ASCII MOC syntax and that pixel numbers are in the legal range for thier order: https://volute.g-vo.org/svn/trunk/projects/apps/MOC/
---++ 
---++ Comments Prior to Official RFC Period

<span style="background-color: transparent;"> </span>

As I was considering semantic validation cases, I noticed this sentence in section 2.3.2:
<blockquote>"Warning: In this basic simple ASCII string format the values may be not sorted, and the MOC may be not well-formed."</blockquote>

which seems to contradict section 2.2.3:
<blockquote>" An encoded MOC must also be &ldquo;well-formed&rdquo;. To keep the canonical property of MOC, the redundant cells are not allowed and the hierarchical encoding principle must be respected. Thus it is not allowed to encode 4 sibling cells instead of their parent (only at level 0 for the 12 first diamonds). Using this simple constraint, there is one and only one way to describe a specific region and this makes the interoperability principle easy to implement."</blockquote>

Maybe the former was just a legacy from MOC 1.0 where ASCII MOC was less formal, perhaps intended for hand-crafted MOCs not intended for serious use. With ASCII MOC now being formalized, can we remove that sentence and require that ASCII MOCs must be just as well-formed as their FITS counterparts?

-- IVOA.TomDonaldson - 2019-06-14

---
---
---

---++ Comments from the IVOA Community during RFC/TCG review period: 2019-06-14 - 2019-07-29

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 TWiki.WikiName 
      * Response (by TWiki.WikiName)

---
---

---++ Comments from TCG member during the RFC/TCG Review Period: 2019-06-14 - 2019-07-29

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

---+++ [[IvoaApplications][Applications Working Group]]

---+++ [[IvoaDAL][Data Access Layer Working Group]]

---+++ [[IvoaDataModel][Data Model Working Group]]

---+++ [[IvoaGridAndWebServices][Grid & Web Services Working Group]]

---+++ [[IvoaResReg][Registry Working Group]]

---+++ [[IvoaSemantics][Semantics Working Group]]

---+++ [[IvoaDCP][Data Curation & Preservation Interest Group]]

---+++ [[IvoaTheory][Education Interest Group]]

---+++ [[IvoaKDD][Knowledge Discovery Interest Group]]

---+++ [[IvoaSS][Solar System Interest Group]]

---+++ [[IvoaTheory][Theory Interest Group]]

---+++ [[IvoaVOEvent][Time Domain Interest Group]]

---+++ [[IvoaOps][Operations]]

---+++ [[IvoaStdsDocsProc][Standards and Processes Committee]]

---

---++ TCG Vote: 2019-06-14 - 2019-07-29

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.

| Group | Yes | No | Abstain | Comments |
| TCG | | | | |
| Apps | | | | |
| DAL | | | | |
| DM | | | | |
| GWS | | | | |
| Registry | | | | |
| Semantics | | | | |
| DCP | | | | |
| KDIG | | | | |
| SSIG | | | | |
| Theory | | | | |
| TD | | | | |
| Ops | | | | |
| <nop>StdProc | | | | |

---

<br /> <!--</p> <ul> <li> <ul> <li> Set ALLOWTOPICRENAME =<span class="WYSIWYG_PROTECTED"> IVOA.TWikiAdminGroup</span> </li> </ul></li> </ul>-->
   * MOC_ASCII_in_Aladin.png: <br /> <img width="546" alt="MOC_ASCII_in_Aladin.png" src="%ATTACHURLPATH%/MOC_ASCII_in_Aladin.png" height="158" />
Attachments
Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
png	MOC_ASCII_in_Aladin.png	r1	manage	9.3 K	2019-05-17 - 08:32	PierreFernique
This topic: IVOA > WebHome > IvoaApplications > MocInfo > MOC11RFC
Topic revision: r8 - 2019-06-14 - TomDonaldson