Closed bpow closed 6 years ago
Most of these items are "Family" entities, which have "description" attributes. And more generally, there are "description" attributes on other items, and a few things that are notated with a UserLabel
in the defunct UserLabel
model.
Fixing the UserLabel
modelling will fix that last few. For the others, I think there are a couple of options for how to move forward:
By way of editorial comments: I'm a bit hesitant about option 1 since that gives us two special cases. Option 2 is probably OK. I don't think we have to go as far as option 3. Option 4 seems like overkill for the Family objects, but might be reasonable for the others.
Of all of the "Family" entities, one had a label ("12A") in addition to its description (Family #001
). In the interests of consistency, I am removing the "12A" label so this is more like the others. @larrybabb : does this seem right? If not, this could be a place to use a UserLabel.
Changed entity for A073 from E40 to E01 (Statement), made its cardinality 0..* (was 0..1)
Added A130 to E39 (UserLabel.labelFor)
As I moved descriptions up to UserLabels, I made labels for the Ascrt objects as well, but I am not sure whether the labels should go there or in the UserLabel objects...
for CG-EX:UsrLabl001:
for CG-EX:UsrLabl002:
for CG-EX:UsrLabl003:
While I was at it, I changed all of the CG-EXAMPLE: prefixes to CG-EX: for consistency.
Additional time: about 40 minutes (including figuring out about #198)
splitting off from #193 as a relatively-isolated issue.
The relevant items are: