-
Notifications
You must be signed in to change notification settings - Fork 1
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
Support reference of document elements generated by LutaML (other than lutaml_figure
and lutaml_table
)
#41
Comments
That won't be a problem to implement, although currently, we need to decide the union naming of all entries. I used templates from citygml and ogc-dggs, both of them have their own ids structure, for example, the class table uses |
Proposed macro names:
|
@w00lf agree with the new macro names. |
…_class`, `lutaml_table_enum`, `lutaml_table_data_type`, lookup xmi entities in the document by their name
…_class`, `lutaml_table_enum`, `lutaml_table_data_type`, lookup xmi entities in the document by their name
…of macroses: `lutaml_table_package`, `lutaml_table_class`, `lutaml_table_enum`, `lutaml_table_data_type`
…_class`, `lutaml_table_enum`, `lutaml_table_data_type`, lookup xmi entities in the document by their name
lutaml_figure
and lutaml_table
)
We need to unify all the anchor naming, currently we have these patterns:
|
We also have to keep in mind the different 2 kinds of templates and their components:
|
@ronaldtse changed citygml section ids to be the same as with ogc - |
@ronaldtse can we close this one? |
We need the functionality in Ruby, not encoded in the template as conventions. |
lutaml-figure:[...]
has been implemented for the referencing of included figures, but we also need macros to refer to other elements generated by LutaML in the document, they include:Anything else?
Originally posted by @w00lf in #34 (comment)
The text was updated successfully, but these errors were encountered: