Change usage of double colon to single colon for scalar structured identifiers

[oskogstad]

Introduction

There's currently a disparity between "party" and "serviceResource" encoding.

    "serviceResource": "urn:altinn:resource:super-simple-service",
    "party": "urn:altinn:organization:identifier-no::310702749",

The rest of Altinn is using a single colon, and treating the last item as the value within the NSS-part of the URN in scenarios where we need to split this into eg. XACML attribute ids and values. Using a single colon is also more in line with typical NSS-usage (see examples on the wikipedia-page).

If we for some reason need to have a literal colon as the value, it should be percent-escaped, but no known case for this currently exists so code for this (handling escaping) should not be added at this time.

Tasks

Preview Give feedback

1. Change Party identifier separator in dialog and events, as well as splitting logic, to use a single colon
2. Create a migration script to fix existing dialogs (do not care about outbox)
3. Notify users in public dev-Slack
4. Prepare documentation (if relevant - either update working document, or add a new file in docs)
5. Add e2e-test (if relevant)

[elsand]

I've grown ambivalent to the whole double colon thing. While it provides a fairly robust way of splitting namespace from value in a scalar string, it's a bit unorthodox and not really used anywhere else (not even in Altinn). We should consider keeping this being a single colon, and always consider the last element when splitting by ":" to be the value, and expect any literal colons within the value to be URL encoded (ie %3A). Thoughts?

[elsand]

I've discussed this briefly with @altinnadmin, and we want to change this back to using just a single colon. Ie. splitting logic will have to change from splitting on "::" to splitting on a single colon and treat the last item as the value. I'll go ahead and change this issue to reflect this.