Closed tomkralidis closed 1 year ago
- changing from
"pattern": "^+[1-9]{1}[0-9]{3,14}$"
to"^\\+[1-9]{1}[0-9]{3,14}$"
, but I'm not sure if this is expected per se. It is critical that we provide a few examples for this property. Can someone provide?
This is expected. It just fixes a regexp from invalid to valid.
Here is an example: https://github.com/opengeospatial/ogcapi-records/issues/263#issuecomment-1557046209
Is this a relevant example then? I can add to PR but just wanted to make sure :)
What is a "relevant" example? It's just a random example of a phone number...
Thanks. I wanted to ensure it's random so that someone is not receiving years of phone calls because of the specification :)
~Not sure, 83 is the prefix of University of Münster. I haven't checked whether 98765 is used. But the issue always exists. A phone number that is "random" and "unused" right now may be used tomorrow.~
Hah, I found some example phone numbers that are reserved as examples: https://softwareengineering.stackexchange.com/questions/376535/whats-the-phone-number-equivalent-of-example-org
So you can use:
Updated to +14165550142
As part of automated WMO Core Metadata Profile (WCMP2) validation, we are implementing a schema which extends the Records model per https://github.com/wmo-im/wcmp2/blob/3aabc432ae2d66fd408a54475ef41a286058717a/schemas/wcmpRecordGeoJSON.yaml
We create a bundled schema of the resulting record schema using Stoplight Studio. Steps can be found at https://github.com/wmo-im/wcmp2/blob/main/schemas/README.md (note: if anyone is aware of existing Python tooling that can automate conversion from YAML to JSON [including reference resolving] I'll gladly switch).
We then use check-jsonschema to perform validation of instance documents against the bundle as part of CI workflow.
check-jsonschema
is reporting the following errors with the schema proper:type: null
totype: "null"
fixes the error"pattern": "^+[1-9]{1}[0-9]{3,14}$"
to"^\\+[1-9]{1}[0-9]{3,14}$"
, but I'm not sure if this is expected per se. It is critical that we provide a few examples for this property. Can someone provide?PR to fix is in #262, but I'd like some feedback on the impact of these changes related to other tooling.
cc @pvretano @kalxas @m-mohr