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 have foundry-interlex mappings, the internal mappings in the python code, and the mappings from the protcur working sheets. These all need to land in a single place so that we can have version control of these.
The two current sources of mappings in the code itself.
In principle mappings.py has been written so that we can source the mappings from external sources. One issue is that these mappings currently do not account for context, you have to know where it is appropriate to use a particular mapping function.
@jgrethe I'm considering exporting the mappings from InterLex/foundry as a ttl file so that we can version it and integrate it with everything else.
The text was updated successfully, but these errors were encountered:
We have foundry-interlex mappings, the internal mappings in the python code, and the mappings from the protcur working sheets. These all need to land in a single place so that we can have version control of these.
The two current sources of mappings in the code itself.
In principle mappings.py has been written so that we can source the mappings from external sources. One issue is that these mappings currently do not account for context, you have to know where it is appropriate to use a particular mapping function.
@jgrethe I'm considering exporting the mappings from InterLex/foundry as a ttl file so that we can version it and integrate it with everything else.
The text was updated successfully, but these errors were encountered: