Maximilian Pilz

Additionally the uniqueness is not a given, i.e. "its definition" in the original text would have to be replaced by "a definition" and "the private coding system" by "a private coding system" for it being remotely correct in the current way. Why not write something like Wherever an SDC BASE PARTICIPANT declares a private code as detailed in IEEE Std 11073-10101, the respective SDC BASE PARTICIPANT SHALL specify the semantics of the respective private code by providing a pm:Translation with a @CodingSystem...

For inserts and deletions the MdibVersion has to be incremented, thus it is just a matter of the MdibVersion being transmitted. In case it is transmitted, there can not be both i.e. deletion and insertion of an element with the same handle in a single Report with a fixed MdibVersion, and in case it is not transmitted then you get another issue, because insertions and deletions can be distributed over multiple Reports, not just ReportParts, whereas the Reports also do not necessarily have a specified...

R0886 uses different URI/IRI standard

Yes, it is a potential problem.

Could be fixed by changing the XML Schema links to link to the XML Schema version 1.1 and use RFC 3987. https://sourceforge.net/p/opensdc/ieee11073-10207/246/ https://sourceforge.net/p/opensdc/ieee11073-20701/47/

R0886 uses wrong URI/IRI standard

R0886 uses wrong URI standard

R0886 uses wrong URI standard