From 0f90990ba04de2b4a6b8c6191a8ad07e8c54aa48 Mon Sep 17 00:00:00 2001 From: Sebastian Friedl Date: Mon, 1 Jul 2024 14:27:45 +0200 Subject: [PATCH] add URL-Encoding for BrowseNames --- Spec.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Spec.md b/Spec.md index dc403da..a133785 100644 --- a/Spec.md +++ b/Spec.md @@ -81,7 +81,9 @@ For the umati Dashboard, this topic structure is restricted as follows: - ` = Expanded NodeId of the object representing the machine` - ` = BrowsePath` -The BrowsePath in the DataSetWriter is built with a "." between each BrowseName. The BrowseNames use only the namespace index to avoid collisions. For identification of the object, the name of the DataSet with expanded NodeId must be used. +The BrowsePath in the DataSetWriter is built with a "." between each BrowseName. The BrowseNames use only the namespace index to avoid collisions. +Special character as `'/''.''<'| '>' | ':' | '#' | '!' | '&' ` in the `name` field of the BrowseName need to encode by [URL-Encoding](https://de.wikipedia.org/wiki/URL-Encoding) using an underscore instead of a '%'. +For identification of the object, the name of the DataSet with expanded NodeId must be used. If two node has the same BrowsePath a iterator ("_Number") can be send to avoid collisions (e.g, `3:Partent.3:Tool_1`, `3:Partent.3:Tool_2` `3:Partent.3:Tool_3` ) ### Examples