Skip to content

Define and use contents of <SchemaInfo> #111

Description

@StokesMIDE

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    SchemaRelated to the EBML schematadevelopmentDevelopment issues: package deployment, project organization, etc.documentationenhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions