Dear Andy

>From my understanding both solutions should work. Is it possible to have these 
>using riot command line tool?

I ask about "literals-as-subject triples" because this is the line which riot 
reports as error.

Currently I delete rdfs:range from datatype properties in the ontology before 
inferencing to eliminate the problem.

Thanks in advance!

Sincerely,

17 января 2025, 12:40:50, От "Andy Seaborne" <a...@apache.org>:

> Hi Larysa,
> 
> Are you looking to simply not get the literals-as-subject triples or 
> have an RDF-legal blank node form:
> 
> https://www.w3.org/TR/rdf12-semantics/#entailment_rules
> 
> Instead of:
> 
> ex:a ex:p "literal" .
> ex:p rdfs:range xsd:string .
> -----
> "literal" rdf:type xsd:string
> 
> then this is possible:
> 
> ex:a ex:p "literal" .
> ex:p rdfs:range xsd:string .
> -----
> ex:a ex:p "literal" .
> ex:a ex:p _:b .
> _:b rdf:type xsd:string .
> 
>      Andy
> 
> On 16/01/2025 12:52, Larysa Zhuchyi wrote:
> > Dear Martynas
> > 
> > I infer using riot triples like "2022-08-11”^^xsd:date rdf:type xsd:date . 
> > Then cannot merge the corrupted file with valid one using riot. The issue 
> > 1720 is not closed. Does this mean that triples of this kind is an expected 
> > behavior of riot?
> > 
> > Is there any way to avoid this? Maybe with any other jena command line 
> > tools.
> > 
> > Thanks in advance!
> > 
> > 16 января 2025, 13:33:07, От "Martynas Jusevičius" <marty...@atomgraph.com>:
> > 
> >> Hi Larysa,
> >>
> >> Maybe this issue? https://github.com/apache/jena/issues/1720
> >>
> >> On Thu, Jan 16, 2025 at 1:27 PM Larysa Zhuchyi <larisa_zhuc...@ukr.net> 
> >> wrote:
> >>>
> >>> Dear all
> >>>
> >>> I'm am using apache-jena-4.9.0. Encountered same issue as in 
> >>> https://stackoverflow.com/questions/77772260/jena-riot-infers-invalid-rdf-with-literals-as-subjects.
> >>>  Could not find it at https://github.com/apache/jena/issues. Was 
> >>> wandering if it was fixed. If yes then in what version?
> >>>
> >>> Thanks in advance!
> >>>
> >>> --
> >>> Sincerely,
> >>> Larysa Zhuchyi
> >>
> >>
> > 
> > 
> 
> 
> 


-- 
Sincerely, 
Larysa Zhuchyi

Reply via email to