Skip to content

feature detection #141

@bergos

Description

@bergos

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']

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions