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
It would be very useful for us to extend the specification toaccept non default formats for type yearmonth, in the same way as date, time and datetime.
If we extend the specification for type yearmonth, it would be logical to extend it also for type year.
Our usecase is to describe a large database with tableschema, where yearmonth is writen with format YYYYMM and not default YYYY-MM.
This would allow us to validate the data, and to generate fake data with our beta library tsfaker.
The text was updated successfully, but these errors were encountered:
Consider a datetime type property modifier, similar to numeric, integer and boolean, to specify a different EDTF level, e.g. EDTF-0, EDTF-1, EDTF-2
with EDTF-0 as the default, which is ISO-8601-1 (see detail below).
Three conformance levels are defined: level 0, level 1, and level 2. Level 0 specifies features of ISO 8601-1; Levels 1 and 2 specify features described ISO 8601-2.
It would be very useful for us to extend the specification toaccept non default formats for type
yearmonth
, in the same way asdate
,time
anddatetime
.If we extend the specification for type
yearmonth
, it would be logical to extend it also for typeyear
.Our usecase is to describe a large database with tableschema, where
yearmonth
is writen with formatYYYYMM
and not defaultYYYY-MM
.This would allow us to validate the data, and to generate fake data with our beta library tsfaker.
The text was updated successfully, but these errors were encountered: