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
Using underscores potentially eases Python users' life by allowing them to type IDs as variable names (say `dax.datasets.noaa_weather_data_jfk_airport). If it's not possible, we would have to do a dash-underscore conversion on one end.
The text was updated successfully, but these errors were encountered:
We'll check with the OpenAIHub team to see if this would pose a problem. My understanding is that we used this convention to mimic what was implicitly done in https://github.ibm.com/IBMCode/Code-Data, where the id is the slug name.
For MLX we need to ensure that given an id that contains underscores (_), the generated DLF/DataShim YAML has a metadata.name that conforms to DNS-1123 subdomain naming restrictions (must consist of lower case alphanumeric characters, - or .)
Currently IDs use dashes instead of underscores:
exchange-metadata-converter/dax-data-set-descriptors/jfk.yaml
Line 1 in 7160fd4
Using underscores potentially eases Python users' life by allowing them to type IDs as variable names (say `dax.datasets.noaa_weather_data_jfk_airport). If it's not possible, we would have to do a dash-underscore conversion on one end.
The text was updated successfully, but these errors were encountered: