+ Updated STC directory to most recent Volute updates (AR) + Process through xslt scripts: NOTE: had some issues with web schema (Namespace), downloaded to xsd directory and redirected (as file: URL) in build.properties. Coords: xmi2vo-dml = OK validate = FAIL * Target role of subsets constraint on 'domain.pixel.PixelFrame' with vodml-ref stc2_coordinates:coordsystem.CoordFrame.coordSpace can not be found Meas: xmi2vo-dml = OK validate = FAIL * Many of: domain.redshift.RedshiftCoordMeasure has more than one extends relation. .RedshiftCoordMeasure .RedshiftSimpleCoordMeasure .Position .Velocity .SimplePosition .SimplePosition1D .SimplePosition2D .SimplePosition3D .SimpleVelocity .SimpleVelocity1D .SimpleVelocity2D .SimpleVelocity3D .SpectralCoordMeasure .SpectralSimpleCoordMeasure .TimeMeasure .TimeSimpleMeasure * Several constraint targets not found o change reference to local/new coords model corrects all but 2 * Target datatype of subsets constraint on 'domain.space.SimplePosition' with vodml-ref stc2_coordinates:domain.space.SpatialCoord can not be found * Target datatype of subsets constraint on 'domain.space.SimpleVelocity' with vodml-ref stc2_coordinates:domain.space.SpatialCoord can not be found o object is 'SpatialCoordValue' in current model MCD Modelio Model(s) + coords_V2.0: 01/12/2018 = my equivalent to current AR model + coords_V2.0_alt: 9/25/2017 = my alternate modeling, prior to TS work; OBSOLETE + coords_V2.0_alt2: 10/25/2017 = most migrated from TS work; includes some shortcuts, but does NOT include Frame relation change. + meas_V2.0: 01/12/2018 = my equivalent to current AR model + meas_V2.0_alt: 10/12/2017 = no 'shortcuts'; updated subset stereotype content + meas_V2.0_alt2: 10/25/2017 = includes 'shortcuts' for spatial and temporal; updated subset content MCD Task List: o double check subset specs in Modelio.. so they process through scripts [DONE] o update 'base' Modelio models to current AR model equivalents [DONE] o process through xslt scripts [DONE] o remove 'alt' versions from volute o update example serializations o make change request list: from review of serializations and alt2 migrations (from TS work) + Review of AR model vs MCD equivalent model * AR: STC2.0ModelCoords.xmi r4612 via diagrams * MCD: stc_coords_v2.0_uml2p4p1.xmi 20170112 + Review of Coords Model: coordsystem: + CoordSpace.coordAxis[] .. AR has [1..3]; MCD has [1..*] coords: + MCD has package named 'coordz'.. Modelio issue with package and model of same name?.. NOTE: would like to remove the coords and coordsystem packages.. bring objects to base level. domain.generic: + MCD does not constrain axis multiplicity to 1. domain.pixel: AR TODO: PixelFrame has composition to PixelSpace.. (with subset).. this relation was removed in this revision AR TODO: PixelCoordinate*D => can not rename attribute on subset (pixCmpt == MultiCoordValue.cmpt) domain.polarization: + cval dtype deltas.. Modelio cannot extend Enum, so layout is different AR TODO: remove composite PolarizationCoord object domain.redshift: AR TODO: remove composite RedshiftCoord object domain.spatial: + AR has specialized Frames ( GalacticFrame, EclipticFrame, EquatorialFrame ) with specialized StdRefFrame enums corresponding to these. ( leans StdRefFrame toward being a semanticConcept rather than an enum.. ) AR TODO: remove epoch from Frame (redundant with that in spatial CoordValue types ) domain.spectral: AR TODO: remove composite spectralCoord object domain.time: AR TODO: remove composite TimeStamp object; revert TimeStampValue to TimeStamp Measurement Model: AR: better if doc/diagram/meas only has 'measurement' model diagrams.. remove proxy diagrams of coord objects. AR: We had discussed creating a parent 'CoordMeasure' type from which we extend a) Polarization b) the currrent CoordMeasure.. renamed == parent to all the value+error measures c) potentially a 'Virtual' type which would handle functionally generated values uncertainty AR TODO: migrate CoordMeasure,[Resolution,Error] to base package MCD TODO: add 'Resolution' [DEFER] stcTypes Contains "Uncertainty" class hierarchy.. I have at base level, if anything, this should be the 'uncertainty' package. domain.generic:OK domain.pixel: OK + MCD - there is no pixel 'measure' domain.polarization: AR TODO: remove PolarizationCM and PolSimpleCoord.. PolarizatonCoord composite type to be removed PolCoord -> Polarization domain.redshift: AR TODO: remove RedshiftCM and RedshiftSimpleCoordMeasure.. RedshiftCoord composite type to be removed domain.spatial: AR TODO: PositionCM -> Position SimplePosition -> SkyPosition (The shortcuts are 'specific'; I'd like the name to be also.) SkyPosition.coord::SpatialCoord -> SpaceCoord (does not match coords model type) domain.spectral: AR TODO: remove SpectralCM and SpectralSimpleCoordMeasure.. SpectralCoord composite type to be removed domain.time: AR TODO: TimeCM -> TimeMeasure (or TimeCoordMeasure to match spectral, redshift, generic domains) TimeMeasure + TimeSimpleMeasure o I have "GenTimeMeasure" with GenTimeMeasure.coord::TimeOffset "StdTimeMeasure" with StdTimeMeasure.coord::TimeStamp << JD,MJD,ISOtime COMMENTS I'd like to move the time domain to the representation we have migrated to during the TS serializations. Coords: == 'specialized' time types (JD,MJD,ISOtime) extend 'BasicCoordValue' like 'SpaceCoord' does. == extension of TimeStamp.. cval::RealQuantity JD,MJD == extensions of JDTime ISOtime == extension of TimeStamp.. cval::datetime NOTE: removes need for DateTimeQuantity Meas: == head of Time Measurement types GenTimeMeasure == subset coord::TimeOffset << serves TimeOffset StdTimeMeasure == subset coord::TimeStamp << serves JD, MJD, ISO which are very specialized/defined