From e0c4fb1bc1c66e5655a41ddcbfaafb07e32b93a2 Mon Sep 17 00:00:00 2001 From: David Robillard 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/files.lv2/files.ttl | 31 +++++++++++++++---------------- 1 file changed, 15 insertions(+), 16 deletions(-) (limited to 'ext/files.lv2/files.ttl') diff --git a/ext/files.lv2/files.ttl b/ext/files.lv2/files.ttl index a83889d..4f1b68b 100644 --- a/ext/files.lv2/files.ttl +++ b/ext/files.lv2/files.ttl @@ -38,51 +38,50 @@ foaf:homepage ; rdfs:seeAlso ] ; - rdfs:comment """ -This extension provides a mechanism for plugins to create new files for + lv2:documentation """ +

This extension provides a mechanism for plugins to create new files for storing arbitrary data (e.g. waveforms), which can be persisted using the LV2 Persist extension. This allows plugins to work with potentially very large data via files, -and save/restore these files. +and save/restore these files.

-The motivating idea behind this extension is that all details of file +

The motivating idea behind this extension is that all details of file management must be handled by the host in whatever way is most appropriate for that host. Plugins MUST NOT make any assumption about filesystem locations -beyond what is explicitly guaranteed by this extension. +beyond what is explicitly guaranteed by this extension.

-To create a new file, plugins request a filename from the host. This way, +

To create a new file, plugins request a filename from the host. This way, the host is aware of files used by the plugin and can use an appropriate location for them that the plugin alone could not know (e.g. using an -appropriate disk volume for recording). +appropriate disk volume for recording).

-Plugins may also use pre-existing files from elsewhere on the filesystem. +

Plugins may also use pre-existing files from elsewhere on the filesystem. Using the LV2 Persist extension, the host can save both these types of files in an appropriate way (by e.g. storing a link, or copying the file to export -or archive a project). - +or archive a project).

""" . files:fileSupport a lv2:Feature ; rdfs:label "Support for plugin-created files" ; - rdfs:comment """ -This feature allows plugins to use pre-existing or newly created files, + lv2:documentation """ +

This feature allows plugins to use pre-existing or newly created files, and files them (e.g. across project saves and restores). If a host supports this feature it passes a LV2_Files_FileSupport structure to the plugins instantiate method as a feature (with URI http://lv2plug.in/ns/ext/files#FileSupport). This structure provides a function the plugin can use to create new file names. If and only if the host supports this feature, the plugin MAY files and restore values of -type LV2_FILES_FILENAME. +type LV2_FILES_FILENAME.

-A plugin SHOULD use this facility to create any new files it may need +

A plugin SHOULD use this facility to create any new files it may need (e.g. samples, waveforms for recording). Plugins MUST NOT expect their state to be correctly restored if they do not use this mechanism to -create new files. +create new files.

""" . files:FilePath a atom:AtomType ; rdfs:label "File Path" ; - rdfs:comment """ + lv2:documentation """ The full path to a file on the local filesystem. The format of a files:filePath is a C string (escaped or otherwise restricted in whatever way necessary for the system). This URI (http://lv2plug.in/ns/ext/files#FilePath), -- cgit v1.2.1