Modelling team sandbox

Ideas that the modelling are thinking about and discussing

 

Standard Properties (to be reused in a consistent way):

  • Label
  • Description
  • Definition
  • Language (for non-textual objects)
  • Comments (internal)
  • Notes (public)

LS-41 - Getting issue details... STATUS

Need to ensure that objects are not just empty shells, and actually have properties.

Also when adding a property which holds the main "value" of an object, particularly if the datatype of that property is xs:string the property should be called "content".

For example, Text.content of type xs:string. 

 

Identification issues:

  • Identifiable objects are identifiable by agency, id, and version. This identifier is universally unique. Sometimes, the id alone is universally unique – there is an extra field in AnnotatedIdentifiable to document this.
  • AnnotatedIdentifiable: Within a given context you can define a localId and a localVersion. Example: in the context of a dataset, a variable name is unique and is therefore a localId.

 

Modelling nested collections (added by Flavio)

The new collection structure has a container (Collection) and members (Member). In order to allow for nested collections without resorting to multiple inheritance, we have to make Member a subclass of Collection. That has implications in cases like Node and NodeSet, since it will make Node a Collection too. To address the issue, there is a constraint defined on the subclass relationship between Member and Collection: If isCollection = true then Member is a subclass of Collection, otherwise it is not. The default is false. The following diagram illustrates the model:


Modelling correspondences/maps (added by Flavio)

We have two different ways of modelling correspondences at the member level. A correspondence between members is a set containing all members that map to each other, i.e. they are equivalent of similar. In such a generic representation there is no order between members. However, order might be needed in some cases, e.g. GSIM Map has a source and a target. There are two ways to introduce order in this scenario. The first one is by making the MemberCorrespondence object a subtype of Collection, in which case we could define precedence as an order relation, as shown in the following diagram:

The second option is to create a subtype of MemberCorrespondence to deal with order, as shown in the following diagram:

We need to decide which one to use.

 

 

  File Modified

Microsoft Powerpoint Presentation data objects.pptx

Nov 19, 2014 by Wiki Editor

Microsoft Powerpoint Presentation library organization v2.pptx

Nov 19, 2014 by Therese Lalor

Microsoft Word Document Using the DDI 4 Process Model to Describe Historical and Prescriptive Processes_0_1.docx

Nov 21, 2014 by Wiki Editor

PNG File A DDI 4 Processing Pipeline.png

Nov 24, 2014 by Wiki Editor

PDF File Collections and Maps.pdf

Nov 26, 2014 by Therese Lalor

PNG File image2014-11-26 9:35:58.png

Nov 26, 2014 by Therese Lalor

PNG File image2014-11-26 9:38:27.png

Nov 26, 2014 by Therese Lalor

Microsoft Excel Spreadsheet DiscoverySpreadsheet.xlsx

Nov 26, 2014 by Wendy Thomas

PNG File image2014-11-26 11:27:21.png

Nov 26, 2014 by Therese Lalor

PNG File image2014-11-26 11:30:12.png

Nov 26, 2014 by Therese Lalor

PNG File image2014-11-26 11:31:8.png

Nov 26, 2014 by Therese Lalor

PNG File image2014-11-26 11:33:56.png

Nov 26, 2014 by Therese Lalor

PNG File image2014-11-27 5:43:15.png

Nov 27, 2014 by Therese Lalor

PNG File image2014-11-27 5:46:6.png

Nov 27, 2014 by Therese Lalor

PNG File image2014-11-27 5:47:4.png

Nov 27, 2014 by Therese Lalor

Text File PairedCodeValueType.txt

Dec 10, 2014 by Wendy Thomas

Microsoft Powerpoint Presentation sampling instance.pptx

Aug 05, 2015 by Wendy Thomas

Microsoft Powerpoint Presentation OrderRelationsQualitativeFiles.pptx

Aug 05, 2015 by Wendy Thomas

Microsoft Word Document Classifications and order relations.docx

Aug 05, 2015 by Wendy Thomas