From 2b809fbf4090ae64d728988454c4f1b721f4c323 Mon Sep 17 00:00:00 2001 From: David Robillard Date: Mon, 3 Sep 2012 01:41:19 +0000 Subject: Use relative links between extensions so local documentation links work. Automatically link prefixed names to the appropriate resource. --- lv2/lv2plug.in/ns/ext/patch/patch.ttl | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'lv2/lv2plug.in/ns/ext/patch/patch.ttl') diff --git a/lv2/lv2plug.in/ns/ext/patch/patch.ttl b/lv2/lv2plug.in/ns/ext/patch/patch.ttl index 17f13cc..6267c71 100644 --- a/lv2/lv2plug.in/ns/ext/patch/patch.ttl +++ b/lv2/lv2plug.in/ns/ext/patch/patch.ttl @@ -17,9 +17,9 @@ plugins, but is useful in many contexts.

The main feature of this design is that the messages themselves are described in the same format as the data they work with. In particular, -messages can be serialised as an LV2 Object or in Turtle (or any -other RDF serialisation).

+messages can be serialised as a binary Object or in Turtle (or any other RDF +serialisation).

The idea behind using a property-based interface for control is to prevent an an explosion of message types. Instead of a custom message for each action, @@ -37,9 +37,9 @@ One benefit of this approach is that a persistent state model is available

This specification is strictly metadata and does not define any binary mechanism, though it can be completely expressed by standard types in the LV2 Atom extension. Thus, hosts can -be expected to be capable of transmitting it between plugins, or between a -plugin and its UI, making it a good choice for advanced plugin control.

+href="../atom/atom.html">LV2 Atom extension. Thus, hosts can be expected +to be capable of transmitting it between plugins, or between a plugin and its +UI, making it a good choice for advanced plugin control.

""" . patch:Ack -- cgit v1.2.1