From 4e86fd59522c70b3654e5920a60ce748640f5a2c Mon Sep 17 00:00:00 2001 From: David Robillard Date: Sat, 22 Nov 2014 22:36:35 -0500 Subject: Remove blank lines between list items. Markdown seems to put paragraphs inside list items if you separate them with blank lines, oddly even if they are in the same list. --- content/pages/bundle-definition.md | 14 -------------- 1 file changed, 14 deletions(-) (limited to 'content/pages/bundle-definition.md') diff --git a/content/pages/bundle-definition.md b/content/pages/bundle-definition.md index fffe011..734d6dc 100644 --- a/content/pages/bundle-definition.md +++ b/content/pages/bundle-definition.md @@ -12,37 +12,29 @@ host authors typically do not need to be concerned with the details. * All information necessary for a host to discover (but not necessarily use) the contents of a bundle MUST be present in `manifest.ttl`. - * The host can discover which plugins are present by scanning `manifest.ttl` for statements like ` a lv2:Plugin`. - * The data files for each plugin are listed with the `rdfs:seeAlso` property, for example ` rdfs:seeAlso `. - * Descriptions may be split across several files, and several bundles. File boundaries are not significant. - * If a statement like ` a lv2:Specification` is found, then `` is specification which may contain information like additional plugin categories, properties, and human-readable labels for things. The host SHOULD load the corresponding data files. - * If a statement like ` a pset:Preset` is found, then `` is a preset. The `lv2:appliesTo` property indices which plugin the preset applies to. See the [presets extension](http://lv2plug.in/ns/ext/presets) for details. - ## Installation * The name of a bundle itself MUST NOT be given any long-term significance (for example, in saved files). - * Hosts may include special plugin bundles as part of their installation and depend on the existence of those bundles in their search path, but otherwise the discovery process should be identical. - * Users MUST be able to rename installed bundle directories without any save files breaking. @@ -51,7 +43,6 @@ host authors typically do not need to be concerned with the details. * If a host encounters a bundle it does not "understand" or care about, it may simply ignore it. - * Hosts MUST consider *all* data files associated with a plugin/spec/preset/etc (including `manifest.ttl`) whenever looking for information about a plugin. @@ -70,7 +61,6 @@ organization clear. ### Plugin * `manifest.ttl` contains the triple ` a lv2:Plugin`. - * `manifest.ttl` MAY contain triples of the form ` rdfs:seeAlso ` which indicates that more information can be found in `datafile.ttl`. @@ -78,11 +68,9 @@ organization clear. ### Specification * `manifest.ttl` contains the triple ` a lv2:Specification`. - * `manifest.ttl` MAY contain triples of the form ` rdfs:seeAlso ` which indicates that more information can be found in `datafile.ttl`. - * Hosts SHOULD consider this information part of their LV2 specification. Hosts SHOULD NOT hard-code static assumptions about the specification, such as plugin categories or port types (though of course, they may not support @@ -93,10 +81,8 @@ organization clear. * `manifest.ttl` contains the triple ` a foo:MegaWidget` where `foo:MegaWidget` is a "widget" type the host understands (likely one defined in the [UI specification](http://lv2plug.in/ns/extensions/ui)). - * `manifest.ttl` MAY contain triples of the form ` rdfs:seeAlso ` which indicates that more information can be found in `datafile.ttl`. - * `manifest.ttl` contains a triple of the form ` ui:binary ` where `ui.so` is the module to be dynamically loaded by the host. -- cgit v1.2.1