Difference: STC2 (4 vs. 5)

Revision 52017-04-25 - MarkCresitelloDittmar

 
META TOPICPARENT name="STC"

STC version 2.0

Goal

Defines coordinates, coordinate related metadata and their relationships for use in the IVOA data models.

Changed:
<
<		 Coordinate: location within the coordinate space.
>
>		Coordinate: location within the coordinate space.
 
Changed:
<
<		 Coordinate frame: describes the coordinate space for a domain;
>
>		Coordinate frame: describes the coordinate space for a domain;
 
Changed:
<
<		 Coordinate system: collection of coordinate frames covering the domain space
>
>		Coordinate system: collection of coordinate frames covering the domain space
  Why STC-2.0?
Changed:
<
<		 Version 1 of STC was developed in 2007, prior to the development and adoption of vo-dml modeling practices. As we progress to the development of vo-dml compliant component models, it is necessary to revisit those models which define core content. Additionally, the scope of the STC-1.0 model is very broad, making a complete implementation and development of validators, very difficult. As such it may be prudent to break the content of STC-1.0 into component models itself, which as a group, cover the scope of the original.
>
>		Version 1 of STC was developed in 2007, prior to the development and adoption of vo-dml modeling practices. As we progress to the development of vo-dml compliant component models, it is necessary to revisit those models which define core content. Additionally, the scope of the STC-1.0 model is very broad, making a complete implementation and development of validators, very difficult. As such it may be prudent to break the content of STC-1.0 into component models itself, which as a group, cover the scope of the original.
  This effort will start from first principles with respect to defining a specific project use-case, from which requirements will be drawn, satisfied by the model, and implemented in the use-case. We will make use of the original model to ensure that the coverage of concepts is complete and that the models will be compatible. However, the form and structure may be quite different. This model will use vo-dml modeling practices, and model elements may be structured differently to more efficiently represent the concepts.

Participants

domain experts: ArnoldRots

data modeler: MarkCresitelloDittmar

contributors: ArnoldRots (editor), GerardLemson, OmarLaurino, MarkCresitelloDittmar

Uses cases

1) The primary use case for this work is in support of the CubesDM. This will involve the definition of coordinates and associated metadata in several physical domains and pixel domain.

Requirements

Changed:
<
<
  • Structure
>
>
  • Structure
 
    • The model shall be vo-dml compliant, producing a validated vo-dml XML description.
    • shall produce documentation in standard pdf format, and as vo-dml HTML
    • shall re-use, or refer to, dependent models.
Changed:
<
<
  • Scope
    • Requirements of the Cube model incorporate the following concepts/relations within the STC area of discourse
>
>
  • Scope
    • Requirements of the Cube model incorporate the following concepts/relations within the STC area of discourse
 
      • Coordinate frames; describing domain axes, orientation and origin
      • Coordinate systems; collection of coordinate frames providing a complete description of the domain space
      • Coordinates; locations within the coodinate space, with association to corresponding domain spec.
      • Defining relation between two coordinate frames within the same domain.
      • Derived coordinates; measured or calculated values including associated errors
    • Requirements of Cube model include the Pixel, Spatial, Temporal, Spectral, and Polarization domains.
Changed:
<
<
  • Content
>
>
  • Application/Usage
Added:
>
>
    • Users should be able to identify and use basic content with minimal specialized information.
      • in other words, a generic utility should be able to find and use core elements without knowing a lot about the various extensions and uses of those elements.
  • Content
 
    • Shall facilitate the specification of the various concepts in all supported domains
Changed:
<
<
    • Coordinate frames:
      • Shall faciliate the specification of the nature of the domain.
>
>
    • Coordinate frames:
      • Shall faciliate the specification of the nature of the domain.
 
        • dimensionality
        • origin
        • orientation vectors ( for greater than 1D domains )
      • May be specified using generally accepted standard definitions
      • Must be customizable to facilitate origin relocation
Changed:
<
<
    • Coordinate systems:
>
>
    • Coordinate systems:
 
      • Shall provide the Frame specifications for the entire domain space
      • Shall NOT require specification in all supported domains
      • Any specific domain Shall NOT appear more than once in a single coordinate system specification.
Changed:
<
<
    • Coordinates:
>
>
    • Coordinates:
 
      • Shall identify a location within the coordinate domain space
      • Shall be associated with a corresponding coordinate frame or axis
      • Shall be complete value quantities, including value and units as appropriate
Changed:
<
<
    • Derived Coordinates:
>
>
    • Derived Coordinates:
 
      • Shall relate a coordinate value with associated errors
      • Shall support multiple error associations per value to provide errors from different sources
      • Any specific error source may appear only once.
      • errors may not be separable for greater than 1-D domains ( ie: may apply to coordinate pair or triplet as a whole )
Added:
>
>
      • values associated with different domains may have correlated errors (ie: components of coordinate tuple may refer to different domains, and have non-separable errors)
 
    • Shall facilitate the relation of two coordinate frames through a mathematical formula (Transforms)
Changed:
<
<
    • Transforms:
      • Must support the following industry standard transform specifications
>
>
    • Transforms:
      • Must support the following industry standard transform specifications
 
        • FITS WCS
        • Linear
        • Matrix
        • Lookup

Documents

Latest Document:

The document has not yet been released outside of the working group.

Volute:

The current working draft of the document, including all images and source document can be found in the volute repository.. here

UML Model:

We also provide an export of the UML specification in XMI format (version 2.4.1), which is compatible with the vo-dml xslt scripts for generating the vo-dml XML representation.

vo-dml:

VO-DML XML serialization of the model and corresponding HTML page are here

Discussion Topics

Significant discussion threads from dm working group mailing list:

STC2 and VO-DML compliance:

Discussion on conflicts between stc2 model and vo-dml rules, specifically regarding the multiplicity of attributes.

Implementations

META TOPICMOVED by="GiuliaIafrate" date="1452001555" from="Main.STC2" to="IVOA.STC2"
View topic | History: r35 < r34 < r33 < r32 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback