http://docs.openlinksw.com/virtuoso/internetservices.html OpenLink Virtuoso Universal Server: Documentation virtuoso.docs@openlinksw.com Wed, 09 Apr 2008 14:35:56 GMT OpenLink Software Documentation Team webmaster@openlinksw.com http://docs.openlinksw.com/virtuoso/../images/misc/logo.jpg http://docs.openlinksw.com/virtuoso/internetservices.html OpenLink Virtuoso Universal Server: Documentation http://docs.openlinksw.com/virtuoso/webdavserver.html virtuoso.docs@openlinksw.com WebDAV Server http://docs.openlinksw.com/virtuoso/webdavserver.html Wed, 09 Apr 2008 14:35:56 GMT Virtuoso supports the WebDAV protocol, which is an extension of HTTP for cooperative work on the Internet. DAV resources can be of any mime type, including binary types. The DAV resources are stored in the Virtuoso database as large objects, they are not in the file system and can only be accessed through the DAV protocol. Direct SQL access to the DAV tables is also possible, so there's a set of Virtuoso/PL procedures that acts as DAV API to let server-side applications access DAV. Virtuoso DAV can be extended by virtual collections. Instead of accessing DAV tables, DAV server can retrieve data from applications, thus an application can generate documents on demand and these documents will be available via DAV as well as plain DAV resources. Moreover, resources can be submitted directly to the application via DAV. Virtuoso DAV provides settable access rights and ownership of resources. Access rights as such are not covered by the DAV specification but Virtuoso implements both ACLs (access control lists) and a Unix file system like scheme for ownership and permissions. SQL accounts enabled for DAV are valid owners of DAV resources. A resource has both a user owner and a group owner, plus an optional access control list that can grant privileges to users and roles alike. A user can have DAV-only access, SQL/ODBC-only access, both of them or neither. User account information is stored in relational tables and can be manipulated from SQL or through a Web UI. Virtuoso DAV can store metadata about resources. These metadata are extracted from resources automatically, and can be edited by users. In addition, users can place public and personal 'tags' on resources to categorize data according for personal needs without interference between users. Virtuoso DAV has a powerful and scalable search engine that let application locate resources that match given list of criteria. The search can process both plain DAV resources and data published by applications in virtual collections. Search criteria can check for resource properties, content, metadata and tags. Certain special processing is provided for the following types of DAV resources: http://docs.openlinksw.com/virtuoso/uriqa.html virtuoso.docs@openlinksw.com URIQA Semantic Web Enabler http://docs.openlinksw.com/virtuoso/uriqa.html Wed, 09 Apr 2008 14:35:56 GMT Virtuoso supports the URIQA (URI Query Agent) extension of HTTP WebDAV protocol. URIQA adds three new methods to HTTP in order to retrieve, add and remove RDF metadata about a given subject. The subject is identified by its URI. If the subject is a DAV resource then URIQA will usually reuse the DAV URI of the resource. If the subject is not a resource but something else (physical entity, imaginary thing or vocabulary item) then URIQA can be used to process metadata about the subject even if the subject itself can not be accessed via HTTP. URIQA-specific HTTP methods are called MGET (to retrieve existing metadata), MPUT (to add or update RDF triples) and MDELETE (to remove some or all triples). A single URIQA request usually deals with a single subject that is specified by request URI. The MGET response, however, can return metadata about more than one RDF subject, e.g., the request about a book can return both data about the book itself plus some data about persons who are known as authors of the book. In addition to URIQA-specific HTTP methods, Virtuoso implements a semantic web service interface that allows plain HTTP clients to access metadata using traditional GET or POST HTTP methods. http://docs.openlinksw.com/virtuoso/maildelivstore.html virtuoso.docs@openlinksw.com Mail Delivery & Storage http://docs.openlinksw.com/virtuoso/maildelivstore.html Wed, 09 Apr 2008 14:35:56 GMT http://docs.openlinksw.com/virtuoso/nntpnewsgroups.html virtuoso.docs@openlinksw.com NNTP Newsgroups http://docs.openlinksw.com/virtuoso/nntpnewsgroups.html Wed, 09 Apr 2008 14:35:56 GMT http://docs.openlinksw.com/virtuoso/mime.html virtuoso.docs@openlinksw.com MIME & Internet Messages http://docs.openlinksw.com/virtuoso/mime.html Wed, 09 Apr 2008 14:35:56 GMT http://docs.openlinksw.com/virtuoso/ftpservices.html virtuoso.docs@openlinksw.com FTP Services http://docs.openlinksw.com/virtuoso/ftpservices.html Wed, 09 Apr 2008 14:35:56 GMT Virtuoso provides both FTP client and server functionality. The Virtuoso FTP client functions allow for programmatic access to ftp servers from Virtuoso/ PL to list, submit and retrieve files from an FTP server. The Virtuoso FTP server provides FTP access to the Virtuoso WebDAV repository using the same authentication and permissions system as WebDAV, and an configurable anonymous user access. http://docs.openlinksw.com/virtuoso/vspguide.html virtuoso.docs@openlinksw.com VSP Guide http://docs.openlinksw.com/virtuoso/vspguide.html Wed, 09 Apr 2008 14:35:56 GMT http://docs.openlinksw.com/virtuoso/ldap.html virtuoso.docs@openlinksw.com LDAP http://docs.openlinksw.com/virtuoso/ldap.html Wed, 09 Apr 2008 14:35:56 GMT The Lightweight Directory Access Protocol (LDAP) is a protocol for accessing online directory services. It runs directly over TCP and can be used to access a standalone LDAP directory service or a directory service maintained by X.500. A directory is type of database that stores information that is read more often that written to and so services are typically geared for high volume read access and offer simpler transaction support than general purpose databases. The LDAP directory service model is based on entries. An entry is a collection of attributes that has a "distinguished name" (DN). The DN is used to refer to the entry unambiguously. Each of the entry's attributes has a type and one or more values. The types are typically mnemonic strings, like "cn" for common name, or "mail" for email address. The values depend on what type of attribute it is: an email attribute might contain the string value "foo@bar.org". A jpegPhoto attribute would contain a photograph in binary JPEG format. LDAP directory entries are arranged in a hierarchical tree-like structure that may reflect political, geographic and/or organizational boundaries. Hence, entries representing countries appear at the top of the tree, below them are entries representing states or national organizations, then, entries representing people, printers, documents, anything else... LDAP provides methods for authentication. Directories can be made accessible to the general public or protected however the case my be.