We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
i am in favor of a plainer-text format for the manifest. this is an opportunity to do better than ivy/repo.
like skdb's. the diffs are much awesomer, more hand-editable...
very diffable (text-wise, but also graph-wise), searchable, and the world doesn't need another xml schema.
though would introduce a dependencies on non-stdlib. sad. however, we should be pip installable anyway.
perhaps a plugin structure for manifest? the core code shouldn't be monkeying with xml/rdf anyway.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
i am in favor of a plainer-text format for the manifest. this is an opportunity to do better than ivy/repo.
Alternate formats
YAML
like skdb's. the diffs are much awesomer, more hand-editable...
YAML-RDF, N3/Turtle
very diffable (text-wise, but also graph-wise), searchable, and the world doesn't need another xml schema.
BAD
though would introduce a dependencies on non-stdlib. sad. however, we should be pip installable anyway.
Implementation
perhaps a plugin structure for manifest? the core code shouldn't be monkeying with xml/rdf anyway.
The text was updated successfully, but these errors were encountered: