<div dir="ltr"><div><div><div>Laurent,<br><br></div><div>To answer the primary question:<br></div><div> Yes, the models do allow for 'discrete' data, and this is exercised with the Polarization object.<br></div><div> The values (coord) are PolCoordValue types from the coordinates model, which are Enumerations (matching your second use case).<br><br></div><div>My expectation for Source model is that it will define other properties which extend Measure in much <br></div><div>the same way as the current suite ( Position, Velocity, ProperMotion, Time, Polarization ). By extending <br></div><div>Measure, they will automatically be usable in Cube-s.<br><br></div><div>As for non-numeric data.. it really depends on what the string represents.<br></div><div> e.g. "Q" = Stokes Polarization.<br><br></div><div>In your examples, a MOC or STC-S string do not equate to Measure.<br></div><div>STC-S = a standardized serialization for specific sets of STC-1.33 objects.<br></div><div>o The string itself maps to a set of complex objects, not a single value<br></div><div>o It spans more of STC-1.33 than is covered by the new component models (Coords, Meas, Trans).<br></div><div> So, while it should be possible to express a Measurement instance as an STC-S string, not all STC-S<br></div><div> strings can be resolved into NEW component model instances. For example, STC-S includes Regions<br></div><div> and Intervals, as well as some properties not covered (Spectral) in the current Measurement model.<br></div><br></div>So, when working the Source model, it'll be important to identify which Properties can extend Measure<br></div><div>(or reuse components thereof), and what concepts are 'missing' (eg: Region).<br></div><div><div><br></div><div>Mark<br><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 26, 2019 at 11:26 AM Laurent Michel <<a href="mailto:laurent.michel@astro.unistra.fr">laurent.michel@astro.unistra.fr</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello DMers,<br>
<br>
I'm experimenting the use of STC2 (Meas/Cood) for a proposal for a generic model for source data.<br>
<br>
The idea is to use, as lond as possible, STC2 measures for all quantities attached to one source.<br>
<br>
My question is to know whether it is possible to have a Measurement with non numerical values.<br>
I've 2 use cases:<br>
- Object shape: a MOC or a STC string, both being possibly serialized as strings<br>
- Object type: literal<br>
<br>
Can I use Generic classes (GenericMeasure and GenericCoord) or should I extend meas:Measure with my own stuff?<br>
<br>
Best<br>
Laurent<br>
<br>
-- <br>
jesuischarlie/Tunis/Paris/Bruxelles/Berlin<br>
<br>
Laurent Michel<br>
SSC XMM-Newton<br>
Tél : +33 (0)3 68 85 24 37<br>
Fax : +33 (0)3 )3 68 85 24 32<br>
Université de Strasbourg <<a href="http://www.unistra.fr" rel="noreferrer" target="_blank">http://www.unistra.fr</a>><br>
Observatoire Astronomique<br>
11 Rue de l'Université<br>
F - 67200 Strasbourg<br>
<br>
</blockquote></div></div></div>