



01/08/2019

Below are the uris I'm considering :
"https://opcfoundation.org/UA/",
"http://siemens.com/automation/OPCUA/",
"https://opcfoundation.org/UA/RockwellAutomation/",
"urn://SVENG-NB04/BeckhoffAutomation/Ua/PLC1",
"urn:xyz/opcfoundation.org/UA/",
"urn:ses2-modbus/opcfoundation.org/UA/",
"urn:SimulatedData/SimulatedData",
"urn:xyz/xyzURI",
"urn:xyz:IEtyilo3-56000",
"urn://siemens.com/automation/OPCUA/SIMATIC_S7/PLC1",
"urn:xyz/opcfoundation.org",
"urn:"
Please let me know if we should consider any other valid uris.

05/30/2017

12.39 UriString says "Any string that conforms to URI as defined by RFC 3986"
URIs in UA are opaque strings that are compared using case sensitive string comparisons.
The comparison rules in RFC 3986 are not used.
1.05.03 adds the following discussion for URIs:
These URIs conform to RFC 3986, however, this specification is very open ended. This clause provides recommendations for constructing these URIs.
The recommendations help ensure that URIs are unique by providing a scope controlled by a single authority (e.g. the domain name) and are human readable. Programs shall always treat URIs as opaque strings that can only be tested for equality with a case sensitive string comparison. URIs should be tag URIs (RFC 4151) or HTTP URLs (RFC 3986). URLs should only be used if they link to actual webpages.
The scheme and domain name portions of the URI are in lower case. URIs may include query subcomponents and/or fragments.
1 Guest(s)