When description metadata in different repositories about the same software project / asset / distribtion uses identical URIs or other identifiers, we canderive that the description metadata is about the same software. In this case, it is a matter of agreeing on using common URIs or other identifiers for software, as discussed his issue. As a rule-of-thumb the most recent description metadata (or the one of the most trusted author) should be treated with priority.
When identical software assets and software assets located in different repositories have different identifiers, there is no deterministic way of determining unicity. Heuristics ("matching") will need to be applied and once a URI1 and URI2 have been found to denote the same software project / asset / distribution we can assert that they are identical using owl:sameAs. There is no silver bullet.
Comments
When description metadata in different repositories about the same software project / asset / distribtion uses identical URIs or other identifiers, we canderive that the description metadata is about the same software. In this case, it is a matter of agreeing on using common URIs or other identifiers for software, as discussed his issue. As a rule-of-thumb the most recent description metadata (or the one of the most trusted author) should be treated with priority.
When identical software assets and software assets located in different repositories have different identifiers, there is no deterministic way of determining unicity. Heuristics ("matching") will need to be applied and once a URI1 and URI2 have been found to denote the same software project / asset / distribution we can assert that they are identical using owl:sameAs. There is no silver bullet.