-
Notifications
You must be signed in to change notification settings - Fork 19
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
Unit of Meansurement (uom) rendering issue #415
Comments
I've seen both cases. The file I don't think HNAP enforces it, at least I don't find that in the specification. In any case, the code enforcing it is iso19139.ca.HNAP/src/main/plugin/iso19139.ca.HNAP/update-fixed-info.xsl Lines 915 to 929 in adcfe95
Maybe can be added a variable in the xsl to enforce the URL or use the provided value as it is. |
Do you mean in the current HNAP schema enforcing logic which is the /update-fixed-info.xsl We should not append the url to the unit. We should use the unit as is? What I understand it the codelist in HNAP which been pointed is same as what ISO19139 looks like. So I dont see any advantage to add such url in front of the unit like: "http://standards.iso.org/ittf/PubliclyAvailableStandards/ISO_19139_Schemas/resources/uom/gmxUom.xml#m" I have created a pull request to get this url removed in update-fixed-info #417 and make it same as how indexing works iso19139.ca.HNAP/src/main/plugin/iso19139.ca.HNAP/index-fields/index.xsl Lines 576 to 578 in adcfe95
|
The current UI is not able to handle HNAP uom spec
The ISO13139 standard has no such url as part of the uom part.
So wonder why HNAP needs such url and how to make the UI handle such url?
The text was updated successfully, but these errors were encountered: