[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (UBL-172) JSON schema incompatibilities
Ken Holman created UBL-172: ------------------------------ Summary: JSON schema incompatibilities Key: UBL-172 URL: https://issues.oasis-open.org/browse/UBL-172 Project: OASIS Universal Business Language (UBL) TC Issue Type: Bug Components: Naming and Design Rules (NDR) Reporter: Ken Holman Assignee: Ken Holman Priority: Minor https://lists.oasis-open.org/archives/ubl-comment/201802/msg00000.html Adam Wojnakowski: Trace Financial Ltd.: 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. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]