| • first define strictly the terms: |
| • THIS: means the fragment we are standing
on | | • to link: means to be able to walk from
source (the fragment mentioning a ref)
to the target (to the fragment which
contains the ref) | | • ref: TODO (see#/paper/paper/mdd-structur⸨#/paper/paper/mdd-structur⸩) | | • trail: TODO |
|
| • what is the objective of linking? |
| • keep other fragments referencing THIS
correctly | | • keep meta-data of THIS fragment
correctly linked to THIS |
|
| • what is the subject of linking? |
| • fragment | | • can more then headings be linked? | | • can a link be linked? | | • paragraph, table, cell, image ? |
|
| • what is the lifecycle of the problem? |
| • can we hook the actual event of change
and intercept it? so correct it
immediatelly at the moment of change? | | • or we need to expect to handle it
ex-post? so anytime after the text was
changed, and still be able to correct
it. | | • or? | | | | • should we expect the text if changed in
repolero codeditor only? or also in an
external editor? or external refactoring
opeation? |
|
|
| • problem of sync |
| • keep in sync the source and targets | | • also keep the meta-data in sync |
|
| • when would refs change? |
| • rename the heading of a fragment | | • rename the PARENT heading of a fragment | | • move the fragment to different location |
|
| • renaming a heading means: |
| • delete a ref | | • create a new one | | • and optionally!: rename old links to the
new one |
|
| • then there is also delete... |
• see 【similiar software/internal links
problem |