MOC 1.1 Proposed Recommendation: Request for Comments


Latest Draft: MOC 1.1 (officially Working Draft)

The substantive differences between version 1.1 of MOC and the preceding version 1.0 are:

  • The String MOC serialization was moved from an informative section (suggested syntax) to the normative section.
  • A MOCORDER convention for String MOC and JSON MOC was added.

Reference Interoperable Implementations

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

  • MOCPy >=0.5.6
  • Aladin (>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 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.
To see non-trivial examples for ASCII MOCs coming out of a database, run something like

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


Implementations Validators

(If any, indicate here the links to Implementations Validators)

Comments Prior to Official RFC Period

Comment here prior to the official RFC period. Include your Wiki Name. Discussion can be continued on the mailing list (

Ignore Below Until RFC Period Starts

Comments from the IVOA Community during RFC/TCG review period: RFC_start_date_TBD - RFC_end_date_TBD

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

Comments from TCG member during the RFC/TCG Review Period: TCG_start_date_TBD - TCG_end_date_TBD

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

Data Access Layer Working Group

Data Model Working Group

Grid & Web Services Working Group

Registry Working Group

Semantics Working Group

Data Curation & Preservation Interest Group

Education Interest Group

Knowledge Discovery Interest Group

Solar System Interest Group

Theory Interest Group

Time Domain Interest Group


Standards and Processes Committee

TCG Vote : Vote_start_date - Vote_end_date

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

  • MOC_ASCII_in_Aladin.png:
Edit | Attach | Print version | History: r19 | r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r5 - 2019-05-17 - PierreFernique
This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback