Skip to content
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

mei30To40: should generate<appInfo> entry #24

Open
bwbohl opened this issue Nov 23, 2020 · 3 comments
Open

mei30To40: should generate<appInfo> entry #24

bwbohl opened this issue Nov 23, 2020 · 3 comments

Comments

@bwbohl
Copy link
Member

bwbohl commented Nov 23, 2020

The mei30To40.xsl does a very good job of adding a <change> corresponding to its execution, thus documenting it has been executed on the file. Nevertheless, this change points from its @resp to an @xml:id, which cannot be resolved against the resulting document.
Ideally, this would be fixed by introducing an entry in the <appInfo> referencing the script, potentially identifying the processor or transformation engine.

@bwbohl
Copy link
Member Author

bwbohl commented Nov 23, 2020

alternatively it could point to this repo and the XSLT in the respective release version

@bwbohl
Copy link
Member Author

bwbohl commented Nov 23, 2020

opinions?

@bwbohl bwbohl changed the title mei v3 to v4 xsltshould generate<appInfo> entry mei v3 to v4 xslt should generate<appInfo> entry Dec 15, 2020
@musicEnfanthen
Copy link
Member

@bwbohl Can we use the same approach as in the mei40to50 XSLT here?

@github-project-automation github-project-automation bot moved this to 🆕 New in ODD meetings Jan 15, 2025
@bwbohl bwbohl changed the title mei v3 to v4 xslt should generate<appInfo> entry mei30To40: should generate<appInfo> entry Jan 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: 🆕 New
Development

No branches or pull requests

2 participants