[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-219322-105":53,"doc-detail-219322-en":127},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":120,"head_meta":122,"extra_data":124,"updated_unix":126},105,"en","observation-data-model-core-components-version-11-ivoa-recommendation","Observation Data Model Core Components - Version 1.1 - IVOA Recommendation","","Defines the core components of the Observation data model for astronomical data discovery across distributed data centers. Presents observation discovery use cases, explains the model, and provides implementation guidelines for a data access service based on the Table Access Protocol (TAP). Specifies minimal queryable metadata for global discovery via TAP services, introduces ObsTAP and ObsCoreDM, and leverages STC, Utypes, Units, and UCDs with VOTable serialization.",{"@graph":63,"@context":119},[64,80,102],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/observation-data-model-core-components-version-11-ivoa-recommendation/219322/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/observation-data-model-core-components-version-11-ivoa-recommendation/219322.png","ImageObject",442,249,{"name":88,"@type":89},"WPS_1786070896","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/vnd.openxmlformats-officedocument.wordprocessingml.document","2026-10-30","2026-09-08",true,{"@type":98,"interactionType":99,"userInteractionCount":101},"InteractionCounter",{"@type":100},"ViewAction",13,{"@type":103,"mainEntity":104},"FAQPage",[105,111,115],{"name":106,"@type":107,"acceptedAnswer":108},"What problem does the Observation Data Model Core Components specification address?","Question",{"text":109,"@type":110},"It defines core queryable metadata needed to support global discovery of observational data across multiple sites using TAP services.","Answer",{"name":112,"@type":107,"acceptedAnswer":113},"How is ObsCoreDM implemented for data discovery?",{"text":114,"@type":110},"ObsCoreDM is implemented as a data access service named ObsTAP, built on top of the Table Access Protocol (TAP) and supporting ADQL querying.",{"name":116,"@type":107,"acceptedAnswer":117},"What are the key technical dependencies of ObsCoreDM?",{"text":118,"@type":110},"ObsCoreDM uses STC, Utypes, Units, and UCDs, and can be serialized as a VOTable; it may also reference more complete related data models.","https://schema.org",{"og:url":78,"og:type":121,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":123,"canonical":78},"index,follow",{"doc_id":125,"site_id":56},219322,1791731600,{"code":4,"msg":5,"data":128},{"doc_id":125,"user_id":129,"nickname":88,"user_avatar":130,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":131,"file_id":132,"file_url":133,"file_type":134,"file_size":135,"view_count":101,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":136,"language":137,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":138,"faqs":139,"seo_title":140,"seo_description":61,"update_tm":141,"read_time":142},549768072016,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","International\nVirtual\nObservatory\nAlliance\nObservation Data Model Core Components and its Implementation in the Table Access Protocol\nVersion 1.1\nIVOA Recommendation, May 09, 2017\nApproved by IVOA executive committee March 20, 2017\nWorking Groups: Data Model, Data Access Layer\nThis version:\n\u0013 HYPERLINK \"http://www.ivoa.net/Documents/ObsCore/20170509/REC-ObsCore-v1.1-20170509.pdf\n\" \u0014http://www.ivoa.net/Documents/ObsCore/20170509/REC-ObsCore-v1.1-20170509.pdf\n\u0015Latest version:\n\u0013 HYPERLINK \"http://www.ivoa.net/Documents/ObsCore/20170509/REC-ObsCore-v1.1-20170509.pdf%20\" \u0014http://www.ivoa.net/Documents/ObsCore/20170509/REC-ObsCore-v1.1-20170509.pdf\u0015\nPrevious version(s):\n\u0013HYPERLINK \"http://www.ivoa.net/Documents/ObsCore/20161004/PR-ObsCore-v1.1-20161004.pdf\"\u0014http://www.ivoa.net/Documents/ObsCore/20161004/PR-ObsCore-v1.1-20161004.pdf\n\u0015\nEditors:\nMireille Louys, Doug Tody, Patrick Dowler, Daniel Durand\nAuthors:\nMireille Louys, Doug Tody, Patrick Dowler, Daniel Durand, Laurent Michel, Francois Bonnarel, Alberto Micol and the IVOA DataModel working group\nAbstract\nThis document defines the core components of the Observation data model that are necessary to perform data discovery when querying data centers for astronomical observations of interest.  It exposes use-cases to be carried out, explains the model and provides guidelines for its implementation as a data access service based on the Table Access Protocol (TAP).  It aims at providing a simple model easy to understand and to implement by data providers that wish to publish their data into the Virtual Observatory.  This interface integrates data modeling and data access aspects in a single service and is named ObsTAP. It will be referenced as such in the IVOA registries.  In this document, the Observation Data Model Core Components (ObsCoreDM) defines the core components of queryable metadata required for global discovery of observational data.  It is meant to allow a single query to be posed to TAP services at multiple sites to perform global data discovery without having to understand the details of the services present at each site.  It defines a minimal set of basic metadata and thus allows for a reasonable cost of implementation by data providers. The combination of the ObsCoreDM with TAP is referred to as an ObsTAP service.  As with most of the VO Data Models, ObsCoreDM makes use of STC, Utypes, Units and UCDs.  The ObsCoreDM can be serialized as a VOTable.  ObsCoreDM can make reference to more complete data models such as Characterisation DM, Spectrum DM or Simple Spectral Line Data Model (SSLDM).\nObsCore shares a large set of common concepts with DataSet Metadata Data Model \u0003\u0013 CITATION Cre16 \\l 1036 \u0014(Cresitello-Dittmar et al. 2016)\u0015\u0004 which binds together most of the data model concepts from the above models in a comprehensive and more general frame work.\nThis current specification on the contrary provides guidelines for implementing these concepts using the TAP protocol and answering ADQL queries. It is dedicated to global discovery.\nStatus of this document\nThis document is a revision of the ObsCore v1.0 recommendation. It extends the metadata provided for discovery of data via VO compliant TAP services. In addition, ObsCore has been selected as the core data model for data discovery by the Simple Image Access protocol version 2 (SIAv2) \u0003\u0013CITATION SIAv215 \\l 1036 \u0014(Dowler, Tody et Bonnarel, IVOA Simple Image Access V2.0 2015)\u0015\u0004 and future parameter-based DAL services. From the experience on the ObsCore v1.0 implementation, and to better describe datasets in support of data discovery via DAL services, new data model fields have been added.\nThis document has been updated by the IVOA Data Model (DM) working group, in coordination with partners involved in the definition of data access protocols (DAL) and of the ADQL language. It describes the core components and the metadata to be attached to an astronomical observation, and contains a guide for implementing this model within the","cbCaisSGTyi7O3i2","https://ap.wps.com/l/cbCaisSGTyi7O3i2","docx",486356,66,"English","# List of Acronyms\n# 1. Introduction\n## 1.1. First building block: Data Models\n## 1.2. Second building block: the Table Access Protocol (TAP)\n## 1.3. The goal of this effort\n# 2. Use cases\n# 3. Observation Core Components Data Model\n## 3.1. UML description of the model\n## 3.2. Main Concepts of the ObsCore Data Model\n## 3.3. Specific Data Model Elements","[{\"question\":\"What problem does the Observation Data Model Core Components specification address?\",\"answer\":\"It defines core queryable metadata needed to support global discovery of observational data across multiple sites using TAP services.\"},{\"question\":\"How is ObsCoreDM implemented for data discovery?\",\"answer\":\"ObsCoreDM is implemented as a data access service named ObsTAP, built on top of the Table Access Protocol (TAP) and supporting ADQL querying.\"},{\"question\":\"What are the key technical dependencies of ObsCoreDM?\",\"answer\":\"ObsCoreDM uses STC, Utypes, Units, and UCDs, and can be serialized as a VOTable; it may also reference more complete related data models.\"}]","Observation Data Model Core Components - Version 1.1 - IVOA Recommendation | DOCX",1788864909,23]