Further questions on SMP WD06

[Philip Helger <philip@helger.com>]

Hi guys,

while trying to implement the SMP 2 specs in Java, I stumbled upon a few
issues and questions (based on WD 06), that might be relevant for you:

* Chapter 4.3.4 - The data model allows to intermix "Endpoint" and
"Redirect" model - that will most likely cause confusion in practise and
requires additional profiling. Was that done by purpose? Is it the goal
for users of the specification to create profiles before using it?
According to the text is states "either or". So my suggestion is to add
an additional "<xs:choice>" in the XSD around "Endpoint" and "Redirect"
elements.

* Chapter 4.3.6 - the terminology "SHOULD" in "ActivationDate" and
"ExpirationDate" is causing problems in production, because clients are
not enforced to reject expired elements. Maybe you can consider changing
the "SHOULD" to "MUST" and add a statement, that if the elements are not
present, it means they are valid since forever or until infinity.

* Chapter 4.3.6 - editorial - the description of elements
"ActivationDate" and "ExpirationDate" refers to "ExpirationData" instead
of "ExpirationDate"

* Chapter 4.3.7 - the documentation states "0..1" "Certificate"
elements, but the XSD uses "0..unbounded" - what is true?

* Chapter 4.3.8 - Element "ContentBinaryObject" has an attribute
"mimeCode" - is there a codelist of registered MIME code values and
their meaning that MUST be supported?

* Appendix B - editorial - the XML code has one closing angle bracket
too much (the very last char)

* Another question on XSD: what is the motivation on having the 2 basic
types "ParticipantIDType" and "IDType" that have the same semantics?
Can't the types be merged (without changing the element names)?

hth and BR,

 Philip

-- 
Philip Helger

Skype: phelger
Twitter: @philiphelger
GitHub: https://github.com/phax