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
we currently expect the type to produce is known and directed from the template - i.e. passed as the argument | xsd('int') will lead to type-assessment + addition of ^^xsd:int
however, we can think about cases where the data itself is typed (as a python int, float, ... datetime, ...) and something like | xsd('auto') could be used to indicate we want to have the python type detected and converted into the matching ^^xsd format
additionally, we could also know about all values to be strings (as they come from csv, yml, json, or xml sources) and ask the template to try out applying a certain order of conversions | xsd('try', ['int', ...] ) to take the first one that actually matches
The text was updated successfully, but these errors were encountered:
we currently expect the type to produce is known and directed from the template - i.e. passed as the argument
| xsd('int')
will lead to type-assessment + addition of^^xsd:int
however, we can think about cases where the data itself is typed (as a python int, float, ... datetime, ...) and something like
| xsd('auto')
could be used to indicate we want to have the python type detected and converted into the matching ^^xsd formatadditionally, we could also know about all values to be strings (as they come from csv, yml, json, or xml sources) and ask the template to try out applying a certain order of conversions
| xsd('try', ['int', ...] )
to take the first one that actually matchesThe text was updated successfully, but these errors were encountered: