Skip to content

Define relations between different ALTO components #88

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
cipriandinu opened this issue May 15, 2025 · 0 comments
Open

Define relations between different ALTO components #88

cipriandinu opened this issue May 15, 2025 · 0 comments

Comments

@cipriandinu
Copy link
Member

Currently there is no option to express different relations between different ALTO objects (object = page, textblock, textline, string, illustration, composed block) except reading order and a default parent/child relation.

Might be usefull to be able to express other types of relations. Several examples:

"note" - a footnote textblock could be linked by its reference from text (a link between a string and a text block)
"key"/"value" relations - for specific documents for example invoices, "price" can be a "key" for the price itself, and price itself can be a "value" for "price" (here could be a link between two strings"
"relatedTo" - an illustration/table with its caption block
"..." - cells in a table linked to column/raw header
"parent"/"child" relations, other than default nested structure (page/textblocks/textlines/strings)

As technical implementation, we may use these as a separate collection of links (like "smLinks" in METS 1), a link being identified by a source, a type and retated object.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant