updates of markup, adding questions 23 and 27, 28 #3
Conversation
| Furthermore, in practical implementations we advise to “filter” out protocol and schema for comparing IRI identifiers. For example, following IDs should be considered equal: | ||
| - https://admin-shell.io/some_id_example | ||
| - http://admin-shell.io/some_id_example | ||
| - ftp://admin-shell.io/some_id_example |
There was a problem hiding this comment.
ftp really equal to https etc.?
There was a problem hiding this comment.
Idea was to ignore the protocol-specific schema to make implementation practical
There was a problem hiding this comment.
2020-08-24 Meeting Exemplarische Modellierungen: no change needed, this is what should be done when comparing ids.
| (Answered: 2020-08-19) | ||
|
|
||
| **How to refer to semantic concepts of existing standards like VDI 2770 properties or OPC UA companion specifications (e.g. “Serial number” property from OPC UA DI companion spec)?** <!-- ID: 27, 28 --> | ||
| Map concepts to “admin-shell.io” namespace (see [custom identifier best practices](#id18)). Within the concept description itself use “sourceOfDefinition” or “isCaseOf” to link to “original” concept. |
There was a problem hiding this comment.
The link custom identifier best practices is very strange... does not jump to the question but to complete FAQ list. It seems to me that the labels id18 etc. were only introduced in comments and thus are not effective?
| Examples of several suppliers are found at: http://admin-shell-io.com/samples/ | ||
| (Answered: 2020-08-13) | ||
|
|
||
| **What are best practices for creating custom IRI identifiers for generic concepts.** <a name="id18"></a><!-- ID: 18 --> |
There was a problem hiding this comment.
2020-08-24 Meeting Exemplarische Modellierung: check whether still valid, seems to be obsolete, replace by id.... of parent element
2 participants
@aorzelskiGH @BirgitBoss I have added two more questions, also hiddnen ID's for the question for an easy tracibility.