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
Currently all configuration fields are pseudo randomly generated. It would be better to unify these fields and deliver a consistent naming scheme.
I propose that we should create a json-ld context that denotes the ontology used in the configuration. Certainly look at the following ontologies
It would be amazing to create a stream datatype that carries some type in some serialization and use this with fno parameters!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Currently all configuration fields are pseudo randomly generated. It would be better to unify these fields and deliver a consistent naming scheme.
I propose that we should create a json-ld context that denotes the ontology used in the configuration.
Certainly look at the following ontologies
It would be amazing to create a stream datatype that carries some type in some serialization and use this with fno parameters!
The text was updated successfully, but these errors were encountered: