Versions Compared

Old Version 157

changes.mady.by.user Wendy Thomas

Saved on

compared with

New Version 158

changes.mady.by.user Wendy Thomas

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Expand
titleVirtual meeting 2017-07-05

ATTENDEES: Wendy, Jay, Oliver, Larry

Went over emails regarding collection model and realization
Talked about Universe, Population, UnitType being a subtype of Concept (using concept sets to describe collections of them)
CategorySet to CodeList to StatisticalClassification

What needs to get done for CodeBook:
Statistics - Variable and category level (DataDescription)
Vocabulary for types of methodologies - we have the generic but need some documentation probably flesh out what Sanda did in a formal document

Documentation of View capture:
Want to do documentation at the view level which is more for users of view but we don't really have the resources at the moment to add class level documentation. Figure out what kind of document is needed and what format we should use now. See what format we have and then put documentation in that format and find anything that doesn't have a home.


Expand
titleVirtual meeting 2017-06-28

ATTENDEES: Wendy, Oliver, Jay, Dan G.

Proposed game plan discussions

  • Software version of the content is good but there could be other drawback

Documentation of Views:

  • YAML structures were discussed, putting these examples into Lion
  • Be able to have instances to prove and use as examples

Patterns:
Update on realizations and XML for Collection Pattern

  • Classification - maybe start with CodeList and then add levels
  • Make a view for realizations
  • Workflow
  • Logical/Format description
  • CustomValues

Signification Pattern (new issue DMT-137 describing task).

  • Please review model in terms of locations where signification pattern should be realized.
  • We need to have clearer rules in terms of realization
  • Many classes, such as concept, realize multiple pattern classes and we need to be clear on how these compliment each or conflict (if they do so)
  • The extent to which we use a pattern - there are instances where the pattern applies but may be of such a character that we aren't realizing (i.e. Identification where we can specify how ID's are formed by relationship to the pattern, but to most seem pretty straight forward). We don't want to twist people into strict knots by forcing realization of a pattern. Difference between the conceptual model and creating the binding and implementing the binding.
  • The big issue is whether people want to actually model it. At what level is that made invisible - at the point of binding or the point of an instance.
  • The sweet spot is in doing metadata management. You can start looking at ties between identifiers and how they are formed.
  • How do we go about exploring this in an efficient way. Lawrence paper should be linked to DMT-137
  • How its currently modeled is tied to nodes and so if we lose nodes there isn't a representation to hang our hat on.
  • In walking from the abstract to the concrete it had to do with the modeling. Signification would need to be pulled into at least realizations of part of the collection. May cause the review of the rule that pattern classes can't realize other pattern classes. They extend.

APPROACH:

  • Re look at the material we have
  • Review the use of Nodes and effect on signification on that
  • Create a realization of Statistical Classification or CodeList which use both collection and signification
  • Evaluate signification within this
  • Use signification only where it is useful
  • Better definition of when signification should be used and where it may be superfluous

...