From 994a8b17a2501d95e485e12dea0eb6f408df6b0d Mon Sep 17 00:00:00 2001
From: David Robillard Reference to a Blob. 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
-LV2_Blob_Support.
A Reference is a special case of Atom with type = 0
.
"Null" is the unique Atom with type = 0
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 LV2_Feature with
-URI
http://lv2plug.in/ns/ext/atom#blobSupport
-and data
pointing to a LV2_Blob_Support.
+MUST pass a LV2_Feature with URI
+http://lv2plug.in/ns/ext/atom#blobSupport and data
pointing to a
+LV2_Blob_Support.
""" .
reference:Blob a rdfs:Class ;
rdfs:label "Blob" ;
lv2:documentation """
-
Base class for all dynamically allocated blobs. An LV2_Blob ia 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.
+Base class for all dynamically allocated blobs. An
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
--
cgit v1.2.1