KVP binding with parameters containing comma

[autermann]

I've observed a strange behaviour: if a parameter contains a comma (for example 6951 - PM2,5 GRIMM - procedure) the KVP parser treats it like a list of identifiers. If I want to request the features of this procedure using the KVP binding, I get two exceptions that the procedure is invalid, as it is split on the , (doesn't matter whether I use %2C or ,):

http://geo.irceline.be/sos/service/kvp?service=SOS&version=2.0.0&request=GetFeatureOfInterest&procedure=6951%20-%20PM2%2C5%20GRIMM%20-%20procedure

<ows:ExceptionReport xmlns:ows="http://www.opengis.net/ows/1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="2.0.0" xsi:schemaLocation="http://www.opengis.net/ows/1.1 http://schemas.opengis.net/ows/1.1.0/owsAll.xsd">
  <ows:Exception exceptionCode="InvalidParameterValue" locator="procedure">
    <ows:ExceptionText>The value '6951 - PM2' of the parameter 'procedure' is invalid</ows:ExceptionText>
  </ows:Exception>
  <ows:Exception exceptionCode="InvalidParameterValue" locator="procedure">
    <ows:ExceptionText>The value '5 GRIMM - procedure' of the parameter 'procedure' is invalid</ows:ExceptionText>
  </ows:Exception>
</ows:ExceptionReport>

Whats the expected behaviour here? Is it illegal to have a comma inside an identifier? Is there some kind of escaping I'm not aware of? Is it a bug in the KVP parser?

[3V3RYONE]

Can anyone confirm if it is the right behavior?
Else we can pick on working on it..