Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve XDS Validations #279

Open
unixoid opened this issue Dec 10, 2019 · 5 comments
Open

Improve XDS Validations #279

unixoid opened this issue Dec 10, 2019 · 5 comments
Labels

Comments

@unixoid
Copy link
Member

unixoid commented Dec 10, 2019

As reported in https://groups.google.com/forum/#!topic/ipf-user/FTvCuqXSaJ4:
According to ITI TF-3:4.1.4, we have to check that the SubmissionSet contains Associations to all its DocumentEntries, Folders, and Folder-DocumentEntry Associations.

@unixoid unixoid added the ihe label Dec 10, 2019
@unixoid
Copy link
Member Author

unixoid commented Jan 23, 2020

Subtask 1 -- Check completeness of XDS Associations, see above

Subtask 2 -- Check uniqueness of uniqueIDs
As reported in https://groups.google.com/forum/#!topic/ipf-dev/Bj58Vl-7IeI:
XDSRegistryDuplicateUniqueIdInMessage error shall be returned when
"A uniqueId value was found to be used more than once within the submission. The errorCode indicates where the error was detected. The codeContext shall indicate the duplicate uniqueId"

@unixoid unixoid changed the title Check completeness of XDS Associations Improve XDS Validations Jan 23, 2020
Thopap added a commit that referenced this issue May 26, 2020
* Check uniqueness of uniqueIDs
@FinOxy
Copy link

FinOxy commented Jul 1, 2020

Current OIDValidator regexp require two digit at the begining of OID, but for example ISO root start with one digit.

See https://wiki.ihe.net/index.php/OID_Registration and https://en.wikipedia.org/wiki/Object_identifier

@ohr
Copy link
Member

ohr commented Jul 1, 2020

Note quite. It allows one or two digits at the beginning.
Which is a bit lax, as OIDs may only start with 0, 1 or 2.

@FinOxy
Copy link

FinOxy commented Jul 2, 2020

I disagree. You can test it here https://regexr.com/38m0v
Better version of regexp would be "([1-9]|[1-9][0-9])(.(0|([1-9][0-9])))+" or this most recent "([1-9]|[1-9][0-9])(\.(0|([1-9][0-9])))+"
Which OIDs start with zero?

@Thopap
Copy link
Member

Thopap commented Aug 24, 2020

@FinOxy: In the wikipedia link you have mentioned (e.g. https://en.wikipedia.org/wiki/Object_identifier) and also the ISO 9834 specification, you can see that the root arc "0" belong to ITU-T, here a official Oid from that tree: http:https://www.oid-info.com/cgi-bin/display?oid=0.9.2342.19200300.100.4 So the first digit can be only a 0,1 or 2 - so the regex is ok (but sure not perform according to the iso spec).

The java JDK also bring a Oid class (org.ietf.jgss.Oid) which contain a strong validation (also following certain other rules of ISO 9834). We could think about replacing the regex with the validation by the Oid class constructor, but since validation is quiet often performed and might be performance critical, the regex might be sufficient for our purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants