Difference between revisions of "SIG:GraphTechnologies"

From TEIWiki
Jump to navigation Jump to search
Line 15: Line 15:
 
The import to neo4j runs with:
 
The import to neo4j runs with:
  
 +
<code>
 
// Import xml-example from DTA to neo4j
 
// Import xml-example from DTA to neo4j
 
call apoc.xml.import('https://seafile.rlp.net/f/6282a26504cc4f079ab9/?dl=1', {connectCharacters: true, charactersForTag:{lb:' '}, filterLeadingWhitespace: true}) yield node  
 
call apoc.xml.import('https://seafile.rlp.net/f/6282a26504cc4f079ab9/?dl=1', {connectCharacters: true, charactersForTag:{lb:' '}, filterLeadingWhitespace: true}) yield node  
 
return node;
 
return node;
 +
</code>

Revision as of 16:45, 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-Testfile and this is the Link to the DTA-Version.

The import to neo4j runs with:

// Import xml-example from DTA to neo4j call apoc.xml.import('https://seafile.rlp.net/f/6282a26504cc4f079ab9/?dl=1', {connectCharacters: true, charactersForTag:{lb:' '}, filterLeadingWhitespace: true}) yield node return node;