franta-hg@59: # LV2 plugins are installed in a ``bundle'', a directory with a standard
franta-hg@59: # structure.  Each bundle has a Turtle file named `manifest.ttl` which lists
franta-hg@59: # the contents of the bundle.
franta-hg@59: #
franta-hg@59: # Hosts typically read the manifest of every installed bundle to discover
franta-hg@59: # plugins on start-up, so it should be as small as possible for performance
franta-hg@59: # reasons.  Details that are only useful if the host chooses to load the plugin
franta-hg@59: # are stored in other files and linked to from `manifest.ttl`.
franta-hg@59: #
franta-hg@59: # ==== URIs ====
franta-hg@59: #
franta-hg@59: # LV2 makes use of URIs as globally-unique identifiers for resources.  For
franta-hg@59: # example, the ID of the plugin described here is
franta-hg@59: # `<http://lv2plug.in/plugins/eg-amp>`.  Note that URIs are only used as
franta-hg@59: # identifiers and don't necessarily imply that something can be accessed at
franta-hg@59: # that address on the web (though that may be the case).
franta-hg@59: #
franta-hg@59: # ==== Namespace Prefixes ====
franta-hg@59: #
franta-hg@59: # Turtle files contain many URIs, but prefixes can be defined to improve
franta-hg@59: # readability.  For example, with the `lv2:` prefix below, `lv2:Plugin` can be
franta-hg@59: # written instead of `<http://lv2plug.in/ns/lv2core#Plugin>`.
franta-hg@59: 
franta-hg@59: @prefix lv2:  <http://lv2plug.in/ns/lv2core#> .
franta-hg@59: @prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .
franta-hg@59: 
franta-hg@59: # ==== Describing a Plugin ====
franta-hg@59: 
franta-hg@59: # Turtle files contain a set of ``statements'' which describe resources.
franta-hg@59: # This file contains 3 statements:
franta-hg@59: # [options="header"]
franta-hg@59: # |================================================================
franta-hg@59: # | Subject                             | Predicate    | Object
franta-hg@59: # | <http://lv2plug.in/plugins/eg-amp>  | a            | lv2:Plugin
franta-hg@59: # | <http://lv2plug.in/plugins/eg-amp>  | lv2:binary   | <amp.so>
franta-hg@59: # | <http://lv2plug.in/plugins/eg-amp>  | rdfs:seeAlso | <amp.ttl>
franta-hg@59: # |================================================================
franta-hg@59: 
franta-hg@59: # Firstly, `<http://lv2plug.in/plugins/eg-amp>` is an LV2 plugin:
franta-hg@59: <http://lv2plug.in/plugins/eg-amp> a lv2:Plugin .
franta-hg@59: 
franta-hg@59: # The predicate ```a`'' is a Turtle shorthand for `rdf:type`.
franta-hg@59: 
franta-hg@59: # The binary of that plugin can be found at `<amp.ext>`:
franta-hg@59: <http://lv2plug.in/plugins/eg-amp> lv2:binary <amp.so> .
franta-hg@59: 
franta-hg@59: # This file is a template; the token `@LIB_EXT@` is replaced by the build
franta-hg@59: # system with the appropriate extension for the current platform before
franta-hg@59: # installation.  For example, in the output `manifest.ttl`, the binary would be
franta-hg@59: # listed as `<amp.so>`.  Relative URIs in manifests are relative to the bundle
franta-hg@59: # directory, so this refers to a binary with the given name in the same
franta-hg@59: # directory as this manifest.
franta-hg@59: 
franta-hg@59: # Finally, more information about this plugin can be found in `<amp.ttl>`:
franta-hg@59: <http://lv2plug.in/plugins/eg-amp> rdfs:seeAlso <amp.ttl> .
franta-hg@59: 
franta-hg@59: # ==== Abbreviation ====
franta-hg@59: #
franta-hg@59: # This file shows these statements individually for instructive purposes, but
franta-hg@59: # the subject `<http://lv2plug.in/plugins/eg-amp>` is repetitive.  Turtle
franta-hg@59: # allows the semicolon to be used as a delimiter that repeats the previous
franta-hg@59: # subject.  For example, this manifest would more realistically be written like
franta-hg@59: # so:
franta-hg@59: 
franta-hg@59: <http://lv2plug.in/plugins/eg-amp>
franta-hg@59: 	a lv2:Plugin ;
franta-hg@59: 	lv2:binary <amp.so>  ;
franta-hg@59: 	rdfs:seeAlso <amp.ttl> .