In original (and thus in the normalized) Wikipathways data, there are e.g. different type EntityReference objects (Dna/Rna/ProteinReference) in multiple files that have the same Identifiers.org based URI.
And cPath2 Merger did not replace such URIs with new ones (to use PC2 xml:base), which causes then various range violation errors (mostly about SPE.entityReference property) during the merge of these multiple models into a single target model...
PS:
Looks, we should only use the Identifiers.org URIs for valid UnificationXrefs (e.g., UniProt, ChEBI) and PublicationXrefs (PubMed), but not for any EntityReference nor ControlledVocabulary types...
In original (and thus in the normalized) Wikipathways data, there are e.g. different type EntityReference objects (Dna/Rna/ProteinReference) in multiple files that have the same Identifiers.org based URI. And cPath2 Merger did not replace such URIs with new ones (to use PC2 xml:base), which causes then various range violation errors (mostly about SPE.entityReference property) during the merge of these multiple models into a single target model...
PS: Looks, we should only use the Identifiers.org URIs for valid UnificationXrefs (e.g., UniProt, ChEBI) and PublicationXrefs (PubMed), but not for any EntityReference nor ControlledVocabulary types...