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

feature detection #141

Open
bergos opened this issue Jan 21, 2019 · 1 comment
Open

feature detection #141

bergos opened this issue Jan 21, 2019 · 1 comment

Comments

@bergos
Copy link
Member

bergos commented Jan 21, 2019

As proposed in #136 new features should get it's own spec. Maybe it would be good if we define a standard way for feature detection in this spec, as it will be the core spec other spec will refer to.

In #123 @jacoscaz proposed this:

Not everything can be standardized. Any feature that is relevant to only a few use cases, such as the advanced filtering mentioned above, might not be everyone's cup of tea. However, it would be nice to have a standardized way to advertise such features, so that other components using RDF/JS interfaces would be able to make use of these non-standard features when possible while normally defaulting to standard expectations. Something like the following could work:

source.supportedFeatures = ['source-filters']

@jacoscaz
Copy link
Contributor

jacoscaz commented Jul 16, 2020

Based on some thinking in https://github.com/rdfjs/data-model-spec/issues/166 and others, I guess we could have a supportedInterfaces property pointing to which interfaces are supported by a given object? This would require interfaces to be free of optional methods IMHO. Which I would be fine with, I think.

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

No branches or pull requests

2 participants