Add mechanism to allow linking anchors for XMI defined objects that are not generated in document

[ronaldtse]

From metanorma/ogc-citygml-xmi#110

In the CityGML 3.0 XMI file, the following classes are used (by other classes) but not defined because they are out of scope:

Area
Boolean
Character
CharacterString
Date
DateTime
EngineeringCRS
GenericName
Integer
Length
Measure
Real
ScopedName
TM_Duration
URI
UnitOfMeasure
Volume

However, the plugin today creates links to these anchors but they are not present in the current document:

Area-section
Boolean-section
Character-section
CharacterString-section
Date-section
DateTime-section
EngineeringCRS-section
GenericName-section
Integer-section
Length-section
Measure-section
Real-section
ScopedName-section
TM_Duration-section
URI-section
UnitOfMeasure-section
Volume-section

This means we need to have a YAML configuration that "defines where the classes that are out of scope should link to", e.g.

packages:
  - "Core"
  - "Appearance"
external_classes:
  - "Area": {{Area}}
  - "Boolean": my-section-for-boolean
  - ...
section_depth: 3
render_style: data_dictionary
include_root: true

[ronaldtse]

From @w00lf

I have implemented #70, tried to implement it for metanorma/ogc-citygml-xmi#101 issue but now i see that sections were changed to the new lutaml format, eg:

term-URI => URI-section

Should i create a PR with the old mappings and return old refs?

Yes. The anchors in this commit (metanorma/ogc-citygml-xmi@bcc7cf7) should be removed and replaced with the new functionality. Thanks!

[w00lf]

@ronaldtse used new logic in metanorma/ogc-citygml-xmi#122

[w00lf]

This was implemented in #73 and implemented in metanorma/ogc-citygml-xmi#122. @ronaldtse can we close this one?

[ronaldtse]

@w00lf this is not fixed because the exceptions are manually encoded. We need an automatic solution where LutaML detects which models are not defined in the document, and does not create those links.