You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 23, 2022. It is now read-only.
Original issue 28 created by josiahpeters on 2012-05-02T16:56:56.000Z:
I noticed that the validator wasn't validating a message that I considered to be valid.
My message had a geocode value of:
<geocode>
<valueName>profile:CAP-CP:Location:0.4</valueName>
<value>2435027</value>
</geocode>
Which according to the spec should be valid? Looking at the validator code I'm suspecting that my change might solve that, however I did not check out the entire repo to build and run the test cases. Hopefully this helps.
Thanks, Josiah! The Canadian validation code hadn't been updated in a while. I've pushed a new validator with your fix and will be submitting the patch to the repo.
Original issue 28 created by josiahpeters on 2012-05-02T16:56:56.000Z:
I noticed that the validator wasn't validating a message that I considered to be valid.
My message had a geocode value of:
<geocode>
<valueName>profile:CAP-CP:Location:0.4</valueName>
<value>2435027</value>
</geocode>
Which according to the spec should be valid? Looking at the validator code I'm suspecting that my change might solve that, however I did not check out the entire repo to build and run the test cases. Hopefully this helps.
Joey Peters
joey@mystateusa.com
The text was updated successfully, but these errors were encountered: