Skip to content

Use mf:requires for optional test behavior #365

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

Closed
gkellogg opened this issue Jan 29, 2020 · 5 comments · Fixed by #368
Closed

Use mf:requires for optional test behavior #365

gkellogg opened this issue Jan 29, 2020 · 5 comments · Fixed by #368

Comments

@gkellogg
Copy link
Member

See #337 (comment). This would be useful for rdfDirection and HTML processing.

@kasei
Copy link
Contributor

kasei commented Jan 30, 2020

Would this be useful for tests involving "generalized RDF"? I build on a stack that has no support for such data, so currently try to key off of the produceGeneralizedRdf option in the test manifests. It would be nice to have that explicitly indicated as a required feature to be able to evaluate the test.

@gkellogg
Copy link
Member Author

Yes, we should add something for generalizedRdf, HTML and the variations on base direction.

@davidlehn
Copy link
Contributor

If feature flags are being designed, might be useful if they could also be used for a formal or informal implementation feature detection API for general application use.

@gkellogg
Copy link
Member Author

The SPARQL mf:requires, and it's various values, are described here.

gkellogg added a commit that referenced this issue Feb 12, 2020
…quirements defined in the test vocabulary.

Fixes #365.
@gkellogg
Copy link
Member Author

@kasei see #368.

gkellogg added a commit that referenced this issue Feb 14, 2020
…quirements defined in the test vocabulary.

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

Successfully merging a pull request may close this issue.

3 participants