You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jena.apache.org by "afs (via GitHub)" <gi...@apache.org> on 2023/10/06 09:03:10 UTC

[I] Jena5: Node Changes [jena]

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

   Changes to Node and related classes (RDF Terms)
   
   * Simplify type hierarchy
   * `LiteralLabel`:
     * Convert to class
     * Restrict use to Node implementation.
     * Make it terms centric.
     * Eager and lazy forms for value calculation
   * Remove BlankNodeId redirection in Node_Blank
   * Remove partial, incomplete RDF 1.0 support


-- 
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: issues-unsubscribe@jena.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org


Re: [I] Jena5 Node Changes [jena]

Posted by "afs (via GitHub)" <gi...@apache.org>.
afs closed issue #2020: Jena5 Node Changes
URL: https://github.com/apache/jena/issues/2020


-- 
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: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org


Re: [I] Jena5 Node Changes [jena]

Posted by "arne-bdt (via GitHub)" <gi...@apache.org>.
arne-bdt commented on issue #2020:
URL: https://github.com/apache/jena/issues/2020#issuecomment-1772332364

   In the Jena5 branch `org.apache.jena.graph.impl.LiteralLabel#valueMode` seems to be fixed to `EAGER`. 
   Did I miss something or are you planning to initialize it via `org.apache.jena.shared.impl.JenaParameters#enableEagerLiteralValidation` in the future?
   Or possibly replace it completely by `enableEagerLiteralValidation` since there is only one usage of `valueMode`?


-- 
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: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org


Re: [I] Jena5 Node Changes [jena]

Posted by "afs (via GitHub)" <gi...@apache.org>.
afs commented on issue #2020:
URL: https://github.com/apache/jena/issues/2020#issuecomment-1772481979

   SPARQL execution has it's own value system.
   
   The ModelAPI and the code in LiteralLabel backing that up, is about mapping some java types.
   
   SPARQL is XSD related, it has wider coverage, no direct java mapping, and has to comply with XQuery/XPath Functions and Operators evaluation. 
   


-- 
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: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org


Re: [I] Jena5 Node Changes [jena]

Posted by "arne-bdt (via GitHub)" <gi...@apache.org>.
arne-bdt commented on issue #2020:
URL: https://github.com/apache/jena/issues/2020#issuecomment-1772431423

   Thank you for the detailed explanation.
   
   So the values would be parsed (lazy initialised) during the SPARQL execution for filters and aggregates, for example?


-- 
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: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org


Re: [I] Jena5 Node Changes [jena]

Posted by "afs (via GitHub)" <gi...@apache.org>.
afs commented on issue #2020:
URL: https://github.com/apache/jena/issues/2020#issuecomment-1772408873

   `LiteralLabel.valueMode` should be "lazy" but as the comment says, further work is needed on the test suite. Looks like it got left in "safe" mode. 
   
   The idea is that if the value isn't needed it isn't calculated. This happens on the parser path including database loading.
   Model API use passing in a value is "eager" by nature. #2050.
   
   `JenaParameters#enableEagerLiteralValidation` is only controlling whether exceptions are thrown or ill-formed literals are allowed. It ought to be be removed and the default behaviour (false) be the only behaviour.
   
   In RDF 1.0, the position of the standard was more that ill-formed literals made everything illegal. But that means a processor must have an understanding of all datatypes including custom ones.
   
    In RDF 1.1, ill-formed literals are treated as local errors. They cause parser warnings.
   
   Generally, I think `JenaParameters` should go away -- #2049.
   I don't have much faith in running with non-default settings.
   
   The OWL related flag can move to somewhere in OntModel code. Ditto the Inf related one.
   


-- 
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: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org


Re: [I] Jena5 Node Changes [jena]

Posted by "afs (via GitHub)" <gi...@apache.org>.
afs commented on issue #2020:
URL: https://github.com/apache/jena/issues/2020#issuecomment-1783150447

   It is probably better to raise specific issues for Node evolution.
   
   Closing this issue based on #2020.
   


-- 
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: issues-unsubscribe@jena.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@jena.apache.org
For additional commands, e-mail: issues-help@jena.apache.org