Remove old urn:struct code linking stuff.

This ugly way of linking to code has been deprecated by the automagic
Doxygen code links stuff.

3 files changed, 16 insertions, 21 deletions

diff --git a/ext/atom.lv2/atom.h b/ext/atom.lv2/atom.h
index bebe477..4f803ba 100644
--- a/ext/atom.lv2/atom.h
+++ b/ext/atom.lv2/atom.h
@@ -50,10 +50,9 @@
 
    Note that an LV2_Atom is the latter two fields of an LV2_Event as defined by
    the <a href="http://lv2plug.in/ns/ext/event">LV2 events extension</a>. The
-   host MAY marshal an <a href="urn:struct:LV2_Event">LV2_Event</a> to an <a
-   href="urn:struct:LV2_Atom">LV2_Atom</a> by simply pointing to the offset of
-   <code>type</code>. The macro LV2_ATOM_FROM_EVENT is provided in this header
-   for this purpose.
+   host MAY marshal an LV2_Event to an LV2_Atom by simply pointing to the
+   offset of <code>type</code>. The macro LV2_ATOM_FROM_EVENT is provided in
+   this header for this purpose.
 */
 typedef struct {
 
diff --git a/ext/contexts.lv2/contexts.ttl b/ext/contexts.lv2/contexts.ttl
index 85245b1..3fb4358 100644
--- a/ext/contexts.lv2/contexts.ttl
+++ b/ext/contexts.lv2/contexts.ttl
@@ -99,8 +99,7 @@ ctx:MessageContext a ctx:Context , lv2:Feature ;
 A non-realtime context for plugin control via message passing.  This context
 has a run method which takes a bitset of flags for parameters specifying which
 input and output ports are valid before and after the run method has executed,
-respectively (see <a href="urn:struct:LV2_Contexts_MessageContext"
->LV2_Contexts_MessageContext</a>).
+respectively (see <code>LV2_Contexts_MessageContext</code>).
 """ .
 
 ctx:IdleContext a ctx:Context , lv2:Feature ;
@@ -112,10 +111,9 @@ This context never has any ports.
 ctx:RequestRunFeature a lv2:Feature ;
 	lv2:documentation """
 A feature allowing the plugin to request the execution of a particular context
-at an arbitrary time.  To support this feature, the host MUST pass an <a href=
-"urn:struct:LV2_Feature">LV2_Feature</a> to <code>instantiate</code> with
-<code>data</code> pointing to a <a href="urn:struct:LV2_Contexts_Request_Run_Feature"
->LV2_Contexts_Request_Run_Feature</a>.
+at an arbitrary time.  To support this feature, the host MUST pass an
+LV2_Feature to <code>instantiate</code> with <code>data</code> pointing to a
+LV2_Contexts_Request_Run_Feature.
 
 <p>The plugin MAY call <code>request_run</code> with the given
 <code>data</code> from any non-realtime context to demand soon-as-possible execution
diff --git a/ext/reference.lv2/reference.ttl b/ext/reference.lv2/reference.ttl
index 8c8281f..e928e06 100644
--- a/ext/reference.lv2/reference.ttl
+++ b/ext/reference.lv2/reference.ttl
@@ -51,7 +51,7 @@ reference:Reference a rdfs:Class ;
 <p>Reference to a <a href="#Blob">Blob</a>.  The actual contents of a Reference
 are opaque and host specific, and must not be copied, serialized, or otherwise
 interpreted by a plugin, except via functions provided by the host in
-<a href="urn:struct:LV2_Blob_Support">LV2_Blob_Support</a>.</p>
+LV2_Blob_Support.</p>
 
 <p>A Reference is a special case of Atom with <code>type = 0</code>.
 "Null" is the unique Atom with <code>type = 0</code> and
@@ -62,21 +62,19 @@ reference:blobSupport a lv2:Feature ;
 	rdfs:label "Blob support" ;
 	lv2:documentation """
 Support for dynamically allocated blobs.  If a host supports this feature, it
-MUST pass a <a href="urn:struct:LV2_Feature">LV2_Feature</a> with
-<code>URI</code> http://lv2plug.in/ns/ext/atom#blobSupport
-and <code>data</code> pointing to a <a href="urn:struct:LV2_Blob_Support"
->LV2_Blob_Support</a>.
+MUST pass a LV2_Feature with <code>URI</code>
+http://lv2plug.in/ns/ext/atom#blobSupport and <code>data</code> pointing to a
+LV2_Blob_Support.
 """ .
 
 reference:Blob a rdfs:Class ;
 	rdfs:label      "Blob" ;
 	lv2:documentation """
-<p>Base class for all dynamically allocated blobs.  An <a
-href="urn:struct:LV2_Blob" >LV2_Blob</a> ia an opaque pointer to host
-data.  The type and data of a blob can be accessed via host-provided
-functions in <a href="urn:struct:LV2_Blob_Support">LV2_Blob_Support</a>.
-The type of a blob can be any URI that describes a data format.  Blobs are
-always allocated by the host, and unlike atoms are not necessarily POD.</p>
+<p>Base class for all dynamically allocated blobs.  An <a LV2_Blob is an opaque
+pointer to host data.  The type and data of a blob can be accessed via
+host-provided functions in LV2_Blob_Support.  The type of a blob can be any URI
+that describes a data format.  Blobs are always allocated by the host, and
+unlike atoms are not necessarily POD.</p>
 
 <p>Blob data MUST NOT be used in any way by an implementation that does not
 understand that blob type (unlike Atoms, meaningful type-oblivious use