Difference between revisions of "SIG:GraphTechnologies"
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
The main goal of the TEI-Graph-SIG is to model the textual phenomenons of the TEI in a Graph and to develop routines to import TEI-encoded XML-files into graph databases. | The main goal of the TEI-Graph-SIG is to model the textual phenomenons of the TEI in a Graph and to develop routines to import TEI-encoded XML-files into graph databases. | ||
| − | In a first step we import a small xml-example into a [https://neo4j.com neo4j] instance using | + | In a first step we import a small xml-example into a [https://neo4j.com neo4j] instance using [https://github.com/neo4j-contrib/neo4j-apoc-procedures-function apoc.import.xml] |
| + | |||
| + | The example is a [https://seafile.rlp.net/f/6282a26504cc4f079ab9/?dl=1 page] from the [https://www.deutschestextarchiv.de DTA]. [Here] you can find the XML. | ||
Revision as of 16:37, 25 January 2019
As TEI is not a format, though many people think it is. It's a de facto standard that specifies Guidelines for document interchange. Actually the Guidelines are based on the XML but this is only one possible technical way of expressing the phenomenons.
The aim of the Graph-SIG is to find a way of expressing the language phenomenons of the TEI in Graphs.
- In the graph you can use multi-hierarchical annotations layers.
- Graph models are very easy to read and understand. So DH-People and “normal” scientists have a level of discussion in common.
- A Graph can be expressed as RDF so the step from a Graph to linked open data is easy to make.
The main goal of the TEI-Graph-SIG is to model the textual phenomenons of the TEI in a Graph and to develop routines to import TEI-encoded XML-files into graph databases.
In a first step we import a small xml-example into a neo4j instance using apoc.import.xml
The example is a page from the DTA. [Here] you can find the XML.
