Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Importing a Turtle file

Agrafe can create a project from an existing Turtle (.ttl) ontology, so you do not have to retype it in Dolfin.

How to import

  1. Open the project list and choose Import from Turtle.
  2. Pick a .ttl or .turtle file. It must be UTF-8 text.
  3. A new project appears with the placeholder name New project. Rename it inline, exactly as after New project.

If the file cannot be read, you get an error (Could not read turtle: …) and no project is created: the Turtle is translated before anything is stored.

Imported projects always start private and count against your private-project limit. The import is refused if your licence has expired, if you are at your project limit, or if the generated Dolfin files would exceed your per-project file limit.

What you get

  • Dolfin files. The Turtle is translated to .dlf files. Each entity goes into the file named by its rdfs:isDefinedBy triple; Turtle without that information is split by IRI structure. See Turtle & OWL Correspondence for the exact rules.
  • package.dlf. Built from the Turtle’s owl:Ontology metadata. If the Turtle has none, a default manifest is generated.
  • The original Turtle. It is stored in the project as a normal file named <file name>.ttl and recorded as the project’s origin. Everything that follows (the editor, Reveal, sync and Re-translate) works on this file.

The base IRI of the project is the subject of the Turtle’s owl:Ontology. It is recorded once at import, and later features reuse it so that translation and sync always agree.

The origin file in the file tree

The origin file is pinned at the top of the tree with an origin badge. Otherwise it behaves like any file:

  • It is editable, collaborative, versioned and included in project ZIP exports.
  • You can rename it. The project remembers it by identity, not by name.
  • It does not count against the per-project file limit.
  • It is ignored by everything Dolfin: compilation, linting, the wire format and deployments only look at .dlf files.

Deleting the origin file

Deleting the origin asks for confirmation:

This is the project’s original Turtle file. Deleting it breaks “Reveal in turtle source” and syncing Dolfin edits back to Turtle. Delete anyway?

If you confirm, the project stops being a turtle-origin project: the origin, the sync baseline and the sync state are removed. Reveal falls back to Reveal in turtle export, and there is no automatic sync or Re-translate any more.

Projects imported before this feature

Older imported projects have no origin: the original Turtle was discarded at import and cannot be recovered. They keep working normally, and Reveal in turtle export is available, but they have no sync and no Re-translate. To get the full feature, import the Turtle again as a new project.

Other .ttl files

You can add other .ttl files to a project. They open in the Turtle editor and are otherwise ignored, but they are not an origin: no sync, no Re-translate, no Reveal in dolfin.