Project frameworks and language

[natebass]

I am thinking about using the Apache Jena framework for interacting with semantic web files.

• Apache Jena https://jena.apache.org/
• Using Java instead of Python. Apache Jena has good docs that I could use while learning concepts about RDF and semantic web.
• Open to discussing reasons to use Python.
• SPARQL and other stuff included in Apache Jena https://jena.apache.org/documentation/query/index.html. This brings up the first feature you posted [Feature]: Ingest one or more local knowledge graph files. I think using RDF and n3 files are good at local level. SPARQL is something once we start spidering and building a bigger graph.

My test project with example https://github.com/natebass/be-local-graph-java-04.

[DanHugoDanHugo]

@natebass

Selecting a starting point in an established platform, library, etc, is a good idea. The same way starting with a technology long-established is often a better idea than creating something from scratch. This is arguable but so is everything.

You are more than welcome to kick off a java-based development effort. Diversity in implementation is good (software companies need to ship products so tech stack selection is critical, nonprofit community projects are not so constrained).

Why Python? Very early work with RDF was done with python-based tools, eg https://www.w3.org/2000/10/swap/doc/cwm.html and modern support for RDF is fairly broad and well-established. Python (and Javascript) are accessible for those curious in general, thus the python-based paths.

Some potentially-useful clarifications for additional learning

• RDF is a framework for graph representation via triples
• n3 is a language for describing RDF relations (this link mistakenly calls RDF a language, it is in the sense that there is a vocabulary), and is arguably more easily read and written than the default RDF/XML interchange data format, there are a few ways to work in RDF (JSON-LD, ttl, n3, xml, etc)
• SPARQL is a query language for RDF graphs