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.

Sign up for GitHub

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

Jump to bottom

Define and use contents of <SchemaInfo> #111

Open
StokesMIDE opened this issue Mar 25, 2022 · 0 comments
Open

Define and use contents of <SchemaInfo> #111

StokesMIDE opened this issue Mar 25, 2022 · 0 comments
Labels
development Development issues: package deployment, project organization, etc. documentation enhancement New feature or request Schema Related to the EBML schemata

Comments

@StokesMIDE
Copy link
Member

Some schemata have a header element, <SchemaInfo>. The intention was to have it contain metadata, but was never fully developed; it's arguably useful to humans, but is currently ignored by the schema parser.

Two things should be done:

  1. Specify all the child elements. Currently, schemata use <Author> and <Description>. Maybe we should use the standard set of Python module 'dunder' variables as the model.
  2. Get Schema to parse the info. Some can be ignored and left for humans, but a few things are useful.

This arguably ties into #110.
@StokesMIDE StokesMIDE added enhancement New feature or request Schema Related to the EBML schemata documentation development Development issues: package deployment, project organization, etc. labels Mar 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
development Development issues: package deployment, project organization, etc. documentation enhancement New feature or request Schema Related to the EBML schemata
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@StokesMIDE