From e0c4fb1bc1c66e5655a41ddcbfaafb07e32b93a2 Mon Sep 17 00:00:00 2001
From: David Robillard <d@drobilla.net>
Date: Fri, 26 Nov 2010 20:25:02 +0000
Subject: Mark up documentation with lv2:documentation as per discussion on
 lv2-dev. Use unified lv2plug.in style for ontology documentation.

---
 ext/midi.lv2/midi.ttl | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

(limited to 'ext/midi.lv2')

diff --git a/ext/midi.lv2/midi.ttl b/ext/midi.lv2/midi.ttl
index 12725ad..a8c7c6a 100644
--- a/ext/midi.lv2/midi.ttl
+++ b/ext/midi.lv2/midi.ttl
@@ -34,8 +34,8 @@
 	doap:name "LV2 MIDI Events" ;
 	rdfs:comment "Defines an LV2 event type for standard raw MIDI" ;
     doap:release [
-        doap:revision "1" ;
-        doap:created "2008-08-11" ;
+        doap:revision "1.1pre1" ;
+        doap:created "2010-10-29"
     ] ;
 	doap:maintainer [
 		a foaf:Person ;
@@ -51,11 +51,11 @@
 midi:MidiEvent a rdfs:Class ;
 	rdfs:label      "LV2 MIDI event" ;
 	rdfs:subClassOf lv2ev:Event ;
-	rdfs:comment    """
-A single raw (sequence of bytes) MIDI event.
+	lv2:documentation """
+<p>A single raw (sequence of bytes) MIDI event.</p>
 
-These events are equivalent to standard MIDI events, with the following
-restrictions to ease the burden on plugin authors:
+<p>These events are equivalent to standard MIDI events, with the following
+restrictions to ease the burden on plugin authors:</p>
 <ul>
   <li>Running status is not allowed. Every event must have its own status
     byte.</li>
@@ -83,5 +83,5 @@ restrictions to ease the burden on plugin authors:
   events to the buffer, and the MIDI reader (plugin or host) can assume that
   all events are valid.</li>
 </ul>
-"""^^lv2:basicXHTML .
+""" .
 
-- 
cgit v1.2.1