Versions Compared

Key

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

...

Fleshing out Infrastructure

Make sure all refset patterns are covered.  In particular we need to add support for "association reference" refset entries as these are currently not modeled.

  • See everywhere that AttributeValueRefSetMember is used and model it also for AssociationReferenceRefSetMember (it's considered a concept refset)

Next, attribute value and association reference refset entries can be associated with either descriptions or concepts

  • Split AttributeValueRefSetMember and AssociationReferenceRefSetMember into two kinds
    • AttributeValueDescriptionRefSetMember - these are attributes on descriptions
    • AssociationReferenceDescriptionRefSetMember - this is description history info
      • the target componnet is always still a concept, this only changes the referenced component
    • AttributeValueConceptRefSetMember - these are attributes on concepts
    • AssociationReferenceConceptRefSetMember - this is concept history info
      • the target componnet is always still a concept, this only changes the referenced component

Make sure all refset patterns are covered.  In particular we need to add support for "association reference" refset entries as these are currently not modeled.

  • See everywhere that AttributeValueRefSetMember is used and model it also for AssociationReferenceRefSetMember (it's considered a concept refset)

Core improvements to model

  • equals/hashcode - ignore effectiveTime, id, defaultPreferredName, label and sub-objects (like concept-> description), but parent objects should be included
  • copy constructors

Fleshing out APIs

 

Step 1

ContentServiceJpa defines many more methods then the rest API.  We want to implement these as REST services.  Start with the various getXXX() methods and implement across the stack.

...

Release admin tool

ReleaseHistory object?

Full and Extension/Edition loaders

  • Also loaders need to be able to flexibly use the "terminology" and "version" settings - pass as parameters so that an 
  • consider what's involved in loading core + a number of extensions and labelling them correctly (e.g. terminology)  - I think using Module for this is ideal.
  • Support an "exxtension" loader that is basically a delta loader but tuned for loading extensions