Add VVO to TRIAS-Providers.md

[GerdC]

I have tested this API, no key needed.

[derhuerst]

Can you also add the respective JSON file describing the API?

You can check bwegt-trias.json or vrn-trias.json as a template.

[GerdC]

I thought about that before this pull request.

I have no idea what the official coverage is, I'm pretty sure it is not possible to ask TRIAS API about the coverage.
Short tests showed it is possible to route to Kiel and to Constance, so it should be DELFI-land.

I have no client that uses / validates / tests these JSON files.
I'm reluctant providing something I can't test.

[derhuerst]

I have no idea what the official coverage is, I'm pretty sure it is not possible to ask TRIAS API about the coverage. Short tests showed it is possible to route to Kiel and to Constance, so it should be DELFI-land.

There are currently three levels of coverage that you can express. If you're not sure, pick a rather conservative estimation (e.g. anyCoverage only).

I have no client that uses / validates / tests these JSON files. I'm reluctant providing something I can't test.

The CI validates these, so you'll see after pushing.

Locally, you can use any JSON Schema validator by specifying schema.json as the schema file.

[GerdC]

added vvo-trias.json.
It validates. Checked version 1.1, rendered coverage on my app to check.

Only unchecked guess is "LocationInformationRequest" and "supportedLanguages": [ "en", "de" ]. That is copied from bwegt-trias, which is also a version 1.1 form MENTZ.

[GerdC]

Looks good for me. Asking for https separately.

[GerdC]

I asked VVO to support https

[derhuerst]

Thanks!