Procedure names which differ only by case will result in 404 when calling sensor details

[ridoo]

Problem:
Procedure names which differ only by case will result in 404 when calling sensor details

Analysis:
Sensor details are transformed via XSLT to HTML. The transformed file is stored under the generated folder. When requesting the HTML representation of a procedure for which a similar procedure description was generated before, a Windows server will respond with 404 error. With the current workflow, this will cause Windows to indicate that the file exists already while requesting that file via URL won't find the file (because it is case-sensitive).

Example:
Borgsdorf_Q#TagMittel.html vs. Borgsdorf_q#TagMittel.html (points to the same file within Windows file system, ... on Linux file system this is not an issue as file names are case-sensitive there)

Solution:
Include a further name discriminator, e.g. another parameter as discriminator. I expect the phenomenon parameter as best candidate.

Consequences:
Client Providers may consider to clean the generated folder as already transformed files won't be accessible anymore (resources will have different file names when another parameter is being used as discriminator)