VSS uses dot as delimiter between node names.
As that will be problematic when the VSS path is used in an HTTP URL, the spec mandates that slash shall be used as delimiter in paths. The spec also mentions the fact that VSS uses dot delimiters, and that it is up to the VISS server to handle the translation between VISS and VSS.
Using dot as delimiter is only a problem in the path component of HTTP URLs, it is e. g. possible to use in an HTTP ULR query component, in Websocket payloads, and in responses for both HTTP and Websocket.
The amount of delimiter translations, in both directions, would be reduced if the specification only mandated slash delimiter usage in HTTP URL path components, and left it optional is all other usages.
I think we should change from mandatory everywhere in VISS to the latter proposal.
VSS uses dot as delimiter between node names. As that will be problematic when the VSS path is used in an HTTP URL, the spec mandates that slash shall be used as delimiter in paths. The spec also mentions the fact that VSS uses dot delimiters, and that it is up to the VISS server to handle the translation between VISS and VSS. Using dot as delimiter is only a problem in the path component of HTTP URLs, it is e. g. possible to use in an HTTP ULR query component, in Websocket payloads, and in responses for both HTTP and Websocket. The amount of delimiter translations, in both directions, would be reduced if the specification only mandated slash delimiter usage in HTTP URL path components, and left it optional is all other usages. I think we should change from mandatory everywhere in VISS to the latter proposal.