afs opened a new issue, #3615:
URL: https://github.com/apache/jena/issues/3615

   Node.matches and the related Triple.matches functionality is related to 
pre-SPARQL, and pre-RDQL, query system in jena-core.
   
   jena-core does not use this functionality. The contract is unclear - 
experimentally it is "node.sameValueAs".
   
   `Node.sameValueAs` is the contact for the java mapping in model API so it 
affects literals.
   
   Ther are a total of 51 errors. 13 of these are non-test errors. All are 
related to providing the interface operation except for `MinimalStoreStrategy` 
(`org.apache.jena.mem2.store.roaring`).
   
   Proposal:
   
   The principle is that `Triple`/`Node` are the structures in RDF 
Concepts,`Node` being "RDF Term".
   
   Deprecated for-removal, `Triple.getMatchSubject`, 
`Triple.getMatchPredicate`, and `Triple.getMatchObject`.
   They are getters that perform "anyToNull" on the slot. These might be used 
by some user code. Removal would happen at 6.1 or later.
   
   Ensure Jena code does not use `Triple.getMatch*`.
   
   Remove `Triple.matches` and `Node.matches`.
   
   See also:
   https://lists.apache.org/thread/y2hphd9cjbq3vlv2fr1hhj77sjjnvdwg


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to