As on the website, there is no mechanism to record changes or persist them: the data is volatile.
Proposed alternative method: deploy URI mappings to the appropriate repository (lod.coop), and have a travis or other continuous-integration mechanism automatically deploy this change to the website.
This will require rewriting the command_create_w3id method in SeOpenData::Cli, and adding a the CI mechanism (to be determined) to the lod.coop repository.
As on the website, there is no mechanism to record changes or persist them: the data is volatile.
Proposed alternative method: deploy URI mappings to the appropriate repository (lod.coop), and have a travis or other continuous-integration mechanism automatically deploy this change to the website.
This will require rewriting the
command_create_w3idmethod in SeOpenData::Cli, and adding a the CI mechanism (to be determined) to the lod.coop repository.