ubl-comment

 View Only
  • 1.  Re: [ubl-comment] UBL v2.1 JSON Schemas

    Posted 02-15-2018 15:02
    Thank you, very kindly, Adam, for your input to our work products.

    I have created this ticket to track the progress of our deliberations
    and results:

    https://issues.oasis-open.org/browse/UBL-172

    We will respond formally when we have a final disposition of your
    valuable comments.

    Thank you, again.

    . . . . . . Ken

    At 2018-02-15 11:35 +0000, Adam Wojnakowski wrote:
    >Hi All,
    >
    >I have been looking at the Universal Business Language specification
    >and the JSON schemas.
    >
    >I found that some schemas that seemed invalid against the JSON
    >schema specification 0.4 - 0.7.
    >
    >I've summarized the encountered issues below. Just wanted to check
    >if this is intended and if so, why? Else, we just wanted to let you know.
    >
    > * Most of the schemas have a misplaced "additionalProperties" keyword.
    >
    > * "additionalProperties" placed as child of "properties", for
    > example: file UBL-UnqualifiedDataTypes-2.1.json, line 207
    > * though not prohibited, the "additionalProperties" keyword for
    > type "array" has no meaning. An example: file UBL-CreditNote-2.1.json, line 58
    >
    > * The "format" keyword with value "date-time" is used together
    > with a "pattern" keyword, but the pattern does not match a valid
    > "date-time" format.
    >
    >According to JSON Schema specification the date-time should comply
    >to ISO 8601 and consist of: full-date
    >T full-time
    >But this will never match some of the patterns. For example:
    >
    > File UBL-UnqualifiedDataTypes-2.1.json, at line
    > 218, defines a property called "DateContent" and the "format" :
    > "date-time" keyword is used.
    > The regex pattern at line 226: ^-*[^T:-]+-[^T:]+$
    >will not allow the ISO 8601 date time, where the time part is
    >required with ':' separators.
    >
    >
    >Best Regards,
    >
    >Adam Wojnakowski
    >Trace Financial Ltd.


    --
    Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/o/ |
    Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
    Streaming hands-on XSLT/XPath 2 training class @ US$45 (5 hours free) |




  • 2.  Re: [ubl-comment] UBL v2.1 JSON Schemas

    Posted 11-08-2018 02:21
    Thank you, again, Adam, for bringing issues to light regarding the
    JSON Schemas for UBL.

    Until the advent of Draft-07 it was not possible to address all of
    your comments. However, when Draft-07 was released, the committee was
    busy with the publishing of UBL 2.2 and the ticket languished.

    Finally, now, the ticket https://issues.oasis-open.org/browse/UBL-172
    has been updated with a proposed disposition of your comments. An
    implementation following this disposition is underway and I will
    update the ticket accordingly.

    Your feedback is most welcome.

    . . . . . . Ken

    At 2018-02-15 10:02 -0500, G. Ken Holman wrote:
    >Thank you, very kindly, Adam, for your input to our work products.
    >
    >I have created this ticket to track the progress of our
    >deliberations and results:
    >
    > https://issues.oasis-open.org/browse/UBL-172
    >
    >We will respond formally when we have a final disposition of your
    >valuable comments.
    >
    >Thank you, again.
    >
    >. . . . . . Ken
    >
    >At 2018-02-15 11:35 +0000, Adam Wojnakowski wrote:
    >>Hi All,
    >>
    >>I have been looking at the Universal Business Language
    >>specification and the JSON schemas.
    >>
    >>I found that some schemas that seemed invalid against the JSON
    >>schema specification 0.4 - 0.7.
    >>
    >>I've summarized the encountered issues below. Just wanted to check
    >>if this is intended and if so, why? Else, we just wanted to let you know.
    >>
    >> * Most of the schemas have a misplaced "additionalProperties" keyword.
    >>
    >> * "additionalProperties" placed as child of "properties", for
    >> example: file UBL-UnqualifiedDataTypes-2.1.json, line 207
    >> * though not prohibited, the "additionalProperties" keyword for
    >> type "array" has no meaning. An example: file UBL-CreditNote-2.1.json, line 58
    >>
    >> * The "format" keyword with value "date-time" is used together
    >> with a "pattern" keyword, but the pattern does not match a valid
    >> "date-time" format.
    >>
    >>According to JSON Schema specification the date-time should comply
    >>to ISO 8601 and consist
    >>of: full-date T full-time
    >>But this will never match some of the patterns. For example:
    >>
    >> File UBL-UnqualifiedDataTypes-2.1.json, at line
    >> 218, defines a property called "DateContent" and the "format" :
    >> "date-time" keyword is used.
    >> The regex pattern at line 226: ^-*[^T:-]+-[^T:]+$
    >>will not allow the ISO 8601 date time, where the time part is
    >>required with ':' separators.
    >>
    >>
    >>Best Regards,
    >>
    >>Adam Wojnakowski
    >>Trace Financial Ltd.


    --
    Contact info, blog, articles, etc. http://www.CraneSoftwrights.com/o/ |
    Check our site for free XML, XSLT, XSL-FO and UBL developer resources |
    Streaming hands-on XSLT/XPath 2 training class @ US$45 (5 hours free) |