Skip to content

Authoring Graph View

New to Folio? Start here

Graph View

Graph View draws an RDF file as nodes and edges. Agents write a lot of RDF quickly, and a picture is taken in faster than text, so Graph View is what you look at to see what an agent read and wrote. It draws one node for each named resource, with the values, lists and blocks that resource holds drawn inside it.

One file, two drawings

fleet.ttl describes one solar installation in Turtle: its type, name and capacity, the company that operates it, the capacity of each construction phase as a list, and its point of interconnection as a block. The terms it uses are declared in plants.ttl, a domain model in the same workspace.

Drawn with a node for every resource and for every value the file writes, and an edge for every statement, the file is 16 nodes and 15 edges, three of the nodes blank.

fleet.ttl with a node per resource and per written value, and an edge per statement.

Graph View draws the same file as one node.

fleet.ttl
One node in Folio's Graph View, desert-ridge, with its address and a Solar installation badge. It lists capacityMW 240, name Desert Ridge Solar and operator Helios Energy, then a POINTOFINTERCONNECTION group with substation Palo Verde and voltageKV 230, then a PHASECAPACITIESMW group with rows 1 and 2, each 120.
fleet.ttl in Graph View: one node for desert-ridge, with Helios Energy shown by its label in the operator row.

Inside a node

Graph View draws each of the six parts below inside a node rather than as nodes and edges of its own. It does this for every file.

Types

A type, written a, draws as a badge under the node's name, showing the class's rdfs:label, rather than as an edge to the class.

a plants:SolarInstallation, drawn as the Solar installation badge.

Values

A literal, such as a name, a number or a date, draws as a row on its subject's node.

The capacity and the name, drawn as two rows.

Resources with only values

A named resource whose only statements are its types and values draws as a link in the row that refers to it, showing its rdfs:label.

:helios-energy, drawn as Helios Energy in the operator row.

Blocks

A [ … ] block draws as a group inside the node that holds it, headed by the property that holds it.

The point of interconnection block, drawn as a group of its two values.

Lists

A list, written ( … ), draws as a group of numbered rows, one for each item, in order.

The phase capacities, drawn as rows 1 and 2.

Property shapes

In Folio, a class is represented using RDFS and SHACL, and each property shape a class lists draws as a row in its node's Instance properties table, with the value it takes and how many. A node takes the shape its type calls for: desert-ridge, a solar installation, draws its values as rows, and SolarInstallation, with the Class Schema badge, draws its property shapes as this table.

Turtle
# A SolarInstallation is a photovoltaic power plant connected to the grid.
# It has every PowerPlant property, and adds an optional panel count.
:SolarInstallation a svs:ClassSchema ;
  rdfs:label "Solar installation"@en ;
  rdfs:comment "A photovoltaic power plant connected to the grid."@en ;
  rdfs:subClassOf :PowerPlant ;
  sh:property [
    sh:path :panelCount ;
    sh:name "panel count"@en ;
    sh:description "Number of photovoltaic panels installed."@en ;
    sh:datatype xsd:integer
  ] .
SolarInstallation in plants.ttl. Its own panel count sits beside the nine properties it inherits from PowerPlant under the inherited-properties rule.

A block inside a block

Graph View draws the inner block as a group inside the outer block's group. Here the point of interconnection holds the interconnection agreement it operates under.

Turtle
plants:pointOfInterconnection [
  a plants:GridConnection ;
  plants:substation "Palo Verde" ;
  plants:voltageKV 230 ;
  plants:agreement [
    a plants:InterconnectionAgreement ;
    plants:agreementId "IA-2291" ;
    plants:signedOn "2023-02-14"^^xsd:date
  ]
] .
The agreement block, drawn as a group inside the point of interconnection group.

A block more than two levels down keeps its own node, linked from the row that holds it.