Revisions for CorrespondenceTable

RevisionTermsStatus
Saved 03/15/2018 - 20:36 by wendy

changed has publication to Neither TC-60

Proposal current revision (published)
Saved 02/27/2018 - 22:08 by wendy

removed reference to Node Sets in definition, added example, and corrected explanatory notes

Proposal archived
Saved 12/13/2017 - 22:12 by wendy

changed target of maps to Statistical classification

Proposal archived
Saved 11/29/2017 - 23:52 by wendy

contains to correspondence DMT-144

Proposal archived
Saved 11/27/2017 - 21:15 by wendy

first pass to get rid of conflicts (issues)

Proposal archived
Saved 01/07/2017 - 23:30 by wendy

moved contains to property

Proposal archived
Saved 10/06/2016 - 08:56 by oliver.hopt

BUG FIX contactPersons was left in properties and therefore doubled

Proposal archived
Saved 09/12/2016 - 19:17 by wendy

changed AgentAssociation to Agent and move to relationships

Proposal archived
Saved 09/12/2016 - 17:52 by wendy

Aligned with Collection pattern.

Proposal archived
Saved 12/17/2015 - 20:06 by wendy

changed publication from property to relationship target type ExternalMaterial

Proposal archived
Saved 11/03/2015 - 18:06 by wendy

changed effectivePeriod to effectiveDates and DateRange. changed owner, maintence unit, and contact persons to AgentAssociation

Proposal archived
Saved 03/30/2015 - 21:11 by flavio.rizzolo

Changed name of date property to effectivePeriod (retained the Date type because it can also represent periods)

Proposal archived
Saved 01/31/2015 - 17:38 by flavio.rizzolo

Fixed definition (it applies to NodeSets now rather than just StatisticalClassifications). Moved part of the definition to explanatory notes. Deleted identifier (inherited from Identifiable) Changed datatypes of owners, maintenanceUnit, contactPersons to String Changed publications to StructuredString Deleted sourceLevel and targetLevel properties and created relationships to Level instead. Replaced floating by date, since it denotes the date of validity of the correspondence. Do we want to make date into an “interval of validity” for a more generic time travel support?

Proposal archived
Saved 01/31/2015 - 17:25 by flavio.rizzolo
Proposal archived
Saved 01/31/2015 - 17:23 by flavio.rizzolo
Proposal archived
Saved 12/11/2014 - 15:37 by flavio.rizzolo
Proposal archived
Saved 12/11/2014 - 15:35 by flavio.rizzolo

Removed source and target properties and made them into relationships. Removed relationshipType since cardinalities are expressed in the new source and target relationships.

Proposal archived
Saved 12/11/2014 - 15:26 by flavio.rizzolo

Copy of the revision from Fri, 11/28/2014 - 04:37.

Proposal archived
Saved 12/11/2014 - 15:23 by flavio.rizzolo

Removed source and target properties since they are now inherited from OrderedCollectionCorrespondence.

Proposal archived
Saved 11/28/2014 - 10:37 by flavio.rizzolo
Proposal archived
Saved 11/25/2014 - 17:24 by marcel
Proposal archived
Saved 11/25/2014 - 11:51 by flavio.rizzolo
Proposal archived
Saved 11/19/2014 - 22:14 by flavio.rizzolo
Proposal archived
Saved 11/19/2014 - 22:08 by flavio.rizzolo
Proposal archived
Saved 10/23/2014 - 16:38 by therese.lalor
Proposal archived
Saved 10/23/2014 - 16:32 by therese.lalor
Proposal archived
Saved 10/23/2014 - 16:02 by therese.lalor
Proposal archived