Patrick Hochstenbach

> in the same way that ex:me should not be parsed as ex1:me even if ex:me owl:sameAs ex1:me. I think this owl:sameAs is on yet another level (already an inference)....

In the N3 inference engine I'm trying to build there is a similar definition of a rule but with different names. I've actually tried to search for better names than...

My Rule looks more like (with your template): ```typescript interface Rule { premise: { quantifiers: Map; quads: RDF.Quad[]; }; conclusion: { quantifiers: Map; quads: RDF.Quad[]; }; equals(other: Rule | null...

Indeed, this is way how N3 is interpreted. The mapping has a different purpose in the premise and conclusion. **Premise** Given a formula like: ``` { ?subject a [ a...

With: ``` "unit": {"@type": "xsd:anyType", "@id": "odrl:unit"}, ``` the translation becomes: ``` _:b2 "http://dbpedia.org/resource/Dots_per_inch"^^ . ``` Shouldn't it be: ``` "unit": { "@id": "odrl:unit" , "@type": "@id"}, ``` to get...

I don't think it is a pure parsing problem but an interpretation problem. As I understand, the JSON spec does not require JSON processors to handle non-unique names in a...

I read in https://www.w3.org/TR/json-ld11-api/#terminology: > Terms imported from [ECMAScript Language Specification](https://tc39.es/ecma262/) [[ECMASCRIPT](https://www.w3.org/TR/json-ld11-api/#bib-ecmascript)], [The JavaScript Object Notation (JSON) Data Interchange Format](https://tools.ietf.org/html/rfc8259) [[RFC8259](https://www.w3.org/TR/json-ld11-api/#bib-rfc8259)], [Infra Standard](https://infra.spec.whatwg.org/) [[INFRA](https://www.w3.org/TR/json-ld11-api/#bib-infra)], and [Web IDL](https://heycam.github.io/webidl/) [[WEBIDL](https://www.w3.org/TR/json-ld11-api/#bib-webidl)] And a...