You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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']
The text was updated successfully, but these errors were encountered:
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.
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:
The text was updated successfully, but these errors were encountered: