-
Notifications
You must be signed in to change notification settings - Fork 5
Use Schema attributes for version info #110
Copy link
Copy link
Open
Labels
SchemaRelated to the EBML schemataRelated to the EBML schematadevelopmentDevelopment issues: package deployment, project organization, etc.Development issues: package deployment, project organization, etc.enhancementNew feature or requestNew feature or request
Description
Activity
Metadata
Metadata
Assignees
Labels
SchemaRelated to the EBML schemataRelated to the EBML schematadevelopmentDevelopment issues: package deployment, project organization, etc.Development issues: package deployment, project organization, etc.enhancementNew feature or requestNew feature or request
In schemas, we currently use default values in some of the
EBMLchild elements to define version info (DocType,DocVersion,ReadVersion, etc.). This is not the best place for it; the user has to root around to find the values when updating the schema, and it's a bit of a hack.Some of the schemata have attributes in the root
<Schema>element, like:This is a better place for this sort of information, but it isn't actually used at this point. The schema parser should read these, and fall back to the
<EBML>child element defaults if they aren't present (for backwards compatibility).The default values of the
EBML*child elements should also be elsewhere, either as additional<Schema>attributes, or maybe elements in<SchemaInfo>with the same name as the EBML element, like:These are essentially constants, though, so they should be optional.