Closed phax closed 2 years ago
It might considerate to limitate the data content in advance, I mean, the data processor (e.g. DO) could control data contents, length among others, but the message is already sent, It could be reasonable to have some limitations in advance?, as a first filter, furthermore those limitations were consensuated from the beggining in the model, I guess.
what do you think?
Yes I agree. But I don't know what that exactly means. What technical solutions do you have in mind?
No, nothing to do with a technical solution, just I think that it doesn't hurt to have a data fits limitations
Okay. Yes I agree with that - but I think the length restrictions should all be on the same place. So either all in XSD or all somewhere else. My best guess would be a Schematron, but I know you are reluctant to that
Indeed I am supporter of Schematron, but it was a members decision not to apply that validation layer level for this purposes. So, in this case, maybe we can include more lenght or whatever limitations in the XSDs as workaround
So, if some extra validation or limits update raise we will include them on the fly. May we close this issue by now?
Fine for me
In many cases, you try to limit the XML Schema types with a
maxLength
. In certain cases this is however not done, as e.g. with:AgentName
of typecv:NameType
CanonicalEventCatalogUri
of typexs:anyURI
DataSubjectPerson
andDataSubjectCompany
as they are based on the eIDAS typesIn general it is imho bad practise to length limit the types in the XML Schema - that should be done on an upper level of the application.