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

define convention for expressing Matroska fragments in readable text #129

Open
dericed opened this issue May 26, 2017 · 2 comments
Open

define convention for expressing Matroska fragments in readable text #129

dericed opened this issue May 26, 2017 · 2 comments
Labels

Comments

@dericed
Copy link
Contributor

@dericed dericed commented May 26, 2017

For instance to explain the examples in here https://github.com/Matroska-Org/matroska-specification/blob/3e689519b9a84e508d98b1dcbd97d17744e144a3/chapters.md#example-1--basic-chaptering. This issue supersedes this discussion.

@robUx4
Copy link
Contributor

@robUx4 robUx4 commented Jul 14, 2017

That seems to be more related to expressing EBML "fragments" in readable text. Once we have that Matroska can use it. It may refine how to define certain Binary data like the Block and BlockSimple.

@robUx4
Copy link
Contributor

@robUx4 robUx4 commented Feb 13, 2022

IMO this should be in a separate document. There can be many formats to describe a binary format in text (json, xml, yaml, etc). That should influence (or block) how the binary format is defined.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants