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
I would like to use both slots and attributes in one schema. I was having issue with creating attributes column (see #128 ), but I found a cli option --use-attributes, but if I use this option it looks like everything is treated as attributes and I would like to have an option to do both.
For example, for a table:
| Proposed BICAN Field | SubGroup/LinkML Class Name | Range |
|----------------------|----------------------------|---------|
|> slot | class | range |
|----------------------|----------------------------|---------|
| attr1 | class1 | integer |
| attr2 | class2 | float |
| slot1 | | float |
| slot1 | class1 | |
I would think that attr1 and attr2 could be treated as attributes but slot1 that has two rows (one with class the other without) could be treated as a slot
The text was updated successfully, but these errors were encountered:
I think we should allow for explicit control on a per-slot basis as you suggest, as well as global. I think the most straightforward way would be to allow attribute in place of slot
I would like to use both
slots
andattributes
in one schema. I was having issue with creatingattributes
column (see #128 ), but I found a cli option--use-attributes
, but if I use this option it looks like everything is treated asattributes
and I would like to have an option to do both.For example, for a table:
I would think that
attr1
andattr2
could be treated asattributes
butslot1
that has two rows (one with class the other without) could be treated as aslot
The text was updated successfully, but these errors were encountered: