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.

Sign up for GitHub

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

Jump to bottom

Deprecate the extent@action attribute, templates are sufficient (for discussion) #61

Closed
prushforth opened this issue Jun 4, 2020 · 2 comments · Fixed by #77
Closed

Deprecate the extent@action attribute, templates are sufficient (for discussion) #61

prushforth opened this issue Jun 4, 2020 · 2 comments · Fixed by #77

Comments

@prushforth
Copy link
Member

The extent@action attribute was created as a first pass at conceiving an encoding of map and layer behaviour in markup, but it turns out that templated links provide a more faithful representation of how maps are actually implemented on the Web today.

As such, it is proposed to deprecate and remove the extent@action attribute from the MapML spec.
@prushforth prushforth mentioned this issue Jul 3, 2020
Closed
@Malvoz
Copy link
Member

Malvoz commented Jul 10, 2020

I take it as <link tref=""> is sufficient for content retrieval, does this mean the other form related attributes enctype and method can be removed as well?

@prushforth
Copy link
Member Author

does this mean the other form related attributes enctype and method can be removed as well?

Yes

@prushforth prushforth mentioned this issue Jul 18, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove deprecated input types xmin,ymin,xmax,ymax,projection. prushforth/MapML-Specification
2 participants
@prushforth @Malvoz