#9508 closed enhancement (fixed)
Centralized service for validator rules
Reported by: | naoliv | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 14.01 |
Component: | Core validator | Version: | |
Keywords: | Cc: |
Description
Likewise we have an option to select and enable external sources for map paint styles, tagging presets and plugins, couldn't we also have this service for a centralized validation rules?
As an example, we (the Brazilian community) are collecting a series of tests for our needs (if the ref tag follows a specific regex rule, for example) that aren't useful for other countries.
Other countries/regions could do the same.
Rules could be created and enabled for very specialized cases if needed.
The user could enable and disable tests as he needs and also always have the latest version (exactly how the plugins work).
Attachments (0)
Change History (19)
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Component: | External preset → Core validator |
---|---|
Milestone: | → 14.01 |
comment:3 by , 11 years ago
This requires the setup of some Trac machinery on (like for Styles plus http://josm.openstreetmap.de/styles).
Vincent, would you set that up? Then we could integrate the SourceEditor
in JOSM.
comment:4 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Yep, I will do that :) I hope to be able to have enough time for 14.01 milestone (see 9538#comment3 for my idea). If not it will be for 14.02 :)
comment:6 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | assigned → new |
Not sure to have a lot of time to work on it right now...
follow-up: 11 comment:8 by , 11 years ago
@Vincent:
I changed to use #!rules and not #!mapcss. Otherwise surely there will be any trouble in future, especially when we want to add an validator for correct rules. Also completed the server implementation.
comment:9 by , 11 years ago
Seems to work (also can be joined with styles and presets on one page).
Missing:
- Editor support
- Documentation in Wiki, especially I think the possibility, that Styles, Presets and Rules can be on one page should somehow be made clear
- Check if Zip files with multiple elements is only downloaded once when really used multiple times (i.e. style and rule)
follow-up: 12 comment:10 by , 11 years ago
Do we want to manage the JOSM styles in Wiki also? In this case we'd need to add a locking mechanism like for the default entries in Maps-Page.
Currently "Maps" pages get validated, Styles, Presets and Rules not. An validator for the XML formats is easy to add. Is there something for MapCSS?
comment:11 by , 11 years ago
comment:12 by , 11 years ago
Replying to stoecker:
Do we want to manage the JOSM styles in Wiki also?
I don't know if it's worth it.
By the way I'm implementing the GUI stuff right now :)
follow-up: 16 comment:15 by , 11 years ago
I updated the site checker, so it also checks presets and styles and not only maps pages. Also added rules, but for the mapcss formats there is no validation engine available yet. Is there anything which can be used to verify basic validity of data format? Best would be some python code :-)
comment:16 by , 11 years ago
Replying to stoecker:
Is there anything which can be used to verify basic validity of data format? Best would be some python code :-)
For the internal files, we have source:trunk/test/unit/org/openstreetmap/josm/data/validation/tests/MapCSSTagCheckerTest.java
Writing another implementation in Python seems to be a lot of work …
comment:17 by , 11 years ago
@naoliv: do you think you'll be able to share a custom rule before we release the tested version ? It would be great to see at least a community rule on the wiki :)
comment:18 by , 11 years ago
I am working on this :-)
I just need to migrate some rules from the old format (.cfg) to the new one and then I will publish it.
Excellent idea !