Page Comparison

NOTE there was not meeting 2017-04-05 due to the NADDI Conference

ATTENDEES: Wendy, Jay, Larry, Oliver
Node/NodeSet

• What is the status of Arofan? As he was involved in the original solution of Node and GSIM.
• Larry was not involved in the conversations and so it seems to just add a layer of complexity.
• Meant to solve 2 different problems at the same time
• The way we put together model in terms of an abstract on top of an abstract and something we should revisit. We need to think of this more broadly in terms of the patterns and how they are linked. We need to be clear what the issues.
• Look for past notes from Toronto or Vancouver
• Get this well set up for Sprint.
• In terms of what we've done we never refactored once we've made the Collection Pattern and ended up complicating the Node/NodeSet with the pattern. If we had started over and refactored how this works together. If we do this there would obviously be a lot of changes to the representation package. It would be justifiable if this simplified the structure and the uses of packages together.
• In looking at clickable GSIM and its Node and it does. Classification Item, Code Item, and Category Item. Look at the how this functions and with our collection pattern we do this differently. Biggest difference is the levels. How does this interrelate to ordering in Collections. Some may want to walk away from "Levels" by using 2 order relations one within and one between collections.
• Methodology and Process pattern were already having attempts to use it which is an advantage.
• This is an logical model that produces implementation.
• Strict sequence is a good example of simplicity. Can we simplify where we simplify. We would have to look at the inheritance pattern. For example could inherit directly from Binary Relation as you would then not end up with a set of pairs.
• When you look at StrictOrderRelation it is abstract. So a list can be created from the pairs and visa versa so we don't have to worry so much about the conceptual inheritance of it.
• Its beautiful in definition in terms of its transitive, reflexive, symmetry
• If the only reason for realizing an abstract relation is to restrict what it is ordering, is this a valid reason for creating a large number of new realized classes.
• There are instances when you want to use pairs and instances when you don't. For example, partial orders or use of the Allen's Rules requires pairs. We want to be able to simple things simply and complex things clearly.
• Being able to do temporal and spatial orderings is important and so we need the complexity to do these things clearly and the pairs is a good mechanism for that.

Questioned whether for a codebook which is retrospective (or at least descriptively focused) there is a need for multiple moods.

Oliver won't be available next week.

Primitive data types - send Oliver issue number