Unlike #24, which would deal primarily with data entry, the concern with smushing is taking URIRefs that are already in a graph and marking them as referring to the same entity (i.e., with an owl:sameAs statement) and, optionally, replacing triples having a secondary identifier with the preferred identifier.
These tools must support an algorithm for smushing through analysis of existing owl:sameAs links in order to entail transitive sameness.
The tools must also support at least one other algorithm that works on a graph as a whole (e.g., smushing based on owl:InverseFunctionalProperty).
The tools must support a manual 'smush' of two identifiers as commanded by a user
Manual smushing support should include a means for automated checking of the validity of the graph according to certain rules.
Unlike #24, which would deal primarily with data entry, the concern with smushing is taking URIRefs that are already in a graph and marking them as referring to the same entity (i.e., with an
owl:sameAsstatement) and, optionally, replacing triples having a secondary identifier with the preferred identifier.These tools must support an algorithm for smushing through analysis of existing
owl:sameAslinks in order to entail transitive sameness.The tools must also support at least one other algorithm that works on a graph as a whole (e.g., smushing based on owl:InverseFunctionalProperty).
The tools must support a manual 'smush' of two identifiers as commanded by a user
Manual smushing support should include a means for automated checking of the validity of the graph according to certain rules.
Relates to #24