It would be usefull to distinguish a posteriori if an id was autogenerated or user input
The translator could add a prefix like "id_".
Then auto id could be regenerated on translation if needed with a special flag or the kleio element (ignore-auto-ids). This would clean up auto ids when sources or acts change their ids that were used for auto id generation.
The problem would be if those autogenerated ids were already used in record linking. This could be handled with a id changes export file (icef) with two columns. The icef file name with be tagged so with the translations number of the kleio file: b1686_icef_45.csv. meaning id changes made in the 45 translation of b686.cli
"Blank node identifiers are local identifiers that are used in some concrete RDF syntaxes or RDF store implementations. They are always locally scoped to the file or RDF store, and are not persistent or portable identifiers for blank nodes."
"Systems may wish to mint Skolem IRIs in such a way that they can recognize the IRIs as having been introduced solely to replace blank nodes. This allows a system to map IRIs back to blank nodes if needed."
It would be usefull to distinguish a posteriori if an id was autogenerated or user input
The translator could add a prefix like "id_".
Then auto id could be regenerated on translation if needed with a special flag or the kleio element (ignore-auto-ids). This would clean up auto ids when sources or acts change their ids that were used for auto id generation.
The problem would be if those autogenerated ids were already used in record linking. This could be handled with a id changes export file (icef) with two columns. The icef file name with be tagged so with the translations number of the kleio file: b1686_icef_45.csv. meaning id changes made in the 45 translation of b686.cli