Skip to content

Capability: JS independence #32

@AmeliaBR

Description

@AmeliaBR

This issue is for discussion of the map viewer capability (potential requirement) “Display a basic map without JavaScript”.


From the 2015 use cases report's list of limitations of current tools:

Reliance on script
All of the above Web map techniques depend on JavaScript, and so Web maps, considered as a feature of the Web, require a scripted environment to even exist. JavaScript on the Web embodies the 'code-on-demand' optional constraint of the Web. Thus a feature such as Web maps depends on an optional feature of the Web itself. When the option is not available or fails, the Web itself fails, or does not possess this feature. The fact that a sophisticated, not to say important, feature such as Web maps can be enabled by virtue of an optional feature of the Web is however, a testament to the magical qualities of the Web. Nevertheless, dependence on this facet of the Web has lead to a situation where there are no inherent map semantics in HTML, or on the Web.

Turning this around, a capability of a web map viewer is its ability to provide at least basic function when JS is disabled or fails for other reasons.

Metadata

Metadata

Assignees

No one assigned

    Labels

    discussion: capabilitya specific capability or feature: should it be included? what details? should it be a requirement?section: map viewerCapabilities & use cases for declarative map viewer widgetsstatus: editor's draftthere's a draft section in the report that corresponds to this discussion

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions