@prefix rdf: . @prefix sioc: . rdf:type sioc:Space ; sioc:name "OpenLink Virtuoso Features Demonstrations and Tutorials" . @prefix ns2: . sioc:space_of ns2:web2 . ns2: sioc:space_of ns2:xmlxslt , ns2:rdf , ns2:intprot , ns2:services , ns2:wap , ns2:bpeldemo , ns2:web , ns2:apps , ns2:xmlapps , ns2:linkeddata , ns2:hosting , ns2:xml , ns2:repl , ns2:rdfview ; sioc:description "OpenLink Virtuoso Features Demonstrations and Tutorials" . ns2:hosting rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Data Management - SQL\n " . ns2:xml rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Data Management - XML\n " . ns2:repl rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Data Management - Data Replication\n " . ns2:rdfview rdf:type sioc:Container , "Tutorial" ; sioc:container_of ; sioc:has_space ns2: ; sioc:description "Data Management - RDF\n " . ns2:services rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Web Services - SOAP Services\n " . ns2:wap rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , ; sioc:has_space ns2: ; sioc:description "Web Services - Wireless Access Protocols\n " . ns2:bpeldemo rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Business Process Integration - BPEL\n " . ns2:web rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Development - Web 1.0\n " . ns2:web2 rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , , , , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Development - Web 2.0\n " . ns2:xmlxslt rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , ; sioc:has_space ns2: ; sioc:description "Development - XML\n " . ns2:rdf rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , ; sioc:has_space ns2: ; sioc:description "Development - RDF\n " . ns2:intprot rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Development - NNTP\n " . ns2:apps rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , , , , , , ; sioc:has_space ns2: ; sioc:description "Demo applications - Framework Hosting\n " . ns2:xmlapps rdf:type sioc:Container , "Tutorial" ; sioc:container_of , , , , ; sioc:has_space ns2: ; sioc:description "Demo applications - XML Data Access\n " . ns2:linkeddata rdf:type sioc:Container , "Tutorial" ; sioc:container_of , ; sioc:has_space ns2: ; sioc:description "Demo applications - Linked Data\n " . @prefix foaf: . rdf:type foaf:Document . @prefix dc: . dc:title "Integrating Common Language Runtime Objects with Virtuoso" ; sioc:content "\n Overview\n The following tutorial demonstrates how Virtuoso can be extended \n through the use of a .NET bound language such as C# to create User Defined \n Types (UDTs), Stored Procedures, and Functions. This is an enhancement of its \n Object-Relational Database functionality. \n The demonstrations in this section highlight transparent integration \n (hosting) between Virtuoso and the Microsoft .NET and Mono implementations of \n the ECMA Common Language Infrastructure (CLI). \n \n Prerequisites\n The following prerequisites ensure the usability of these \n tutorial demos on Windows or Linux (and in other future Mono implementations): \n\n Linux\n \n Mono Runtime and Frameworks (ideally the version bundled with Virtuoso)\n Mono SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Linux with Mono Hosting\n \nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n\n The following tutorial shows how C# classes are used to create User\n Defined Types (UDTs) in Virtuoso. \n Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the \"Set Initial State\" link which registers the two C# classes with Virtuoso. Click on the \"ho_s_2.sql\" link to see the code behind this step \n Click on the \"Run\" links to actually experience the demo\n\n\nDemo Breakdown\n\n\n \"ho_s_2.sql\" performs the following steps\n \n Registers the \"MyFinances\" and \"Point\" classes with Virtuoso. Click \n on the \"MyFinances.cs\" and \"Point.cs\" links to see the C# source code of these \n classes\n Creates the conventional SQL table \"Employee\" \n Creates the Object-Relational table \"Supplier\" that includes a column \n named \"Location\" that is of Type \"Point\" (a UDT)\n Populates each of the newly created tables with data\n Creates the \"distance\" stored procedure which uses a C# function \n member (method) to calculate the distance between points.\n \n\n \t\"vsp1.vsp\" uses the static method \"tax\" of the \"MyFinances\" class to \n compute the payroll tax values for each employee via the \"salary\" column (like \n a SQL function would). Take note of the Virtuoso class invocation syntax for \n static C# methods (the relevant member function type in this demo; true to \n C# these are called by name rather than instance).\n \"vsp2.vsp\" uses the \"distance\" method of the UDT based column \n \"location\" to test for distance values less than \"3\". The distance values are \n return values from the \"Point\" class. Note that the \"Point\" class computes \n the distance between two arbitrary points.\n \"vsp3.vsp\" is a variation of the previous demo, with the column \n \"location\" being used to access and conditionally test the values of data \n member \"x\" (shown in \"Point.cs\" as 0).\n \"vsp4.vsp\" is another variation of a query on the \"Supplier\" table, \n in this particular case the query uses a Stored Procedure (see definition in \n \"ho_s_2.sql\") to filter its result set. It achieves this by using data member \n values \"x\" and \"y\" from column \"location\", and the arbitrary values 1 & \n 2 as input parameters for the Stored Procedure \"distance\". It then tests \n the return values for those less than 3.\n \n " ; sioc:has_container ns2:hosting ; sioc:description "Using C# Objects to extend Virtuoso via User Defined Types." . @prefix dcterms: . dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" . @prefix content: . content:encoded "\n Overview\n The following tutorial demonstrates how Virtuoso can be extended \n through the use of a .NET bound language such as C# to create User Defined \n Types (UDTs), Stored Procedures, and Functions. This is an enhancement of its \n Object-Relational Database functionality. \n The demonstrations in this section highlight transparent integration \n (hosting) between Virtuoso and the Microsoft .NET and Mono implementations of \n the ECMA Common Language Infrastructure (CLI). \n \n Prerequisites\n The following prerequisites ensure the usability of these \n tutorial demos on Windows or Linux (and in other future Mono implementations): \n\n Linux\n \n Mono Runtime and Frameworks (ideally the version bundled with Virtuoso)\n Mono SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Linux with Mono Hosting\n \nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n\n The following tutorial shows how C# classes are used to create User\n Defined Types (UDTs) in Virtuoso. \n Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the "Set Initial State" link which registers the two C# classes with Virtuoso. Click on the "ho_s_2.sql" link to see the code behind this step \n Click on the "Run" links to actually experience the demo\n\n\nDemo Breakdown\n\n\n "ho_s_2.sql" performs the following steps\n \n Registers the "MyFinances" and "Point" classes with Virtuoso. Click \n on the "MyFinances.cs" and "Point.cs" links to see the C# source code of these \n classes\n Creates the conventional SQL table "Employee" \n Creates the Object-Relational table "Supplier" that includes a column \n named "Location" that is of Type "Point" (a UDT)\n Populates each of the newly created tables with data\n Creates the "distance" stored procedure which uses a C# function \n member (method) to calculate the distance between points.\n \n\n \t"vsp1.vsp" uses the static method "tax" of the "MyFinances" class to \n compute the payroll tax values for each employee via the "salary" column (like \n a SQL function would). Take note of the Virtuoso class invocation syntax for \n static C# methods (the relevant member function type in this demo; true to \n C# these are called by name rather than instance).\n "vsp2.vsp" uses the "distance" method of the UDT based column \n "location" to test for distance values less than "3". The distance values are \n return values from the "Point" class. Note that the "Point" class computes \n the distance between two arbitrary points.\n "vsp3.vsp" is a variation of the previous demo, with the column \n "location" being used to access and conditionally test the values of data \n member "x" (shown in "Point.cs" as 0).\n "vsp4.vsp" is another variation of a query on the "Supplier" table, \n in this particular case the query uses a Stored Procedure (see definition in \n "ho_s_2.sql") to filter its result set. It achieves this by using data member \n values "x" and "y" from column "location", and the arbitrary values 1 & \n 2 as input parameters for the Stored Procedure "distance". It then tests \n the return values for those less than 3.\n \n \n " . rdf:type foaf:Document ; dc:title "Sending an SMS message through an ASP .NET SOAP Client to update a table " ; sioc:content "\n Overview\n The following tutorial demonstrates how a C# based Managed SOAP \n Client is used to create SMS based database notification services inside \n Virtuoso. This demo executes a database trigger every time a new Supplier \n record is added, updated or deleted. In this example a C# class acts as a\n SOAP client to a 3rd party XML Web Service that provides the SMS (Short Message \n Services) delivery to mobile phones. Note, this demo will work with any phone \n that is capable of receiving SMS (TEXT) messages.\n \n Prerequisites\n This demo currently works only on a Virtuoso server running under Microsoft Windows with following components installed:\n \n Windows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting.\n \n \n \n \n Tutorial Example\n\n Please follow the steps below to maximize the value of this tutorial:\n \n Click on the \"Set Initial State\" link which registers the \"redcoalsmssvc\" service with Virtuoso. Click on the \"ho_s_3.sql\" link to see the code behind this step\n Click on the \"Run\" links to actually experience the demo\n \n\n Demo Breakdown\n \n \"ho_s_3.sql\" performs the following steps\n \n Registers the \"redcoalsmssvc\" class with Virtuoso. Click on the \"redcoalsms.cs\" and \"redcoalsmsref.cs\" links to see the C# source code. Note that the class \"redcoalsmssvc\" is part of an assembly that has the namespace \"redcoalsms\"\n Creates the \"Suppliers\" table \n Creates a stored procedure \"redcoal_send_sms\" which demonstrates the syntax for creating an instance variable which includes the assembly namespace in the type reference. Specifically, note the use of an underscore instead of a dot when making this assignment \n Creates a Trigger named \"send_sms_to_mgr_new_supp\" that sends an SMS message each time a new \"Supplier\" table record is inserted\n Creates a Trigger named \"send_sms_to_mgr_mod_supp\" that sends an SMS message each time a \"Supplier\" record is updated\n Creates a Trigger named \"send_sms_to_mgr_mod_supp\" that sends an SMS message each time a supplier record is deleted\n \n \"setup_sms.vsp\" sets up all of the base data and verifies that SMS service connectivity required by this demo is available.\n \"handler.vsp\" is the actual interface through which you add or delete supplier records which result in SMS notifications being sent to your mobile phone.\n \n\n\n " ; sioc:has_container ns2:hosting ; sioc:description "Demonstrating the use of C# to create Virtuoso hosted Stored \n Procedures and Triggers. In this demo the database events trigger SMS \n messages that are relayed via C# based SOAP Client." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "\n Overview\n The following tutorial demonstrates how a C# based Managed SOAP \n Client is used to create SMS based database notification services inside \n Virtuoso. This demo executes a database trigger every time a new Supplier \n record is added, updated or deleted. In this example a C# class acts as a\n SOAP client to a 3rd party XML Web Service that provides the SMS (Short Message \n Services) delivery to mobile phones. Note, this demo will work with any phone \n that is capable of receiving SMS (TEXT) messages.\n \n Prerequisites\n This demo currently works only on a Virtuoso server running under Microsoft Windows with following components installed:\n \n Windows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting.\n \n \n \n \n Tutorial Example\n\n Please follow the steps below to maximize the value of this tutorial:\n \n Click on the "Set Initial State" link which registers the "redcoalsmssvc" service with Virtuoso. Click on the "ho_s_3.sql" link to see the code behind this step\n Click on the "Run" links to actually experience the demo\n \n\n Demo Breakdown\n \n "ho_s_3.sql" performs the following steps\n \n Registers the "redcoalsmssvc" class with Virtuoso. Click on the "redcoalsms.cs" and "redcoalsmsref.cs" links to see the C# source code. Note that the class "redcoalsmssvc" is part of an assembly that has the namespace "redcoalsms"\n Creates the "Suppliers" table \n Creates a stored procedure "redcoal_send_sms" which demonstrates the syntax for creating an instance variable which includes the assembly namespace in the type reference. Specifically, note the use of an underscore instead of a dot when making this assignment \n Creates a Trigger named "send_sms_to_mgr_new_supp" that sends an SMS message each time a new "Supplier" table record is inserted\n Creates a Trigger named "send_sms_to_mgr_mod_supp" that sends an SMS message each time a "Supplier" record is updated\n Creates a Trigger named "send_sms_to_mgr_mod_supp" that sends an SMS message each time a supplier record is deleted\n \n "setup_sms.vsp" sets up all of the base data and verifies that SMS service connectivity required by this demo is available.\n "handler.vsp" is the actual interface through which you add or delete supplier records which result in SMS notifications being sent to your mobile phone.\n \n\n\n \n " . rdf:type foaf:Document ; dc:title "Hosting CLR types using VSPX session management" ; sioc:content "Overview\n This is a variation of HO-S-3 with the SOAP client implemented ASP.NET and also demonstrates Virtuoso Server Pages for XML (VSPX) session management.\n \n Prerequisites\n This demo currently works only on a Virtuoso server running under Microsoft Windows with following components installed:\n \n Windows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting.\n \n \n \n \n Tutorial Example\n \n The setup_sms.vspx sets up the SMS sending unit.\n The handler.vspx does inserts/deletes/updates to demonstrate the SMS sending from triggers.\n The redcoalsms*.cs is an MS Visual Studio.NET generated SOAP client.\n The redcoalsms.dll should be installed as a private assembly (not as CodeBase) because of permissions.\n For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n \n " ; sioc:has_container ns2:hosting ; sioc:description "Demonstrating the use of C# to create Virtuoso hosted Stored \n Procedures and Triggers. In this demo a database events trigger SMS \n messages that are relayed via a C# based SOAP Client. It also demonstrates \n Virtuoso Server Pages session management." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "Overview\n This is a variation of HO-S-3 with the SOAP client implemented ASP.NET and also demonstrates Virtuoso Server Pages for XML (VSPX) session management.\n \n Prerequisites\n This demo currently works only on a Virtuoso server running under Microsoft Windows with following components installed:\n \n Windows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting.\n \n \n \n \n Tutorial Example\n \n The setup_sms.vspx sets up the SMS sending unit.\n The handler.vspx does inserts/deletes/updates to demonstrate the SMS sending from triggers.\n The redcoalsms*.cs is an MS Visual Studio.NET generated SOAP client.\n The redcoalsms.dll should be installed as a private assembly (not as CodeBase) because of permissions.\n For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n \n \n " . rdf:type foaf:Document ; dc:title "Hosting CLR types using VSPX session management" ; sioc:content "Overview\n HO-S-5 is a variation of HO-S-3 that makes use of VSPX session management\n \n Prerequisites\n The following prerequisites ensure the usability of these \n tutorial demos on Windows or Linux (and in other future Mono implementations): \n\n Linux\n \n Mono Runtime and Frameworks (ideally the version bundled with Virtuoso)\n Mono SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Linux with Mono Hosting\n \nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n \n The setup_sms.vspx sets up the SMS sending unit.\n The handler.vspx does inserts/deletes/updates to demonstrate the SMS sending from triggers.\n The redcoalsms_dom.cs is an HttpWebRequest SOAP client using DOM to process SOAP result.\n The redcoalsms_dom.dll should be installed as a private assembly (not as CodeBase) because of permissions.\n For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n This service is compatible with Mono (http://go-mono.com)\n \n " ; sioc:has_container ns2:hosting ; sioc:description "Demonstrating the use of C# to create Virtuoso hosted Stored \n Procedures and Triggers. In this demo a database event trigger SMS messages \n that are relayed via a .NET DOM frameworks based C# SOAP Client. It also \n demonstrates Virtuoso Server Pages session management." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "Overview\n HO-S-5 is a variation of HO-S-3 that makes use of VSPX session management\n \n Prerequisites\n The following prerequisites ensure the usability of these \n tutorial demos on Windows or Linux (and in other future Mono implementations): \n\n Linux\n \n Mono Runtime and Frameworks (ideally the version bundled with Virtuoso)\n Mono SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Linux with Mono Hosting\n \nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n \n The setup_sms.vspx sets up the SMS sending unit.\n The handler.vspx does inserts/deletes/updates to demonstrate the SMS sending from triggers.\n The redcoalsms_dom.cs is an HttpWebRequest SOAP client using DOM to process SOAP result.\n The redcoalsms_dom.dll should be installed as a private assembly (not as CodeBase) because of permissions.\n For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n This service is compatible with Mono (http://go-mono.com)\n \n \n " . rdf:type foaf:Document ; dc:title "Integrating Common Language Runtime Objects with Virtuoso" ; sioc:content "\n Overview\n The HO-S-10 sample is very similar to HO-S-2. The difference is using syntax CREATE LIBRARY. The statement imports assembly to internal Virtuoso table and imports types from it. After this the assembly can be removed from physical path and next time will be read from the table. The \"DROP LIBRARY\" removes assembly from table and drops imported types. \n \n Prerequisites\n The following prerequisites ensure the usability of these tutorial demos on Windows\n\nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n\n The following tutorial shows how C# classes are used to create User\n Defined Types (UDTs) in Virtuoso. \n Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the \"Set Initial State\" link which registers the two C# classes with Virtuoso.\n It also copies the Point_ho_s_10.dll file to \"tmp\" directory in the server root. \n Note that the directory must exists, must be writeable for the user running virtuoso and must be in the DirsAllowed parameter in Virtuoso ini file.\n Click on the \"ho_s_10.sql\" link to see the code behind this step \n Click on the \"Run\" links to actually experience the demo\n\n\nDemo Breakdown\n\n\n \"ho_s_10.sql\" performs the following steps\n \n Registers the \"Point\" classes with Virtuoso. Click \n on the \"Point_ho_s_10.cs\" links to see the C# source code of these \n classes\n Creates the Object-Relational table \"Supplier_ho_s_10\" that includes a column \n named \"Location\" that is of Type \"Point\" (a UDT)\n Populates table with data\n Using syntax: CREATE LIBRARY/ASSEMBLY \"myPoint\" as \"assembly\" WITH PERMISSION_SET = SAFE WITH AUTOREGISTER\n is simular to:\n CREATE LIBRARY/ASSEMBLY \"myPoint\" as \"assembly\"; and \n import_clr ('myPoint', NULL);\n \n\n \"vsp1.vsp\" is a variation of HO-S-2 (vsp3.vsp), with the column \n \"location\" being used to access and conditionally test the values of data \n member \"x\" (shown in \"Point.cs\" as 0).\n\n " ; sioc:has_container ns2:hosting ; sioc:description "Using C# Objects to extend Virtuoso via User Defined Types using CREATE LIBRARY/ASSEMBLY syntax." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "\n Overview\n The HO-S-10 sample is very similar to HO-S-2. The difference is using syntax CREATE LIBRARY. The statement imports assembly to internal Virtuoso table and imports types from it. After this the assembly can be removed from physical path and next time will be read from the table. The "DROP LIBRARY" removes assembly from table and drops imported types. \n \n Prerequisites\n The following prerequisites ensure the usability of these tutorial demos on Windows\n\nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n\n The following tutorial shows how C# classes are used to create User\n Defined Types (UDTs) in Virtuoso. \n Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the "Set Initial State" link which registers the two C# classes with Virtuoso.\n It also copies the Point_ho_s_10.dll file to "tmp" directory in the server root. \n Note that the directory must exists, must be writeable for the user running virtuoso and must be in the DirsAllowed parameter in Virtuoso ini file.\n Click on the "ho_s_10.sql" link to see the code behind this step \n Click on the "Run" links to actually experience the demo\n\n\nDemo Breakdown\n\n\n "ho_s_10.sql" performs the following steps\n \n Registers the "Point" classes with Virtuoso. Click \n on the "Point_ho_s_10.cs" links to see the C# source code of these \n classes\n Creates the Object-Relational table "Supplier_ho_s_10" that includes a column \n named "Location" that is of Type "Point" (a UDT)\n Populates table with data\n Using syntax: CREATE LIBRARY/ASSEMBLY "myPoint" as "assembly" WITH PERMISSION_SET = SAFE WITH AUTOREGISTER\n is simular to:\n CREATE LIBRARY/ASSEMBLY "myPoint" as "assembly"; and \n import_clr ('myPoint', NULL);\n \n\n "vsp1.vsp" is a variation of HO-S-2 (vsp3.vsp), with the column \n "location" being used to access and conditionally test the values of data \n member "x" (shown in "Point.cs" as 0).\n\n \n " . rdf:type foaf:Document ; dc:title "Integrating Common Language Runtime Objects with Virtuoso" ; sioc:content "\n Overview\n This tutorial demonstrates the options PERMISSION_SET = SAFE and \n\tPERMISSION_SET = UNRESTRICTED on CREATE LIBRARY / ASSEMBLY.\n \n Prerequisites\n The following prerequisites ensure the usability of these demos on Windows\n\nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n\n The tutorial shows how C# classes are used to create User\n Defined Types (UDTs) in Virtuoso. \n Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the \"Set Initial State\" link which registers the \n two C# classes within Virtuoso. \n It also copies the restricted.dll and unrestricted.dll files to \"tmp\" directory in the server root. \n Note that the directory must exists, must be writeable for the user running virtuoso and must be in the DirsAllowed parameter in Virtuoso ini file.\n Click on the \"ho_s_11.sql\" link to examine \n the code behind this step.\n Click on the \"Run\" links to execute the demo.\n\n\nDemo Breakdown\n\n\n \"ho_s_11.sql\" performs the following steps\n \n Registers the \"Rest\" and \"UnRest\" classes with Virtuoso. Click \n on the \"restricted.cs\" and \"unrestricted.cs\" links to see the C# source code of these \n classes.\n \n\n The \"unrestricted.vsp\" is shows classes that try to access \n File system and system variables. The \"restricted.vsp\", uses the same \n clases, but cannot complete the execution sucessfully because the assembly \n is imported with PERMISSION_SET = SAFE. The sample shows the error returned upon \n executing the classes.\n\n " ; sioc:has_container ns2:hosting ; sioc:description "Using Restrictions for C# Imported types." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "\n Overview\n This tutorial demonstrates the options PERMISSION_SET = SAFE and \n\tPERMISSION_SET = UNRESTRICTED on CREATE LIBRARY / ASSEMBLY.\n \n Prerequisites\n The following prerequisites ensure the usability of these demos on Windows\n\nWindows\n \n .NET Runtime and Frameworks\n .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server for Windows with .NET CLR Hosting\n \n\n \n Tutorial Example\n\n The tutorial shows how C# classes are used to create User\n Defined Types (UDTs) in Virtuoso. \n Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the "Set Initial State" link which registers the \n two C# classes within Virtuoso. \n It also copies the restricted.dll and unrestricted.dll files to "tmp" directory in the server root. \n Note that the directory must exists, must be writeable for the user running virtuoso and must be in the DirsAllowed parameter in Virtuoso ini file.\n Click on the "ho_s_11.sql" link to examine \n the code behind this step.\n Click on the "Run" links to execute the demo.\n\n\nDemo Breakdown\n\n\n "ho_s_11.sql" performs the following steps\n \n Registers the "Rest" and "UnRest" classes with Virtuoso. Click \n on the "restricted.cs" and "unrestricted.cs" links to see the C# source code of these \n classes.\n \n\n The "unrestricted.vsp" is shows classes that try to access \n File system and system variables. The "restricted.vsp", uses the same \n clases, but cannot complete the execution sucessfully because the assembly \n is imported with PERMISSION_SET = SAFE. The sample shows the error returned upon \n executing the classes.\n\n \n " . rdf:type foaf:Document ; dc:title "Making Table valued functions in C#" ; sioc:content "\n\tOverview\n\tThe following tutorial demonstrates how Virtuoso can be extended \n\t through the use of a .NET bound language such as C# to create resultsets. \n\tThe demonstrations in this section highlight transparent integration \n\t (hosting) between Virtuoso and the Microsoft .NET and Mono implementations of \n\t the ECMA Common Language Infrastructure (CLI) as well as how to use the Virtuoso\n\t in-process ODBC client to call back the server from hosted managed code. \n \n\tPrerequisites\n\tThe following prerequisites ensure the usability of these \n\t tutorial demos on Windows or Linux (and in other future Mono implementations): \n\t\n\t Linux\n\t\t\n\t\t Mono Runtime and Frameworks (ideally the version bundled with Virtuoso)\n\t\t Mono SDK (if you seek to write your own Objects for integration with Virtuoso)\n\t\t Virtuoso Universal Server for Linux with Mono Hosting\n\t\t Virtuoso .NET provider\n\t\t\n\t \n\t Windows\n\t\t\n\t\t .NET Runtime and Frameworks\n\t\t .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n\t\t Virtuoso Universal Server for Windows with .NET CLR Hosting\n\t\t Virtuoso .NET provider\n\t\t\n\t \n\t\n \n\tTutorial Example\n\tThe following tutorial shows how C# classes can interact with the Virtuoso server. \n\tPlease follow the steps below to maximize the value of this tutorial:\n\t\n\t Copy the file ho_s_14.dll next to the OpenLink.Data.VirtuosoClient.dll (if not allready there).\n\t Click on the \"Set Initial State\" link which registers the C# class with Virtuoso. Click on the \"ho_s_14.sql\" link to see the code behind this step \n\t Click on the \"Run\" links to actually experience the demo\n\t\n\tDemo Breakdown\n\t\n\t \"ho_s_14.sql\" registers the \"openlink.virtuoso.tutorial.ho_s_14.add_data\" C# static method with Virtuoso. Click \n\t\ton the \"ho_s_14.cs\" link to see the C# source code of this class\n\t \t\"vsp1.vsp\" uses the static method \"add_data\" of the \"openlink.virtuoso.tutorial.ho._s_14\" class to \n\t\tmake a resultset (like a SQL function would) through an in-process connection to the server. Take note of the\n\t\tusage of \"OpenLink.Virtuoso.InProcessPort\" key from AppDomain.GetData() to get the port on which the hosting Virtuoso server is listening at.\n\t\n " ; sioc:has_container ns2:hosting ; sioc:description "Using C# Objects to make table valued functions." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "\n\tOverview\n\tThe following tutorial demonstrates how Virtuoso can be extended \n\t through the use of a .NET bound language such as C# to create resultsets. \n\tThe demonstrations in this section highlight transparent integration \n\t (hosting) between Virtuoso and the Microsoft .NET and Mono implementations of \n\t the ECMA Common Language Infrastructure (CLI) as well as how to use the Virtuoso\n\t in-process ODBC client to call back the server from hosted managed code. \n \n\tPrerequisites\n\tThe following prerequisites ensure the usability of these \n\t tutorial demos on Windows or Linux (and in other future Mono implementations): \n\t\n\t Linux\n\t\t\n\t\t Mono Runtime and Frameworks (ideally the version bundled with Virtuoso)\n\t\t Mono SDK (if you seek to write your own Objects for integration with Virtuoso)\n\t\t Virtuoso Universal Server for Linux with Mono Hosting\n\t\t Virtuoso .NET provider\n\t\t\n\t \n\t Windows\n\t\t\n\t\t .NET Runtime and Frameworks\n\t\t .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n\t\t Virtuoso Universal Server for Windows with .NET CLR Hosting\n\t\t Virtuoso .NET provider\n\t\t\n\t \n\t\n \n\tTutorial Example\n\tThe following tutorial shows how C# classes can interact with the Virtuoso server. \n\tPlease follow the steps below to maximize the value of this tutorial:\n\t\n\t Copy the file ho_s_14.dll next to the OpenLink.Data.VirtuosoClient.dll (if not allready there).\n\t Click on the "Set Initial State" link which registers the C# class with Virtuoso. Click on the "ho_s_14.sql" link to see the code behind this step \n\t Click on the "Run" links to actually experience the demo\n\t\n\tDemo Breakdown\n\t\n\t "ho_s_14.sql" registers the "openlink.virtuoso.tutorial.ho_s_14.add_data" C# static method with Virtuoso. Click \n\t\ton the "ho_s_14.cs" link to see the C# source code of this class\n\t \t"vsp1.vsp" uses the static method "add_data" of the "openlink.virtuoso.tutorial.ho._s_14" class to \n\t\tmake a resultset (like a SQL function would) through an in-process connection to the server. Take note of the\n\t\tusage of "OpenLink.Virtuoso.InProcessPort" key from AppDomain.GetData() to get the port on which the hosting Virtuoso server is listening at.\n\t\n \n " . rdf:type foaf:Document ; dc:title "Accessing COM Objects via C#" ; sioc:content "\n\tOverview\n\tThe following tutorial demonstrates how Virtuoso can access MS Windows COM\n\t objects via .NET. \n\tThe demonstrations in this section highlight transparent integration \n\t (hosting) between Virtuoso, the Microsoft .NET implementations of \n\t the ECMA Common Language Infrastructure (CLI) and the Win32 COM Layer. \n \n\tPrerequisites\n\tThe following prerequisites ensure the usability of these \n\t tutorial demos on Windows: \n\t\t\n\t\t .NET Runtime and Frameworks\n\t\t .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n\t\t Virtuoso Universal Server for Windows with .NET CLR Hosting\n\t\t\n \n\tTutorial Example\n\tThe following tutorial shows how the Virtuoso server can call native Win32 COM objects using\n\t the .NET runtime as intermediary. \n\tPlease follow the steps below to maximize the value of this tutorial:\n\t\n\t Register the COM library COM/VirtCOMServer/Debug/VirtCOMServer.dll with COM (via regsvr32.exe COM/VirtCOMServer/Debug/VirtCOMServer.dll).\n\t Copy the interop assembly COM/VirtCOMServer/VirtCOMServer.dll next to the virtuoso server binary (if not allready there).\n\t Click on the \"Set Initial State\" link which registers the C# interop class for the Interface IVirtCOMObject with Virtuoso. Click on the \"ho_s_15.sql\" link to see the code behind this step \n\t Click on the \"Run\" links to actually experience the demo\n\t\n\tDemo Breakdown\n\t\n\t \"ho_s_15.sql\" registers the \"VirtCOMServer.CVirtCOMObjectClass\" C# interop class with Virtuoso. Click \n\t\ton the \"VirtCOMObject.c\" and \"VirtCOMObject.h\" link to see the C++ source code of this interface and it's class\n\t \t\"vsp1.vsp\" uses the methods \"AddAmount\", \"Clear\" and \"get_balance\" of the \"VirtCOMServer.IVirtCOMObject\" Interface to \n\t\tsum a number of amounts and get the resulting total.\n\t\n " ; sioc:has_container ns2:hosting ; sioc:description "Using the .NET to access native COM objects from Virtuoso/PL" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "\n\tOverview\n\tThe following tutorial demonstrates how Virtuoso can access MS Windows COM\n\t objects via .NET. \n\tThe demonstrations in this section highlight transparent integration \n\t (hosting) between Virtuoso, the Microsoft .NET implementations of \n\t the ECMA Common Language Infrastructure (CLI) and the Win32 COM Layer. \n \n\tPrerequisites\n\tThe following prerequisites ensure the usability of these \n\t tutorial demos on Windows: \n\t\t\n\t\t .NET Runtime and Frameworks\n\t\t .Net Runtime and Framework SDK (if you seek to write your own Objects for integration with Virtuoso)\n\t\t Virtuoso Universal Server for Windows with .NET CLR Hosting\n\t\t\n \n\tTutorial Example\n\tThe following tutorial shows how the Virtuoso server can call native Win32 COM objects using\n\t the .NET runtime as intermediary. \n\tPlease follow the steps below to maximize the value of this tutorial:\n\t\n\t Register the COM library COM/VirtCOMServer/Debug/VirtCOMServer.dll with COM (via regsvr32.exe COM/VirtCOMServer/Debug/VirtCOMServer.dll).\n\t Copy the interop assembly COM/VirtCOMServer/VirtCOMServer.dll next to the virtuoso server binary (if not allready there).\n\t Click on the "Set Initial State" link which registers the C# interop class for the Interface IVirtCOMObject with Virtuoso. Click on the "ho_s_15.sql" link to see the code behind this step \n\t Click on the "Run" links to actually experience the demo\n\t\n\tDemo Breakdown\n\t\n\t "ho_s_15.sql" registers the "VirtCOMServer.CVirtCOMObjectClass" C# interop class with Virtuoso. Click \n\t\ton the "VirtCOMObject.c" and "VirtCOMObject.h" link to see the C++ source code of this interface and it's class\n\t \t"vsp1.vsp" uses the methods "AddAmount", "Clear" and "get_balance" of the "VirtCOMServer.IVirtCOMObject" Interface to \n\t\tsum a number of amounts and get the resulting total.\n\t\n \n " . rdf:type foaf:Document ; dc:title "Integrating Java Objects with Virtuoso" ; sioc:content "\n Overview\n The following tutorial demonstrates how Virtuoso can be extended \n through the use of Java to create User Defined Types (UDTs), Stored Procedures, \n and Functions. This is an enhancement of its Object-Relational Database functionality. \n The demonstrations in this section highlight transparent integration \n (hosting) between Virtuoso and the Java Runtime Environment. \n \n Prerequisites\n The following prerequisites ensure the usability of these tutorial demos on any platform with a Java Runtime environment:\n\n Java Runtime (J2EE 1.2 and Higher)\n Java SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server with Java Runtime Hosting \n \n\n Tutorial Example\nThe following tutorial shows how Java Classes are used to create User Defined Types (UDTs), Stored Procedures, and Functions in Virtuoso. \nPlease follow the steps below to maximize the value of this tutorial:\n\n Click on the \"Set Initial State\" link which registers the Java classes used in this demo with Virtuoso. Click on the \"ho_s_1.sql\" link to see the code behind this step \n Click on the \"Run\" links to actually experience the demo\n\n\nDemo Breakdown\n\n \"ho_s_1.sql\" performs the following steps\n \n Registers the \"MyFinances\" and \"Point\" Classes with Virtuoso as \n UDTs. Click on the \"MyFinances.java\" and \"Point.java\" links to see the \n JAVA source code \n Creates the conventional SQL table \"Employee\" \n Creates the Object-Relational table \"Supplier\" that includes a \n column named \"Location\" that is of Type \"Point\" (which is a UDT)\n Populates each of the newly created tables with data\n Creates the \"distance\" stored procedure which uses UDT \n methods to calculate the distance between points.\n \n \n \"vsp1.vsp\" uses the static method \"tax\" of the \"MyFinances\" \n class to compute the payroll tax values for each employee via the \n \"salary\" column (like a SQL function would). \n \"vsp2.vsp\" uses the \"distance\" method of the UDT based column \n \"location\" to test for distance values less than \"3\". The distance values are return values from the \"Point\" UDT. Note that \"Point\" class is computing the distance between two arbitrary points\n \"vsp3.vsp\" is a variation of the previous demo, with the UDT based \n column \"location\" being used to access and conditionally test the values of \n data member \"x\" (shown in \"Point.java\" as 0)\n \"vsp4.vsp\" is another variation of a query on the \"Supplier\" table, \n in this particular case the query uses a Stored Procedure (see definition in \n \"ho_s_2.sql\") to filter its result set. It achieves this by using data member \n values \"x\" and \"y\" from column \"location\", and the arbitrary values 1 & 2 \n as input parameters for the Stored Procedure \"distance\". It then tests \n the return values for those less than 3.\n\n " ; sioc:has_container ns2:hosting ; sioc:description "Using Java Objects to extend Virtuoso via User Defined Types." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "\n Overview\n The following tutorial demonstrates how Virtuoso can be extended \n through the use of Java to create User Defined Types (UDTs), Stored Procedures, \n and Functions. This is an enhancement of its Object-Relational Database functionality. \n The demonstrations in this section highlight transparent integration \n (hosting) between Virtuoso and the Java Runtime Environment. \n \n Prerequisites\n The following prerequisites ensure the usability of these tutorial demos on any platform with a Java Runtime environment:\n\n Java Runtime (J2EE 1.2 and Higher)\n Java SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server with Java Runtime Hosting \n \n\n Tutorial Example\nThe following tutorial shows how Java Classes are used to create User Defined Types (UDTs), Stored Procedures, and Functions in Virtuoso. \nPlease follow the steps below to maximize the value of this tutorial:\n\n Click on the "Set Initial State" link which registers the Java classes used in this demo with Virtuoso. Click on the "ho_s_1.sql" link to see the code behind this step \n Click on the "Run" links to actually experience the demo\n\n\nDemo Breakdown\n\n "ho_s_1.sql" performs the following steps\n \n Registers the "MyFinances" and "Point" Classes with Virtuoso as \n UDTs. Click on the "MyFinances.java" and "Point.java" links to see the \n JAVA source code \n Creates the conventional SQL table "Employee" \n Creates the Object-Relational table "Supplier" that includes a \n column named "Location" that is of Type "Point" (which is a UDT)\n Populates each of the newly created tables with data\n Creates the "distance" stored procedure which uses UDT \n methods to calculate the distance between points.\n \n \n "vsp1.vsp" uses the static method "tax" of the "MyFinances" \n class to compute the payroll tax values for each employee via the \n "salary" column (like a SQL function would). \n "vsp2.vsp" uses the "distance" method of the UDT based column \n "location" to test for distance values less than "3". The distance values are return values from the "Point" UDT. Note that "Point" class is computing the distance between two arbitrary points\n "vsp3.vsp" is a variation of the previous demo, with the UDT based \n column "location" being used to access and conditionally test the values of \n data member "x" (shown in "Point.java" as 0)\n "vsp4.vsp" is another variation of a query on the "Supplier" table, \n in this particular case the query uses a Stored Procedure (see definition in \n "ho_s_2.sql") to filter its result set. It achieves this by using data member \n values "x" and "y" from column "location", and the arbitrary values 1 & 2 \n as input parameters for the Stored Procedure "distance". It then tests \n the return values for those less than 3.\n\n \n " . rdf:type foaf:Document ; dc:title "Integrating Java Objects with Virtuoso" ; sioc:content "\n Overview\n The following tutorial demonstrates how Virtuoso can Restrict Java hosted types. \n \n Prerequisites\n The following prerequisites ensure the usability of these tutorial demos on any platform with a Java Runtime environment:\n\n Java Runtime (J2EE 1.2 and Higher)\n Java SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server with Java Runtime Hosting \n \n\n Tutorial Example\nPlease follow the steps below to maximize the value of this tutorial:\n\n Click on the \"Set Initial State\" link which registers the Java classes used in this demo with Virtuoso. Click on the \"ho_s_13.sql\" link to see the code behind this step \n Click on the \"Run\" links to actually experience the demo\n\n\nDemo Breakdown\n\n \"ho_s_13.sql\" performs the following steps\n \n Registers the \"Restricted\" and \"Unrestricted\" Classes with Virtuoso as \n UDTs. Click on the \"Restricted.java\" and \"Unrestricted.java\" links to see the \n JAVA source code \n The Restricted types can't write to FS, can't read System envariment. For full list from restrictions, please see documentation.\n \n \n\n " ; sioc:has_container ns2:hosting ; sioc:description "Using Restrictions for Java hosted types." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:52 GMT" ; content:encoded "\n Overview\n The following tutorial demonstrates how Virtuoso can Restrict Java hosted types. \n \n Prerequisites\n The following prerequisites ensure the usability of these tutorial demos on any platform with a Java Runtime environment:\n\n Java Runtime (J2EE 1.2 and Higher)\n Java SDK (if you seek to write your own Objects for integration with Virtuoso)\n Virtuoso Universal Server with Java Runtime Hosting \n \n\n Tutorial Example\nPlease follow the steps below to maximize the value of this tutorial:\n\n Click on the "Set Initial State" link which registers the Java classes used in this demo with Virtuoso. Click on the "ho_s_13.sql" link to see the code behind this step \n Click on the "Run" links to actually experience the demo\n\n\nDemo Breakdown\n\n "ho_s_13.sql" performs the following steps\n \n Registers the "Restricted" and "Unrestricted" Classes with Virtuoso as \n UDTs. Click on the "Restricted.java" and "Unrestricted.java" links to see the \n JAVA source code \n The Restricted types can't write to FS, can't read System envariment. For full list from restrictions, please see documentation.\n \n \n\n \n " . rdf:type foaf:Document ; dc:title "Filter WebDAV content content by XQuery" ; sioc:content "\n\tPreliminary\n\t\n\t XQuery collection function can be used to get all parsed documents in collection. Virtuoso engine supports several types of collections:\n\t\n\t\n\t http://local.virt/DAV/PATHTO - local DAV collection. Contains all documents in DAV collection with path \"PATHTO\".\n\t \n\t http://host:port/path - any other URL that can be used to access remote WebDAV collections \n\t\n\tIn this example collection function is used to filter local blog entries and all cached blog entries from subscriptions. search.vsp uses this collection to filter blogs by XPath exression. For instance, search.vsp with '//a' expression returns all link from all blogs.\n\t\n\t\n\t text.vsp uses collection function to search blogs which contain some word. Note, it uses \"contains\" predicate to search blogs, this means it is case sensitive.\n\t\n \n\tPrerequisites\n\tThis example needs the following VAD packages to be installed:\n\t\n\t Conductor\n\t Framework\n\t Briefcase\n\t Feed Manager\n\t Weblog\n\t\n\tIf you do not have permissions to install the above please ask the administrator.\n\tThe VAD installation can be done via Conductor (if it's installed) or via ISQL tool using vad_install() API function. \n\t For more details on vad installation please read the user manual.\n\t\n\t Important: before to run any of the actions bellow you need to setup a ODS account (or use tutorial_demo with password secret).\n\t In both cases you will need to login in ODS and create instances of the Briefcase, Feed Manager and Weblog applications. \n\t\n\t\n\t Using the Feed Manager you should subscribe to some news feeds in RSS, Atom or RDF format.\n\t\n\t\n\t Using the Briefcase you can upload some sample data in the account's home directory.\n\t\n\t\n\t Using the Weblog, make few sample blog posts.\n\t\n \n\tExample overview\n\tThis example demonstrates:\n\t\n\t XQuery collection function\n\t XPath extension functions\n\t WebDAV Resource Filtering and WebDAV Extension Types (DETs)\n\t\n \n\tExample Operation\n\t\n\t Login into ODS using the link bellow, after successfull authentication the ODS login will redirect browser back to this page\n\t Using the link 'Run' start the search.vsp\n\t Initially you will have the ODS account's home directory set as a base, so you can change it using the browse button\n\t If you don't have initial data loaded or data which not satisfies the conditions, the query execution will be produce empty result.\n\t\n \n\tExample Setup\n\tThe demo support functions are prepared by loading the supplied SQL file\n \n How to run the examples\n\t\n\t In order to enter the initial data via ODS you need to login and create instances via ODS. After entering the initial data, you will need to go back to this page. If you already done this just skip this step\n\t In order to run the examples, you need to login in the Web Applications.\n\t To login you can use the already defined user \"tutorial_demo\" with password \"secret\" case sensitive. \n\t When you click the \"Run\" link of the search.vsp file the browser will be redirected to ODS login page. After succefull login the browser will be redirected back to this page. \n\t\n " ; sioc:has_container ns2:xmlapps , ns2:xml ; sioc:description "fn:collection usage example" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\n\tPreliminary\n\t\n\t XQuery collection function can be used to get all parsed documents in collection. Virtuoso engine supports several types of collections:\n\t\n\t\n\t http://local.virt/DAV/PATHTO - local DAV collection. Contains all documents in DAV collection with path "PATHTO".\n\t \n\t http://host:port/path - any other URL that can be used to access remote WebDAV collections \n\t\n\tIn this example collection function is used to filter local blog entries and all cached blog entries from subscriptions. search.vsp uses this collection to filter blogs by XPath exression. For instance, search.vsp with '//a' expression returns all link from all blogs.\n\t\n\t\n\t text.vsp uses collection function to search blogs which contain some word. Note, it uses "contains" predicate to search blogs, this means it is case sensitive.\n\t\n \n\tPrerequisites\n\tThis example needs the following VAD packages to be installed:\n\t\n\t Conductor\n\t Framework\n\t Briefcase\n\t Feed Manager\n\t Weblog\n\t\n\tIf you do not have permissions to install the above please ask the administrator.\n\tThe VAD installation can be done via Conductor (if it's installed) or via ISQL tool using vad_install() API function. \n\t For more details on vad installation please read the user manual.\n\t\n\t Important: before to run any of the actions bellow you need to setup a ODS account (or use tutorial_demo with password secret).\n\t In both cases you will need to login in ODS and create instances of the Briefcase, Feed Manager and Weblog applications. \n\t\n\t\n\t Using the Feed Manager you should subscribe to some news feeds in RSS, Atom or RDF format.\n\t\n\t\n\t Using the Briefcase you can upload some sample data in the account's home directory.\n\t\n\t\n\t Using the Weblog, make few sample blog posts.\n\t\n \n\tExample overview\n\tThis example demonstrates:\n\t\n\t XQuery collection function\n\t XPath extension functions\n\t WebDAV Resource Filtering and WebDAV Extension Types (DETs)\n\t\n \n\tExample Operation\n\t\n\t Login into ODS using the link bellow, after successfull authentication the ODS login will redirect browser back to this page\n\t Using the link 'Run' start the search.vsp\n\t Initially you will have the ODS account's home directory set as a base, so you can change it using the browse button\n\t If you don't have initial data loaded or data which not satisfies the conditions, the query execution will be produce empty result.\n\t\n \n\tExample Setup\n\tThe demo support functions are prepared by loading the supplied SQL file\n \n How to run the examples\n\t\n\t In order to enter the initial data via ODS you need to login and create instances via ODS. After entering the initial data, you will need to go back to this page. If you already done this just skip this step\n\t In order to run the examples, you need to login in the Web Applications.\n\t To login you can use the already defined user "tutorial_demo" with password "secret" case sensitive. \n\t When you click the "Run" link of the search.vsp file the browser will be redirected to ODS login page. After succefull login the browser will be redirected back to this page. \n\t\n \n " . rdf:type foaf:Document ; dc:title "Filter blogs content by XQuery" ; sioc:content "\n Example\n collection description\n \n XQuery collection function can be used to get all parsed documents in collection. Virtuoso engine supports several types of collections:\n \n \n http://local.virt/DAV/PATHTO - local DAV collection. Contains all documents in DAV collection with path \"PATHTO\".\n \n http://..... - any other URI relates to remote DAV collections \n \n In this example collection function is used to concatenate the entries from several RSS feed files and show their titles and link to the articles. example.vsp uses this collection to filter blogs by XPath exression. For instance, example.vsp with '//link' expression returns all link from all feeds.\n Click on the \"Set initial state\" link to load the XML files in /DAV/feeds/xq_s_2a/ DAV Collection.\n Click on the \"Run\" link to experience the demo. Please note that some of the options query files loaded in demo XQ-S-2.\n " ; sioc:has_container ns2:xmlapps , ns2:xml ; sioc:description "collection usage example" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\n Example\n collection description\n \n XQuery collection function can be used to get all parsed documents in collection. Virtuoso engine supports several types of collections:\n \n \n http://local.virt/DAV/PATHTO - local DAV collection. Contains all documents in DAV collection with path "PATHTO".\n \n http://..... - any other URI relates to remote DAV collections \n \n In this example collection function is used to concatenate the entries from several RSS feed files and show their titles and link to the articles. example.vsp uses this collection to filter blogs by XPath exression. For instance, example.vsp with '//link' expression returns all link from all feeds.\n Click on the "Set initial state" link to load the XML files in /DAV/feeds/xq_s_2a/ DAV Collection.\n Click on the "Run" link to experience the demo. Please note that some of the options query files loaded in demo XQ-S-2.\n \n " . rdf:type foaf:Document ; dc:title "Slashdot RSS feed retrieval" ; sioc:content "\n Example\n document description\n \n XQuery document function can be used to get a parsed document via URL.\n \n In this example the document is used to retreive the Slashdot RSS feed and convert the contents into a feed index.\n Click on the \"Set initial state\" link to load the slash.xml file in /DAV/xmlsql/ DAV Collection with execute permisions.\n Click on the \"Run\" link and the browser will be redirected to /DAV/xmlsql/slash.xml?contenttype=text/html.\n " ; sioc:has_container ns2:xmlapps , ns2:xml ; sioc:description "document usage example" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\n Example\n document description\n \n XQuery document function can be used to get a parsed document via URL.\n \n In this example the document is used to retreive the Slashdot RSS feed and convert the contents into a feed index.\n Click on the "Set initial state" link to load the slash.xml file in /DAV/xmlsql/ DAV Collection with execute permisions.\n Click on the "Run" link and the browser will be redirected to /DAV/xmlsql/slash.xml?contenttype=text/html.\n \n " . rdf:type foaf:Document ; dc:title "OPML file generation from XHTML source" ; sioc:content "\n Example\n \n\t The demo retrieve a HTML pages containing attendees or bloggers listings and convert them to OPML.\n\t The conversion is done with XQuery and user-defined XPath functions to resolve the feeds URLs. \n \n \n\t The demo also retrieve few OPML files and re-construct them having the feeds URLs if they are missing.\n \n \n\t When setting the initial state, the demo starts to retrieve pages from the different sites. \n\t It could take a long time depending on the Internet connection of the machine that Virtuoso is running on. \n\t It is safe to leave the pop-up open without waiting it to finish and press on the \"Run\" links,\n\t however if this is the first time you run the initial state, the demo will show only partial results.\n\t Once the feeds are resolved they will be cached locally in a database table and the generated OPML files will\n\t be stored as a WebDAV resources.\n \n \n\t The following are source references used in the demo:\n \n \n\t http://wiki.techcrunch.com/third_meetup \t\t\t\t \n\t http://news.com.com/html/ne/blogs/CNETNewsBlog100.opml\t\t\t\n\t http://conferences.oreillynet.com/pub/w/23/speakers.html \n\t http://conferences.oreillynet.com/pub/w/38/speakers.html \n\t http://www.alwayson-network.com/comments.php?id=10852_0_11_0_C \n\t http://www.gnomedex.com/holdings/br_2005%20Gnomedexers.opml\t\t\t\n\t http://www.web2con.com/pub/w/40/speakers.html \n\t http://www.thenewpr.com/wiki/pmwiki.php?pagename=Resources.CEOBlogsList \n\t http://nwr.cowblock.net/index.php?action=list\t\t\t\t\n\t http://okrasoup.typepad.com/black_looks/2005/05/naija_blogs.html\t\t\n\t http://allafrica.com/afdb/blogs/blogafrica.opml \n \n " ; sioc:has_container ns2:xml , ns2:xmlapps ; sioc:description "document usage example" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\n Example\n \n\t The demo retrieve a HTML pages containing attendees or bloggers listings and convert them to OPML.\n\t The conversion is done with XQuery and user-defined XPath functions to resolve the feeds URLs. \n \n \n\t The demo also retrieve few OPML files and re-construct them having the feeds URLs if they are missing.\n \n \n\t When setting the initial state, the demo starts to retrieve pages from the different sites. \n\t It could take a long time depending on the Internet connection of the machine that Virtuoso is running on. \n\t It is safe to leave the pop-up open without waiting it to finish and press on the "Run" links,\n\t however if this is the first time you run the initial state, the demo will show only partial results.\n\t Once the feeds are resolved they will be cached locally in a database table and the generated OPML files will\n\t be stored as a WebDAV resources.\n \n \n\t The following are source references used in the demo:\n \n \n\t http://wiki.techcrunch.com/third_meetup \t\t\t\t \n\t http://news.com.com/html/ne/blogs/CNETNewsBlog100.opml\t\t\t\n\t http://conferences.oreillynet.com/pub/w/23/speakers.html \n\t http://conferences.oreillynet.com/pub/w/38/speakers.html \n\t http://www.alwayson-network.com/comments.php?id=10852_0_11_0_C \n\t http://www.gnomedex.com/holdings/br_2005%20Gnomedexers.opml\t\t\t\n\t http://www.web2con.com/pub/w/40/speakers.html \n\t http://www.thenewpr.com/wiki/pmwiki.php?pagename=Resources.CEOBlogsList \n\t http://nwr.cowblock.net/index.php?action=list\t\t\t\t\n\t http://okrasoup.typepad.com/black_looks/2005/05/naija_blogs.html\t\t\n\t http://allafrica.com/afdb/blogs/blogafrica.opml \n \n \n " . rdf:type foaf:Document ; dc:title "Overview" ; sioc:content "\nXMLELEMENT() function. Overview\n\nXMLELEMENT takes an element name for identifier, an optional collection of attributes for the element, \n and arguments that make up the element's content. \n It returns an XML element. The second parameter may be omitted and at that time the \n rest parameters may be present. If one of the arguments is a call of the xpath_eval returning \n an attribute value, then this value would be added to element's content (not to element's attributes).\n\n\nXMLATTRIBUTES() function. Overview\n\n This function creates a vector that may be used only as argument of \n XMLELEMENT function. The vector has an even number of elements, each odd element is a name of an attribute, an\n even element is its value. If the attribute value is NULL, then no attribute and no value is created.\n If none of the attribute is created, then the function returns null.\n If a parameter of the function is a column name, then you can omit the 'AS clause', and Virtuoso uses the partially escaped form of \n the column name as the attribute name. \n\n\nsx_e_? Demos\n\n Countinue with the next sx_e_? demos to see examples of functoins usage\n\n" ; sioc:has_container ns2:xml ; sioc:description "XMLELEMENT() function." ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nXMLELEMENT() function. Overview\n\nXMLELEMENT takes an element name for identifier, an optional collection of attributes for the element, \n and arguments that make up the element's content. \n It returns an XML element. The second parameter may be omitted and at that time the \n rest parameters may be present. If one of the arguments is a call of the xpath_eval returning \n an attribute value, then this value would be added to element's content (not to element's attributes).\n\n\nXMLATTRIBUTES() function. Overview\n\n This function creates a vector that may be used only as argument of \n XMLELEMENT function. The vector has an even number of elements, each odd element is a name of an attribute, an\n even element is its value. If the attribute value is NULL, then no attribute and no value is created.\n If none of the attribute is created, then the function returns null.\n If a parameter of the function is a column name, then you can omit the 'AS clause', and Virtuoso uses the partially escaped form of \n the column name as the attribute name. \n\n\nsx_e_? Demos\n\n Countinue with the next sx_e_? demos to see examples of functoins usage\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element without content" ; sioc:content "\nExample 1\nThis example shows a simple use of the XMLELEMENT() for creating the xml element 'Employee' (for each \nemployee) without content:\n\n\nselect XMLELEMENT (\"Employee\") from \"Demo\".\"demo\".\"Employees\"\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element without content" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 1\nThis example shows a simple use of the XMLELEMENT() for creating the xml element 'Employee' (for each \nemployee) without content:\n\n\nselect XMLELEMENT ("Employee") from "Demo"."demo"."Employees"\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with a text content" ; sioc:content "\nExample 2\nThis example shows a use of the XMLELEMENT() for creating the xml element 'EmployeeName' \n(for each employee) with the text content that is value of the 'LastName' column from the \n\"Demo\".\"demo\".\"Employees\" table.\n\n\nselect XMLELEMENT (\"EmployeeName\", \"LastName\") \nfrom \"Demo\".\"demo\".\"Employees\";\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with a text content" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 2\nThis example shows a use of the XMLELEMENT() for creating the xml element 'EmployeeName' \n(for each employee) with the text content that is value of the 'LastName' column from the \n"Demo"."demo"."Employees" table.\n\n\nselect XMLELEMENT ("EmployeeName", "LastName") \nfrom "Demo"."demo"."Employees";\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with attributes" ; sioc:content "\nExample 3\nThis example shows a use of the XMLELEMENT() for creating the xml element 'Emp' with three \nattributes - 'EmployeeID', 'firstname' and 'lastname' getting their values from the \n'EmployeeID', 'FirstName' and 'LastName' columns, respectively. The pairs of attribute and its \nvalue are produced by XMLATTRIBUTES() function. If a parameter of the XMLATTRIBUTES() has no 'as clause', \nVirtuoso uses the partially escaped form of the column name as the attribute name. \n\n\nselect\n XMLELEMENT (\"Emp\", XMLATTRIBUTES (\"EmployeeID\", \"FirstName\" as \"firstname\", \"LastName\" as \"lastname\"))\nfrom \"Demo\".\"demo\".\"Employees\";\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with attributes" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 3\nThis example shows a use of the XMLELEMENT() for creating the xml element 'Emp' with three \nattributes - 'EmployeeID', 'firstname' and 'lastname' getting their values from the \n'EmployeeID', 'FirstName' and 'LastName' columns, respectively. The pairs of attribute and its \nvalue are produced by XMLATTRIBUTES() function. If a parameter of the XMLATTRIBUTES() has no 'as clause', \nVirtuoso uses the partially escaped form of the column name as the attribute name. \n\n\nselect\n XMLELEMENT ("Emp", XMLATTRIBUTES ("EmployeeID", "FirstName" as "firstname", "LastName" as "lastname"))\nfrom "Demo"."demo"."Employees";\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with attribute, a text content and a sublement" ; sioc:content "\nExample 4\nThis example shows a use of the XMLELEMENT() for creating the xml element 'Employee' with the \n'EmployeeID' attribute, text content that is concatenations of the value of the 'FirstName' column, \nof the blank character and of the value of the 'LastName', and the 'Title' subelement having \n'title' attribute.\n\n\nselect XMLELEMENT ('Employee', XMLATTRIBUTES (\"EmployeeID\"), \"FirstName\"||' '||\"LastName\", \n XMLELEMENT(\"Title\", XMLATTRIBUTES ( \"Title\" as \"title\")))\nfrom \"Demo\".\"demo\".\"Employees\";\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with attribute, a text content and a sublement" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 4\nThis example shows a use of the XMLELEMENT() for creating the xml element 'Employee' with the \n'EmployeeID' attribute, text content that is concatenations of the value of the 'FirstName' column, \nof the blank character and of the value of the 'LastName', and the 'Title' subelement having \n'title' attribute.\n\n\nselect XMLELEMENT ('Employee', XMLATTRIBUTES ("EmployeeID"), "FirstName"||' '||"LastName", \n XMLELEMENT("Title", XMLATTRIBUTES ( "Title" as "title")))\nfrom "Demo"."demo"."Employees";\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with two nested subelements" ; sioc:content "\nExample 5\nThis example shows a use of the XMLELEMENT() for creating the xml element \n'FullName' with two subelements 'firstname' and 'lastname'. Both subelements have the \nsimple text content. \n\n\nselect\n XMLELEMENT ('FullName',\n XMLELEMENT ('firstname', \"FirstName\"),\n XMLELEMENT ('lastname', \"LastName\"))\nfrom \"Demo\".\"demo\".\"Employees\";\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with two nested subelements" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 5\nThis example shows a use of the XMLELEMENT() for creating the xml element \n'FullName' with two subelements 'firstname' and 'lastname'. Both subelements have the \nsimple text content. \n\n\nselect\n XMLELEMENT ('FullName',\n XMLELEMENT ('firstname', "FirstName"),\n XMLELEMENT ('lastname', "LastName"))\nfrom "Demo"."demo"."Employees";\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with nested XMLFOREST() function" ; sioc:content "\nExample 6\nThe example shows a use of the XMLELEMENT() with the nested call of XMLFOREST() function. The result is identical\nto the previous example.\n\n\nselect\n XMLELEMENT ('FullName',\n XMLFOREST (\"FirstName\"as \"firstname\", \"LastName\" as \"lastname\"))\nfrom \"Demo\".\"demo\".\"Employees\";\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with XMLFOREST() function call as parameter" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 6\nThe example shows a use of the XMLELEMENT() with the nested call of XMLFOREST() function. The result is identical\nto the previous example.\n\n\nselect\n XMLELEMENT ('FullName',\n XMLFOREST ("FirstName"as "firstname", "LastName" as "lastname"))\nfrom "Demo"."demo"."Employees";\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with nested XMLCONCAT() function" ; sioc:content "\nExample 7\nThe example shows a use of the XMLELEMENT() with the nested call of XMLCONCAT() function. The result is identical\nto the previous two examples.\n\n\nselect\n XMLELEMENT ('FullName',\n XMLCONCAT (\n XMLELEMENT ('firstname', \"FirstName\"),\n XMLELEMENT ('lastname', \"LastName\"))) \nfrom \"Demo\".\"demo\".\"Employees\";\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with XMLCONCAT() function call as parameter" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 7\nThe example shows a use of the XMLELEMENT() with the nested call of XMLCONCAT() function. The result is identical\nto the previous two examples.\n\n\nselect\n XMLELEMENT ('FullName',\n XMLCONCAT (\n XMLELEMENT ('firstname', "FirstName"),\n XMLELEMENT ('lastname', "LastName"))) \nfrom "Demo"."demo"."Employees";\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with nested XMLAGG() function" ; sioc:content "\nExample 8\nThis example produces an 'Emp' element with attribute 'Title'\nand a list of all employees having the title 'Sales Representative' as element content.\n\n\nselect XMLELEMENT ('Emp', XMLATTRIBUTES (\"Title\"), \n XMLAGG (XMLELEMENT ('Name', \"FirstName\", ' ', \"LastName\")))\nfrom \"Demo\".\"demo\".\"Employees\"\nwhere \"Title\"= 'Sales Representative';\n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with XMLAGG() function call as parameter" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 8\nThis example produces an 'Emp' element with attribute 'Title'\nand a list of all employees having the title 'Sales Representative' as element content.\n\n\nselect XMLELEMENT ('Emp', XMLATTRIBUTES ("Title"), \n XMLAGG (XMLELEMENT ('Name', "FirstName", ' ', "LastName")))\nfrom "Demo"."demo"."Employees"\nwhere "Title"= 'Sales Representative';\n\n\n " . rdf:type foaf:Document ; dc:title "Making an XML element with the entity objects as parameters " ; sioc:content "\nExample 9\nThis example creates an 'FullAddress' element with \n\n four attributes, three of them ('PostalCode', 'Address', 'City') are\n produced by XMLATTRIBUTES, and the fourth attribute - 'country' is calculated by \n xquery_eval \n 'Region' subelement, that is produced by xtree_doc\n text content, that is produced by xpath_eval \n 'emp' subelement with text content from the column \"LastName\", that is created by nested\n XMLELEMENT\n\n\nselect XMLELEMENT ('FullAddress',\n XMLATTRIBUTES ( \"PostalCode\", \"Address\", \"City\"),\n xtree_doc ('WA'),\n xquery_eval('//@country', xtree_doc('')),\n xpath_eval('//@Phone', xtree_doc('')),\n XMLELEMENT('emp', \"LastName\"))\nfrom \"Demo\".\"demo\".\"Employees\" \n\n" ; sioc:has_container ns2:xml ; sioc:description "XML element with the entity objects as parameters" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nExample 9\nThis example creates an 'FullAddress' element with \n\n four attributes, three of them ('PostalCode', 'Address', 'City') are\n produced by XMLATTRIBUTES, and the fourth attribute - 'country' is calculated by \n xquery_eval \n 'Region' subelement, that is produced by xtree_doc\n text content, that is produced by xpath_eval \n 'emp' subelement with text content from the column "LastName", that is created by nested\n XMLELEMENT\n\n\nselect XMLELEMENT ('FullAddress',\n XMLATTRIBUTES ( "PostalCode", "Address", "City"),\n xtree_doc ('<Region>WA</Region>'),\n xquery_eval('//@country', xtree_doc('<a country="USA"/>')),\n xpath_eval('//@Phone', xtree_doc('<a Phone="(206) 555-9857"/>')),\n XMLELEMENT('emp', "LastName"))\nfrom "Demo"."demo"."Employees" \n\n\n " . rdf:type foaf:Document ; dc:title "Making a Forest of XML elements" ; sioc:content "\nXMLFOREST() function. Overview\n\nXMLFOREST produces a forest of XML elements from the given list of arguments. \n The arguments may be string expressions with optional aliases. If string expression is a column name, \n then you can omit the 'AS clause', and Virtuoso uses the partially escaped form of \n the column name as the name of the enclosing tag. If the expression evaluates to NULL, then no element is \n created for that expression. If none of the element is created, then the function returns null.\n\n\nExample 1\nThis example produces a forest of five (or four) elements ('FName', 'LName', 'Title', 'Region' - if there is a value, 'str') \nwith the text content from 'FirstName', 'LastName', 'Title', and 'Region' \ncolumns of the \"Employees\" table and 'simple_string' string,\nand concatenates the elements produced. Five elements are created for the employee with \"EmployeeId\" = 1 and four elements \nare created for the employee with \"EmployeeId\" = 5:\n\n\nselect XMLFOREST (\"FirstName\" as \"FName\", \"LastName\" as \"LName\", \"Title\", \"Region\", 'simple_string' as \"str\")\n from \"Demo\".\"demo\".\"Employees\" \n where \"EmployeeId\" = 1 or \"EmployeeId\" = 5\n\n" ; sioc:has_container ns2:xml ; sioc:description "XMLFOREST() function" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nXMLFOREST() function. Overview\n\nXMLFOREST produces a forest of XML elements from the given list of arguments. \n The arguments may be string expressions with optional aliases. If string expression is a column name, \n then you can omit the 'AS clause', and Virtuoso uses the partially escaped form of \n the column name as the name of the enclosing tag. If the expression evaluates to NULL, then no element is \n created for that expression. If none of the element is created, then the function returns null.\n\n\nExample 1\nThis example produces a forest of five (or four) elements ('FName', 'LName', 'Title', 'Region' - if there is a value, 'str') \nwith the text content from 'FirstName', 'LastName', 'Title', and 'Region' \ncolumns of the "Employees" table and 'simple_string' string,\nand concatenates the elements produced. Five elements are created for the employee with "EmployeeId" = 1 and four elements \nare created for the employee with "EmployeeId" = 5:\n\n\nselect XMLFOREST ("FirstName" as "FName", "LastName" as "LName", "Title", "Region", 'simple_string' as "str")\n from "Demo"."demo"."Employees" \n where "EmployeeId" = 1 or "EmployeeId" = 5\n\n\n " . rdf:type foaf:Document ; dc:title "Making a Forest of XML elements by XMLCONCAT() function" ; sioc:content "\nXMLCONCAT() function Overview\n\nXMLCONCAT() accepts a list of XML value expressions as its arguments, and produces a forest of elements by \n concatenating the XML values that are returned from the same row to make one value. \n XMLCONCAT works like XMLFOREST,\n except that XMLCONCAT parameters is a list of XML elements. \n Null expressions are dropped from the result. If all the value expressions are null, then the function returns null.\n\nExample 1\n This example produces a forest from the 'FName', 'LName' and 'Region' (if a column value is not NULL)\n elements for each employee: \n\n\nselect XMLCONCAT (\n XMLELEMENT ('FName', \"FirstName\"), XMLELEMENT ('LName', \"LastName\"), \n XMLELEMENT ('Region', \"Region\") )\nfrom \"Demo\".\"demo\".\"Employees\"; \n\n" ; sioc:has_container ns2:xml ; sioc:description "XMLCONCAT() function" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nXMLCONCAT() function Overview\n\nXMLCONCAT() accepts a list of XML value expressions as its arguments, and produces a forest of elements by \n concatenating the XML values that are returned from the same row to make one value. \n XMLCONCAT works like XMLFOREST,\n except that XMLCONCAT parameters is a list of XML elements. \n Null expressions are dropped from the result. If all the value expressions are null, then the function returns null.\n\nExample 1\n This example produces a forest from the 'FName', 'LName' and 'Region' (if a column value is not NULL)\n elements for each employee: \n\n\nselect XMLCONCAT (\n XMLELEMENT ('FName', "FirstName"), XMLELEMENT ('LName', "LastName"), \n XMLELEMENT ('Region', "Region") )\nfrom "Demo"."demo"."Employees"; \n\n\n " . rdf:type foaf:Document ; dc:title "Making a Forest of XML elements by XMLAGG() function" ; sioc:content "\nXMLAGG() function. Overview\n\nXMLAGG is aggregate function that produces a forest of XML elements from the given list of xml elements. \n It concatenates the values returned from one column of multiple rows, unlike XMLCONCAT, \n which concatenates the values returned from multiple columns in the same row.\n\n\nExample 1\nThis example produces a forest of all 'Name' of the employees having \nthe title 'Sales Representative' and places it into one top-level element:\n\n select XMLELEMENT ('SalesRepresentatives',\n XMLAGG (XMLELEMENT ('Name', \"FirstName\", ' ', \"LastName\")) )\n from \"Demo\".\"demo\".\"Employees\"\n where \"Title\"='Sales Representative';\n\n" ; sioc:has_container ns2:xml ; sioc:description "XMLAGG() function" ; dcterms:created_at "Fri, 27 Dec 2019 14:12:54 GMT" ; content:encoded "\nXMLAGG() function. Overview\n\nXMLAGG is aggregate function that produces a forest of XML elements from the given list of xml elements. \n It concatenates the values returned from one column of multiple rows, unlike XMLCONCAT, \n which concatenates the values returned from multiple columns in the same row.\n\n\nExample 1\nThis example produces a forest of all 'Name' of the employees having \nthe title 'Sales Representative' and places it into one top-level element:\n\n select XMLELEMENT ('SalesRepresentatives',\n XMLAGG (XMLELEMENT ('Name', "FirstName", ' ', "LastName")) )\n from "Demo"."demo"."Employees"\n where "Title"='Sales Representative';\n\n\n " . rdf:type foaf:Document ; dc:title "Making a freetext index" ; sioc:content "\nPreliminaries\n\n Virtuoso provides a compact and efficient free text indexing capability\n for text and XML data. A free text index can be created on any character\n column, including wide and long data.\n If the column being indexed is XML data, this can be declared and enforced\n by the text index. XML data will be indexed specially to support efficient\n XPATH predicate evaluation with the xcontains predicate.\n\ncreate_freetext_index\n\t: CREATE TEXT [XML] INDEX ON q_table_name '(' column ')'\n\t[WITH KEY column]\n\t[NOT INSERT] \n\t[CLUSTERED WITH '(' column_commalist ')' ] \n\t[USING FUNCTION]\n\t[LANGUAGE STRING]\n\t;\nThe XML keyword specifies that the data is to be indexed as XML, hence\nelement names and attributes will be processed separately for use with the\nXCONTAINS predicate.\n\n\nExample\n\n The script inserts the files into the table.\n The data is stored as text, not as persistent XML.\n A VSP page shows the list of rows in the table.\n Each row has the following links:\n \n XML source - send the XML text as escaped text enclosed in an HTML 
 tag.\n     Raw XML - send the XML to the user agent, which must be able to render XML.\n   \n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Freetext index over XML data" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  Virtuoso provides a compact and efficient free text indexing capability\n   for text and XML data.  A free text index can be created on any character\n   column, including wide and long data.\n  If the column being indexed is XML data, this can be declared and enforced\n   by the text index.  XML data will be indexed specially to support efficient\n   XPATH predicate evaluation with the xcontains predicate.\n\ncreate_freetext_index\n\t: CREATE TEXT [XML] INDEX ON q_table_name '(' column ')'\n\t[WITH KEY column]\n\t[NOT INSERT]  \n\t[CLUSTERED WITH '(' column_commalist ')' ] \n\t[USING FUNCTION]\n\t[LANGUAGE STRING]\n\t;\nThe XML keyword specifies that the data is to be indexed as XML, hence\nelement names and attributes will be processed separately for use with the\nXCONTAINS predicate.\n\n\nExample\n\n  The script inserts the files into the table.\n  The data is stored as text, not as persistent XML.\n  A VSP page shows the list of rows in the table.\n  Each row has the following links:\n   \n     XML source - send the XML text as escaped text enclosed in an HTML <pre> tag.\n     Raw XML - send the XML to the user agent, which must be able to render XML.\n   \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Making a freetext index" ;
	sioc:content	"\nExample\n\n  Take the table def from nwxml3.sql\n  note the create text xml index ....\n  The script inserts the files into the table.\n  The data is stored as persistent XML.\n  A VSP page shows the list of rows in the table.\n  Each row has the following links:\n    \n      XML source - send the XML text as escaped text enclosed in an HTML 
 tag.\n      Raw XML - send the XML to the user agent. Must be able to render XML.\n    \n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Freetext index over persistent XML data" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample\n\n  Take the table def from nwxml3.sql\n  note the create text xml index ....\n  The script inserts the files into the table.\n  The data is stored as persistent XML.\n  A VSP page shows the list of rows in the table.\n  Each row has the following links:\n    \n      XML source - send the XML text as escaped text enclosed in an HTML <pre> tag.\n      Raw XML - send the XML to the user agent. Must be able to render XML.\n    \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Search on freetext indexed data" ;
	sioc:content	"\nExample\n\n  The example shows entity references using data from XS-S-1.\n  The VSP page has a button for retrieving title elements from a selected document, where the\n   title element contains a substring.\n  The example uses the 'xpath-contains' predicate.\n  The VSP page has a second button with the same function using text-contains.\n  This illustrates that xcontains + text-contains does not go through links, but that xpath_contains +\ncontains does.\n  The example has a viewer for the source of each page so that the entity references can be seen.\n  The page has some of the rows of the text table as persistent XML and others as text.\n  The columns are declared as ANY in SQL. This illustrates the late binding dependent on representation.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Search on freetext indexed data" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample\n\n  The example shows entity references using data from XS-S-1.\n  The VSP page has a button for retrieving title elements from a selected document, where the\n   title element contains a substring.\n  The example uses the 'xpath-contains' predicate.\n  The VSP page has a second button with the same function using text-contains.\n  This illustrates that xcontains + text-contains does not go through links, but that xpath_contains +\ncontains does.\n  The example has a viewer for the source of each page so that the entity references can be seen.\n  The page has some of the rows of the text table as persistent XML and others as text.\n  The columns are declared as ANY in SQL. This illustrates the late binding dependent on representation.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Storing of XSLT results" ;
	sioc:content	"\nExample\n\n  The example shows entity references using data from XS-S-1.\n  The VSP page has a button for retrieving title elements from a selected document, where the title\n   element contains a substring.\n  The example uses the 'xpath contains' predicate.\n  The VSP page has a second button with the same function using text-contains.\n  This illustrates that xcontains + text-contains does not go through links, but that xpath_contains +\ncontains does.\n  The example has a viewer for the source of each page so that the entity references can be seen.\n  The page has some of the rows of the text table as persistent XML and others as text.\n  The columns are declared as ANY in SQL. This illustrates the late binding dependent on representation.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Search on freetext indexed data using xcontains predicate" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample\n\n  The example shows entity references using data from XS-S-1.\n  The VSP page has a button for retrieving title elements from a selected document, where the title\n   element contains a substring.\n  The example uses the 'xpath contains' predicate.\n  The VSP page has a second button with the same function using text-contains.\n  This illustrates that xcontains + text-contains does not go through links, but that xpath_contains +\ncontains does.\n  The example has a viewer for the source of each page so that the entity references can be seen.\n  The page has some of the rows of the text table as persistent XML and others as text.\n  The columns are declared as ANY in SQL. This illustrates the late binding dependent on representation.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Storing of XSLT results" ;
	sioc:content	"\nExample\n\n  The sample shows storing of XSLT results into a table.\n  The sample will take abstracts and other suitable subsections from the\n  XS-S-1 data and insert them into another table.\n  The VSP will show the source and result of the transformation side by side for any given document.\n  The example uses data from XS-S-1, so it is important to set it first before trying this demo.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Storing of XSLT results" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nExample\n\n  The sample shows storing of XSLT results into a table.\n  The sample will take abstracts and other suitable subsections from the\n  XS-S-1 data and insert them into another table.\n  The VSP will show the source and result of the transformation side by side for any given document.\n  The example uses data from XS-S-1, so it is important to set it first before trying this demo.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"XPATH interpreter" ;
	sioc:content	"\nExample\n\n  This example allows a selection from a document formed by\n   XS-S-1, and applies a user-written XPATH expression to it.\n   The page has selectable sample expressions including:\n   \n    Count of all titles\n    Sum of the length of sect2 titles\n    All first paragraphs of sect2's.\n   \n  The example uses xpath_eval, and iterates on the results if an array is produced.\n  A single element of the XS-S-1 data is picked as the context node.\n  A special button applies the operation on all rows with xpath_contains, showing the result set\n   with doc name and result.\n  This shows how one row can make multiple results with xpath_contains,\n   but will return an array with xpath_eval.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Applying the XPATH expression" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nExample\n\n  This example allows a selection from a document formed by\n   XS-S-1, and applies a user-written XPATH expression to it.\n   The page has selectable sample expressions including:\n   \n    Count of all titles\n    Sum of the length of sect2 titles\n    All first paragraphs of sect2's.\n   \n  The example uses xpath_eval, and iterates on the results if an array is produced.\n  A single element of the XS-S-1 data is picked as the context node.\n  A special button applies the operation on all rows with xpath_contains, showing the result set\n   with doc name and result.\n  This shows how one row can make multiple results with xpath_contains,\n   but will return an array with xpath_eval.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"XSL-T transformation" ;
	sioc:content	"\nExample\n\n  This example uses the result from the XML parser in HTML mode to pass a parameter to the XSL-T style-sheet.\n  The XSL-T style-sheet renders the target XML document.\n  The section to be transformed is passed as the entity.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Passing an XML entity as parameter to the XSL-T style-sheet" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nExample\n\n  This example uses the result from the XML parser in HTML mode to pass a parameter to the XSL-T style-sheet.\n  The XSL-T style-sheet renders the target XML document.\n  The section to be transformed is passed as the entity.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Freetext indexing hooks" ;
	sioc:content	"\nFreetext Index\n\n  The freetext index has a default mechanism for indexing and unindexing.\n  By default indexing/unindexing is performed over data column.\n  A custom PL hook can be made for indexing/unindexing, and be associated to the \n   freetext index definition.\n  The data from additional columns can be indexed in the custom PL hooks.\n  Working together with off-band data columns to make index sensitive to changes in the additional columns data \n  they should be declared as off-band data.\n\n\nExample\nThe example SQL script does the following steps:\n\n  Definition of the hooks\n  Making of text index\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Building a freetext index using a custom PL indexing hooks" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nFreetext Index\n\n  The freetext index has a default mechanism for indexing and unindexing.\n  By default indexing/unindexing is performed over data column.\n  A custom PL hook can be made for indexing/unindexing, and be associated to the \n   freetext index definition.\n  The data from additional columns can be indexed in the custom PL hooks.\n  Working together with off-band data columns to make index sensitive to changes in the additional columns data \n  they should be declared as off-band data.\n\n\nExample\nThe example SQL script does the following steps:\n\n  Definition of the hooks\n  Making of text index\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Using the xpath_eval()" ;
	sioc:content	"\nPreliminaries\nThe xpath_eval() function returns the result of applying the xpath expression to the\ncontext node.  By default only the first result is returned, but supplying a third argument \nallows an index for the value to be specified. The default assumes a value of 1 here.  \nA value of 0 returns an array of 0 or more elements, one for each value selected by the\nxpath expression.\n\nExamples\nThe examples create an internal representation of the XML image using xml_tree_doc().\nAn xpath_eval() statement is then executed against the internal representation of the XML document\nspecified as /ROOT/Customers which identifies the  nodes to be processed.\n\nThe loop iterates over result for each attribute value (as CustomerID and ContactName in the first example) \nand retrieves the necessary values. \nThen the PL procedures calls result_names() and result() to send the result set to the client.\n\nThe first example will produce (when applying via ISQL utility)\n\nCustomerID  ContactName\nVARCHAR     VARCHAR\n________________________\n\nVINET       Paul Henriot\nLILAS       Carlos Gonzalez\n\n\nHere is the result from execution of the second script:\n\nOrderID    CustomerID    OrderDate              ProductID     Quantity\nVARCHAR    VARCHAR       VARCHAR                VARCHAR       VARCHAR\n______________________________________________________________________\n\n10248      VINET         1996-07-04T00:00:00    11            12\n10248      VINET         1996-07-04T00:00:00    42            10\n10283      LILAS         1996-08-16T00:00:00    72            3\n\n\nThe VSP code displays the same data, but formats it into a table.\n\nThe third example shows XML entities that have returned from first execution of the xpath_eval();\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Making the resultsets with xpath_eval() function" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nPreliminaries\nThe xpath_eval() function returns the result of applying the xpath expression to the\ncontext node.  By default only the first result is returned, but supplying a third argument \nallows an index for the value to be specified. The default assumes a value of 1 here.  \nA value of 0 returns an array of 0 or more elements, one for each value selected by the\nxpath expression.\n\nExamples\nThe examples create an internal representation of the XML image using xml_tree_doc().\nAn xpath_eval() statement is then executed against the internal representation of the XML document\nspecified as /ROOT/Customers which identifies the <Customers> nodes to be processed.\n\nThe loop iterates over result for each attribute value (as CustomerID and ContactName in the first example) \nand retrieves the necessary values. \nThen the PL procedures calls result_names() and result() to send the result set to the client.\n\nThe first example will produce (when applying via ISQL utility)\n\nCustomerID  ContactName\nVARCHAR     VARCHAR\n________________________\n\nVINET       Paul Henriot\nLILAS       Carlos Gonzalez\n\n\nHere is the result from execution of the second script:\n\nOrderID    CustomerID    OrderDate              ProductID     Quantity\nVARCHAR    VARCHAR       VARCHAR                VARCHAR       VARCHAR\n______________________________________________________________________\n\n10248      VINET         1996-07-04T00:00:00    11            12\n10248      VINET         1996-07-04T00:00:00    42            10\n10283      LILAS         1996-08-16T00:00:00    72            3\n\n\nThe VSP code displays the same data, but formats it into a table.\n\nThe third example shows XML entities that have returned from first execution of the xpath_eval();\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Overview" ;
	sioc:content	"\nMapping Schemas as XML views.\n\n\nXML views of relational data is similar to creating views by using CREATE VIEW statements.\nXML views can be created by using the XML Schema Definition (XSD) language, and then can be queried by using XML Path \nlanguage (XPATH) queries or XML Query (XQUERY) queries with using xmlview function.\n\n \nAn XSD schema with the special set of annotations is referred to as a mapping schema. These annotations are used \nwithin the XSD schema to specify XML data to relational store mapping. This includes mapping between elements and \nattributes in the XSD schema to tables (views) and columns in the databases. If you do not specify the annotations, \ndefault mapping takes place. By default, an XSD element with complex type maps to a table (view) name in the \nspecified database and an element or attribute with a simple type maps to the column with the same name as \nthe element/attribute.\nThese annotations can also be used to specify the hierarchical relationships in XML \n(thus, representing the relationships in the database because XSD schemas are simply an XML view of relational data).\n\n\nA file containg a mapping schema may be loaded by calling the \nxml_load_mapping_schema_decl \nfunction. A name (without extension .xsd) of the file containg a mapping schema is considered to be the name of \nthe xml view, defined by a given mapping schema.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Mapping Schemas" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nMapping Schemas as XML views.\n\n\nXML views of relational data is similar to creating views by using CREATE VIEW statements.\nXML views can be created by using the XML Schema Definition (XSD) language, and then can be queried by using XML Path \nlanguage (XPATH) queries or XML Query (XQUERY) queries with using xmlview function.\n\n \nAn XSD schema with the special set of annotations is referred to as a mapping schema. These annotations are used \nwithin the XSD schema to specify XML data to relational store mapping. This includes mapping between elements and \nattributes in the XSD schema to tables (views) and columns in the databases. If you do not specify the annotations, \ndefault mapping takes place. By default, an XSD element with complex type maps to a table (view) name in the \nspecified database and an element or attribute with a simple type maps to the column with the same name as \nthe element/attribute.\nThese annotations can also be used to specify the hierarchical relationships in XML \n(thus, representing the relationships in the database because XSD schemas are simply an XML view of relational data).\n\n\nA file containg a mapping schema may be loaded by calling the \nxml_load_mapping_schema_decl \nfunction. A name (without extension .xsd) of the file containg a mapping schema is considered to be the name of \nthe xml view, defined by a given mapping schema.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"" ;
	sioc:content	"\nPreliminaries\n\nThe sql:relation annotation maps an XML node in the XSD schema to a database table. \nThe name of a table (view) is specified as the value of the sql:relation annotation.\nWhen sql:relation is specified on an element, the scope of this annotation applies to all attributes and \nsubelements that are described in the complex type definition of that element, therefore, providing a shortcut \nin writing annotations.\nThe sql:relation annotation also may be used if identifiers that are valid in SQL \nare not valid in XML. For example, 'Order Details' is a valid table name in SQL, but not in XML. \nIn such cases, the sql:relation annotation can be used to specify the mapping, for example:\n\n...\n\nThe sql:field annotation maps an XML node in the schema to a database column. It's not allowed to specify \nsql:field on an empty content element.\n\n\nExample\n\nIn this example, the XSD schema consists of an 'Emp' element of complex type with 'FirstName',\n'LastName' and 'title' child elements and the 'EmpID' attribute.\nThe sql:relation annotation maps the 'Emp' element to the Demo.demo.Employees table. The sql:field \nannotation maps the 'title' element to the 'Title' column and the 'EmpID' attribute \nto the \"EmployeeID\" column.\nNo annotations are specified for the 'FirstName' and 'LastName' elements. This results in a \ndefault mapping of the elements to the columns with the same names. \n\n\n\n  \n   \n     \n         \n        \n        \n     \n     \n    \n  \n\n\nLet the schema is written to the file 'EmpSchema.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'EmpSchema'] /*\n\nthe second example will produce a result for the XQuery query:\n\n select xquery_eval('{for $r in xmlview(\"EmpSchema\")/* return $r}', xtree_doc('')); \n\n\n is necessary for serialization (any name instead 'doc' is possible)\n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using sql:relation and sql:field" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\nThe sql:relation annotation maps an XML node in the XSD schema to a database table. \nThe name of a table (view) is specified as the value of the sql:relation annotation.\nWhen sql:relation is specified on an element, the scope of this annotation applies to all attributes and \nsubelements that are described in the complex type definition of that element, therefore, providing a shortcut \nin writing annotations.\nThe sql:relation annotation also may be used if identifiers that are valid in SQL \nare not valid in XML. For example, 'Order Details' is a valid table name in SQL, but not in XML. \nIn such cases, the sql:relation annotation can be used to specify the mapping, for example:\n<xsd:element name="OrderDetails" sql:relation="Order Details">\n...\n\nThe sql:field annotation maps an XML node in the schema to a database column. It's not allowed to specify \nsql:field on an empty content element.\n\n\nExample\n\nIn this example, the XSD schema consists of an 'Emp' element of complex type with 'FirstName',\n'LastName' and 'title' child elements and the 'EmpID' attribute.\nThe sql:relation annotation maps the 'Emp' element to the Demo.demo.Employees table. The sql:field \nannotation maps the 'title' element to the 'Title' column and the 'EmpID' attribute \nto the "EmployeeID" column.\nNo annotations are specified for the 'FirstName' and 'LastName' elements. This results in a \ndefault mapping of the elements to the columns with the same names. \n\n\n<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"\n            xmlns:sql="urn:schemas-microsoft-com:mapping-schema">\n  <xsd:element name="Emp" sql:relation="Demo.demo.Employees" >\n   <xsd:complexType>\n     <xsd:sequence>\n        <xsd:element name="FirstName"  \n                     type="xsd:string" /> \n        <xsd:element name="LastName"  \n                     type="xsd:string" />\n        <xsd:element name="title"  \n\t\t     sql:field="Title"\n                     type="xsd:string" />\n     </xsd:sequence>\n     <xsd:attribute name="EmpID"  sql:field="EmployeeID"  type="xsd:integer" />\n    </xsd:complexType>\n  </xsd:element>\n</xsd:schema>\n\nLet the schema is written to the file 'EmpSchema.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'EmpSchema'] /*\n\nthe second example will produce a result for the XQuery query:\n\n select xquery_eval('<doc>{for $r in xmlview("EmpSchema")/* return $r}</doc>', xtree_doc('<q/>')); \n\n\n<doc> is necessary for serialization (any name instead 'doc' is possible)\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"" ;
	sioc:content	"\nPreliminaries\n\nIn the annotated XSD schema, the sql:relationship annotation is used to nest the schema elements hierarchically, \non the basis of primary key and foreign key relationships among the underlying tables to which the elements map. \nIn specifying the sql:relationship annotation, you must identify: \n The parent table (Customers) and the child table (Orders).\n The necessary join condition. (CustomerID in Orders is a child key that refers to the CustomerID parent key in the Customers table.) \n\nThis information is used in generating the proper hierarchy. (For each parent element, the related child \nelements appear as subelements.)\nTo provide the table names and the necessary join information, the following attributes are specified on the \nsql:relationship annotation: \n\n   \n'name' specifies the unique name of the relationship;\n  \n  'parent' specifies the parent relation (table). This is an optional attribute; if the attribute is not specified, the parent \ntable name is obtained from information in the child hierarchy in the document. If the schema specifies two \nparent-child hierarchies that use the same  but different parent elements, you do not specify \nthe parent attribute in . This information is obtained from the hierarchy in the schema.\n  \n   'parent-key' specifies the parent key of the parent. If the parent key is composed of multiple columns, values are specified \nwith a space between them. There is a positional mapping between the values that are specified for the multicolumn \nkey and for the corresponding child key.\n  \n  'child' specifies the child relation (table).\n  \n  'child-key' specifies the child key in the child referring to parent-key in parent. If the child key is composed of multiple \nattributes (columns), the child-key values are specified with a space between them. There is a positional \nmapping between the values that are specified for the multicolumn key and for the corresponding parent key.\n  \n\nThese attributes are valid only with the  element.\n\n\n\nExample. Specifying the sql:relationship annotation on an element.\n\nThe following annotated XSD schema includes 'Customer' and 'Order' elements. \nThe 'Order' element is a subelement of the 'Customer' element.\nIn the schema, the sql:relationship annotation is specified on the 'Order' subelement. The relationship \nitself is defined in the 'appinfo' element.\nThe 'relationship' element identifies CustomerID in the Orders table as a foreign key that refers to the \nCustomerID primary key in the Customers table. Therefore, orders that belong to a customer appear as a subelement of \nthat 'Customer' element.\n\n\n\n\n  \n    \n  \n\n\n  \n   \n     \n        \n           \n              \n              \n           \n        \n     \n         \n        \n    \n\n\nLet the schema is written to the file 'CustOr_constant.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Customer_Order'] /Customer[@CustomerID=\"QUEEN\"];\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('{for $r in xmlview(\"Customer_Order\")/*[@CustomerID=\"QUEEN\"] return $r}', xtree_doc(''))\n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using sql:relationship to Specify Relationships" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\nIn the annotated XSD schema, the sql:relationship annotation is used to nest the schema elements hierarchically, \non the basis of primary key and foreign key relationships among the underlying tables to which the elements map. \nIn specifying the sql:relationship annotation, you must identify: \n The parent table (Customers) and the child table (Orders).\n The necessary join condition. (CustomerID in Orders is a child key that refers to the CustomerID parent key in the Customers table.) \n\nThis information is used in generating the proper hierarchy. (For each parent element, the related child \nelements appear as subelements.)\nTo provide the table names and the necessary join information, the following attributes are specified on the \nsql:relationship annotation: \n\n   \n'name' specifies the unique name of the relationship;\n  \n  'parent' specifies the parent relation (table). This is an optional attribute; if the attribute is not specified, the parent \ntable name is obtained from information in the child hierarchy in the document. If the schema specifies two \nparent-child hierarchies that use the same <sql:relationship> but different parent elements, you do not specify \nthe parent attribute in <sql:relationship>. This information is obtained from the hierarchy in the schema.\n  \n   'parent-key' specifies the parent key of the parent. If the parent key is composed of multiple columns, values are specified \nwith a space between them. There is a positional mapping between the values that are specified for the multicolumn \nkey and for the corresponding child key.\n  \n  'child' specifies the child relation (table).\n  \n  'child-key' specifies the child key in the child referring to parent-key in parent. If the child key is composed of multiple \nattributes (columns), the child-key values are specified with a space between them. There is a positional \nmapping between the values that are specified for the multicolumn key and for the corresponding parent key.\n  \n\nThese attributes are valid only with the <sql:relationship> element.\n\n\n\nExample. Specifying the sql:relationship annotation on an element.\n\nThe following annotated XSD schema includes 'Customer' and 'Order' elements. \nThe 'Order' element is a subelement of the 'Customer' element.\nIn the schema, the sql:relationship annotation is specified on the 'Order' subelement. The relationship \nitself is defined in the 'appinfo' element.\nThe 'relationship' element identifies CustomerID in the Orders table as a foreign key that refers to the \nCustomerID primary key in the Customers table. Therefore, orders that belong to a customer appear as a subelement of \nthat 'Customer' element.\n\n\n<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"\n            xmlns:sql="urn:schemas-microsoft-com:mapping-schema">\n<xsd:annotation>\n  <xsd:appinfo>\n    <sql:relationship name="CustOrders"\n          parent="Demo.demo.Customers"\n          parent-key="CustomerID"\n          child="Demo.demo.Orders"\n          child-key="CustomerID" />\n  </xsd:appinfo>\n</xsd:annotation>\n\n  <xsd:element name="Customer" sql:relation="Demo.demo.Customers" type="CustomerType" />\n   <xsd:complexType name="CustomerType" >\n     <xsd:sequence>\n        <xsd:element name="Order" \n                     sql:relation="Demo.demo.Orders"\n                    sql:relationship="CustOrders" >\n           <xsd:complexType>\n              <xsd:attribute name="OrderID" type="xsd:integer" />\n              <xsd:attribute name="CustomerID" type="xsd:string" />\n           </xsd:complexType>\n        </xsd:element>\n     </xsd:sequence>\n        <xsd:attribute name="CustomerID"   type="xsd:string" /> \n        <xsd:attribute name="ContactName"  type="xsd:string" />\n    </xsd:complexType>\n</xsd:schema>\n\nLet the schema is written to the file 'CustOr_constant.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Customer_Order'] /Customer[@CustomerID="QUEEN"];\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('<doc>{for $r in xmlview("Customer_Order")/*[@CustomerID="QUEEN"] return $r}</doc>', xtree_doc('<q/>'))\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"" ;
	sioc:content	"\nExample.\n\nThe schema in this example includes a 'Customer' element with 'CustomerID' and \n'ContactName' child \nelements and an OrderIDList attribute of IDREFS type. The 'Customer' element maps to the Customers table. \nBy default, the scope of this mapping applies to all the child elements or attributes unless sql:relation \nis specified on the child element or attribute, in which case, the appropriate primary-key/foreign-key \nrelationship must be defined using the 'relationship' element. And the child element or attribute, \nwhich specifies the different table using the relation annotation, must also specify the relationship annotation.\n\n\n\n\n  \n    \n     \n\n\n  \n   \n     \n        \n        \n        \n     \n     \n        \n      \n    \n\n\nLet the schema is written to the file 'Cust_Order_attr.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Cust_Order_attr'] /Customer[@CustomerID=\"QUEEN\"]\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('{for $r in xmlview(\"Cust_Order_attr\")/*[@CustomerID=\"QUEEN\"] return $r}', xtree_doc('')); \n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using sql:relationship to Specify Relationship on an attribute" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample.\n\nThe schema in this example includes a 'Customer' element with 'CustomerID' and \n'ContactName' child \nelements and an OrderIDList attribute of IDREFS type. The 'Customer' element maps to the Customers table. \nBy default, the scope of this mapping applies to all the child elements or attributes unless sql:relation \nis specified on the child element or attribute, in which case, the appropriate primary-key/foreign-key \nrelationship must be defined using the 'relationship' element. And the child element or attribute, \nwhich specifies the different table using the relation annotation, must also specify the relationship annotation.\n\n\n<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"\n            xmlns:sql="urn:schemas-microsoft-com:mapping-schema">\n<xsd:annotation>\n  <xsd:appinfo>\n    <sql:relationship name="CustOrders"\n          parent="Demo.demo.Customers"\n          parent-key="CustomerID"\n          child="Demo.demo.Orders"\n          child-key="CustomerID" />\n     </xsd:appinfo>\n</xsd:annotation>\n\n  <xsd:element name="Customer" sql:relation="Demo.demo.Customers" type="CustomerType" />\n   <xsd:complexType name="CustomerType" >\n     <xsd:sequence>\n        <xsd:element name="ContactName"  type="xsd:string" />\n        <xsd:element name="CompanyName"  type="xsd:string" />\n        <xsd:element name="City"  type="xsd:string" />\n     </xsd:sequence>\n     <xsd:attribute name="OrderIDList" \n                     type="xsd:IDREFS" \n                     sql:relation="Demo.demo.Orders" \n                     sql:field="OrderID"\n                     sql:relationship="CustOrders" >\n        </xsd:attribute>\n     <xsd:attribute name="CustomerID"   type="xsd:string" /> \n    </xsd:complexType>\n</xsd:schema>\n\nLet the schema is written to the file 'Cust_Order_attr.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Cust_Order_attr'] /Customer[@CustomerID="QUEEN"]\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('<doc>{for $r in xmlview("Cust_Order_attr")/*[@CustomerID="QUEEN"] return $r}</doc>', xtree_doc('<q/>')); \n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"" ;
	sioc:content	"\nExample. Specifying sql:relationship on multiple elements.\n\nIn this example, the annotated XSD schema contains the 'Customer', 'Order', and 'OD' \nelements. The 'Order' element is a subelement of the 'Customer' element.  \nis specified on the 'Order' subelement; therefore, orders that belong to a customer appear as subelements \nof 'Customer'.\nThe 'Order' element includes the 'OD' subelement. 'sql:relationship' is specified \non 'OD' subelement, \nso the order details that pertain to an order appear as subelements of that 'Order' element.\n\n\n\n\n  \n    \n\n    \n  \n\n\n  \n   \n     \n        \n          \n              \n                \n                  \n                    \n                    \n                    \n                  \n                \n              \n              \n              \n          \n        \n      \n      \n     \n  \n\n\nLet the schema is written to the file 'Cust_Order_OD.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Cust_Order_OD'] /Customer[@CustomerID=\"QUEEN\"];\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('{for $r in xmlview(\"Cust_Order_OD\")/*[@CustomerID=\"QUEEN\"] return $r}', xtree_doc(''))\n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using sql:relationship to Specify Relationship on multiple elements." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample. Specifying sql:relationship on multiple elements.\n\nIn this example, the annotated XSD schema contains the 'Customer', 'Order', and 'OD' \nelements. The 'Order' element is a subelement of the 'Customer' element. <sql:relationship> \nis specified on the 'Order' subelement; therefore, orders that belong to a customer appear as subelements \nof 'Customer'.\nThe 'Order' element includes the 'OD' subelement. 'sql:relationship' is specified \non 'OD' subelement, \nso the order details that pertain to an order appear as subelements of that 'Order' element.\n\n\n<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"\n            xmlns:sql="urn:schemas-microsoft-com:mapping-schema">\n<xsd:annotation>\n  <xsd:appinfo>\n    <sql:relationship name="CustOrders"\n        parent="Demo.demo.Customers"\n        parent-key="CustomerID"\n        child="Demo.demo.Orders"\n        child-key="CustomerID" />\n\n    <sql:relationship name="OrderOrderDetail"\n        parent="Demo.demo.Orders"\n        parent-key="OrderID"\n        child="Demo.demo.Order_Details"\n        child-key="OrderID" />\n  </xsd:appinfo>\n</xsd:annotation>\n\n  <xsd:element name="Customer" sql:relation="Demo.demo.Customers" >\n   <xsd:complexType>\n     <xsd:sequence>\n        <xsd:element name="Order" sql:relation="Demo.demo.Orders"  \n              sql:relationship="CustOrders" maxOccurs="unbounded" >\n          <xsd:complexType>\n              <xsd:sequence>\n                <xsd:element name="OrderDetail" \n                             sql:relation="Demo.demo.Order_Details" \n                             sql:relationship="OrderOrderDetail" \n                             maxOccurs="unbounded" >\n                  <xsd:complexType>\n                    <xsd:attribute name="OrderID" type="xsd:integer" />\n                    <xsd:attribute name="ProductID" type="xsd:string" />\n                    <xsd:attribute name="Quantity" type="xsd:integer" />\n                  </xsd:complexType>\n                </xsd:element>\n              </xsd:sequence>\n              <xsd:attribute name="OrderID" type="xsd:integer" />\n              <xsd:attribute name="CustomerID" type="xsd:string" />\n          </xsd:complexType>\n        </xsd:element>\n      </xsd:sequence>\n      <xsd:attribute name="CustomerID" type="xsd:string" />\n     </xsd:complexType>\n  </xsd:element>\n</xsd:schema>\n\nLet the schema is written to the file 'Cust_Order_OD.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Cust_Order_OD'] /Customer[@CustomerID="QUEEN"];\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('<doc>{for $r in xmlview("Cust_Order_OD")/*[@CustomerID="QUEEN"] return $r}</doc>', xtree_doc('<q/>'))\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"" ;
	sioc:content	"\nPreliminaries\n\nThe sql:is-constant annotation can be used to specify a constant element, an element in the XSD schema \nthat does not map to any database table or column. sql:is-constant takes a Boolean value (false, true), 0 and 1\n(0 = false, 1 = true).  The is-constant annotation can be specified on an element \nthat does not have any attributes. If this annotation is specified on an element with the value true (or 1), \nthat element is not mapped to the database but still appears in the XML document. The sql:is-constant annotation \ncan be added to a  element.\n\n\n\nExample. Specifying sql:is-constant to add a container element\n\nIn this annotated XSD schema, 'CustomerOrders'  is defined as a constant element by specifying \nthe sql:is-constant attribute with the value of 1. Therefore, 'CustomerOrders' element is not mapped to \nany database table or column. \nThis constant element consists of the 'Order' subelements.\nAlthough 'CustomerOrders' element does not map to any database table or column, it still appears in the \nresulting XML as a container element containing the 'Order' subelements.\n\n\n\n\n  \n    \n  \n\n\n  \n    \n      \n        \n          \n            \n              \n                \n                   \n                   \n                \n              \n            \n          \n        \n      \n          \n    \n  \n\n\nLet the schema is written to the file 'CustOr_constant.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'CustOr_constant'] /*[@CustomerID=\"QUEEN\"]\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('{for $r in xmlview(\"CustOr_constant\")/*[@CustomerID=\"QUEEN\"] return $r}', xtree_doc(''))\n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using sql:is-constant for creating constant elements " ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\nThe sql:is-constant annotation can be used to specify a constant element, an element in the XSD schema \nthat does not map to any database table or column. sql:is-constant takes a Boolean value (false, true), 0 and 1\n(0 = false, 1 = true).  The is-constant annotation can be specified on an element \nthat does not have any attributes. If this annotation is specified on an element with the value true (or 1), \nthat element is not mapped to the database but still appears in the XML document. The sql:is-constant annotation \ncan be added to a <complexType> element.\n\n\n\nExample. Specifying sql:is-constant to add a container element\n\nIn this annotated XSD schema, 'CustomerOrders'  is defined as a constant element by specifying \nthe sql:is-constant attribute with the value of 1. Therefore, 'CustomerOrders' element is not mapped to \nany database table or column. \nThis constant element consists of the 'Order' subelements.\nAlthough 'CustomerOrders' element does not map to any database table or column, it still appears in the \nresulting XML as a container element containing the 'Order' subelements.\n\n\n<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"\n            xmlns:sql="urn:schemas-microsoft-com:mapping-schema">\n<xsd:annotation>\n  <xsd:appinfo>\n    <sql:relationship name="CustOrders"\n        parent="Demo.demo.Customers"\n        parent-key="CustomerID"\n        child="Demo.demo.Orders"\n        child-key="CustomerID" />\n  </xsd:appinfo>\n</xsd:annotation>\n\n  <xsd:element name="Customer" sql:relation="Demo.demo.Customers" >\n    <xsd:complexType>\n      <xsd:sequence>\n        <xsd:element name="CustomerOrders" sql:is-constant="1" >\n          <xsd:complexType>\n            <xsd:sequence>\n              <xsd:element name="Order" sql:relation="Demo.demo.Orders"\n                           sql:relationship="CustOrders" \n                           maxOccurs="unbounded" >\n                <xsd:complexType>\n                   <xsd:attribute name="OrderID" type="xsd:integer" />\n                   <xsd:attribute name="CustomerID" type="xsd:string" />\n                </xsd:complexType>\n              </xsd:element>\n            </xsd:sequence>\n          </xsd:complexType>\n        </xsd:element>\n      </xsd:sequence>\n          <xsd:attribute name="CustomerID" type="xsd:string" />\n    </xsd:complexType>\n  </xsd:element>\n</xsd:schema>\n\nLet the schema is written to the file 'CustOr_constant.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'CustOr_constant'] /*[@CustomerID="QUEEN"]\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('<doc>{for $r in xmlview("CustOr_constant")/*[@CustomerID="QUEEN"] return $r}</doc>', xtree_doc('<q/>'))\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"" ;
	sioc:content	"\nPreliminaries\n\nRows returned from a database query can be limited on the basis of some limiting value. \nThe sql:limit-field is used to identify the database column that contains \nlimiting values and sql:limit-value annotations is used to specify a specific limiting value to be used \nto filter the data returned.\nThe sql:limit-value annotation is optional. If sql:limit-value is not specified, \na NULL value is assumed.\n\n\n\nExample.\n\nThis is the mapping schema in which the 'product_Chai' schema attribute maps to the 'ProductID' \ncolumn in the 'Demo.demo.Products' relation. The values that are returned for this attribute are limited \nto only 'ProductName' having the 'Chai' value by specifying the sql:limit-field and sql:limit-value \nannotations. Similarly, \nthe 'product_Chang' schema attribute returns only the \n'ProductID' limited to 'ProductName' having the 'Chang' value.\n\n\n\n\n\n  \n    \n  \n\n\n  \n   \n     \n        \n        \n        \n        \n     \n         \n        \n    \n\n\n\nLet the schema is written to the file 'Cat_Product.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Cat_Product'] /*[@CategoryID=1]\n\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('{for $r in xmlview(\"Cat_Product\")/*[@CategoryID=1] return $r}', xtree_doc(''))\n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Filtering Values by Using sql:limit-field and sql:limit-value " ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\nRows returned from a database query can be limited on the basis of some limiting value. \nThe sql:limit-field is used to identify the database column that contains \nlimiting values and sql:limit-value annotations is used to specify a specific limiting value to be used \nto filter the data returned.\nThe sql:limit-value annotation is optional. If sql:limit-value is not specified, \na NULL value is assumed.\n\n\n\nExample.\n\nThis is the mapping schema in which the 'product_Chai' schema attribute maps to the 'ProductID' \ncolumn in the 'Demo.demo.Products' relation. The values that are returned for this attribute are limited \nto only 'ProductName' having the 'Chai' value by specifying the sql:limit-field and sql:limit-value \nannotations. Similarly, \nthe 'product_Chang' schema attribute returns only the \n'ProductID' limited to 'ProductName' having the 'Chang' value.\n\n\n\n<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"\n            xmlns:sql="urn:schemas-microsoft-com:mapping-schema">\n<xsd:annotation>\n  <xsd:appinfo>\n    <sql:relationship name="CategoryProduct"\n          parent="Demo.demo.Categories"\n          parent-key="CategoryID"\n          child="Demo.demo.Products"\n          child-key="CategoryID" />\n  </xsd:appinfo>\n</xsd:annotation>\n\n  <xsd:element name="category" sql:relation="Demo.demo.Categories" type="CategoryType" />\n   <xsd:complexType name="CategoryType" >\n     <xsd:sequence>\n        <xsd:element name="product_Chai" \n                       type="xsd:string" \n                     sql:relation="Demo.demo.Products"\n                     sql:field="ProductID"\n                     sql:limit-field="ProductName"\n                     sql:limit-value="Chai"\n                     sql:relationship="CategoryProduct" >\n        </xsd:element>\n        <xsd:element name="product_Chang" \n                       type="xsd:string" \n                     sql:relation="Demo.demo.Products"\n                     sql:field="ProductID"\n                     sql:limit-field="ProductName"\n                     sql:limit-value="Chang"\n                     sql:relationship="CategoryProduct" >\n        </xsd:element>\n     </xsd:sequence>\n        <xsd:attribute name="CategoryID"  type="xsd:integer" /> \n        <xsd:attribute name="description"  sql:field="Description"  type="xsd:string" />\n    </xsd:complexType>\n\n</xsd:schema>\n\nLet the schema is written to the file 'Cat_Product.xsd', then after loading this file by \nxml_load_mapping_schema_decl function, the first example will produce a result for the XPath query:\n\n\nXPATH [__view 'Cat_Product'] /*[@CategoryID=1]\n\n\n\nthe second example will produce a result for the XQuery query:\n\n\nselect xquery_eval('<doc>{for $r in xmlview("Cat_Product")/*[@CategoryID=1] return $r}</doc>', xtree_doc('<q/>'))\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Genaral" ;
	sioc:content	"\nXPATH Implementation and SQL\n\nVirtuoso offers XPATH as a query language for XML views. The statement is there converted into SQL in the context \nof the mapping defined by the __view XPATH option, which is mandatory. An XPATH query string is a valid top \nlevel SQL statement. This is interpreted as a single select or union of selects with the result columns \nbeing specified by various XPATH options. \nThe basic query string \n\n\nXPATH [__view \"xmlview_name\"] /xpath_query\n\n\nThe same functionality can be got by the following query:\n\n\nselect * from (XPATH '[__view \"xmlview_name\"]/xpath_query')n\n\nXml view can be created by two methods:\n\n   using CREATE XML VIEW statement \n   using Annotated XSD Schemas\n\n\n  The second method is described in 'Using Annotated XSD Schemas for Creating XML View' chapter \n  of this tutorial.\n\n\nCREATE XML VIEW statement\n\nThe XML view declaration establishes a 'virtual document' a context within which XML hierarchy relationships \ncan be translated into arbitrary joins. The virtual document can be then materialized into an actual set of persistent \nXML elements or used to generate SQL from XPATH. \nThe XML view declaration corresponds to the grammar rules described in XML Support chapter, Virtuoso XML Services section.\n\n\t\t\t\nEach table in the declaration generates an element into the result\ndocument. SQL views can be used as tables to accommodate for hidden joins, sub-queries, ordering and\naggregates. If a view is used, which by nature has no primary key, the primary key\nclause should be used to define a uniquely identifying set of view columns.\n\t\n\t\t\t\nEach level of the hierarchy is declared as a list of child elements. Each such element maps\none table or view into an entity according to a join condition.  The join conditions\ncan reference columns from the associated table and columns from tables in parent elements.\nThe join condition can also have scalar filtering conditions. A top element's join\ncondition may only specify scalar conditions.  \n\n\t\t\t\nEach set of sibling child nodes is delimited by braces {}.  The top \nlevel of the view typically consists of one element in the outermost braces.  This element \nhas itself a child list delimited by braces.  Each such list can have more than \none different element. \n\n\t\t\t\nEach element specifies:\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\tSQL table\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tCorrelation name for use in subsequent joins for this table\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tXML element name to use for delimiting a row of this table\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tList of columns, with optional XML element or attribute names\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tjoin condition - will relate rows of this table to rows of the table in the enclosing element.\n  If this element is at the top level, this can only consist of scalar conditions\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tOptional PRIMARY KEY clause, needed if the table in this element is a view, does not \n  have a primary key or if a non-primary key unique identity is desired\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tOptional ELEMENT flag\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tOptional list of child elements, delimited by braces\n\t\t\t\t\n\t\t\t\n\t\t\t\nThe column list can mention a single column or a single column renamed into an\nXML attribute of a different name. If a column of a table is referenced in a subsequent join\ncondition it must appear in the output columns list.  Expressions are not directly allowed\nbut a view with expression columns can be used.\n\t\n\t\t\t\nThe opt_public clause, when present, offers a shorthand for calling xml_view_publish \nat the same time as making the definition.  This makes a DAV resource reflecting the contents \nof the view.  The contents may either be generated on demand or persisted as a DAV accessible XML document.\nIn the latter case the document may be regenerated at a fixed interval. The interval is \nexpressed in minutes.\n\t\n\t\t\t\nThe path is expressed as an absolute path from the root collection of the DAV server.\n\t\n\n\n\t\t\t\tExamples\n\t\t\t\t\ncreate xml view \"cat\" as\n{\n  \"Demo\".\"demo\".\"Categories\" \"C\" as \"category\"\n\t(\"CategoryID\", \"Description\" as \"description\")\n    {\n      \"Demo\".\"demo\".\"Products\" \"P\" as \"product\"  (\"ProductName\")\n\ton (\"P\".\"CategoryID\" = \"C\".\"CategoryID\")\n    }\n}\n\n\t\t\t\t\nThis declares a two level hierarchy with a category node for each category\nand a product child node for each product in the category.\n\n\t\t\t\t\ncreate xml view \"cats_e\" as\n  select \"category\".\"CategoryID\", \"CategoryName\", \n    \"ProductName\", \"ProductID\"\n    from \"Demo\"..\"Categories\" \"category\", \"Demo\"..\"Products\" as \"product\" \n    where \"product\".\"CategoryID\" = \"category\".\"CategoryID\" element;\n\n\t\t\t\tHere is a similar example, this time using the element option.\n\ncreate xml view \"product\" as\n{\n  \"Demo\".\"demo\".\"Products\" p as \"product\" \n      (\"ProductID\", \"ProductName\" as \"product_name\",\"UnitPrice\" as \"price\", \"SupplierID\",\"CategoryID\")\n    {\n      \"Demo\".\"demo\".\"Suppliers\" s as \"supplier\"  (\"CompanyName\")\n\ton (s.\"SupplierID\" = p.\"SupplierID\")\n       ,\n      \"Demo\".\"demo\".\"Categories_aux\" c as \"category\"  (\"Description\")\n\ton (c.\"CategoryID\" = p.\"CategoryID\")\n\n    }\n}\n\n\nThis declares a two level hierarchy with a product node for each product\nand a supplier and category children node for each supplier and category in the product.\n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using XPath queries to XML views. Overview." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nXPATH Implementation and SQL\n\nVirtuoso offers XPATH as a query language for XML views. The statement is there converted into SQL in the context \nof the mapping defined by the __view XPATH option, which is mandatory. An XPATH query string is a valid top \nlevel SQL statement. This is interpreted as a single select or union of selects with the result columns \nbeing specified by various XPATH options. \nThe basic query string \n\n\nXPATH [__view "xmlview_name"] /xpath_query\n\n\nThe same functionality can be got by the following query:\n\n\nselect * from (XPATH '[__view "xmlview_name"]/xpath_query')n\n\nXml view can be created by two methods:\n\n   using CREATE XML VIEW statement \n   using Annotated XSD Schemas\n\n\n  The second method is described in 'Using Annotated XSD Schemas for Creating XML View' chapter \n  of this tutorial.\n\n\nCREATE XML VIEW statement\n\nThe XML view declaration establishes a 'virtual document' a context within which XML hierarchy relationships \ncan be translated into arbitrary joins. The virtual document can be then materialized into an actual set of persistent \nXML elements or used to generate SQL from XPATH. \nThe XML view declaration corresponds to the grammar rules described in XML Support chapter, Virtuoso XML Services section.\n\n\t\t\t\nEach table in the declaration generates an element into the result\ndocument. SQL views can be used as tables to accommodate for hidden joins, sub-queries, ordering and\naggregates. If a view is used, which by nature has no primary key, the primary key\nclause should be used to define a uniquely identifying set of view columns.\n\t\n\t\t\t\nEach level of the hierarchy is declared as a list of child elements. Each such element maps\none table or view into an entity according to a join condition.  The join conditions\ncan reference columns from the associated table and columns from tables in parent elements.\nThe join condition can also have scalar filtering conditions. A top element's join\ncondition may only specify scalar conditions.  \n\n\t\t\t\nEach set of sibling child nodes is delimited by braces {}.  The top \nlevel of the view typically consists of one element in the outermost braces.  This element \nhas itself a child list delimited by braces.  Each such list can have more than \none different element. \n\n\t\t\t\nEach element specifies:\n\n\t\t\t\n\t\t\t\t\n\t\t\t\t\tSQL table\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tCorrelation name for use in subsequent joins for this table\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tXML element name to use for delimiting a row of this table\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tList of columns, with optional XML element or attribute names\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tjoin condition - will relate rows of this table to rows of the table in the enclosing element.\n  If this element is at the top level, this can only consist of scalar conditions\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tOptional PRIMARY KEY clause, needed if the table in this element is a view, does not \n  have a primary key or if a non-primary key unique identity is desired\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tOptional ELEMENT flag\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\tOptional list of child elements, delimited by braces\n\t\t\t\t\n\t\t\t\n\t\t\t\nThe column list can mention a single column or a single column renamed into an\nXML attribute of a different name. If a column of a table is referenced in a subsequent join\ncondition it must appear in the output columns list.  Expressions are not directly allowed\nbut a view with expression columns can be used.\n\t\n\t\t\t\nThe opt_public clause, when present, offers a shorthand for calling xml_view_publish \nat the same time as making the definition.  This makes a DAV resource reflecting the contents \nof the view.  The contents may either be generated on demand or persisted as a DAV accessible XML document.\nIn the latter case the document may be regenerated at a fixed interval. The interval is \nexpressed in minutes.\n\t\n\t\t\t\nThe path is expressed as an absolute path from the root collection of the DAV server.\n\t\n\n\n\t\t\t\tExamples\n\t\t\t\t\ncreate xml view "cat" as\n{\n  "Demo"."demo"."Categories" "C" as "category"\n\t("CategoryID", "Description" as "description")\n    {\n      "Demo"."demo"."Products" "P" as "product"  ("ProductName")\n\ton ("P"."CategoryID" = "C"."CategoryID")\n    }\n}\n\n\t\t\t\t\nThis declares a two level hierarchy with a category node for each category\nand a product child node for each product in the category.\n\n\t\t\t\t\ncreate xml view "cats_e" as\n  select "category"."CategoryID", "CategoryName", \n    "ProductName", "ProductID"\n    from "Demo".."Categories" "category", "Demo".."Products" as "product" \n    where "product"."CategoryID" = "category"."CategoryID" element;\n\n\t\t\t\tHere is a similar example, this time using the element option.\n\ncreate xml view "product" as\n{\n  "Demo"."demo"."Products" p as "product" \n      ("ProductID", "ProductName" as "product_name","UnitPrice" as "price", "SupplierID","CategoryID")\n    {\n      "Demo"."demo"."Suppliers" s as "supplier"  ("CompanyName")\n\ton (s."SupplierID" = p."SupplierID")\n       ,\n      "Demo"."demo"."Categories_aux" c as "category"  ("Description")\n\ton (c."CategoryID" = p."CategoryID")\n\n    }\n}\n\n\nThis declares a two level hierarchy with a product node for each product\nand a supplier and category children node for each supplier and category in the product.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Examples" ;
	sioc:content	"\nXML serialization text\nYou can get xml serialization text of the selected entity by the query \n\nXPATH [__view \"xmlview_name\"] /xpath_query\n\ne.g. for given 'cat' xml view the full serialization text can be received by the query\n\nXPATH [__view \"cat\"] /*\n\nor\n\nXPATH [__view \"cat\"] /category\n\nsee xp_v_2_sample\n\nSelect all columns instead of a serialization text\n\nYou can select all columns of the selected entity instead of its serialization text by using __* option:\n\n\nXPATH [__* __view \"cat\"] //product\n\nProductID ProductName SupplierID CategoryID QuantityPerUnit UnitPrice UnitsInStock UnitsOnOrder ReorderLevel Discontinued\nINTEGER    VARCHAR     INTEGER     INTEGER     VARCHAR  DOUBLE PRECISION  SMALLINT    SMALLINT    SMALLINT    SMALLINT\n______________________________________________________________________________________________________________________\n\n 1         Chai           1          1     10 boxes x 20bags     8          39          0          10            0\n 2         Chang          1          1     24 - 12 oz bottles   19          17         40          25            0\n 3      Aniseed Syrup     1          2     12 - 550 ml bottles  10          13         70          25            0\n.  .  .  .  .  .   \n\n\n\nThis is only valid when __view is specified and the result set is homogeneous. \n\n\n\nSelect the key instead of the serialization text\n\nYou can select the key of the selected entities instead of the serialization text by using __key option:\n\n\nXPATH [__key __view \"cat\"] /*; \n\nCategoryID\nINTEGER NOT NULL\n_______________________________________________________________________________\n \n   1\n   2\n   3\n   4\n   5\n   6\n   7\n   8                                                                                                \n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using XPath queries with options." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nXML serialization text\nYou can get xml serialization text of the selected entity by the query \n\nXPATH [__view "xmlview_name"] /xpath_query\n\ne.g. for given 'cat' xml view the full serialization text can be received by the query\n\nXPATH [__view "cat"] /*\n\nor\n\nXPATH [__view "cat"] /category\n\nsee xp_v_2_sample\n\nSelect all columns instead of a serialization text\n\nYou can select all columns of the selected entity instead of its serialization text by using __* option:\n\n\nXPATH [__* __view "cat"] //product\n\nProductID ProductName SupplierID CategoryID QuantityPerUnit UnitPrice UnitsInStock UnitsOnOrder ReorderLevel Discontinued\nINTEGER    VARCHAR     INTEGER     INTEGER     VARCHAR  DOUBLE PRECISION  SMALLINT    SMALLINT    SMALLINT    SMALLINT\n______________________________________________________________________________________________________________________\n\n 1         Chai           1          1     10 boxes x 20bags     8          39          0          10            0\n 2         Chang          1          1     24 - 12 oz bottles   19          17         40          25            0\n 3      Aniseed Syrup     1          2     12 - 550 ml bottles  10          13         70          25            0\n.  .  .  .  .  .   \n\n\n\nThis is only valid when __view is specified and the result set is homogeneous. \n\n\n\nSelect the key instead of the serialization text\n\nYou can select the key of the selected entities instead of the serialization text by using __key option:\n\n\nXPATH [__key __view "cat"] /*; \n\nCategoryID\nINTEGER NOT NULL\n_______________________________________________________________________________\n \n   1\n   2\n   3\n   4\n   5\n   6\n   7\n   8                                                                                                \n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Examples" ;
	sioc:content	"\nExample\n\nAn XPATH expression can appear as a SQL query expression, that is, as a derived table or subquery \npredicate or scalar subquery. This means that the XPATH expression is expanded compile time to the \ncorresponding SQL. \n\n The query\n\n\nselect * from (XPATH '[__* __view \"DB\".\"DBA\".\"cat\"]//product/@ProductName') P order by P.\"ProductName\"\n\n\nwill evaluate the //product query in the context of the 'cat' XML view and produce a result \nset consisting of the ordered 'ProductName' attributes of the product entity as defined in the view:\n\n\nProductName\nVARCHAR\n_______________________________________________________________________________\n\nAlice Mutton\nAniseed Syrup\nBoston Crab Meat\nCamembert Pierrot\nCarnarvon Tigers\nChai\nChang\nChartreuse verte\n.  .  .  .  .  .   \nZaanse koeken   \n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Using XPATH in SQL Queries and Procedures." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample\n\nAn XPATH expression can appear as a SQL query expression, that is, as a derived table or subquery \npredicate or scalar subquery. This means that the XPATH expression is expanded compile time to the \ncorresponding SQL. \n\n The query\n\n\nselect * from (XPATH '[__* __view "DB"."DBA"."cat"]//product/@ProductName') P order by P."ProductName"\n\n\nwill evaluate the //product query in the context of the 'cat' XML view and produce a result \nset consisting of the ordered 'ProductName' attributes of the product entity as defined in the view:\n\n\nProductName\nVARCHAR\n_______________________________________________________________________________\n\nAlice Mutton\nAniseed Syrup\nBoston Crab Meat\nCamembert Pierrot\nCarnarvon Tigers\nChai\nChang\nChartreuse verte\n.  .  .  .  .  .   \nZaanse koeken   \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"General" ;
	sioc:content	"\nUpdategram Overview\n\nUpdategrams allow database updates to be defined as XML.  This is ultimately achieved by mapping the \nXML nodes against corresponding database columns. \n\nUpdategrams can be used to replace existing data access components in a middle tier. A typical \napplication will include a middle tier consisting of Business Logic and Data Access code. The Data Access code \nwill interface with the database using disconnected Recordsets and Command objects calling  stored procedures etc. \nMost of the Data Access section of the middle tier can be replaced with Updategrams. \n\nMost Data Access tiers (both middle tier code and stored procedures) will individually deal with specific \ndatabase tables or groups of related tables. This can inhibit performance and quite often several round trips \nto the database are required to complete a transaction.\n\nUpdategrams can solve this problem by including all of the data in an XML document, which is then mapped to \ndatabase tables and columns. The entire database update can then be accomplished in one fell  swoop. This update \ncan include inserting, updating and deleting data.\n\nThe 'xmlsql_update' function supports XML-based insert, update, and delete operations \nperformed on an existing table in database.\n\nUpdategram Basics\n\nThe general format of an updategram is:\n\n\n\n        \n                \n        \n        \n                \n        \n\n\nor\n\n\n        \n                 \n\t\t   \"value\"\n\t\t   \"value\"\n\t\t   ...\n\t\t\n\t\t...\n        \n        \n                 \n\t\t   \"value\"\n\t\t   \"value\"\n\t\t   ...\n\t\t\n\t\t...\n        \n\n\n\nElements Description\n\n  The  tag of the updategram signifies the beginning of an operation(s).\n  The rows specified in the  refer to existing records in the database.\n  The rows specified in the  block refer to what the user wants in the database.\n  TABLENAME identifies target table.\n  The sql:at-identity attribute stores the last identity value added by the system (if possible). \n  The captured identity value can then be used in subsequent operations.\n  The sql:id attribute is used to mark rows. This forces an association between\n  the record specified in the  and  block in the updategram.\n  When there are multiple instances specified, it is recommended that sql:id\n  attribute be used for all of the instances.\n  Each TABLENAME refers to a single table. Multiple  entries\n  are allowed in the same  , or  tags, or in both  and\n     tags; however, nesting is not allowed.\n  The  and  tags are optional. A missing tag is the same as\n    having a tag with no content.\n\n\nDetermining Actions\n\nIn an updategram if only the  block is specified, the\nrows specified in the  block are inserted in the table(s). If both\nthe  and  blocks are specified, then the rows specified in \nthe  block for which there is no corresponding rows in the  \nblock are inserted in the table(s).\nIn an update operation, the instances (rows) specified in the  block\nrefer to the existing rows in the database. The corresponding instances\n(rows) in the  block reflect what the user wants in the database. A\nrow update operation is performed if there is an instance (row) in both\n and  sections with the same set of values for the attributes\nthat uniquely identify a row in a table. The set of rows specified in the\n block must be valid in the database for the updategram to\nsuccessfully update the rows.\nIn a delete operation, if only the  block is specified in the updategram, \nthe instances (rows) specified in the  block are deleted from\nthe table(s). If both the  and  blocks are specified, the\ninstances (rows) for which there is no corresponding instances (rows) in the\n block are deleted from the table(s). \n\nExample\n\n\n This example creates a SQL function that takes the orders and order lines from the demo database and applies \na stylesheet to the FOR XML rendition of these to make updategrams.  Use the updategrams to fill out\na similar table structure containing order summary with only fulfilled orders included. \n\n\nThe interface will show the sources of the report and the transformed report which is the updategram. \n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Updategrams" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nUpdategram Overview\n\nUpdategrams allow database updates to be defined as XML.  This is ultimately achieved by mapping the \nXML nodes against corresponding database columns. \n\nUpdategrams can be used to replace existing data access components in a middle tier. A typical \napplication will include a middle tier consisting of Business Logic and Data Access code. The Data Access code \nwill interface with the database using disconnected Recordsets and Command objects calling  stored procedures etc. \nMost of the Data Access section of the middle tier can be replaced with Updategrams. \n\nMost Data Access tiers (both middle tier code and stored procedures) will individually deal with specific \ndatabase tables or groups of related tables. This can inhibit performance and quite often several round trips \nto the database are required to complete a transaction.\n\nUpdategrams can solve this problem by including all of the data in an XML document, which is then mapped to \ndatabase tables and columns. The entire database update can then be accomplished in one fell  swoop. This update \ncan include inserting, updating and deleting data.\n\nThe 'xmlsql_update' function supports XML-based insert, update, and delete operations \nperformed on an existing table in database.\n\nUpdategram Basics\n\nThe general format of an updategram is:\n\n\n<sql:sync xmlns:sql="xml-sql">\n        <sql:before>\n                <TABLENAME [sql:id="value"] col="value" col="value"?../>\n        </sql:before>\n        <sql:after>\n                <TABLENAME [sql:id="value"] [sql:at-identity="value"] col="value" col="value"?../>\n        </sql:after>\n</sql:sync>\n\nor\n\n<sql:sync xmlns:sql="xml-sql">\n        <sql:before>\n                <TABLENAME [sql:id="value"]> \n\t\t   <col>"value"</col>\n\t\t   <col>"value"</col>\n\t\t   ...\n\t\t</TABLENAME>\n\t\t...\n        </sql:before>\n        <sql:after>\n                <TABLENAME [sql:id="value"] [sql:at-identity="value"]> \n\t\t   <col>"value"</col>\n\t\t   <col>"value"</col>\n\t\t   ...\n\t\t</TABLENAME>\n\t\t...\n        </sql:after>\n</sql:sync>\n\n\nElements Description\n\n  The <sync> tag of the updategram signifies the beginning of an operation(s).\n  The rows specified in the <before> refer to existing records in the database.\n  The rows specified in the <after> block refer to what the user wants in the database.\n  TABLENAME identifies target table.\n  The sql:at-identity attribute stores the last identity value added by the system (if possible). \n  The captured identity value can then be used in subsequent operations.\n  The sql:id attribute is used to mark rows. This forces an association between\n  the record specified in the <before> and <after> block in the updategram.\n  When there are multiple instances specified, it is recommended that sql:id\n  attribute be used for all of the instances.\n  Each TABLENAME refers to a single table. Multiple <TABLENAME..../> entries\n  are allowed in the same <before> , or <after> tags, or in both <before> and\n    <after> tags; however, nesting is not allowed.\n  The <before> and <after> tags are optional. A missing tag is the same as\n    having a tag with no content.\n\n\nDetermining Actions\n\nIn an updategram if only the <after> block is specified, the\nrows specified in the <after> block are inserted in the table(s). If both\nthe <before> and <after> blocks are specified, then the rows specified in \nthe <after> block for which there is no corresponding rows in the <before> \nblock are inserted in the table(s).\nIn an update operation, the instances (rows) specified in the <before> block\nrefer to the existing rows in the database. The corresponding instances\n(rows) in the <after> block reflect what the user wants in the database. A\nrow update operation is performed if there is an instance (row) in both\n<before> and <after> sections with the same set of values for the attributes\nthat uniquely identify a row in a table. The set of rows specified in the\n<before> block must be valid in the database for the updategram to\nsuccessfully update the rows.\nIn a delete operation, if only the <before> block is specified in the updategram, \nthe instances (rows) specified in the <before> block are deleted from\nthe table(s). If both the <before> and <after> blocks are specified, the\ninstances (rows) for which there is no corresponding instances (rows) in the\n<after> block are deleted from the table(s). \n\nExample\n\n\n This example creates a SQL function that takes the orders and order lines from the demo database and applies \na stylesheet to the FOR XML rendition of these to make updategrams.  Use the updategrams to fill out\na similar table structure containing order summary with only fulfilled orders included. \n\n\nThe interface will show the sources of the report and the transformed report which is the updategram. \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Exercises" ;
	sioc:content	"\nPreliminaries\n This sample program demonstrates the use of parameters in an updategram:\n\n\n  Create a form that allows new records to be inserted into a table.\n  Use the form text fields as input parameters for the updategram. \n  After insert display a list of records to show that new record has been inserted into the table.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Parameter usage in updategrams" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nPreliminaries\n This sample program demonstrates the use of parameters in an updategram:\n\n\n  Create a form that allows new records to be inserted into a table.\n  Use the form text fields as input parameters for the updategram. \n  After insert display a list of records to show that new record has been inserted into the table.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Using a XML temapltes" ;
	sioc:content	"\nPreliminaries\nThis sample program demonstrates the use of XML templates:\n\n\n  Use the XS_U_3 SQL script\n  to create a Web virtual directory that allows execution of the XML template.\n  \n  Create a form that allows new records to be inserted into\n  a table.\n  Use the form text fields as input parameters for the XML\n  template.\n  The XML template (shippers.xml) will\n  insert a new record using the form parameters. It makes an XML document using\n  SQL/XML query, and renders it with an XML-T style sheet.\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"Row Insertion and Report Generation using XML Templates" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nPreliminaries\nThis sample program demonstrates the use of XML templates:\n\n\n  Use the XS_U_3 SQL script\n  to create a Web virtual directory that allows execution of the XML template.\n  \n  Create a form that allows new records to be inserted into\n  a table.\n  Use the form text fields as input parameters for the XML\n  template.\n  The XML template (shippers.xml) will\n  insert a new record using the form parameters. It makes an XML document using\n  SQL/XML query, and renders it with an XML-T style sheet.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"General" ;
	sioc:content	"\nFor XML SQL Clause Overview\n\nThis feature enables the execution SQL queries against the Virtuoso Server to return results as XML \ndocuments rather than as standard rowsets. To retrieve results directly, use the FOR XML clause of the \nSELECT statement and in the FOR XML clause, specify one of these XML modes: \n\n   RAW - transforms each row in the query result set into an XML element with the generic identifier row.  \n   AUTO - returns query results as nested XML elements. \n   EXPLICIT - authors of query can control the structure of the XML document returned by the query. \n \n\nExamples\n\nThis example shows a simple use of the For XML SQL 'Auto' statement for executing a query and returning \nthe results in XML format.\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"FOR XML SQL Clause" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nFor XML SQL Clause Overview\n\nThis feature enables the execution SQL queries against the Virtuoso Server to return results as XML \ndocuments rather than as standard rowsets. To retrieve results directly, use the FOR XML clause of the \nSELECT statement and in the FOR XML clause, specify one of these XML modes: \n\n   RAW - transforms each row in the query result set into an XML element with the generic identifier row.  \n   AUTO - returns query results as nested XML elements. \n   EXPLICIT - authors of query can control the structure of the XML document returned by the query. \n \n\nExamples\n\nThis example shows a simple use of the For XML SQL 'Auto' statement for executing a query and returning \nthe results in XML format.\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"General" ;
	sioc:content	"\nExample\nThis sample demonstrates the use of the FOR XML EXPLICIT mode.\n\n\n" ;
	sioc:has_container	ns2:xml ;
	sioc:description	"FOR XML EXPLICIT SQL statements" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nExample\nThis sample demonstrates the use of the FOR XML EXPLICIT mode.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Creating a publication" ;
	sioc:content	"\nPreliminaries\nVirtuoso supports bidirectional transactional replication via mechanism\nof updateable subscriptions.\n\n\n  Every table has only one publisher.\n  Subscribers can update replicated tables on their side and then\nsubmit data back to publisher. Publisher performs conflict resolution\nand either accepts or rejects that data.\n  It is assumed that all the tables in publication with updateable\nsubscriptions option have primary keys and that primary key columns are never\nmodified.\n\n\nExample publication account setup\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab, then go to the \"Transactional\" tab and then go the \"Publications\" sub-tab.\n  Press the \"Create\" button.\n  Enter publication name, check the \"Updateable\" checkbox and press the \"Create\" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create publication \"repldemo\" with log file \"repldemo.log\"\n  \nSQL> repl_publish('repldemo', 'repldemo.log', 1);\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Creating a replication publication account" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nVirtuoso supports bidirectional transactional replication via mechanism\nof updateable subscriptions.\n\n\n  Every table has only one publisher.\n  Subscribers can update replicated tables on their side and then\nsubmit data back to publisher. Publisher performs conflict resolution\nand either accepts or rejects that data.\n  It is assumed that all the tables in publication with updateable\nsubscriptions option have primary keys and that primary key columns are never\nmodified.\n\n\nExample publication account setup\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab, then go to the "Transactional" tab and then go the "Publications" sub-tab.\n  Press the "Create" button.\n  Enter publication name, check the "Updateable" checkbox and press the "Create" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create publication "repldemo" with log file "repldemo.log"\n  \nSQL> repl_publish('repldemo', 'repldemo.log', 1);\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Creating a publication" ;
	sioc:content	"\nTo add a table to publication execute the following steps:\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab, then go to the \"Transactional\" tab and then go the \"Publications\" sub-tab.\n  From the publications list select the link with the name of your publication (\"repldemo\").\n  Press the \"Add Tables\" button.\n  Select a database, then a table or multiple tables\n            (select \"Demo.demo.Orders\"), and then\n            press \"Add to Publication\" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Add table \"Demo.demo.Orders\" to publication \"repldemo\"\n  \nSQL> repl_pub_add('repldemo', 'Demo.demo.Orders', 2, 1, 0);\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Adding tables to publication" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nTo add a table to publication execute the following steps:\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab, then go to the "Transactional" tab and then go the "Publications" sub-tab.\n  From the publications list select the link with the name of your publication ("repldemo").\n  Press the "Add Tables" button.\n  Select a database, then a table or multiple tables\n            (select "Demo.demo.Orders"), and then\n            press "Add to Publication" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Add table "Demo.demo.Orders" to publication "repldemo"\n  \nSQL> repl_pub_add('repldemo', 'Demo.demo.Orders', 2, 1, 0);\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Creating a publication" ;
	sioc:content	"\nPreliminaries\nBecause every table can have only one publisher, conflicts can occur\nonly on publisher (when modifications from subscriber are applied).\n\nEvery table on publisher can have a number of conflict resolvers\nwhich are used for conflict resolution. Each conflict resolver has a type\n('I', 'U', or 'D') and an order. Conflict resolvers are applied\nin ascending order.\n\nConflict resolver is a Virtuoso/PL procedure which receives conflicting\nrow (row from subscriber) and some other arguments. Conflict resolver\nsignatures are described in Virtuoso documentation.\nConflict resolver can modify the row which is passed in as 'inout' arguments.\nConflict resolver should return an integer value which will be used\nfor conflict resolution. Possible return values and their meaning\nare described in Virtuoso documentation.\n\nConflict resolution occurs differently for each kind of DML operation.\nDetails can be found in Virtuoso documentation.\n\nThere is a possibility to automatically generate some types of\nconflict resolvers. Automatically generated conflict resolver classes are:\n\n\n\n  max - \n    row with maximum value of specified column wins\n  min - \n    row with minumum value of specified column wins\n  ave - \n    new value of specified column is calculated as:\n    current_val = (current_val + new_val) / 2\n  add - \n    new value of specified column is calculated as:\n    current_val = current_val + (new_val - old_val)\n  pub_wins - \n    publisher always wins\n  sub_wins - \n    subscriber always wins\n\n\nExample defining a conflict resolver\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab, then go to the \"Transactional\" tab and then go the \"Publications\" sub-tab.\n  Select the link with the name of your publication (\"repldemo\").\n  Select the link with the name of the table (\"Demo.demo.Orders\").\n  Press the \"New Resolver\" button.\n  Enter conflict resolver name suffix for example \"min_OrderDate\",\n  select conflict resolver type (select \"U\"),\n  select conflict resolver class (select \"min\"),\n  select a column (select \"OrderDate\"). You can optionally\n  specify conflict resolver order (default is 100).\n  Press \"Add\" button. A conflict resolver will be added. You\n  can view and edit conflict resolver code by selecting the link with\n  its name from the list of conflict resolvers.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create 'U' conflict resolver for table \"Demo.demo.Orders\" that\n    will choose a row with minimal OrderDate column.\n  \nSQL> repl_add_cr('Demo.demo.Orders', 'min_OrderDate', 'U', 100, 'min', 'OrderDate');\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Defining conflict resolvers" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nBecause every table can have only one publisher, conflicts can occur\nonly on publisher (when modifications from subscriber are applied).\n\nEvery table on publisher can have a number of conflict resolvers\nwhich are used for conflict resolution. Each conflict resolver has a type\n('I', 'U', or 'D') and an order. Conflict resolvers are applied\nin ascending order.\n\nConflict resolver is a Virtuoso/PL procedure which receives conflicting\nrow (row from subscriber) and some other arguments. Conflict resolver\nsignatures are described in Virtuoso documentation.\nConflict resolver can modify the row which is passed in as 'inout' arguments.\nConflict resolver should return an integer value which will be used\nfor conflict resolution. Possible return values and their meaning\nare described in Virtuoso documentation.\n\nConflict resolution occurs differently for each kind of DML operation.\nDetails can be found in Virtuoso documentation.\n\nThere is a possibility to automatically generate some types of\nconflict resolvers. Automatically generated conflict resolver classes are:\n\n\n\n  max - \n    row with maximum value of specified column wins\n  min - \n    row with minumum value of specified column wins\n  ave - \n    new value of specified column is calculated as:\n    current_val = (current_val + new_val) / 2\n  add - \n    new value of specified column is calculated as:\n    current_val = current_val + (new_val - old_val)\n  pub_wins - \n    publisher always wins\n  sub_wins - \n    subscriber always wins\n\n\nExample defining a conflict resolver\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab, then go to the "Transactional" tab and then go the "Publications" sub-tab.\n  Select the link with the name of your publication ("repldemo").\n  Select the link with the name of the table ("Demo.demo.Orders").\n  Press the "New Resolver" button.\n  Enter conflict resolver name suffix for example "min_OrderDate",\n  select conflict resolver type (select "U"),\n  select conflict resolver class (select "min"),\n  select a column (select "OrderDate"). You can optionally\n  specify conflict resolver order (default is 100).\n  Press "Add" button. A conflict resolver will be added. You\n  can view and edit conflict resolver code by selecting the link with\n  its name from the list of conflict resolvers.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create 'U' conflict resolver for table "Demo.demo.Orders" that\n    will choose a row with minimal OrderDate column.\n  \nSQL> repl_add_cr('Demo.demo.Orders', 'min_OrderDate', 'U', 100, 'min', 'OrderDate');\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Creating a subscription" ;
	sioc:content	"\nPreliminaries\nIn order to run this example you need two Virtuoso servers running\n(publisher and subscriber). In the example scripts it is assumed that the first Virtuoso server\n(publisher) is running at localhost:1111 and the second Virtuoso server\n(subscriber) is running at localhost:1112. If you are running ODBC\nversions of the servers there should be 2 ODBC DSN's records named\n\"localhost:1111\" and \"localhost:1112\".\n\n\nExample creating a subscription\nThese steps should be executed on subscriber.\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab, then go to the \"Transactional\" tab and then go the \"Subscriptions\" sub-tab.\n  Press \"New Subscription\" button.\n  Select connected DSN from the list and then press\n    \"Publications list\" button. If the desired DSN is not connected yet\n    you can connect to it using \"Specify new data source\" dialog below.\n  \n  Select a publication and press \"List items\" button.\n  Press \"Subscribe\" button. You can optionally load initial data\n    by checking \"Load data\" checkbox.\n\n\nEquivalent SQL commands to the above\n\n  Connect to the subscriber via ISQL utility as DBA user.\n  Define a replication server \"demoserver\" at \"localhost:1111\"\n    and subscribe to publication \"repldemo\" from it.\n  \nSQL> repl_server('demoserver', 'localhost:1111', 'localhost:1111');\nSQL> repl_subscribe('demoserver', 'repldemo', 'dba', 'dba', 'dba', 'dba');\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Creating a subscription" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nIn order to run this example you need two Virtuoso servers running\n(publisher and subscriber). In the example scripts it is assumed that the first Virtuoso server\n(publisher) is running at localhost:1111 and the second Virtuoso server\n(subscriber) is running at localhost:1112. If you are running ODBC\nversions of the servers there should be 2 ODBC DSN's records named\n"localhost:1111" and "localhost:1112".\n\n\nExample creating a subscription\nThese steps should be executed on subscriber.\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab, then go to the "Transactional" tab and then go the "Subscriptions" sub-tab.\n  Press "New Subscription" button.\n  Select connected DSN from the list and then press\n    "Publications list" button. If the desired DSN is not connected yet\n    you can connect to it using "Specify new data source" dialog below.\n  \n  Select a publication and press "List items" button.\n  Press "Subscribe" button. You can optionally load initial data\n    by checking "Load data" checkbox.\n\n\nEquivalent SQL commands to the above\n\n  Connect to the subscriber via ISQL utility as DBA user.\n  Define a replication server "demoserver" at "localhost:1111"\n    and subscribe to publication "repldemo" from it.\n  \nSQL> repl_server('demoserver', 'localhost:1111', 'localhost:1111');\nSQL> repl_subscribe('demoserver', 'repldemo', 'dba', 'dba', 'dba', 'dba');\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Publishing a table" ;
	sioc:content	"\nPreliminaries\nBidirectional snapshot replication allows you to set up snapshot\nreplication between multiple servers where updates can be performed on all\nservers.\n\n\n  Publisher-subscriber model where each table has only one publisher\n    and when an update is performed on subscriber it goes to publisher first,\n    and then to all other subscribers.\n  \n  Conflict resolution may need to take place on the publisher when\n    data coming from a subscriber is processed.\n  \n  It is assumed that all published tables have primary keys and that\n    primary key columns are never modified.\n  \n\n\nExample publishing a table\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab and then go to the \"Bidirectional Snapshot\" tab.\n  Press the \"Add table\" button.\n  Enter table name or select the table using \"Browse...\" button\n\t    and press \"Add\" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Publish \"Demo.demo.Orders\" table.\n  \nSQL> repl_create_snapshot_pub ('Demo.demo.Orders', 2);\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Publishing a table for replication" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nBidirectional snapshot replication allows you to set up snapshot\nreplication between multiple servers where updates can be performed on all\nservers.\n\n\n  Publisher-subscriber model where each table has only one publisher\n    and when an update is performed on subscriber it goes to publisher first,\n    and then to all other subscribers.\n  \n  Conflict resolution may need to take place on the publisher when\n    data coming from a subscriber is processed.\n  \n  It is assumed that all published tables have primary keys and that\n    primary key columns are never modified.\n  \n\n\nExample publishing a table\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab and then go to the "Bidirectional Snapshot" tab.\n  Press the "Add table" button.\n  Enter table name or select the table using "Browse..." button\n\t    and press "Add" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Publish "Demo.demo.Orders" table.\n  \nSQL> repl_create_snapshot_pub ('Demo.demo.Orders', 2);\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Publishing a table" ;
	sioc:content	"\nPreliminaries\nBecause every table can have only one publisher conflicts can occur\nonly on publisher (when modifications from subscriber are applied).\n\nEvery table on publisher can have a number of conflict resolvers\nwhich are used for conflict resolution. Each conflict resolver has a type\n('I', 'U', or 'D') and an order. Conflict resolvers are applied\nin ascending order.\n\nConflict resolver is a Virtuoso/PL procedure which receives conflicting\nrow (row from subscriber) and some other arguments. Conflict resolver\nsignatures are described in Virtuoso documentation.\nConflict resolver can modify the row which is passed in as 'inout' arguments.\nConflict resolver should return an integer value which will be used\nfor conflict resolution. Possible return values and their meaning\nare described in Virtuoso documentation.\n\nConflict resolution occurs differently for each kind of DML operation.\nDetails can be found in Virtuoso documentation.\n\nThere is a possibility to automatically generate some types of\nconflict resolvers. Automatically generated conflict resolver classes are:\n\n\n\n  max - \n    row with maximum value of specified column wins\n  min - \n    row with minumum value of specified column wins\n  ave - \n    new value of specified column is calculated as:\n    current_val = (current_val + new_val) / 2\n  pub_wins - \n    publisher always wins\n  sub_wins - \n    subscriber always wins\n\n\nExample defining a conflict resolver\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab and then go to the \"Bidirectional Snapshot\" tab.\n  Click \"Conflict Resolvers\" for the desired published table (\"Demo.demo.Orders\").\n  Press \"New Resolver\" button.\n  Enter conflict resolver name suffix (enter \"max_OrderDate\"),\n  select conflict resolver type (select \"U\"),\n  select conflict resolver class (select \"max\"),\n  select a column (select \"OrderDate\"). You can optionally\n  specify conflict resolver order (default is 100).\n  Press \"Add\" button. A conflict resolver will be added. You\n  can view and edit conflict resolver code by selecting a link with\n  its name from the list of conflict resolvers.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create 'U' conflict resolver for table \"Demo.demo.Orders\"\n    that will choose a row with latest OrderDate.\n  \nSQL> REPL_ADD_SNAPSHOT_CR ('Demo.demo.Orders', 'max_OrderDate', 'U', 100, 'max', 'OrderDate');\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Defining conflict resolvers" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nBecause every table can have only one publisher conflicts can occur\nonly on publisher (when modifications from subscriber are applied).\n\nEvery table on publisher can have a number of conflict resolvers\nwhich are used for conflict resolution. Each conflict resolver has a type\n('I', 'U', or 'D') and an order. Conflict resolvers are applied\nin ascending order.\n\nConflict resolver is a Virtuoso/PL procedure which receives conflicting\nrow (row from subscriber) and some other arguments. Conflict resolver\nsignatures are described in Virtuoso documentation.\nConflict resolver can modify the row which is passed in as 'inout' arguments.\nConflict resolver should return an integer value which will be used\nfor conflict resolution. Possible return values and their meaning\nare described in Virtuoso documentation.\n\nConflict resolution occurs differently for each kind of DML operation.\nDetails can be found in Virtuoso documentation.\n\nThere is a possibility to automatically generate some types of\nconflict resolvers. Automatically generated conflict resolver classes are:\n\n\n\n  max - \n    row with maximum value of specified column wins\n  min - \n    row with minumum value of specified column wins\n  ave - \n    new value of specified column is calculated as:\n    current_val = (current_val + new_val) / 2\n  pub_wins - \n    publisher always wins\n  sub_wins - \n    subscriber always wins\n\n\nExample defining a conflict resolver\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab and then go to the "Bidirectional Snapshot" tab.\n  Click "Conflict Resolvers" for the desired published table ("Demo.demo.Orders").\n  Press "New Resolver" button.\n  Enter conflict resolver name suffix (enter "max_OrderDate"),\n  select conflict resolver type (select "U"),\n  select conflict resolver class (select "max"),\n  select a column (select "OrderDate"). You can optionally\n  specify conflict resolver order (default is 100).\n  Press "Add" button. A conflict resolver will be added. You\n  can view and edit conflict resolver code by selecting a link with\n  its name from the list of conflict resolvers.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create 'U' conflict resolver for table "Demo.demo.Orders"\n    that will choose a row with latest OrderDate.\n  \nSQL> REPL_ADD_SNAPSHOT_CR ('Demo.demo.Orders', 'max_OrderDate', 'U', 100, 'max', 'OrderDate');\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Defining subscribers for published table" ;
	sioc:content	"\nPreliminaries\nIn order to run this example you need two Virtuoso servers running\n(publisher and subscriber). In the example scripts it is assumed that the first Virtuoso server\n(publisher) is running at localhost:1111 and the second Virtuoso server\n(subscriber) is running at localhost:1112. If you are running ODBC\nversions of the servers there should be 2 ODBC DSN's records named\n\"localhost:1111\" and \"localhost:1112\". Subscriber should have\n\"ServerName\" configuration parameter set to \"demoserver2\".\n\n\nExample creating a subscription\nThese steps should be executed on publisher.\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab and then go to the \"Bidirectional Snapshot\" tab.\n  Click \"Subscriptions\" for desired published table (\"Demo.demo.Orders\").\n  Press \"New Subscriber\" button.\n  Select connected DSN from the list and then press\n    \"Create Subscription\" button. If the desired DSN is not connected yet\n    you can connect to it using \"Specify new data source\" dialog below.\n  \n\n\nEquivalent SQL commands to above\n\n  Connect to the publisher via ISQL utility as DBA user.\n  Define a replication server \"demoserver2\" at \"localhost:1112\"\n    and subscribe it to published \"Demo.demo.Orders\" table.\n  \nSQL> repl_snp_server('localhost:1112');\nSQL> repl_create_snapshot_sub('demoserver2', 'Demo.demo.Orders', 2, 'dba', 'dba');\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Defining subscribers" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nIn order to run this example you need two Virtuoso servers running\n(publisher and subscriber). In the example scripts it is assumed that the first Virtuoso server\n(publisher) is running at localhost:1111 and the second Virtuoso server\n(subscriber) is running at localhost:1112. If you are running ODBC\nversions of the servers there should be 2 ODBC DSN's records named\n"localhost:1111" and "localhost:1112". Subscriber should have\n"ServerName" configuration parameter set to "demoserver2".\n\n\nExample creating a subscription\nThese steps should be executed on publisher.\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab and then go to the "Bidirectional Snapshot" tab.\n  Click "Subscriptions" for desired published table ("Demo.demo.Orders").\n  Press "New Subscriber" button.\n  Select connected DSN from the list and then press\n    "Create Subscription" button. If the desired DSN is not connected yet\n    you can connect to it using "Specify new data source" dialog below.\n  \n\n\nEquivalent SQL commands to above\n\n  Connect to the publisher via ISQL utility as DBA user.\n  Define a replication server "demoserver2" at "localhost:1112"\n    and subscribe it to published "Demo.demo.Orders" table.\n  \nSQL> repl_snp_server('localhost:1112');\nSQL> repl_create_snapshot_sub('demoserver2', 'Demo.demo.Orders', 2, 'dba', 'dba');\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Bidirectional Snapshot Replication Demo" ;
	sioc:content	"\nPreliminaries\nThis tutorial demonstrates basic snapshot replication features.\nIn order to run this tutorial execute the following steps:\n\nSetup ODBC data source named \"demoserver2\".\nMake sure that user \"demo\" with password \"demo\"\ncan connect to data source \"demoserver2\".\nMake sure that there is no table named \"Shippers\"\nin target data source.\n\n\nThe data source can be Virtuoso data source as well as any other data\nsource type which is supported by Virtuoso bidirectional snapshot replication\n(E.g. Oracle or MS SQL data source). This tutorial will\ndemonstrate Virtuoso heterogeneous snapshot replication capabilities.\n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Bidirectional snapshot replication demo" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nThis tutorial demonstrates basic snapshot replication features.\nIn order to run this tutorial execute the following steps:\n\nSetup ODBC data source named "demoserver2".\nMake sure that user "demo" with password "demo"\ncan connect to data source "demoserver2".\nMake sure that there is no table named "Shippers"\nin target data source.\n\n\nThe data source can be Virtuoso data source as well as any other data\nsource type which is supported by Virtuoso bidirectional snapshot replication\n(E.g. Oracle or MS SQL data source). This tutorial will\ndemonstrate Virtuoso heterogeneous snapshot replication capabilities.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Publishing a DAV collection" ;
	sioc:content	"\nPreliminaries\nBidirectional snapshot replication allows you to set up snapshot\nreplication between multiple servers where updates can be performed on all\nservers.\n\n\n  Publisher-subscriber model where each DAV collection has only one\n    publisher and when an update is performed on subscriber it goes to\n    publisher first, and then to all other subscribers.\n  \n  Conflict resolution may need to take place on the publisher when\n    DAV resources coming from a subscriber are processed.\n  \n\n\nExample publishing a DAV collection\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab and then go to the \"Bidirectional Snapshot\" tab.\n  Press \"Add DAV Collection\" button.\n  Enter DAV collection name or select DAV collection\n            using \"Browse...\" button and press \"Add\" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Publish \"/DAV/doc\" DAV collection.\n  \nSQL> repl_create_snapshot_pub ('/DAV/doc', 1);\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Publishing a DAV collection for replication" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nBidirectional snapshot replication allows you to set up snapshot\nreplication between multiple servers where updates can be performed on all\nservers.\n\n\n  Publisher-subscriber model where each DAV collection has only one\n    publisher and when an update is performed on subscriber it goes to\n    publisher first, and then to all other subscribers.\n  \n  Conflict resolution may need to take place on the publisher when\n    DAV resources coming from a subscriber are processed.\n  \n\n\nExample publishing a DAV collection\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab and then go to the "Bidirectional Snapshot" tab.\n  Press "Add DAV Collection" button.\n  Enter DAV collection name or select DAV collection\n            using "Browse..." button and press "Add" button.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Publish "/DAV/doc" DAV collection.\n  \nSQL> repl_create_snapshot_pub ('/DAV/doc', 1);\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Publishing a DAV collection" ;
	sioc:content	"\nPreliminaries\nEvery DAV collection on publisher can have a number of conflict resolvers\nwhich are used for conflict resolution. Each conflict resolver has an\ninteger number (order) associated with it. Conflict resolvers are applied\nin ascending order.\n\nConflict resolver is a Virtuoso/PL procedure which receives conflicting\nDAV resource. DAV conflict resolver signatures are described in Virtuoso\ndocumentation. Conflict resolver can modify the resource which is passed in\nas 'inout' arguments. Conflict resolver should return an integer value which\nwill be used for conflict resolution. Possible return values and their meaning\nare described in Virtuoso documentation.\n\nThere is a possibility to automatically generate some types of\nconflict resolvers. Automatically generated conflict resolver classes are:\n\n\n\n  max_mtime - \n    resource with maximum modification time wins\n  min_mtime - \n    resource with minumum modification time wins\n  max_ctime - \n    resource with maximum creation time wins\n  min_ctime - \n    resource with minumum creation time wins\n  backup - \n    backup of resource that lost conflict resolution will be performed,\n      conflict resolution will continue\n    \n  \n  notify - \n    \n      owner of resource will be notified if his resource lost conflict\n      resolution\n    \n  \n  pub_wins - \n    publisher always wins\n  sub_wins - \n    subscriber always wins\n\n\nExample defining a conflict resolver\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab and then go to the \"Bidirectional Snapshot\" tab.\n  Click \"Conflict Resolvers\" for desired published DAV collection (\"/DAV/doc\").\n  Press \"New Resolver\" button.\n  Enter conflict resolver name suffix (enter \"max_mtime\"),\n  select conflict resolver class (select \"max_mtime\"). You can optionally\n  specify conflict resolver order (default is 100).\n  Press \"Add\" button. A conflict resolver will be added. You\n  can view and edit conflict resolver code by selecting the link with\n  its name from the list of conflict resolvers.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create a conflict resolver for collection \"/DAV/doc\"\n    that will choose a resource with maximum modification time\n    (more recent resource).\n  \nSQL> REPL_ADD_DAV_CR ('/DAV/doc', 'max_mtime', 100, 'max_mtime');\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Defining conflict resolvers" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nEvery DAV collection on publisher can have a number of conflict resolvers\nwhich are used for conflict resolution. Each conflict resolver has an\ninteger number (order) associated with it. Conflict resolvers are applied\nin ascending order.\n\nConflict resolver is a Virtuoso/PL procedure which receives conflicting\nDAV resource. DAV conflict resolver signatures are described in Virtuoso\ndocumentation. Conflict resolver can modify the resource which is passed in\nas 'inout' arguments. Conflict resolver should return an integer value which\nwill be used for conflict resolution. Possible return values and their meaning\nare described in Virtuoso documentation.\n\nThere is a possibility to automatically generate some types of\nconflict resolvers. Automatically generated conflict resolver classes are:\n\n\n\n  max_mtime - \n    resource with maximum modification time wins\n  min_mtime - \n    resource with minumum modification time wins\n  max_ctime - \n    resource with maximum creation time wins\n  min_ctime - \n    resource with minumum creation time wins\n  backup - \n    backup of resource that lost conflict resolution will be performed,\n      conflict resolution will continue\n    \n  \n  notify - \n    \n      owner of resource will be notified if his resource lost conflict\n      resolution\n    \n  \n  pub_wins - \n    publisher always wins\n  sub_wins - \n    subscriber always wins\n\n\nExample defining a conflict resolver\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab and then go to the "Bidirectional Snapshot" tab.\n  Click "Conflict Resolvers" for desired published DAV collection ("/DAV/doc").\n  Press "New Resolver" button.\n  Enter conflict resolver name suffix (enter "max_mtime"),\n  select conflict resolver class (select "max_mtime"). You can optionally\n  specify conflict resolver order (default is 100).\n  Press "Add" button. A conflict resolver will be added. You\n  can view and edit conflict resolver code by selecting the link with\n  its name from the list of conflict resolvers.\n\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create a conflict resolver for collection "/DAV/doc"\n    that will choose a resource with maximum modification time\n    (more recent resource).\n  \nSQL> REPL_ADD_DAV_CR ('/DAV/doc', 'max_mtime', 100, 'max_mtime');\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Defining subscribers for a pulished DAV collection" ;
	sioc:content	"\nPreliminaries\nIn order to run this example you need two Virtuoso servers running\n(publisher and subscriber). In the example scripts it is assumed that the first Virtuoso server\n(publisher) is running at localhost:1111 and the second Virtuoso server\n(subscriber) is running at localhost:1112. If you are running ODBC\nversions of the servers there should be 2 ODBC DSN's records named\n\"localhost:1111\" and \"localhost:1112\". Subscriber should have\n\"ServerName\" configuration parameter set to \"demoserver2\".\n\n\nExample creating a subscription\nThese steps should be executed on publisher.\n\n  Login to the Conductor UI using the dba account.\n  Go to the \"Replication\" tab and then go to the \"Bidirectional Snapshot\" tab.\n  Click \"Subscriptions\" for desired published DAV collection (\"/DAV/doc\").\n  Press \"New Subscriber\" button.\n  Select connected DSN from the list and then press\n    \"Create Subscription\" button. If desired DSN is not connected yet\n    you can connect to it using \"Specify new data source\" dialog below.\n  \n\n\nEquivalent SQL commands to above\n\n  Connect to the publisher via ISQL utility as DBA user.\n  Define a replication server \"demoserver2\" at \"localhost:1112\"\n    and subscribe it to published \"/DAV/doc\" DAV collection.\n  \nSQL> repl_snp_server('localhost:1112');\nSQL> repl_create_snapshot_sub('demoserver2', '/DAV/doc', 1, 'dba', 'dba');\n  \n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Defining subscribers" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nIn order to run this example you need two Virtuoso servers running\n(publisher and subscriber). In the example scripts it is assumed that the first Virtuoso server\n(publisher) is running at localhost:1111 and the second Virtuoso server\n(subscriber) is running at localhost:1112. If you are running ODBC\nversions of the servers there should be 2 ODBC DSN's records named\n"localhost:1111" and "localhost:1112". Subscriber should have\n"ServerName" configuration parameter set to "demoserver2".\n\n\nExample creating a subscription\nThese steps should be executed on publisher.\n\n  Login to the Conductor UI using the dba account.\n  Go to the "Replication" tab and then go to the "Bidirectional Snapshot" tab.\n  Click "Subscriptions" for desired published DAV collection ("/DAV/doc").\n  Press "New Subscriber" button.\n  Select connected DSN from the list and then press\n    "Create Subscription" button. If desired DSN is not connected yet\n    you can connect to it using "Specify new data source" dialog below.\n  \n\n\nEquivalent SQL commands to above\n\n  Connect to the publisher via ISQL utility as DBA user.\n  Define a replication server "demoserver2" at "localhost:1112"\n    and subscribe it to published "/DAV/doc" DAV collection.\n  \nSQL> repl_snp_server('localhost:1112');\nSQL> repl_create_snapshot_sub('demoserver2', '/DAV/doc', 1, 'dba', 'dba');\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SyncML Server" ;
	sioc:content	"\nPreliminaries\nSyncML is a protocol for syncronizing\n    data between two devices called server and client.\n    Usually as client we may consider PDA, mobile phone\n    or a workstation that have the ability to syncoronize their\n    contacts, calendar etc. databases using SyncML protocol.\n    On the other hand the server have ability to recoginize\n    such requests and to store the data into the repository.\n    Basically this is a protocol for data replication,\n    oriented to the portable devices.\n\n\n\n    The usual message flow is:\n\n\n\n  Initial request from client\n  Server response asking for credentials, if not supplied\n  Client sends credentials included in the request\n  Server accepts or rejects the sync request.\n  When request for sync is accepted, then server\n      checks what sync to perform: slow two-way (full data) or two-way sync.\n  Client send the items that are changed or all items depending of sync type\n  Server sends items that are changed or all items depending of sync type requested.\n\n\n\t\t\n    The Virtuoso WebDAV repository can be used to keep\n    such data. The server will recognize SyncML request by MIME\n    content type 'application/vnd.syncml+xml' or 'application/vnd.syncml+wbxml'\n    upon POST request and will act then as SyncML server over HTTP.\n    \n    Shortly: on server side are needed:\n\t\t\n    \t1.WebDAV collection with permisions for given accounts \n    \t2.Virtual directory assigned to it.\n\t\t\n    \n    Optionally virtual host can be defined in order to work with\n    clients that do not have the ability to specify URL, such clients can work\n    only with virtual root collection. Note that WebDAV collection(s) creation is a\n    vital step; apropriate rights MUST be set before using it with SyncML client;\n    clients can only store items(resources), they can't make sub-folders.\n\t\t\n\n\n    Instructions for setting SyncML server and client\n\n    Create a new folder named '/DAV/sync/' under WebDAV root. This can be done via Conductor UI going to the \"Web Application Server\" tab and then going to the \"Content Management\" tab.\n    Create subfolders calendar and contacts under /DAV/sync/\n    Create a new virtual host with virtual root assigned to /DAV/sync/ WebDAV collection. Please reffer to the documentation for more information.\n\n\nNokia 92x0 Communicator\n\n\n    In Extras menu open \"Remote sync\"\n    In \"Profile settings\" choose \"New Profile\"\n    Select apropriate internet access\n    Enter the Virtuso HTTP server address and port values as you created them earlier.\n    Enter username and password for account which have permissions to the\n\t'/DAV/sync/' and descendants.\n    Select tab \"Data\"\n    Choose Calendar and enter for \"Remote calendar\" './calendar/'.\n    Choose Contacts and enter for \"Remote contacts\" './contacts/'.\n    Close the Sync Profile menus, confirm saving\n    Select \"Sync\" option.\n    Verify that items are uploaded into WebDAV collections: /DAV/sync/calendar/ and /DAV/sync/contacts/. For this  you can use Conductor's WebDAV content management UI\n    Edit some of Contacts/Events on device and perform Sync again. Check the repository as in previous step.\n    Note: Editing the items on the server needs knowlage of VCARD/VCALENDAR formats as they can be edited as text files.\n\n\nSiemens SX1\n\n\nSelect \"menu\" button\nChoose \"Organizer\"\nChoose \"Sync\"\nSelect from menu \"Options\", \"New sync profile\"\nGive a meaningful name for this profile in \"Sync profile name\"\nBearer type: Internet\nAccess point: choose some predefined\nHost address: URL to the SyncML server without HTTP port number\nPort: SyncML HTTP port number\nUser name: username for account which have permissions to the '/DAV/sync/' and descendants.\nPassword: password for the account\nCalendar: Yes\nRemote calendar: ./calendar\nContacts: Yes\nRemote contacts: ./contacts\nHTTP authentication: No\nHTTP user name: blank\nHTTP password: blank\nSelect \"Back\" from menu\nNew profile should exists. Click on it to perform syncronization.\n\n\nSony Ericsson P900\n\n    From main menu choose \"Remote Sync\"\n    Via menu \"Edit\" - \"Preferences\"\n    Server address: [type URL to the SyncML server]\n    User Name:\n    Password:\n    Press button \"Done\"\n    Click on \"Contacts\"\n    Enable task: on\n    Server database: ./contacts\n    Press button \"Done\"\n    To perform Sync on defined items, press button \"Sync\"\n\n\nImportant: Internet connection must be alredy defined and must work with\n    device's browser.\n\n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Setting up SyncML server" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nSyncML is a protocol for syncronizing\n    data between two devices called server and client.\n    Usually as client we may consider PDA, mobile phone\n    or a workstation that have the ability to syncoronize their\n    contacts, calendar etc. databases using SyncML protocol.\n    On the other hand the server have ability to recoginize\n    such requests and to store the data into the repository.\n    Basically this is a protocol for data replication,\n    oriented to the portable devices.\n\n\n\n    The usual message flow is:\n\n\n\n  Initial request from client\n  Server response asking for credentials, if not supplied\n  Client sends credentials included in the request\n  Server accepts or rejects the sync request.\n  When request for sync is accepted, then server\n      checks what sync to perform: slow two-way (full data) or two-way sync.\n  Client send the items that are changed or all items depending of sync type\n  Server sends items that are changed or all items depending of sync type requested.\n\n\n\t\t\n    The Virtuoso WebDAV repository can be used to keep\n    such data. The server will recognize SyncML request by MIME\n    content type 'application/vnd.syncml+xml' or 'application/vnd.syncml+wbxml'\n    upon POST request and will act then as SyncML server over HTTP.\n    \n    Shortly: on server side are needed:\n\t\t\n    \t1.WebDAV collection with permisions for given accounts \n    \t2.Virtual directory assigned to it.\n\t\t\n    \n    Optionally virtual host can be defined in order to work with\n    clients that do not have the ability to specify URL, such clients can work\n    only with virtual root collection. Note that WebDAV collection(s) creation is a\n    vital step; apropriate rights MUST be set before using it with SyncML client;\n    clients can only store items(resources), they can't make sub-folders.\n\t\t\n\n\n    Instructions for setting SyncML server and client\n\n    Create a new folder named '/DAV/sync/' under WebDAV root. This can be done via Conductor UI going to the "Web Application Server" tab and then going to the "Content Management" tab.\n    Create subfolders calendar and contacts under /DAV/sync/\n    Create a new virtual host with virtual root assigned to /DAV/sync/ WebDAV collection. Please reffer to the documentation for more information.\n\n\nNokia 92x0 Communicator\n\n\n    In Extras menu open "Remote sync"\n    In "Profile settings" choose "New Profile"\n    Select apropriate internet access\n    Enter the Virtuso HTTP server address and port values as you created them earlier.\n    Enter username and password for account which have permissions to the\n\t'/DAV/sync/' and descendants.\n    Select tab "Data"\n    Choose Calendar and enter for "Remote calendar" './calendar/'.\n    Choose Contacts and enter for "Remote contacts" './contacts/'.\n    Close the Sync Profile menus, confirm saving\n    Select "Sync" option.\n    Verify that items are uploaded into WebDAV collections: /DAV/sync/calendar/ and /DAV/sync/contacts/. For this  you can use Conductor's WebDAV content management UI\n    Edit some of Contacts/Events on device and perform Sync again. Check the repository as in previous step.\n    Note: Editing the items on the server needs knowlage of VCARD/VCALENDAR formats as they can be edited as text files.\n\n\nSiemens SX1\n\n\nSelect "menu" button\nChoose "Organizer"\nChoose "Sync"\nSelect from menu "Options", "New sync profile"\nGive a meaningful name for this profile in "Sync profile name"\nBearer type: Internet\nAccess point: choose some predefined\nHost address: URL to the SyncML server without HTTP port number\nPort: SyncML HTTP port number\nUser name: username for account which have permissions to the '/DAV/sync/' and descendants.\nPassword: password for the account\nCalendar: Yes\nRemote calendar: ./calendar\nContacts: Yes\nRemote contacts: ./contacts\nHTTP authentication: No\nHTTP user name: blank\nHTTP password: blank\nSelect "Back" from menu\nNew profile should exists. Click on it to perform syncronization.\n\n\nSony Ericsson P900\n\n    From main menu choose "Remote Sync"\n    Via menu "Edit" - "Preferences"\n    Server address: [type URL to the SyncML server]\n    User Name:\n    Password:\n    Press button "Done"\n    Click on "Contacts"\n    Enable task: on\n    Server database: ./contacts\n    Press button "Done"\n    To perform Sync on defined items, press button "Sync"\n\n\nImportant: Internet connection must be alredy defined and must work with\n    device's browser.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Replication Demo between two Datsources (DSNs)" ;
	sioc:content	"\nPreliminaries\nThis sample shows how to replicate two heterogeneous DSNs (MySQL DSN and Microsoft SQL Server DSN for example) with all logic in Virtuoso.\n    The replicated table has two columns. First is varchar Primary key, second integer representing user data.\n\n\n Sample includes: \n\n\n  Select DSN for demo. There must be two connected DSNs to start the sample.\n  Create tables on the two DSNs.\n  Attach tables from these DSNs.\n  Show simple page with table content.\n\n\n How it works: \n\n    The Primary key plus timestamp column from source is replicated locally.\n    On initial state  all date from the first DSN  s copyed to the Second.\n    The user table on the first DSN has one timestamp column more that the table on the second. This column is used to get new / changed rows on replication state.\n\n\n\n    Instructions for setting:\n\n    Click on the \"Set Initial State\" to create virtuoso table.\n    Click on the \"Run\" links to actually experience the demo.\n\n\nImportant: This sample is not thread save.\n\n\n" ;
	sioc:has_container	ns2:repl ;
	sioc:description	"Replication Demo between two Datsources (DSNs)" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nThis sample shows how to replicate two heterogeneous DSNs (MySQL DSN and Microsoft SQL Server DSN for example) with all logic in Virtuoso.\n    The replicated table has two columns. First is varchar Primary key, second integer representing user data.\n\n\n Sample includes: \n\n\n  Select DSN for demo. There must be two connected DSNs to start the sample.\n  Create tables on the two DSNs.\n  Attach tables from these DSNs.\n  Show simple page with table content.\n\n\n How it works: \n\n    The Primary key plus timestamp column from source is replicated locally.\n    On initial state  all date from the first DSN  s copyed to the Second.\n    The user table on the first DSN has one timestamp column more that the table on the second. This column is used to get new / changed rows on replication state.\n\n\n\n    Instructions for setting:\n\n    Click on the "Set Initial State" to create virtuoso table.\n    Click on the "Run" links to actually experience the demo.\n\n\nImportant: This sample is not thread save.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"RDF Views" ;
	sioc:content	"\n    Concept\n    \n      RDF Views map relational data into RDF and allow customizing RDF representation of locally\n      stored RDF data. To let SPARQL clients access relational data as well as physical RDF graphs\n      in a single query, we introduce a declarative Meta Schema Language for mapping SQL Data to\n      RDF Ontologies. As a result, all types of clients can efficiently access all data stored on\n      the server. The mapping functionality dynamically generates RDF Data Sets for popular ontologies\n      such as SIOC, SKOS, FOAF, and ATOM/OWL without disruption to the existing database infrastructure\n      of Web 1.0 or Web 2.0 solutions. RDF views are also suitable for declaring custom representation\n      for RDF triples, e.g. property tables, where one row holds many single-valued properties.\n    \n    \n      The Virtuoso RDF Views meta schema is a built-in feature of Virtuoso's SPARQL to SQL\n      translator. It recognizes triple patterns that refer to graphs for which an alternate\n      representation is declared and translates these into SQL accordingly. The main purpose\n      of this is evaluating SPARQL queries against existing relational databases. There exists\n      previous work from many parties for rendering relational data as RDF and opening it to\n      SPARQL access. We can mention D2RQ, SPASQL, Squirrel RDF, DBLP and others. The Virtuoso\n      effort differs from these mainly in the following:\n    \n    \n      \n        Integration with a triple store. Virtuoso can process a query for which some\n        triple patterns will go to local or remote relational data and some to local physical\n        RDF triples.\n      \n      \n        SPARQL query can be used in any place where SQL can. Database connectivity protocols\n        are neutral to the syntax of queries they transmit, thus any SQL client, e.g. JDBC,\n        ODBC or XMLA application, can send SPARQL queries and fetch result sets. Moreover,\n        a SQL query may contain SPARQL subqueries and SPARQL expressions may use SQL built-in\n        functions and stored procedures.\n      \n      \n        Integration with SQL. Since SPARQL and SQL share the same run time and query optimizer,\n        the query compilation decisions are always made with the best knowledge of the data and\n        its location. This is especially important when mixing triples and relational data or\n        when dealing with relational data distributed across many outside databases.\n      \n      \n        No limits on SPARQL. It remains possible to make queries with unspecified graph or\n        predicate against mapped relational data, even though these may sometimes be inefficient.\n      \n      \n        Coverage of the whole relational model. Multi-part keys etc. are supported in all places.\n      \n    \n  \n    Quad Map Patterns, Value and IRI Classes\n    \n      In the simplest sense, any relational schema can be rendered into RDF by converting all primary\n      keys and foreign keys into IRI's, assigning a predicate IRI to each column, and an rdf:type predicate\n      for each row linking it to a RDF class IRI corresponding to the table. Then a triple with the primary\n      key IRI as subject, the column IRI as predicate and the column's value as object is considered to exist\n      for each column that is neither part of a primary or foreign key.\n    \n    \n      Strictly equating a subject value to a row and each column to a predicate is often good but is too\n      restrictive for the general case.\n    \n    \n      \n        Multiple triples with the same subject and predicate can exist.\n      \n      \n        A single subject can get single-valued properties from multiple tables or in some cases stored procedures.\n      \n      \n        An IRI value of a subject or other field of a triple can be composed from more than one SQL value,\n        these values may reside in different columns, maybe in different joined tables.\n      \n      \n        Some table rows should be excluded from mapping.\n      \n    \n    \n      Thus in the most common case the RDF meta schema should consist of independent transformations; the domain\n      of each transformation is a result-set of some SQL SELECT statement and range is a set of triples. The\n      SELECT that produce the domain is quite simple: it does not use aggregate functions, joins and sorting,\n      only inner joins and WHERE conditions. There is no need to support outer joins in the RDF meta schema\n      because NULLs are usually bad inputs for functions that produce IRIs. In the rare cases when NULLs are\n      OK for functions, outer joins can be encapsulated in SQL views. The range of mapping can be described\n      by a SPARQL triple pattern: a pattern field is a variable if it depends on table columns, otherwise it\n      is a constant. Values of variables in the pattern may have additional restrictions on datatypes, when\n      datatypes of columns are known.\n    \n    \n      This common case of an RDF meta schema is implemented in Virtuoso, with one adjustment. Virtuoso stores\n      quads, not triples, using the graph field (G) to indicate that a triple belongs to some particular\n      application or resource. A SPARQL query may use quads from different graphs without large difference\n      between G and the other three fields of a quad. E.g., variable ?g in expression GRAPH ?g {...} can be\n      unbound. SPARQL has special syntax for \"graph group patterns\" that is convenient for sets of triple\n      patterns with a common graph, but it also has shorthands for common subject and predicate, so the\n      difference is no more than in syntax. There is only one feature that is specific for graphs but not\n      for other fields: the SPARQL compiler can create restrictions on graphs according to FROM and FROM\n      NAMED clauses.\n    \n    \n      Virtuoso RDF Views should offer the same flexibility with the graphs as SPARQL addressing physical triples.\n      A transformation cannot always be identified by the graph used for ranges because graph may be composed\n      from SQL data. The key element of the meta schema is a \"quad map pattern\". A simple quad map pattern fully\n      defines one particular transformation from one set of relational columns into triples that match one SPARQL\n      graph pattern. The main part of quad map pattern is four declarations of \"quad map values\", each declaration\n      specifies how to calculate the value of the corresponding triple field from the SQL data. The pattern also\n      lists boolean SQL expressions that should be used to filter out unwanted rows of source data (and to join\n      multiple tables if source columns belong to different tables). There are also quad map patterns that group\n      together similar quad patterns but do not specify any real transformation or even prevent unwanted\n      transformations from being used, they are described in \"Grouping Map Patterns\" below.\n    \n    \n      Quad map values refer to schema elements of two further types: \"IRI classes\" and \"literal classes\".\n    \n  \n    Implementation\n    \n      In the example script we implement RDF Views for Northwind tables (Customers, Orders, Order Details, Products,\n      Product Categories, Employee, Region, Country, Province).\n    \n    \n      To test the mapper we just use /sparql to execute:\n    \n    \n        sparql select ?o where { graph ?g {?s ?p ?o . filter(?p like '%Country%') }} limit 10;\n    \n    \n      Or use iSparql application.\n    \n  " ;
	sioc:has_container	ns2:rdfview ;
	sioc:description	"Develop custom RDF views for NorthWind database." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Concept\n    \n      RDF Views map relational data into RDF and allow customizing RDF representation of locally\n      stored RDF data. To let SPARQL clients access relational data as well as physical RDF graphs\n      in a single query, we introduce a declarative Meta Schema Language for mapping SQL Data to\n      RDF Ontologies. As a result, all types of clients can efficiently access all data stored on\n      the server. The mapping functionality dynamically generates RDF Data Sets for popular ontologies\n      such as SIOC, SKOS, FOAF, and ATOM/OWL without disruption to the existing database infrastructure\n      of Web 1.0 or Web 2.0 solutions. RDF views are also suitable for declaring custom representation\n      for RDF triples, e.g. property tables, where one row holds many single-valued properties.\n    \n    \n      The Virtuoso RDF Views meta schema is a built-in feature of Virtuoso's SPARQL to SQL\n      translator. It recognizes triple patterns that refer to graphs for which an alternate\n      representation is declared and translates these into SQL accordingly. The main purpose\n      of this is evaluating SPARQL queries against existing relational databases. There exists\n      previous work from many parties for rendering relational data as RDF and opening it to\n      SPARQL access. We can mention D2RQ, SPASQL, Squirrel RDF, DBLP and others. The Virtuoso\n      effort differs from these mainly in the following:\n    \n    \n      \n        Integration with a triple store. Virtuoso can process a query for which some\n        triple patterns will go to local or remote relational data and some to local physical\n        RDF triples.\n      \n      \n        SPARQL query can be used in any place where SQL can. Database connectivity protocols\n        are neutral to the syntax of queries they transmit, thus any SQL client, e.g. JDBC,\n        ODBC or XMLA application, can send SPARQL queries and fetch result sets. Moreover,\n        a SQL query may contain SPARQL subqueries and SPARQL expressions may use SQL built-in\n        functions and stored procedures.\n      \n      \n        Integration with SQL. Since SPARQL and SQL share the same run time and query optimizer,\n        the query compilation decisions are always made with the best knowledge of the data and\n        its location. This is especially important when mixing triples and relational data or\n        when dealing with relational data distributed across many outside databases.\n      \n      \n        No limits on SPARQL. It remains possible to make queries with unspecified graph or\n        predicate against mapped relational data, even though these may sometimes be inefficient.\n      \n      \n        Coverage of the whole relational model. Multi-part keys etc. are supported in all places.\n      \n    \n  \n    Quad Map Patterns, Value and IRI Classes\n    \n      In the simplest sense, any relational schema can be rendered into RDF by converting all primary\n      keys and foreign keys into IRI's, assigning a predicate IRI to each column, and an rdf:type predicate\n      for each row linking it to a RDF class IRI corresponding to the table. Then a triple with the primary\n      key IRI as subject, the column IRI as predicate and the column's value as object is considered to exist\n      for each column that is neither part of a primary or foreign key.\n    \n    \n      Strictly equating a subject value to a row and each column to a predicate is often good but is too\n      restrictive for the general case.\n    \n    \n      \n        Multiple triples with the same subject and predicate can exist.\n      \n      \n        A single subject can get single-valued properties from multiple tables or in some cases stored procedures.\n      \n      \n        An IRI value of a subject or other field of a triple can be composed from more than one SQL value,\n        these values may reside in different columns, maybe in different joined tables.\n      \n      \n        Some table rows should be excluded from mapping.\n      \n    \n    \n      Thus in the most common case the RDF meta schema should consist of independent transformations; the domain\n      of each transformation is a result-set of some SQL SELECT statement and range is a set of triples. The\n      SELECT that produce the domain is quite simple: it does not use aggregate functions, joins and sorting,\n      only inner joins and WHERE conditions. There is no need to support outer joins in the RDF meta schema\n      because NULLs are usually bad inputs for functions that produce IRIs. In the rare cases when NULLs are\n      OK for functions, outer joins can be encapsulated in SQL views. The range of mapping can be described\n      by a SPARQL triple pattern: a pattern field is a variable if it depends on table columns, otherwise it\n      is a constant. Values of variables in the pattern may have additional restrictions on datatypes, when\n      datatypes of columns are known.\n    \n    \n      This common case of an RDF meta schema is implemented in Virtuoso, with one adjustment. Virtuoso stores\n      quads, not triples, using the graph field (G) to indicate that a triple belongs to some particular\n      application or resource. A SPARQL query may use quads from different graphs without large difference\n      between G and the other three fields of a quad. E.g., variable ?g in expression GRAPH ?g {...} can be\n      unbound. SPARQL has special syntax for "graph group patterns" that is convenient for sets of triple\n      patterns with a common graph, but it also has shorthands for common subject and predicate, so the\n      difference is no more than in syntax. There is only one feature that is specific for graphs but not\n      for other fields: the SPARQL compiler can create restrictions on graphs according to FROM and FROM\n      NAMED clauses.\n    \n    \n      Virtuoso RDF Views should offer the same flexibility with the graphs as SPARQL addressing physical triples.\n      A transformation cannot always be identified by the graph used for ranges because graph may be composed\n      from SQL data. The key element of the meta schema is a "quad map pattern". A simple quad map pattern fully\n      defines one particular transformation from one set of relational columns into triples that match one SPARQL\n      graph pattern. The main part of quad map pattern is four declarations of "quad map values", each declaration\n      specifies how to calculate the value of the corresponding triple field from the SQL data. The pattern also\n      lists boolean SQL expressions that should be used to filter out unwanted rows of source data (and to join\n      multiple tables if source columns belong to different tables). There are also quad map patterns that group\n      together similar quad patterns but do not specify any real transformation or even prevent unwanted\n      transformations from being used, they are described in "Grouping Map Patterns" below.\n    \n    \n      Quad map values refer to schema elements of two further types: "IRI classes" and "literal classes".\n    \n  \n    Implementation\n    \n      In the example script we implement RDF Views for Northwind tables (Customers, Orders, Order Details, Products,\n      Product Categories, Employee, Region, Country, Province).\n    \n    \n      To test the mapper we just use /sparql to execute:\n    \n    \n        sparql select ?o where { graph ?g {?s ?p ?o . filter(?p like '%Country%') }} limit 10;\n    \n    \n      Or use iSparql application.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Making an Executable SOAP Directory" ;
	sioc:content	"\nExample\n\n  The SQL script makes a directory in the web server space SOAP capable.\n  The interface page has a test button which sends a SOAP request to the server.\n  The Service for testing will just return its own argument.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  The page shows the command and explains the manual operation for doing this from the admin interface.\n \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Exposing SOAP Endpoints" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The SQL script makes a directory in the web server space SOAP capable.\n  The interface page has a test button which sends a SOAP request to the server.\n  The Service for testing will just return its own argument.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  The page shows the command and explains the manual operation for doing this from the admin interface.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Simple usage of the SOAP service" ;
	sioc:content	"\nExample\n\n  The service function accepts data for entering an order into the demo database.\n  The arguments contain the customer id, item to order and quantity.\n  The response is an element with price and expected delivery date, 10 days forward.\n  The function creates a SOAP exception if the customer is not found in the database.\n  The web page will take the data and call the service on the local server.\n  It will display the in and out going messages, including envelopes.\n \n" ;
	sioc:has_container	ns2:services ,
		ns2:web2 ;
	sioc:description	"Order Entry Service" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The service function accepts data for entering an order into the demo database.\n  The arguments contain the customer id, item to order and quantity.\n  The response is an element with price and expected delivery date, 10 days forward.\n  The function creates a SOAP exception if the customer is not found in the database.\n  The web page will take the data and call the service on the local server.\n  It will display the in and out going messages, including envelopes.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"WSDL description" ;
	sioc:content	"\nExample\n\n  The page shows the automaticaly generated WSDL description of the resources granted to SOAPDEMO user.\n  These descriptions are shown as source, and and also rendered by xslt.\n  The original content of WSDL description can be seen at http://[host:port]/services/services.wsdl\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Generating WSDL descriptions for SOAP Services" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The page shows the automaticaly generated WSDL description of the resources granted to SOAPDEMO user.\n  These descriptions are shown as source, and and also rendered by xslt.\n  The original content of WSDL description can be seen at http://[host:port]/services/services.wsdl\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Data types and SOAP" ;
	sioc:content	"\nExample\n\n  Example has a sample call which passes all supported data types.\n  Composite types e.g. arrays are just repeats of a constant element.\n  The page shows the data going in and out.\n \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Using SQL Data Types in SOAP Services" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  Example has a sample call which passes all supported data types.\n  Composite types e.g. arrays are just repeats of a constant element.\n  The page shows the data going in and out.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & remote data sources" ;
	sioc:content	"\nPreliminaries\n\n  \n  This example demonstrates the processing of a result set obtained from a PL\n  procedure defined on a remote database.\n  \n  The example shows a remote execution of a PL procedure against Microsoft\n  SqlServer and Oracle DBMS.\n  \n  The remote procedure is called via rexecute(). The result set is converted\n  to an XML document by a local PL procedure that can then be called via SOAP.\n  The demo VSP pages offers a form to accept DSN, login info and a search\n  string. A soap_call() is executed with these parameters, and the result is \n  parsed with an XSL-T engine for HTML output. \n  \n\n\nSQLServer Preparation\n\n  \n    Configure this example for SQLServer by loading the ms.sql script\n    using the ISQL tool on behalf of the demo user.\n  \n  \n    Make sure the demo Northwind DB is installed.\n  \n  \n    Create a DSN to the SQLServer DB.\n  \n  \n    Grant rexecute on DSN to the SOAP_SO_S_14 user:\n    GRANT REXECUTE on [SQLServer DSN] to SOAP_SO_S_14;\n  \n\n\nOracle Preparation\n\n  \n    Configure this example for Oracle by loading the ora.sql script\n    using the SQLPLUS tool on behalf of the demo user.\n  \n  \n    Make sure the Oracle demo DB is installed.\n  \n  \n    Create a DSN to the Oracle DB. The driver must be\n    'Microsoft ODBC Driver for Oracle'.\n  \n  \n    Grant rexecute on DSN to the SOAP_SO_S_14 user:\n    GRANT REXECUTE on [Oracle DSN] to SOAP_SO_S_14;\n  \n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Exposing Third-Party SQL Stored Procedures as SOAP Services" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\n\n  \n  This example demonstrates the processing of a result set obtained from a PL\n  procedure defined on a remote database.\n  \n  The example shows a remote execution of a PL procedure against Microsoft\n  SqlServer and Oracle DBMS.\n  \n  The remote procedure is called via rexecute(). The result set is converted\n  to an XML document by a local PL procedure that can then be called via SOAP.\n  The demo VSP pages offers a form to accept DSN, login info and a search\n  string. A soap_call() is executed with these parameters, and the result is \n  parsed with an XSL-T engine for HTML output. \n  \n\n\nSQLServer Preparation\n\n  \n    Configure this example for SQLServer by loading the ms.sql script\n    using the ISQL tool on behalf of the demo user.\n  \n  \n    Make sure the demo Northwind DB is installed.\n  \n  \n    Create a DSN to the SQLServer DB.\n  \n  \n    Grant rexecute on DSN to the SOAP_SO_S_14 user:\n    GRANT REXECUTE on [SQLServer DSN] to SOAP_SO_S_14;\n  \n\n\nOracle Preparation\n\n  \n    Configure this example for Oracle by loading the ora.sql script\n    using the SQLPLUS tool on behalf of the demo user.\n  \n  \n    Make sure the Oracle demo DB is installed.\n  \n  \n    Create a DSN to the Oracle DB. The driver must be\n    'Microsoft ODBC Driver for Oracle'.\n  \n  \n    Grant rexecute on DSN to the SOAP_SO_S_14 user:\n    GRANT REXECUTE on [Oracle DSN] to SOAP_SO_S_14;\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample overview\nThis example demonstrates:\n\n  \n  The use of raw TCP session operations: ses_connect(), ses_disconnect(), ses_read_line(), ses_write().\n  \n  A SOAP call.\n  \n  \n  Using the SMTP protocol for email verification.\n  \n  \n  Processing the results with an XSL-T engine.\n  \n\n\nExample Setup\nThe service is prepared by loading the SQL file.\nThis performs the following:\n\n  \n  Define a stored procedure for the SOAP service that opens a TCP session,\n  and makes a SMTP exchange without sending a mail body to the server.\n  Read responses from the server and makes an XML document.\n  \n  \n  The SOAP service is achieved by defining the /email_service URL to\n  have same functionality as using soap_server() function call.\n  \n\n" ;
	sioc:has_container	ns2:services ,
		ns2:web2 ;
	sioc:description	"Email Address Validation Service" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample overview\nThis example demonstrates:\n\n  \n  The use of raw TCP session operations: ses_connect(), ses_disconnect(), ses_read_line(), ses_write().\n  \n  A SOAP call.\n  \n  \n  Using the SMTP protocol for email verification.\n  \n  \n  Processing the results with an XSL-T engine.\n  \n\n\nExample Setup\nThe service is prepared by loading the SQL file.\nThis performs the following:\n\n  \n  Define a stored procedure for the SOAP service that opens a TCP session,\n  and makes a SMTP exchange without sending a mail body to the server.\n  Read responses from the server and makes an XML document.\n  \n  \n  The SOAP service is achieved by defining the /email_service URL to\n  have same functionality as using soap_server() function call.\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP Interoperability Test Round III" ;
	sioc:content	"\nExample\n\n  This example uses the Virtuoso SOAP client for testing a SOAP interop III endpoints.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  The index page shows operations defined for SOAP Interop Round III tests.\n  The second level pages are SOAP clients defined to perform apropriate SOAP call.\n  The VSP based clients make a specific form for entering the input data and selecting a endpoint to test.\n  Once call is made (invoked with Call button), the results will be extracted from SOAP response and will be shown.\n  Also the request and response wire dumps will be shown for debugging purposes.\n \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"SOAP Interoperability Test Page" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example uses the Virtuoso SOAP client for testing a SOAP interop III endpoints.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  The index page shows operations defined for SOAP Interop Round III tests.\n  The second level pages are SOAP clients defined to perform apropriate SOAP call.\n  The VSP based clients make a specific form for entering the input data and selecting a endpoint to test.\n  Once call is made (invoked with Call button), the results will be extracted from SOAP response and will be shown.\n  Also the request and response wire dumps will be shown for debugging purposes.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\nPreliminaries\n\n  \n  This example demonstrates the ability to access the SOAP API provided by\n  Google.\n  \n  The Google API has three services:\n\t\n\t  Search for text on the web.\n\t  Check details of a page cached by Google.\n\t  Find correct spelling for a partial word.\n\t\n  \n  \n  The service requests may be configured in various ways by the parameters\n  supplied to the API.\n  \n\n\nGoogle Registration\n\n  Google API home page\n  http://www.google.com/apis/\n  has details about the services offered by Google.\n  You must register with Google to be authorized to use the API.\n  You can sign up for a new account from the Google API home page.\n  Verify your email address by accessing a page, as indicated in the\n  email sent by Google.\n  Collect the license key in a subsequent email from Google.\n\n\nSearch Demo\n\n  Enter the registration key for your personal Google account.\n  The key is stored in a browser cookie, and is loaded when the tutorial\n  is run again.\n  \n  Check the box if you wish to view the result as raw XML format.\n  \n  \n  Enter some text to be searched, and press the search button.\n  The raw XML result shows the overview of the search results.\n  If XML view is not checked, then only the number of pages found is shown.\n  \n  \n  Enter a url of a page that is likely to be cached by Google.\n  Then press the button to get the details of this page.\n  The raw XML result will contain the page typically encoded in Base64.\n  If XML view is not checked, then only the size of the page is shown.\n  \n  \n  Enter one or more words to have the spelling verified. A partial word is\n  possible. Then press the button to verify the spelling.\n  The raw XML result shows the suggested spelling.\n  If XML view is not checked, then only the suggested spelling is shown.\n  \n\n" ;
	sioc:has_container	ns2:services ,
		ns2:web2 ;
	sioc:description	"Google API demo" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\n\n  \n  This example demonstrates the ability to access the SOAP API provided by\n  Google.\n  \n  The Google API has three services:\n\t\n\t  Search for text on the web.\n\t  Check details of a page cached by Google.\n\t  Find correct spelling for a partial word.\n\t\n  \n  \n  The service requests may be configured in various ways by the parameters\n  supplied to the API.\n  \n\n\nGoogle Registration\n\n  Google API home page\n  http://www.google.com/apis/\n  has details about the services offered by Google.\n  You must register with Google to be authorized to use the API.\n  You can sign up for a new account from the Google API home page.\n  Verify your email address by accessing a page, as indicated in the\n  email sent by Google.\n  Collect the license key in a subsequent email from Google.\n\n\nSearch Demo\n\n  Enter the registration key for your personal Google account.\n  The key is stored in a browser cookie, and is loaded when the tutorial\n  is run again.\n  \n  Check the box if you wish to view the result as raw XML format.\n  \n  \n  Enter some text to be searched, and press the search button.\n  The raw XML result shows the overview of the search results.\n  If XML view is not checked, then only the number of pages found is shown.\n  \n  \n  Enter a url of a page that is likely to be cached by Google.\n  Then press the button to get the details of this page.\n  The raw XML result will contain the page typically encoded in Base64.\n  If XML view is not checked, then only the size of the page is shown.\n  \n  \n  Enter one or more words to have the spelling verified. A partial word is\n  possible. Then press the button to verify the spelling.\n  The raw XML result shows the suggested spelling.\n  If XML view is not checked, then only the suggested spelling is shown.\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Publishing C function as SOAP service" ;
	sioc:content	"\nExample\n\n  The Virtuoso distribution includes the sample bif, bif_sample.c. It is thus possible to create following function and make server including it.\n  The next step is creating a stored procedure that calls this function and you are back to publishing a Virtuoso stored procedure.\n  The Service for testing will just return string \"Hello world\".\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n \n  \n   static caddr_t\n   bif_hello_world (caddr_t * qst, caddr_t * err_ret, state_slot_t ** args)\n     {\n       return box_dv_short_string (\"Hello world.\");\n     }\n  \n  IMPORTANT: You need to start the sample server containing bif_hello_world , in order run this example.\n  \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Publishing C/C++ functions as Web Services" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The Virtuoso distribution includes the sample bif, bif_sample.c. It is thus possible to create following function and make server including it.\n  The next step is creating a stored procedure that calls this function and you are back to publishing a Virtuoso stored procedure.\n  The Service for testing will just return string "Hello world".\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n \n  \n   static caddr_t\n   bif_hello_world (caddr_t * qst, caddr_t * err_ret, state_slot_t ** args)\n     {\n       return box_dv_short_string ("Hello world.");\n     }\n  \n  IMPORTANT: You need to start the sample server containing bif_hello_world , in order run this example.\n  \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Publishing Java class as SOAP service" ;
	sioc:content	"\nExample\n\n  This example demonstrates how to call Java VM methods from\n  Virtuoso/PL and expose them as SOAP services.\n  It's based on the java class demo_server.java.\n  Also provided is a demonstration of how the JAVA Reflect API\n  can be used to automatically generate PL wrappers.\n  Click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n\n\nSource code detail\n\n  javavm_xml.pl - This file contains a Virtuoso/PL procedure which\n  produces a XML description of the java classes.\n  jvm_ref_describe_class (in class_name varchar,\n\tin inherited integer := 0)\n  First argument is the absolute JAVA class name (example: java_server\n  or java.util.Calendar).\n  Second argument controls whether to create entries for the inherited\n  constructors/ methods/ attributes of the class, or only for the ones\n  defined in it (java.lang.Class.getDeclaredMethods() vs.\n  java.lang.Class.getMethods()).\n  \n  javavm_pl.xsl - Is an XSLT stylesheet that produces the\n  Virtuoso/PL wrappers based on the XML file from jvm_ref_describe_class.\n  The stylesheet has a parameter \"module\" = \"1\" | \"0\" (default \"1\") which\n  controls whether it to generate code for a Virtuoso/PL module, or a set of\n  procedures.\n  For each field it generates Get../Set.. methods (or only Get.. if the\n  field is read-only).\n  It also generates wrappers for each class method.\n  For the non-static fields/methods it instantiates a java object\n  every time the method is invoked.\n  \n  java_pl_wrapper.sql - This file is generated using the above files\n  and then the java_properties procedure is added.\n\n\n    Important: This demo needs Virtuoso server with Java hosting option. \n    Otherwise demo will not run properly.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Publishing Java classes as Web Services" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example demonstrates how to call Java VM methods from\n  Virtuoso/PL and expose them as SOAP services.\n  It's based on the java class demo_server.java.\n  Also provided is a demonstration of how the JAVA Reflect API\n  can be used to automatically generate PL wrappers.\n  Click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n\n\nSource code detail\n\n  javavm_xml.pl - This file contains a Virtuoso/PL procedure which\n  produces a XML description of the java classes.\n  jvm_ref_describe_class (in class_name varchar,\n\tin inherited integer := 0)\n  First argument is the absolute JAVA class name (example: java_server\n  or java.util.Calendar).\n  Second argument controls whether to create entries for the inherited\n  constructors/ methods/ attributes of the class, or only for the ones\n  defined in it (java.lang.Class.getDeclaredMethods() vs.\n  java.lang.Class.getMethods()).\n  \n  javavm_pl.xsl - Is an XSLT stylesheet that produces the\n  Virtuoso/PL wrappers based on the XML file from jvm_ref_describe_class.\n  The stylesheet has a parameter "module" = "1" | "0" (default "1") which\n  controls whether it to generate code for a Virtuoso/PL module, or a set of\n  procedures.\n  For each field it generates Get../Set.. methods (or only Get.. if the\n  field is read-only).\n  It also generates wrappers for each class method.\n  For the non-static fields/methods it instantiates a java object\n  every time the method is invoked.\n  \n  java_pl_wrapper.sql - This file is generated using the above files\n  and then the java_properties procedure is added.\n\n\n    Important: This demo needs Virtuoso server with Java hosting option. \n    Otherwise demo will not run properly.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\nPreliminaries\n\n  \n  The online retailer\n  Amazon.com has provided\n  developers with an interface, that will allow them to do\n  product searches based on a keyword, and a base category.\n  The API is used either by a SOAP call or by a fetch of a\n  XML document.\n  Amazon.com \nsuggests you to download the developer kit. However this is optional, as it is \nnot necessary to run the following OpenLink tutorial.\n  A developer key is required to access the service.\n  One may be applied for at the\n  \n  Amazon.Com Web API page.\n  \n  The service requests may be configured in various ways by the parameters\n  supplied to the API.\n  \n\n\nExample Product search using SOAP API\n\n  In the SQL setup file, the SOAP call is prepared by the\n  function call to soap_wsdl_import() which reads in the web service\n  \".wsdl\" file from Amazon.com.\n  \n  Enter the Developer Key, result type, root node for the search, and the\n  keyword to be searched for.\n  \n  Hit the search button to get the products matching the keyword.\n  This example uses the \"heavy\" mode of results, that contains the\n  full customer reviews.\n  A local stylesheet is applied to the result for either an\n  XML or HTML view.\n\n" ;
	sioc:has_container	ns2:web2 ,
		ns2:services ;
	sioc:description	"Amazon API demo" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\n\n  \n  The online retailer\n  Amazon.com has provided\n  developers with an interface, that will allow them to do\n  product searches based on a keyword, and a base category.\n  The API is used either by a SOAP call or by a fetch of a\n  XML document.\n  Amazon.com \nsuggests you to download the developer kit. However this is optional, as it is \nnot necessary to run the following OpenLink tutorial.\n  A developer key is required to access the service.\n  One may be applied for at the\n  \n  Amazon.Com Web API page.\n  \n  The service requests may be configured in various ways by the parameters\n  supplied to the API.\n  \n\n\nExample Product search using SOAP API\n\n  In the SQL setup file, the SOAP call is prepared by the\n  function call to soap_wsdl_import() which reads in the web service\n  ".wsdl" file from Amazon.com.\n  \n  Enter the Developer Key, result type, root node for the search, and the\n  keyword to be searched for.\n  \n  Hit the search button to get the products matching the keyword.\n  This example uses the "heavy" mode of results, that contains the\n  full customer reviews.\n  A local stylesheet is applied to the result for either an\n  XML or HTML view.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP Interoperability Test Round IV" ;
	sioc:content	"\nExample\n\n  This example uses the Virtuoso SOAP client for testing a SOAP interop IV endpoints.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  This page shows operations defined for SOAP Interop Round IV tests, grouped by encoding and test group name.\n  The demo pages are SOAP clients defined to perform appropriate SOAP call.\n  The VSP based clients make a specific form for entering the input data and selecting an endpoint to test.\n  Once call is made (invoked with Call button), the results will be extracted from SOAP response and shown.\n  Also the request and response wire dumps will be shown for debugging purposes.\n \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"SOAP Interoperability Test Page" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example uses the Virtuoso SOAP client for testing a SOAP interop IV endpoints.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  This page shows operations defined for SOAP Interop Round IV tests, grouped by encoding and test group name.\n  The demo pages are SOAP clients defined to perform appropriate SOAP call.\n  The VSP based clients make a specific form for entering the input data and selecting an endpoint to test.\n  Once call is made (invoked with Call button), the results will be extracted from SOAP response and shown.\n  Also the request and response wire dumps will be shown for debugging purposes.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\n    Example\n    \n      The setup_sms.vspx sets up the SMS sending unit.\n      The handler.vspx does inserts/deletes/updates to demonstrate the SMS sending from triggers.\n      For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n     \n    " ;
	sioc:has_container	ns2:services ;
	sioc:description	"Sending a SMS" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Example\n    \n      The setup_sms.vspx sets up the SMS sending unit.\n      The handler.vspx does inserts/deletes/updates to demonstrate the SMS sending from triggers.\n      For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n     \n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\nOverview\n\n  This example demonstrates how to use Yahoo GeoCode API as a local SOAP service.  \n  For more information on Yahoo GoeCode API visit: \n  http://developer.yahoo.net/maps/rest/V1/geocode.html\n  \n\n  Breakdown\n  \n  In the initial state we create a simple procedure that: \n    \n      takes input parameters as described by Yahoo GoeCode API page. \n      Generates URL and calls it.\n      returns the XML result formated throught raw.xsl.\n    \n  \n  Create SOAP_SO_S_27 user and grant the procedure to it.\n  \n  The SOAP service is achieved by defining the /SOAP_SO_S_27 URL to\n  have same functionality as using soap_server() function call.\n  \n  \n  The client uses AJAX to call the service and show the result.\n  \n  \n" ;
	sioc:has_container	ns2:services ,
		ns2:web2 ;
	sioc:description	"Yahoo GeoCode API demo" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nOverview\n\n  This example demonstrates how to use Yahoo GeoCode API as a local SOAP service.  \n  For more information on Yahoo GoeCode API visit: \n  http://developer.yahoo.net/maps/rest/V1/geocode.html\n  \n\n  Breakdown\n  \n  In the initial state we create a simple procedure that: \n    \n      takes input parameters as described by Yahoo GoeCode API page. \n      Generates URL and calls it.\n      returns the XML result formated throught raw.xsl.\n    \n  \n  Create SOAP_SO_S_27 user and grant the procedure to it.\n  \n  The SOAP service is achieved by defining the /SOAP_SO_S_27 URL to\n  have same functionality as using soap_server() function call.\n  \n  \n  The client uses AJAX to call the service and show the result.\n  \n  \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\nOverview\n\n  This example demonstrates how to implement Google Maps API using XML and Asynchronous RPC (\"AJAX\").\n  For more information on Google Maps API visit: \n  http://www.google.com/apis/maps/documentation/\n  \n\n  Breakdown\n  In the Initial state we will extend the Demo.demo.Customers \n  table with some new fields (Longitude and Latitude). Then we will use \n  Yahoo GeoCode API to find Longitude, Latitude values for the customers addresses \n  and store the values in the database. The data_xml.vsp page generates \n  XML from that table similar to the one described in \n  Google Maps API Documentation. \n  We have extend it a little bit to have information for the Customer Name and Address.\n  Click on the 'googlemaps.vsp' Run link to see the generated Google Map. You can click on the markers to \n  view additional information.\n  \n" ;
	sioc:has_container	ns2:web2 ,
		ns2:services ;
	sioc:description	"Google Maps API demo" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nOverview\n\n  This example demonstrates how to implement Google Maps API using XML and Asynchronous RPC ("AJAX").\n  For more information on Google Maps API visit: \n  http://www.google.com/apis/maps/documentation/\n  \n\n  Breakdown\n  In the Initial state we will extend the Demo.demo.Customers \n  table with some new fields (Longitude and Latitude). Then we will use \n  Yahoo GeoCode API to find Longitude, Latitude values for the customers addresses \n  and store the values in the database. The data_xml.vsp page generates \n  XML from that table similar to the one described in \n  Google Maps API Documentation. \n  We have extend it a little bit to have information for the Customer Name and Address.\n  Click on the 'googlemaps.vsp' Run link to see the generated Google Map. You can click on the markers to \n  view additional information.\n  \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\nOverview\n\n  This example demonstrates how to implement Yahoo Maps API Generated Rss feed.\n  For more information on Yahoo Maps API visit: \n  http://developer.yahoo.net/maps/simple/index.html\n  \n\n  Breakdown\n  Yahoo Maps API can get map information using data formatted in Web-standard RSS format. \n  We show in 'yahoomaps.vsp' how you can easily generated the feed to be posted to yahoo using just \n  one SQL statement with xml_auto function. For more information on xml_auto refer to the documentation.\n  \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Yahoo Maps API demo" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nOverview\n\n  This example demonstrates how to implement Yahoo Maps API Generated Rss feed.\n  For more information on Yahoo Maps API visit: \n  http://developer.yahoo.net/maps/simple/index.html\n  \n\n  Breakdown\n  Yahoo Maps API can get map information using data formatted in Web-standard RSS format. \n  We show in 'yahoomaps.vsp' how you can easily generated the feed to be posted to yahoo using just \n  one SQL statement with xml_auto function. For more information on xml_auto refer to the documentation.\n  \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Research Service for the Microsoft Office 2003" ;
	sioc:content	"\n\n    Overview\n\n    Microsoft Office 2003 provides a new tool called \"The Research Library\", which\n    is available from the task pane in all of the Microsoft Office Suite including\n    Microsoft Office Excel 2003, Microsoft Office PowerPoint 2003, Microsoft Office\n    Word 2003, and Microsoft Office Outlook 2003.\n\nBy default, the Research Library allows to search for terms using several\n    built-in resources. The Research Library is also extensible: users can add their\n    own research service by creating a Web service that follows schemas defined for\n    Microsoft research services. \n\nPrerequisites\n\nThe following prerequisites are needed to ensure that you can experience this\n    demonstration.\n\n\n    Virtuoso 3.5 or above\n    Microsoft Office 2003 or higher \n\n\nTutorial Example\n\nThe following demonstration creates a service which exposes two methods:\n    \"Registration\" and \"Query\". \n\nThe first method allows Microsoft Office to discover the Query service; also it\n    could be extended to log the registration info for specific application\n    purposes. The \"Query\" service is used to make a Free-text search within WebDAV\n    repository by a given set of keywords entered by user in task panel. \n    The demo script also creates a virtual directory which forces \n    \"Document/Literal\" encoding of SOAP messages, which  is another way to expose\n    Virtuoso PL stored procedures without having special SOAP user-defined data-types. \n\nPlease follow the steps below to maximize the value of this tutorial: \n\nStep 1: Run the following sql script to set up so_s_34.sql.  \n\nStep 2: After executing the initial setup above, add the service using a\n    \"Research\" task pane by selecting \"Research Options\" and then \"Add Services\".  \n    Note: To access this Research Task pane, select Research from the Tools menu, or\n    by pressing Ctrl+F1 and choosing Research from the Other Task Panes drop-down list.\n\nStep 3:  In the presented text entry for the Address , type the URL to the demo\n    service http://host:port/VRes/ and press \"Add\", then \"Continue\" and finally\n    \"Install\" (in that step \"Virtuoso FTi Search (PL)\" should be displayed). \n    Once you have installed the demo service, you can query it with typing search\n    keywords in \"Search for\" text entry and selecting the \"Virtuoso FTi Search (PL)\"\n    from drop-down box. On success a list of top 10 public readable items from\n    WebDAV matching the \"AND\" of keywords will be displayed. \n\nAdditional Information:\n\nFor More details regarding the Microsoft Research Library for Microsoft Office\n    2003 see\n    http://www.microsoft.com/office/editions/prodinfo/technologies/research.mspx\n\nFor More details regarding WebDAV see \n    http://docs.openlinksw.com/virtuoso/qswebdav.html#qswebdav\n\nFor More details regarding Free-Text Search see\n    http://docs.openlinksw.com/virtuoso/freetext.html#freetext\n\n\n\n\n\n    \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Creating Research Service for the Microsoft Office 2003 Research Library" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n\n    Overview\n\n    Microsoft Office 2003 provides a new tool called "The Research Library", which\n    is available from the task pane in all of the Microsoft Office Suite including\n    Microsoft Office Excel 2003, Microsoft Office PowerPoint 2003, Microsoft Office\n    Word 2003, and Microsoft Office Outlook 2003.\n\nBy default, the Research Library allows to search for terms using several\n    built-in resources. The Research Library is also extensible: users can add their\n    own research service by creating a Web service that follows schemas defined for\n    Microsoft research services. \n\nPrerequisites\n\nThe following prerequisites are needed to ensure that you can experience this\n    demonstration.\n\n\n    Virtuoso 3.5 or above\n    Microsoft Office 2003 or higher \n\n\nTutorial Example\n\nThe following demonstration creates a service which exposes two methods:\n    "Registration" and "Query". \n\nThe first method allows Microsoft Office to discover the Query service; also it\n    could be extended to log the registration info for specific application\n    purposes. The "Query" service is used to make a Free-text search within WebDAV\n    repository by a given set of keywords entered by user in task panel. \n    The demo script also creates a virtual directory which forces \n    "Document/Literal" encoding of SOAP messages, which  is another way to expose\n    Virtuoso PL stored procedures without having special SOAP user-defined data-types. \n\nPlease follow the steps below to maximize the value of this tutorial: \n\nStep 1: Run the following sql script to set up so_s_34.sql.  \n\nStep 2: After executing the initial setup above, add the service using a\n    "Research" task pane by selecting "Research Options" and then "Add Services".  \n    Note: To access this Research Task pane, select Research from the Tools menu, or\n    by pressing Ctrl+F1 and choosing Research from the Other Task Panes drop-down list.\n\nStep 3:  In the presented text entry for the Address , type the URL to the demo\n    service http://host:port/VRes/ and press "Add", then "Continue" and finally\n    "Install" (in that step "Virtuoso FTi Search (PL)" should be displayed). \n    Once you have installed the demo service, you can query it with typing search\n    keywords in "Search for" text entry and selecting the "Virtuoso FTi Search (PL)"\n    from drop-down box. On success a list of top 10 public readable items from\n    WebDAV matching the "AND" of keywords will be displayed. \n\nAdditional Information:\n\nFor More details regarding the Microsoft Research Library for Microsoft Office\n    2003 see\n    http://www.microsoft.com/office/editions/prodinfo/technologies/research.mspx\n\nFor More details regarding WebDAV see \n    http://docs.openlinksw.com/virtuoso/qswebdav.html#qswebdav\n\nFor More details regarding Free-Text Search see\n    http://docs.openlinksw.com/virtuoso/freetext.html#freetext\n\n\n\n\n\n    \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Route Planner Demo" ;
	sioc:content	"\n    Example\n\n    There are several mapping services available today, but they only provide point\n\tto point services. \n\n    \n    Once such service is from Microsoft, which has a SOAP-based MapPoint service\n    that allows location searching and distance calculations.   The following\n    demonstration uses the Microsoft MapPoint services to resolve addresses and to\n    calculate the distance between two points.   The demonstration will also\n    calculate an optimized round-trip from a given start point to the destinations\n    specified. \n\n\n    In order to run the demonstration a MapPoint username and password are needed. \n    Evaluation accounts from Microsoft are available \n\there.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Using a MS MapPoint service for route planning" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Example\n\n    There are several mapping services available today, but they only provide point\n\tto point services. \n\n    \n    Once such service is from Microsoft, which has a SOAP-based MapPoint service\n    that allows location searching and distance calculations.   The following\n    demonstration uses the Microsoft MapPoint services to resolve addresses and to\n    calculate the distance between two points.   The demonstration will also\n    calculate an optimized round-trip from a given start point to the destinations\n    specified. \n\n\n    In order to run the demonstration a MapPoint username and password are needed. \n    Evaluation accounts from Microsoft are available \n\there.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"eBay API demo" ;
	sioc:content	"\n    Example\n\n    \n\tThis example uses eBay SOAP API to perform browsing of categories \n\ton eBay sandbox site. \n    \n    \n    \n\tThe demo uses WSDL_IMPORT_UDT() function to define SOAP proxy class \n\tfor invocation of the eBay API. This will be done upon initial setup of the demo. \n\tThe source code for imported UDT for SOAP proxy could be read via eBay.sql \n\tsource file below.\n\tAlso it defines a procedure for \"getCategories\" method invocation \n\tand it's used further in functions for vspx tree control to instantiate \n\tthe nodes.\n    \n\n    \n\tTo run the demo you will need to obtain a three developer keys : ApiId, DevId & CertificateId.\n        Further a demo user on ebay sandbox site needs to be created and it's credentials must be used for\n        to make API calls. To obtain developer keys please visit the  \t\n\teBay developer zone and follow the instructions. \n\tOnce you have registered for eBay developer program and have the Api, Dev & Certificate IDs, go to \"getting setup on sandbox\" and follow the instructions to make a test user. \n    \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Using a eBay SOAP API" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Example\n\n    \n\tThis example uses eBay SOAP API to perform browsing of categories \n\ton eBay sandbox site. \n    \n    \n    \n\tThe demo uses WSDL_IMPORT_UDT() function to define SOAP proxy class \n\tfor invocation of the eBay API. This will be done upon initial setup of the demo. \n\tThe source code for imported UDT for SOAP proxy could be read via eBay.sql \n\tsource file below.\n\tAlso it defines a procedure for "getCategories" method invocation \n\tand it's used further in functions for vspx tree control to instantiate \n\tthe nodes.\n    \n\n    \n\tTo run the demo you will need to obtain a three developer keys : ApiId, DevId & CertificateId.\n        Further a demo user on ebay sandbox site needs to be created and it's credentials must be used for\n        to make API calls. To obtain developer keys please visit the  \t\n\teBay developer zone and follow the instructions. \n\tOnce you have registered for eBay developer program and have the Api, Dev & Certificate IDs, go to "getting setup on sandbox" and follow the instructions to make a test user. \n    \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Northwind query via SOAP" ;
	sioc:content	"\n      Preliminaries\n      The SOAP messages are XML documents which may follow \n\t  encoding rules or an XML Schema. The ones that follow encoding rules \n\t  are known as RPC encoded, so the \n\t  XML Schema following messages are known as Document/literal encoded. \n\t  Most of SOAP toolkits can work with both kind of messages, but for some purposes \n\t  RPC encoded messages are not suitable. \n      \n      The MS Office Infopath supports only document/literal encoded SOAP \n\t  messages. So to inter operate with it, Web services have to be set to define \n\t  document/literal SOAP messages and generate appropriate WSDL file.\n      The Virtuoso can expose a services that using document/literal encoding by two ways:\n      \n\t  explicit declarations in stored procedure's definition\n\t  default SOAP encoding as an option of the SOAP enabled virtual directory\n      \n      \n\t  The first approach imply that procedure can be used only in the designated \n\t  encoding style. So the second is more flexabile as it can switch very easy \n\t  between encodings without procedure's re-definition.   \n      \n      \n\t  To allow a stored procedure to be exposed in a virtual directory \n\t  that default SOAP encoding as a document/literal it should not use \n\t  explicit declarations. This is because explicit declarations are not \n\t  compatible in all cases. Instead of explicit declarations a user defined types \n\t  must be used to describe the structures and array modifier have to be used to \n\t  describe array parameters. \n      \n  \n      Example\n      The example script defines a service that do a query on Northwind Demo Database \n      and return an array of structures containing sales volume per product category.\n  To run example, set the initial state and then click on the Run link or point\n  \tyour browser to http://[host]:[port]/NorthwindSvc/services.vsmx \n  \tto go to vsmx test pages.\n  \n      Note: the dateinput must follow ISO8601 format (for example: YYYY-MM-DD'T'HH:MM:SS) \n  \n  " ;
	sioc:has_container	ns2:services ;
	sioc:description	"Building a document style oriented Web services" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n      Preliminaries\n      The SOAP messages are XML documents which may follow \n\t  encoding rules or an XML Schema. The ones that follow encoding rules \n\t  are known as RPC encoded, so the \n\t  XML Schema following messages are known as Document/literal encoded. \n\t  Most of SOAP toolkits can work with both kind of messages, but for some purposes \n\t  RPC encoded messages are not suitable. \n      \n      The MS Office Infopath supports only document/literal encoded SOAP \n\t  messages. So to inter operate with it, Web services have to be set to define \n\t  document/literal SOAP messages and generate appropriate WSDL file.\n      The Virtuoso can expose a services that using document/literal encoding by two ways:\n      \n\t  explicit declarations in stored procedure's definition\n\t  default SOAP encoding as an option of the SOAP enabled virtual directory\n      \n      \n\t  The first approach imply that procedure can be used only in the designated \n\t  encoding style. So the second is more flexabile as it can switch very easy \n\t  between encodings without procedure's re-definition.   \n      \n      \n\t  To allow a stored procedure to be exposed in a virtual directory \n\t  that default SOAP encoding as a document/literal it should not use \n\t  explicit declarations. This is because explicit declarations are not \n\t  compatible in all cases. Instead of explicit declarations a user defined types \n\t  must be used to describe the structures and array modifier have to be used to \n\t  describe array parameters. \n      \n  \n      Example\n      The example script defines a service that do a query on Northwind Demo Database \n      and return an array of structures containing sales volume per product category.\n  To run example, set the initial state and then click on the Run link or point\n  \tyour browser to http://[host]:[port]/NorthwindSvc/services.vsmx \n  \tto go to vsmx test pages.\n  \n      Note: the dateinput must follow ISO8601 format (for example: YYYY-MM-DD'T'HH:MM:SS) \n  \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Serializing Java classes as SOAP structures" ;
	sioc:content	"\n  Example\n  \n    To test the service click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n  \n  \n  \n    This example demonstrates how to use Java user defined types for SOAP datatype mappings.\n    It's based on the java class so_s_30.java.\n  \n  \n    It demontsrates the two approaches in using the user defined types for SOAP structure mappings :\n  \n  \n    Attach a user defined type to a predefined schema instance (user defined type SO_S_30). \n    Generate the WSDL based on the user defined type's definition (user defined type SO_S_30_2).\n  \n  \n    In order that to be runnable the so_s_30.java should be compiled to so_s_30.class with the \n    java compiler and so_s_30.class be present in the server's CLASSPATH.\n  \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Serializing Java classes as SOAP structures" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n  Example\n  \n    To test the service click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n  \n  \n  \n    This example demonstrates how to use Java user defined types for SOAP datatype mappings.\n    It's based on the java class so_s_30.java.\n  \n  \n    It demontsrates the two approaches in using the user defined types for SOAP structure mappings :\n  \n  \n    Attach a user defined type to a predefined schema instance (user defined type SO_S_30). \n    Generate the WSDL based on the user defined type's definition (user defined type SO_S_30_2).\n  \n  \n    In order that to be runnable the so_s_30.java should be compiled to so_s_30.class with the \n    java compiler and so_s_30.class be present in the server's CLASSPATH.\n  \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Serializing SQL native classes as SOAP structures" ;
	sioc:content	"\n  Example\n  \n    To test the service click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n  \n  \n  \n    This example demonstrates how to use SQL user defined types for SOAP datatype mappings.\n  \n  \n    It demontsrates the two approaches in using the user defined types for SOAP structure mappings :\n  \n  \n    \n      Attach a user defined type to a predefined schema instance (user defined type SO_S_30).\n    \n    \n      Generate the WSDL based on the user defined type's definition (user defined type SO_S_30_2).\n    \n  \n  \n    The example uses the implicit constructor for SQL native types (based on the default values).\n  \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Serializing SQL native classes as SOAP structures" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n  Example\n  \n    To test the service click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n  \n  \n  \n    This example demonstrates how to use SQL user defined types for SOAP datatype mappings.\n  \n  \n    It demontsrates the two approaches in using the user defined types for SOAP structure mappings :\n  \n  \n    \n      Attach a user defined type to a predefined schema instance (user defined type SO_S_30).\n    \n    \n      Generate the WSDL based on the user defined type's definition (user defined type SO_S_30_2).\n    \n  \n  \n    The example uses the implicit constructor for SQL native types (based on the default values).\n  \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Serializing CLR classes as SOAP structures" ;
	sioc:content	"\n  Example\n  \n    To test the service click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n  \n  \n  \n    This example demonstrates how to use CLR user defined types for SOAP datatype mappings.\n    It's based on the CLR class so_s_32.cs.\n  \n  \n    It demontsrates the two approaches in using the user defined types for SOAP structure mappings :\n  \n  \n    \n      Attach a user defined type to a predefined schema instance (user defined type SO_S_30).\n    \n    \n      Generate the WSDL based on the user defined type's definition (user defined type SO_S_30_2).\n    \n  \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Serializing CLR classes as SOAP structures" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n  Example\n  \n    To test the service click on the Run link or point your browser to:\n  http://[host]:[port]/services/services.vsmx\n  \n  \n  \n    This example demonstrates how to use CLR user defined types for SOAP datatype mappings.\n    It's based on the CLR class so_s_32.cs.\n  \n  \n    It demontsrates the two approaches in using the user defined types for SOAP structure mappings :\n  \n  \n    \n      Attach a user defined type to a predefined schema instance (user defined type SO_S_30).\n    \n    \n      Generate the WSDL based on the user defined type's definition (user defined type SO_S_30_2).\n    \n  \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\n    Example\n    \n      The redcoal.sql is a script which implements SOAP proxy wrapper for sending SMS messages.\n      The SOAP proxy wrapper is encapsulated in a User Defined Type\n      The sms.vsp is web interface to the SMS sending unit.\n      For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n     \n    " ;
	sioc:has_container	ns2:services ;
	sioc:description	"Sending a SMS using a SOAP and User Defined Type" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Example\n    \n      The redcoal.sql is a script which implements SOAP proxy wrapper for sending SMS messages.\n      The SOAP proxy wrapper is encapsulated in a User Defined Type\n      The sms.vsp is web interface to the SMS sending unit.\n      For details of the Redcoal SOAP service see it's description in http://www.xmethods.com\n     \n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Collaboration with other clients" ;
	sioc:content	"\nVB.NET\nVirtuoso is able to interact with the Microsoft .NET by providing a\nWSDL description of all the stored procedures exposed as a SOAP operation\nwithin a given virtual directory. The WSDL description is an XML document\navailable at http:///SOAP/services.wsdl\non any Virtuoso HTTP server.\n\n\nThis allows for easy creation of .NET clients.\n\n\n\nfishselect example\n\nThe following .NET VBA routine calls the fishselect stored procedure, and prints the results\non the console.\n\n\n\nOpen a new VB.NET project for Console Application.\n\nAdd a web reference to the Virtuoso WSDL end point (http://host:port/SOAP/services.wsdl).\n\nDrag and drop the VirtuosoSOAP() from Class wizard in routine code.\n\n\n\nModule Module1\n\n Sub Main()\n   Dim s As New [drop here the VirtuosoSOAP() method from Class wizard]\n   Dim r As String\n   r = s.fishselect(\"G%\")\n   System.Console.WriteLine(r)\n End Sub\n\nEnd Module\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Consuming a Virtuoso Web Service from Microsoft VB.NET" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nVB.NET\nVirtuoso is able to interact with the Microsoft .NET by providing a\nWSDL description of all the stored procedures exposed as a SOAP operation\nwithin a given virtual directory. The WSDL description is an XML document\navailable at http://<server_http_host_and_port>/SOAP/services.wsdl\non any Virtuoso HTTP server.\n\n\nThis allows for easy creation of .NET clients.\n\n\n\nfishselect example\n\nThe following .NET VBA routine calls the fishselect stored procedure, and prints the results\non the console.\n\n\n\nOpen a new VB.NET project for Console Application.\n\nAdd a web reference to the Virtuoso WSDL end point (http://host:port/SOAP/services.wsdl).\n\nDrag and drop the VirtuosoSOAP() from Class wizard in routine code.\n\n\n\nModule Module1\n\n Sub Main()\n   Dim s As New [drop here the VirtuosoSOAP() method from Class wizard]\n   Dim r As String\n   r = s.fishselect("G%")\n   System.Console.WriteLine(r)\n End Sub\n\nEnd Module\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"WSDL service" ;
	sioc:content	"\nWeb services architecture\n\n  Service providers deploy and publish services by registering them with the Service broker.\n  Service requesters find services by searching the Service broker's registry of published services.\n  Service requesters bind to the Service provider and consume the available services.\n\n\nTechnology Uses\nIn the world of Web services, each of these three operations involves three complimentary yet distinct technologies:\n\n  Publishing services uses the Universal Description, Discovery and Integration (UDDI) API\n  Locating services uses a combination of UDDI and the Web Services Description Language (WSDL)\n  Binding to services leverages WSDL and the Simple Object Access Protocol (SOAP).\n\nAt the most basic level, the Binding operation is the most important of the three.\n\nExample\n\n  The example will create a SOAP based interface and WSDL description for searching an existing Customer Order\n  New orders can be added into the demo database.\n  The first page renders the WSDL as an HTML form for selecting the SOAP method.\n  The second page renders the WSDL again to make a form for input parameters. Note that on this \n      entry form needs to be entered valid _CustomerID (for example ALFKI) and _ProductID (for example is 1).\n      Otherwise the servce will generate SOAP Fault message. Also _ShipVia needs to have a correct value \n      to be entered (for example 1,2 or 3).  \n  \n  Final page displays the result from the SOAP call.\n \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Generating HTML based Service interactions from a WSDL file" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nWeb services architecture\n\n  Service providers deploy and publish services by registering them with the Service broker.\n  Service requesters find services by searching the Service broker's registry of published services.\n  Service requesters bind to the Service provider and consume the available services.\n\n\nTechnology Uses\nIn the world of Web services, each of these three operations involves three complimentary yet distinct technologies:\n\n  Publishing services uses the Universal Description, Discovery and Integration (UDDI) API\n  Locating services uses a combination of UDDI and the Web Services Description Language (WSDL)\n  Binding to services leverages WSDL and the Simple Object Access Protocol (SOAP).\n\nAt the most basic level, the Binding operation is the most important of the three.\n\nExample\n\n  The example will create a SOAP based interface and WSDL description for searching an existing Customer Order\n  New orders can be added into the demo database.\n  The first page renders the WSDL as an HTML form for selecting the SOAP method.\n  The second page renders the WSDL again to make a form for input parameters. Note that on this \n      entry form needs to be entered valid _CustomerID (for example ALFKI) and _ProductID (for example is 1).\n      Otherwise the servce will generate SOAP Fault message. Also _ShipVia needs to have a correct value \n      to be entered (for example 1,2 or 3).  \n  \n  Final page displays the result from the SOAP call.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nSOAP Server setup\n\n  An executable virtual directory is needed to create a SOAP based service.\n  The service in practice is a PL procedure or group of PL procedures.\n       In this example the PL module contains a single procedure.\n       The procedure makes a request to the quotes.nasdaq.com. The retrieved XML document is returned as a\n       string.\n\n  VSP page for WSDL generation:\n       For this example it is so_s_7_wsdl.vsp. A WSDL response is made and sent to the client.\n\n  VSP for SOAP server:\n       The SOAP server can be invoked using a soap_server() call.\n       The so_s_7_server.vsp page shows setup of the SOAP server using the soap_server().\n\n\nExample Virtuoso client invoked from VSP\n\n  Virtuoso client is invoked from the VSP page so_s_7_client.vsp.\n  This page accepts an issuer code and processes it with the Virtuoso SOAP client function - soap_call().\n  The soap method in this request is the name of the procedure defined in Step 2 above.\n  The result from the SOAP request will be transformed with an XSL-T style-sheet, and sent to the browser as an HTML document.\n\n\nExample AJAX SOAP client invoked from JavaScript\n\n  The \"nasdaq_ajax.html\" (listed below) contains a JavaScript code used to invoke SOAP client.\n  This client will invoke the Virtuoso SOAP service as defined above.\n  The JavaScript code uses XMLHttpRequest object.\n\n\nInvoking the operation via VB.NET application\nThe following example demonstrates the usage of the Microsoft .NET against Virtuoso's SOAP service\nas defined in 'Server Setup':\n\n1. Open a new VB.NET project for Console Application.\n2. Add a web reference to the Virtuoso WSDL end point (http://[host:port]/xml-soap/services.wsdl).\n3. Drag and drop the VirtuosoSOAP() from Class wizard in routine code.\n\n\n    Sub Main()\n        Dim soap As New WebReference1.VirtuosoDB_DBA_NasdaqQuotes()\n        Dim result As String\n        Dim sty As New Xml.Xsl.XslTransform()\n\n        result = soap.get_NasdaqQuotes(\"YHOO\")\n\n        sty.Load(\"http://[host:port]/tutorial/services/so_s_7/sr.xsl\")\n\n        Dim strReader As New IO.StringReader(result)\n        Dim xpDoc As New Xml.XPath.XPathDocument(strReader)\n        Dim arg As New Xml.Xsl.XsltArgumentList()\n        Dim strWriter As New IO.StringWriter()\n\n        sty.Transform(xpDoc.CreateNavigator(), arg, strWriter)\n        System.Console.WriteLine(strWriter.ToString)\n    End Sub\n\n" ;
	sioc:has_container	ns2:web2 ,
		ns2:services ;
	sioc:description	"Stock Quotes service" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nSOAP Server setup\n\n  An executable virtual directory is needed to create a SOAP based service.\n  The service in practice is a PL procedure or group of PL procedures.\n       In this example the PL module contains a single procedure.\n       The procedure makes a request to the quotes.nasdaq.com. The retrieved XML document is returned as a\n       string.\n\n  VSP page for WSDL generation:\n       For this example it is so_s_7_wsdl.vsp. A WSDL response is made and sent to the client.\n\n  VSP for SOAP server:\n       The SOAP server can be invoked using a soap_server() call.\n       The so_s_7_server.vsp page shows setup of the SOAP server using the soap_server().\n\n\nExample Virtuoso client invoked from VSP\n\n  Virtuoso client is invoked from the VSP page so_s_7_client.vsp.\n  This page accepts an issuer code and processes it with the Virtuoso SOAP client function - soap_call().\n  The soap method in this request is the name of the procedure defined in Step 2 above.\n  The result from the SOAP request will be transformed with an XSL-T style-sheet, and sent to the browser as an HTML document.\n\n\nExample AJAX SOAP client invoked from JavaScript\n\n  The "nasdaq_ajax.html" (listed below) contains a JavaScript code used to invoke SOAP client.\n  This client will invoke the Virtuoso SOAP service as defined above.\n  The JavaScript code uses XMLHttpRequest object.\n\n\nInvoking the operation via VB.NET application\nThe following example demonstrates the usage of the Microsoft .NET against Virtuoso's SOAP service\nas defined in 'Server Setup':\n\n1. Open a new VB.NET project for Console Application.\n2. Add a web reference to the Virtuoso WSDL end point (http://[host:port]/xml-soap/services.wsdl).\n3. Drag and drop the VirtuosoSOAP() from Class wizard in routine code.\n\n\n    Sub Main()\n        Dim soap As New WebReference1.VirtuosoDB_DBA_NasdaqQuotes()\n        Dim result As String\n        Dim sty As New Xml.Xsl.XslTransform()\n\n        result = soap.get_NasdaqQuotes("YHOO")\n\n        sty.Load("http://[host:port]/tutorial/services/so_s_7/sr.xsl")\n\n        Dim strReader As New IO.StringReader(result)\n        Dim xpDoc As New Xml.XPath.XPathDocument(strReader)\n        Dim arg As New Xml.Xsl.XsltArgumentList()\n        Dim strWriter As New IO.StringWriter()\n\n        sty.Transform(xpDoc.CreateNavigator(), arg, strWriter)\n        System.Console.WriteLine(strWriter.ToString)\n    End Sub\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample overview\nThis example demonstrates:\n\n  Fetching HTML from a foreign host to populate a native table.\n  A SOAP call.\n  SQL to XML conversion with FOR XML EXPLICIT.\n  XSL transformation.\n\n\nExample Setup\nThe service is prepared by loading the SQL file.\nThis performs the following:\n\n  Fetch HTML country and province data from a foreign host.\n  Insert the data into COUNTRY and PROVINCE tables.\n  Fill tables COUNTRY_XML and PROVINCE_XML using http://[host:port]/DAV/factbook/factbook.xml. (http://www.xfront.org/factbook.xml)\n  \n  Define a stored procedure for the SOAP service that queries, using SQL,\n  the data from the tables. The data is returned as XML, by including the\n  FOR XML EXPLICIT clause, using the xml_auto() function to produce this\n  as a string.\n  \n  \n\t    Sample can use data from:\n\t\n  \t  \n\t    Live feed from CIA factbook\n  \t  \n  \t  \n    \t    Cached XML Data\n  \t  \n\t\n  \n  \n  The SOAP service is achieved by defining the /SOAP_SO_S_11 URL to\n  have same functionality as using soap_server() function call.\n  \n\n\nExample Operation\n\n  Makes a SOAP client request. The XML result is held in a stream.\n  Convert the stream using XSLT to HTML.\n  Send the HTML to the browser for display.\n\n\nInvoking the operation via VB.NET application\nThe following example demonstrates the usage of the Microsoft .NET against Virtuoso's SOAP service\nas defined in 'Server Setup':\n\n1. Open a new VB.NET project for Console Application.\n2. Add a web reference to the Virtuoso WSDL end point (http://[host:port]/SOAP_SO_S_11/services.wsdl).\n3. Drag and drop the VirtuosoSOAP() from Class wizard in routine code.\n\n    Sub Main()\n        Dim soap As New WebReference1.VirtuosoSOAP()\n        Dim result As String\n        Dim sty As New Xml.Xsl.XslTransform()\n\n        result = soap.administrative_divisions(\"United States\", \"\")\n\n        sty.Load(\"http://[host:port]/tutorial/services/so_s_11/sr.xsl\")\n\n        Dim strReader As New IO.StringReader(result)\n        Dim xpDoc As New Xml.XPath.XPathDocument(strReader)\n        Dim arg As New Xml.Xsl.XsltArgumentList()\n        Dim strWriter As New IO.StringWriter()\n\n        sty.Transform(xpDoc.CreateNavigator(), arg, strWriter)\n        System.Console.WriteLine(strWriter.ToString)\n    End Sub\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Global provinces and administrative divisions lookup service" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample overview\nThis example demonstrates:\n\n  Fetching HTML from a foreign host to populate a native table.\n  A SOAP call.\n  SQL to XML conversion with FOR XML EXPLICIT.\n  XSL transformation.\n\n\nExample Setup\nThe service is prepared by loading the SQL file.\nThis performs the following:\n\n  Fetch HTML country and province data from a foreign host.\n  Insert the data into COUNTRY and PROVINCE tables.\n  Fill tables COUNTRY_XML and PROVINCE_XML using http://[host:port]/DAV/factbook/factbook.xml. (http://www.xfront.org/factbook.xml)\n  \n  Define a stored procedure for the SOAP service that queries, using SQL,\n  the data from the tables. The data is returned as XML, by including the\n  FOR XML EXPLICIT clause, using the xml_auto() function to produce this\n  as a string.\n  \n  \n\t    Sample can use data from:\n\t\n  \t  \n\t    Live feed from CIA factbook\n  \t  \n  \t  \n    \t    Cached XML Data\n  \t  \n\t\n  \n  \n  The SOAP service is achieved by defining the /SOAP_SO_S_11 URL to\n  have same functionality as using soap_server() function call.\n  \n\n\nExample Operation\n\n  Makes a SOAP client request. The XML result is held in a stream.\n  Convert the stream using XSLT to HTML.\n  Send the HTML to the browser for display.\n\n\nInvoking the operation via VB.NET application\nThe following example demonstrates the usage of the Microsoft .NET against Virtuoso's SOAP service\nas defined in 'Server Setup':\n\n1. Open a new VB.NET project for Console Application.\n2. Add a web reference to the Virtuoso WSDL end point (http://[host:port]/SOAP_SO_S_11/services.wsdl).\n3. Drag and drop the VirtuosoSOAP() from Class wizard in routine code.\n\n    Sub Main()\n        Dim soap As New WebReference1.VirtuosoSOAP()\n        Dim result As String\n        Dim sty As New Xml.Xsl.XslTransform()\n\n        result = soap.administrative_divisions("United States", "")\n\n        sty.Load("http://[host:port]/tutorial/services/so_s_11/sr.xsl")\n\n        Dim strReader As New IO.StringReader(result)\n        Dim xpDoc As New Xml.XPath.XPathDocument(strReader)\n        Dim arg As New Xml.Xsl.XsltArgumentList()\n        Dim strWriter As New IO.StringWriter()\n\n        sty.Transform(xpDoc.CreateNavigator(), arg, strWriter)\n        System.Console.WriteLine(strWriter.ToString)\n    End Sub\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample overview\n\nThis example demonstrates usage of the WSDL_IMPORT_UDT() function.\nThe result from calling of the WSDL_IMPORT_UDT() is the creation of a \nUser Defined Type (UDT) which represents the SOAP service. Each method in the UDT\nrepresents an operation available from this SOAP service (proxy UDT).\n\nAfter successful retrieval of the WSDL, and UDT creation, the function\nreturns UDT definition as string.\n\n    The example also defines one test endpoint where it exposes the \n    imported UDTs are own methods. Therefore it's easy to test using \n    VSMX file for the demo endpoint. \n\n\n    To cleanup the endpoint, use 'Clear cache' button. This would \n    unpublish the SOAP proxy UDTs from the demo test endpoint.\n\n\n    To setup and run, the initial script must be loaded.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Consuming Third-Party Services via WSDL URLs" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample overview\n\nThis example demonstrates usage of the WSDL_IMPORT_UDT() function.\nThe result from calling of the WSDL_IMPORT_UDT() is the creation of a \nUser Defined Type (UDT) which represents the SOAP service. Each method in the UDT\nrepresents an operation available from this SOAP service (proxy UDT).\n\nAfter successful retrieval of the WSDL, and UDT creation, the function\nreturns UDT definition as string.\n\n    The example also defines one test endpoint where it exposes the \n    imported UDTs are own methods. Therefore it's easy to test using \n    VSMX file for the demo endpoint. \n\n\n    To cleanup the endpoint, use 'Clear cache' button. This would \n    unpublish the SOAP proxy UDTs from the demo test endpoint.\n\n\n    To setup and run, the initial script must be loaded.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample\n\n  This example repeats the example SO-S-7, but all VSPs are hosted in WebDAV repository.\n  Important: make sure that EnabledDavVSP is set to 1 in the INI file, to allow VSP execution in WebDAV.\n  The example script loads all pages into the WebDAV, and sets their execution flags.\n  This example needs at least 2 HTTP server threads configured.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Stock Quotes service hosted within Virtuoso's WebDAV repository" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example repeats the example SO-S-7, but all VSPs are hosted in WebDAV repository.\n  Important: make sure that EnabledDavVSP is set to 1 in the INI file, to allow VSP execution in WebDAV.\n  The example script loads all pages into the WebDAV, and sets their execution flags.\n  This example needs at least 2 HTTP server threads configured.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample\n\n  This example repeats the example SO-S-7, but all VSPs for the SOAP client are hosted in the WebDAV repository.\n  The SOAP & WSDL service are achieved by defining the /SOAP_SO_S_9 URL to have same functionality as using soap_server() and soap_wsdl() calls.\n  '/SOAP_SO_S_9' represents the so_s_8_server.vsp and /SOAP_SO_S_9/services.wsdl represents the so_s_8_wsdl.vsp\n  Important: make sure that EnabledDavVSP is set to 1 in the INI file, to allow VSP execution in WebDAV.\n  The example script loads all pages into the WebDAV, and sets their execution flags.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Stock Quotes client execution from within Virtuoso's WebDAV Repository" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example repeats the example SO-S-7, but all VSPs for the SOAP client are hosted in the WebDAV repository.\n  The SOAP & WSDL service are achieved by defining the /SOAP_SO_S_9 URL to have same functionality as using soap_server() and soap_wsdl() calls.\n  '/SOAP_SO_S_9' represents the so_s_8_server.vsp and /SOAP_SO_S_9/services.wsdl represents the so_s_8_wsdl.vsp\n  Important: make sure that EnabledDavVSP is set to 1 in the INI file, to allow VSP execution in WebDAV.\n  The example script loads all pages into the WebDAV, and sets their execution flags.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"WS-ReliableMessaging demo" ;
	sioc:content	"\n\tExample\n\t\n\t    The example below demonstrates configuring an endpoint for WS-Reliable Messaging\n\t    operations. It also contains a simple client for issuing a 'ping' request to an\n\t    endpoint which supports the WS-ReliableMessaging protocol.\n\t\n\t\n\t    Note:\n\t    To use the anonymous client, 'pingback URI' field in the send form should be empty.\n\t\n    " ;
	sioc:has_container	ns2:services ;
	sioc:description	"WS-Reliable Messaging: Setting up a SOAP endpoint" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n\tExample\n\t\n\t    The example below demonstrates configuring an endpoint for WS-Reliable Messaging\n\t    operations. It also contains a simple client for issuing a 'ping' request to an\n\t    endpoint which supports the WS-ReliableMessaging protocol.\n\t\n\t\n\t    Note:\n\t    To use the anonymous client, 'pingback URI' field in the send form should be empty.\n\t\n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Making an SOAP router endpoint" ;
	sioc:content	"\nExample\n\nThis chapter describes general guide lines for using routing capabilities of the Virtuoso SOAP server.\n\n\nIn order to have the rest of examples of this section working, the following steps must be performed.\n\n\n If you are going to try .NET examples the MS WSDK toolkit must be installed on a W2K machine. The .NET examples are tested with 1.0.0.0 version of Microsoft.WSDK.dll, so make sure that version of that assembly is the same.\n Make sure that WS Routing examples of MS WSDK working before trying any of interoperability examples.\n From this page run the setup script (set the initial state), this will define the routing and ultimate endpoints. \n \n\n\nThe SOAP directory option we are using to setup a WS Routing (SOAP router) is:\n\n\n WS-RP - yes/no , this is to enable WS Routing filter\n \n\n\nThe VSP page is example how Virtuoso SOAP client can be used to invoke the sample services as AddInt or echoString.Form this page we can invoke these operations via different routers. Note that \"Operation to invoke\" option must be set properly depending of type of endpoint (see remarks on select page).\n\n\n\nThe .NET client example must be complied before trying it. To do this follow the steps:\n\n\nChange in the RoutingClient.cs and referalCache.config files  to host and port where your virtuoso HTTP server is listening.\ncompile the example issuing nmake command in the tutorial/services/rp_s_1 directory. On that step you may need to have .NET Visual Studio installed and .NET Framework SDK\nif you going to compile the client on an other box, make sure that referralCache.config file is in the same directory where is .exe file.\n \n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Setting up a SOAP router endpoint" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nThis chapter describes general guide lines for using routing capabilities of the Virtuoso SOAP server.\n\n\nIn order to have the rest of examples of this section working, the following steps must be performed.\n\n\n If you are going to try .NET examples the MS WSDK toolkit must be installed on a W2K machine. The .NET examples are tested with 1.0.0.0 version of Microsoft.WSDK.dll, so make sure that version of that assembly is the same.\n Make sure that WS Routing examples of MS WSDK working before trying any of interoperability examples.\n From this page run the setup script (set the initial state), this will define the routing and ultimate endpoints. \n \n\n\nThe SOAP directory option we are using to setup a WS Routing (SOAP router) is:\n\n\n WS-RP - yes/no , this is to enable WS Routing filter\n \n\n\nThe VSP page is example how Virtuoso SOAP client can be used to invoke the sample services as AddInt or echoString.Form this page we can invoke these operations via different routers. Note that "Operation to invoke" option must be set properly depending of type of endpoint (see remarks on select page).\n\n\n\nThe .NET client example must be complied before trying it. To do this follow the steps:\n\n\nChange in the RoutingClient.cs and referalCache.config files <virtuoso:port> to host and port where your virtuoso HTTP server is listening.\ncompile the example issuing nmake command in the tutorial/services/rp_s_1 directory. On that step you may need to have .NET Visual Studio installed and .NET Framework SDK\nif you going to compile the client on an other box, make sure that referralCache.config file is in the same directory where is .exe file.\n \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Manipulating of message path on a WS-Routing enabled endpoints" ;
	sioc:content	"\nExample\n\nIn order to try the following example you need first to setup the RP-S-1 as it uses the endpoints defined there. Also this example needs at least 3 HTTP threads configured in order to work properly.\n\n\n\nThe VSP page demonstrates how routing path can be manipulated on a SOAP routers using the WS-Referral statements.\n\n\nThe example show inserting an intermediary router in routing path\nQuerying a router for already registered intermediary\nExecution of a single call to an endpoint\nTraveling of the message between client and endpoint via first and second router (added on step 1)\nRemoval of a registered intermediary\nIf step 1 is invoked twice sequentially an duplicates error will be shown\nIf step 3 is invoked before step 1 or after step 5, an error for missing intermediary from routing path is shown\n\nNote: To determinate message routing path, see at content of 'rev' element in response message header when invoking the echoString operation.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Routing path manipulation" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nIn order to try the following example you need first to setup the RP-S-1 as it uses the endpoints defined there. Also this example needs at least 3 HTTP threads configured in order to work properly.\n\n\n\nThe VSP page demonstrates how routing path can be manipulated on a SOAP routers using the WS-Referral statements.\n\n\nThe example show inserting an intermediary router in routing path\nQuerying a router for already registered intermediary\nExecution of a single call to an endpoint\nTraveling of the message between client and endpoint via first and second router (added on step 1)\nRemoval of a registered intermediary\nIf step 1 is invoked twice sequentially an duplicates error will be shown\nIf step 3 is invoked before step 1 or after step 5, an error for missing intermediary from routing path is shown\n\nNote: To determinate message routing path, see at content of 'rev' element in response message header when invoking the echoString operation.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample\n\n  This example repeats the example SO-S-7,\n  however client is using AJAX.\n  The AJAX based client retrieves the XML data from Virtuoso SOAP service, and makes a client\n  side XSL-T transformation. \n  \n\n" ;
	sioc:has_container	ns2:web2 ,
		ns2:services ;
	sioc:description	"Stock Quotes Service incorporating AJAX" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example repeats the example SO-S-7,\n  however client is using AJAX.\n  The AJAX based client retrieves the XML data from Virtuoso SOAP service, and makes a client\n  side XSL-T transformation. \n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample\n\n  This example repeats the SO-S-11,\n  however client is using AJAX.\n  Note: The tables and procedures are used from SO-S-11 example, so run SO-S-11 first.\n  The SOAP & WSDL service are achieved by defining the /SOAP_SO_S_11 URL to have same functionality as using soap_server() and soap_wsdl() calls.\n\n" ;
	sioc:has_container	ns2:services ,
		ns2:web2 ;
	sioc:description	"Global provinces and administrative divisions lookup service incorporating AJAX" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example repeats the SO-S-11,\n  however client is using AJAX.\n  Note: The tables and procedures are used from SO-S-11 example, so run SO-S-11 first.\n  The SOAP & WSDL service are achieved by defining the /SOAP_SO_S_11 URL to have same functionality as using soap_server() and soap_wsdl() calls.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL" ;
	sioc:content	"\nExchange Rate Conversion Example\n\n  \n  This example is an exchange calculator in two versions: based on VSP\n  and soap_call() and another AJAX version based on WebService Behaviour.\n  A virtual directory is configured to respond to SOAP service requests,\n  which are handled in the context of the assigned SQL user.\n  \n  \n  \n  The example defines the following service descriptions and links:\n  \n   \n  \n  \n  A SOAP directory of 'exchange' for describing exch's procedures. The\n  WSDL file will be located at\n  http://hostname:[port]/exchange/services.wsdl\n  \n  \n  \n  The server-based webservices file is exchange_rates.vsp, while the AJAX\n  one is exchange_rates_ajax.html. Click on the 'Run' links to experience the demo.\n  \n   \n  \n\n  \n  Note: loading the exchange.sql file will take some time, as it\n  accesses a foreign host.\n  \n\n \n" ;
	sioc:has_container	ns2:web2 ,
		ns2:services ;
	sioc:description	"Exchange Rate Conversion service" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExchange Rate Conversion Example\n\n  \n  This example is an exchange calculator in two versions: based on VSP\n  and soap_call() and another AJAX version based on WebService Behaviour.\n  A virtual directory is configured to respond to SOAP service requests,\n  which are handled in the context of the assigned SQL user.\n  \n  \n  \n  The example defines the following service descriptions and links:\n  \n   \n  \n  \n  A SOAP directory of 'exchange' for describing exch's procedures. The\n  WSDL file will be located at\n  http://hostname:[port]/exchange/services.wsdl\n  \n  \n  \n  The server-based webservices file is exchange_rates.vsp, while the AJAX\n  one is exchange_rates_ajax.html. Click on the 'Run' links to experience the demo.\n  \n   \n  \n\n  \n  Note: loading the exchange.sql file will take some time, as it\n  accesses a foreign host.\n  \n\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP & WSDL service" ;
	sioc:content	"\nExample overview\nThis example demonstrates:\n\n  \n  Fetching a two-dimensional array from a SOAP service to populate a provinces list box.\n  \n  \n  The clients in this case is using AJAX.\n  \n\n\nExample\n\n  This example uses the SO-S-11 for initial setup,\n  and demonstrates making a simple registration form.\n  Note: The tables and procedures are used from SO-S-11 example, so run SO-S-11 first.\n  The SOAP & WSDL service are achieved by defining the /SOAP_SO_S_11 URL to have same functionality as using soap_server() and soap_wsdl() calls.\n\n" ;
	sioc:has_container	ns2:services ,
		ns2:web2 ;
	sioc:description	"Web Registration form exploiting global provinces and administrative divisions lookup service" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample overview\nThis example demonstrates:\n\n  \n  Fetching a two-dimensional array from a SOAP service to populate a provinces list box.\n  \n  \n  The clients in this case is using AJAX.\n  \n\n\nExample\n\n  This example uses the SO-S-11 for initial setup,\n  and demonstrates making a simple registration form.\n  Note: The tables and procedures are used from SO-S-11 example, so run SO-S-11 first.\n  The SOAP & WSDL service are achieved by defining the /SOAP_SO_S_11 URL to have same functionality as using soap_server() and soap_wsdl() calls.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SOAP services" ;
	sioc:content	"\n\nExample overview\nThis example demonstrates:\n\n  \n  Fetching HTML from a foreign host as specified by the user.\n  \n  \n  Rendering the page with regexp_match() to extract the contacts information.\n  For example, it take information from sequences like:\n  \"quoted text\" said John Smith, Manager at A Company.\n  \n  \n  \n  Making a Web search with the company name to find the domain.\n  \n  \n  Making an email address from contact name, and domain name.\n  \n  A SOAP call.\n  \n  Processing the 4 dimensional array in the\n  AJAX based client.\n  \n  \n  XSL transformation.\n  \n\n\nExample Setup\nThe service is prepared by loading the SQL file.\nThis performs the following:\n\n  \n  Define a SOAP type for 4 dimensional array.\n  \n  \n  Define a stored procedure for the SOAP service that queries, web target and makes the contact info.\n  \n  The SOAP service is achieved by defining the /SOAP_SO_S_19 URL to\n  have same functionality as using soap_server() function call.\n  \n\n\nExample Operation\n\n  Get a page from the URL.\n  Substitute characters \" as 0x94 etc.\n  Remove , ,  elements.\n  Take out CR/LF.\n  Make breaks before 
	rdf:type	foaf:Document ;
	dc:title	"Secure SOAP service" ;
	sioc:content	"\nExample\n\n  This example repeats the example SO-S-7, but SOAP call is executed over SSL.\n  The SOAP & WSDL service are achieved by defining the /SOAP URL\n  to have same functionality as using soap_server() and soap_wsdl() calls.\n  '/SOAP' represents the so_s_7_server.vsp and /SOAP/services.wsdl\n  represents the so_s_7_wsdl.vsp\n  Make sure that files containing server and client\n  certificate/key data are exists in the server working directory. The\n  following files are required for the example:\n  \n    srv.cert.pem - server certificate \n    srv.key.pem - server private key \n    ca.pem - CA list \n    cli.p12 - client certificate and private key in PKCS#12 format \n  \n  \n  The example script defines and starts a HTTPS server on port 4433.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Secure SOAP Service invocation over SSL" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example repeats the example SO-S-7, but SOAP call is executed over SSL.\n  The SOAP & WSDL service are achieved by defining the /SOAP URL\n  to have same functionality as using soap_server() and soap_wsdl() calls.\n  '/SOAP' represents the so_s_7_server.vsp and /SOAP/services.wsdl\n  represents the so_s_7_wsdl.vsp\n  Make sure that files containing server and client\n  certificate/key data are exists in the server working directory. The\n  following files are required for the example:\n  \n    srv.cert.pem - server certificate \n    srv.key.pem - server private key \n    ca.pem - CA list \n    cli.p12 - client certificate and private key in PKCS#12 format \n  \n  \n  The example script defines and starts a HTTPS server on port 4433.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Making an Secure SOAP Directory" ;
	sioc:content	"\nExample\n\nIn order to have the rest of examples of this section working, the following steps must be performed.\n\n\n The MS WSDK toolkit must be installed on a W2K mashine. The .NET examples are tested with 1.0.0.0 version of Microsoft.WSDK.dll, so make sure that version of that assembly is the same.\n Make sure that WS Secure examples of MS WSDK are working before trying any of interoperabilty examples.\n From this page run setup script (set the initial state), this will define symmetric keys, there is also included a x.509 import, but it's only for demonstration. \nTo make your WSDK applications to work with Virtuoso you need to export from W2K box the certificate and import with registration page on this example.\nThe setup script also defines a SOAP secure directory (/SecureWebServices) which is used in the rest of the examples.\n\n\n\nThe SOAP directory options we are using to secure the messages are:\n\n\n WSS-SEC - yes/no , this is to enable WS secure processing\n WSS-KEY - name of procedure , which will return a key instance to encrypt the outbound messages\n WSS-Template - string or null, content of signature template, in that examples we will not make signatures on outbound messages. How to make signatures is explained in the x.509 siging example.\n WSS-Type - 1/0 to make signature or to encrypt only\n WSS-Validate-Signature - 0/1/2 - do not validate, validate signature, validate if exists\n in our examples we will accept both of variants, so 2 is used.\n\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Exposing Secure SOAP Endpoints" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nIn order to have the rest of examples of this section working, the following steps must be performed.\n\n\n The MS WSDK toolkit must be installed on a W2K mashine. The .NET examples are tested with 1.0.0.0 version of Microsoft.WSDK.dll, so make sure that version of that assembly is the same.\n Make sure that WS Secure examples of MS WSDK are working before trying any of interoperabilty examples.\n From this page run setup script (set the initial state), this will define symmetric keys, there is also included a x.509 import, but it's only for demonstration. \nTo make your WSDK applications to work with Virtuoso you need to export from W2K box the certificate and import with registration page on this example.\nThe setup script also defines a SOAP secure directory (/SecureWebServices) which is used in the rest of the examples.\n\n\n\nThe SOAP directory options we are using to secure the messages are:\n\n\n WSS-SEC - yes/no , this is to enable WS secure processing\n WSS-KEY - name of procedure , which will return a key instance to encrypt the outbound messages\n WSS-Template - string or null, content of signature template, in that examples we will not make signatures on outbound messages. How to make signatures is explained in the x.509 siging example.\n WSS-Type - 1/0 to make signature or to encrypt only\n WSS-Validate-Signature - 0/1/2 - do not validate, validate signature, validate if exists\n in our examples we will accept both of variants, so 2 is used.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Symmetric Encryption" ;
	sioc:content	"\nExample\n\nThis section describes how to make secure web services call, using a symmetric key encryption.\nThe algorithm used for these examples is tripple-des.\n\n\nBoth server and client have a shared secret, which is used to encryt and decrypt the SOAP message.\nIn practice the key is transfered by some secure way between client and server, as if it's captured the all traffic between server and client can be compromised.\nVirtuoso keeps keys internally and can be instantiated with xenc_key_instance_create ().\nIn this example we are using a key 'WSDK Sample Symmetric Key', imported from WSDK.NET SymmetricEncryption example. This is to have the same key in all places: .NET server and client, Virtuoso server and client.\nAnother posibillity is to generate the key on Virtuoso side with xenc_key_3DES_rand_create() and export to the .NET client and server configuration. To export the 3DES key can be used xenc_key_serialize () function. \n\n\n\nThe Virtuoso VSP based clients demonstrate\n\n\n accessing Virtuoso Web Service with Virtuoso client\n accessing .NET Web service with Virtuoso client\n\n\n\nTo run .NET client against Virtuoso service you need:\n\n\nThis example works with MS WSDK; MS WSE 2.0 obsolete the data encryption directly a key data.\nto change  to host and port where your virtuoso HTTP server is listening.\ncompile the example issuing nmake command in the tutorial/services/ws_s_2 directory.\nif you going to compile the client on an other box, make sure that .config file is in the same directory where is .exe file.\n\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Secure SOAP Client using Symmetric Encryption (3DES)" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nThis section describes how to make secure web services call, using a symmetric key encryption.\nThe algorithm used for these examples is tripple-des.\n\n\nBoth server and client have a shared secret, which is used to encryt and decrypt the SOAP message.\nIn practice the key is transfered by some secure way between client and server, as if it's captured the all traffic between server and client can be compromised.\nVirtuoso keeps keys internally and can be instantiated with xenc_key_instance_create ().\nIn this example we are using a key 'WSDK Sample Symmetric Key', imported from WSDK.NET SymmetricEncryption example. This is to have the same key in all places: .NET server and client, Virtuoso server and client.\nAnother posibillity is to generate the key on Virtuoso side with xenc_key_3DES_rand_create() and export to the .NET client and server configuration. To export the 3DES key can be used xenc_key_serialize () function. \n\n\n\nThe Virtuoso VSP based clients demonstrate\n\n\n accessing Virtuoso Web Service with Virtuoso client\n accessing .NET Web service with Virtuoso client\n\n\n\nTo run .NET client against Virtuoso service you need:\n\n\nThis example works with MS WSDK; MS WSE 2.0 obsolete the data encryption directly a key data.\nto change <virtuoso:port> to host and port where your virtuoso HTTP server is listening.\ncompile the example issuing nmake command in the tutorial/services/ws_s_2 directory.\nif you going to compile the client on an other box, make sure that .config file is in the same directory where is .exe file.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Asymmetric Encryption" ;
	sioc:content	"\nExample\n\nThis section demonstrates how to make encrypted SOAP message using\nasymmetric algorithm (RSA).\n\n\nThese examples are using a X.509 certificate to define the RSA key for encruption.\nTo encrypt the message client uses public key of server's certificate, so only server know private key and can decrypt the message. \nIn practice message itself is encrypted with 3DES algorthm using a random session key. \nThe session key itself is encrypted with public part of RSA key. \nSo the server first decode the session key, and then decrypt the message.\n\n\n\nThe Virtuoso VSP based clients demonstrate\n\n\n accessing Virtuoso Web Service with Virtuoso client using asymmetric algorithm\n accessing .NET Web service with Virtuoso client using asymmetric algorithm\n\n\n\nTo run .NET client against Virtuoso service you need:\n\n\nMicrosoft WSE 2.0 installed\nEdit the Makefile and specify in CSLIBFLAGS where Microsoft.Web.Services.DLL reside.\ncompile the example issuing nmake command in the tutorial/services/ws_s_3 directory.\nif you going to compile the client on an other box, make sure that .config file is in the same directory where is .exe file.\n\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Secure SOAP Client using RSA Encryption" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nThis section demonstrates how to make encrypted SOAP message using\nasymmetric algorithm (RSA).\n\n\nThese examples are using a X.509 certificate to define the RSA key for encruption.\nTo encrypt the message client uses public key of server's certificate, so only server know private key and can decrypt the message. \nIn practice message itself is encrypted with 3DES algorthm using a random session key. \nThe session key itself is encrypted with public part of RSA key. \nSo the server first decode the session key, and then decrypt the message.\n\n\n\nThe Virtuoso VSP based clients demonstrate\n\n\n accessing Virtuoso Web Service with Virtuoso client using asymmetric algorithm\n accessing .NET Web service with Virtuoso client using asymmetric algorithm\n\n\n\nTo run .NET client against Virtuoso service you need:\n\n\nMicrosoft WSE 2.0 installed\nEdit the Makefile and specify in CSLIBFLAGS where Microsoft.Web.Services.DLL reside.\ncompile the example issuing nmake command in the tutorial/services/ws_s_3 directory.\nif you going to compile the client on an other box, make sure that .config file is in the same directory where is .exe file.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"X.509 Signing" ;
	sioc:content	"\nExample\n\nThis chapter demonstrates how to make signed SOAP message.\nThe signed message contains certificate (only) in the Security header.\nIn that example no encrypted data is sent, but in practice the both approaches can be combined.\nThe server checks signature against this certificate and ensures it's validity.\n\n\n\nTo run .NET client using X.509 certificate signed message, against Virtuoso service you need:\n\n\nMicrosoft WSE 2.0 installed\nEdit the Makefile and specify in CSLIBFLAGS where Microsoft.Web.Services.DLL reside.\ncompile the example issuing nmake command in the tutorial/services/ws_s_4 directory.\n\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Secure SOAP Client using X.509 certificate for signing" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nThis chapter demonstrates how to make signed SOAP message.\nThe signed message contains certificate (only) in the Security header.\nIn that example no encrypted data is sent, but in practice the both approaches can be combined.\nThe server checks signature against this certificate and ensures it's validity.\n\n\n\nTo run .NET client using X.509 certificate signed message, against Virtuoso service you need:\n\n\nMicrosoft WSE 2.0 installed\nEdit the Makefile and specify in CSLIBFLAGS where Microsoft.Web.Services.DLL reside.\ncompile the example issuing nmake command in the tutorial/services/ws_s_4 directory.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Username Signing" ;
	sioc:content	"\nExample\n\nThis example demonstrates how to make signed SOAP message.\nThe signed message contains Username and password in the Security header.\nIn that example no encrypted data is sent.\nThe server checks credentials against database users and ensures it's validity.\n\n\n\n    To run .NET client using Username signed message, against Virtuoso service you need:\n\n\nMicrosoft WSE 2.0 installed\nEdit the Makefile and specify in CSLIBFLAGS where Microsoft.Web.Services.DLL resides.\ncompile the example issuing nmake command in the tutorial/services/ws_s_4a directory.\n\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Secure SOAP Client using Username and Password for signing" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nThis example demonstrates how to make signed SOAP message.\nThe signed message contains Username and password in the Security header.\nIn that example no encrypted data is sent.\nThe server checks credentials against database users and ensures it's validity.\n\n\n\n    To run .NET client using Username signed message, against Virtuoso service you need:\n\n\nMicrosoft WSE 2.0 installed\nEdit the Makefile and specify in CSLIBFLAGS where Microsoft.Web.Services.DLL resides.\ncompile the example issuing nmake command in the tutorial/services/ws_s_4a directory.\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Using a Secure SOAP Services" ;
	sioc:content	"\n\tPreliminaries\n\t\n\t    The WS Trust protocol is a SOAP based\n\t    secure service and client that can be used\n\t    to retrieve a security token (X.509 certificate or similar)\n\t    in order to be used for making secure operation with an\n\t    ultimate service in the client's operation.\n\t\n\t\n\t    In common scenario the client asks Token Issuer\n\t    for a security token. Then client uses token from\n\t    WS Trust response to perform second remote call\n\t    signed and/or encrypted to another service which\n\t    is a ultimate target service.\n\t    Usually Token Issuer, Client and Ultimate service are\n\t    located on different physical locations.\n\t\n    \n\tExample\n\t\n\t    Before running this demo make sure that WS-S-1 tutorial\n\t    is set-up and a valid X.509 certificate and corresponding private key\n\t    are imported (for server and client usage) via WS-S-1 example certificate\n\t    upload utility.\n\t\n\t\n\t    This example uses WS Trust client to\n\t    obtain X.509 security token from a Token Issuer service\n\t    and then it uses to make signed request to\n\t    dummy Weblog service. In real situation the Weblog service\n\t    instead of echoing a random URL would create an entry in the\n\t    user's blog.\n\t    Note that in that demo all operations are performed in context\n\t    of a same server (i.e. Token Issuer, Weblog service and client are\n\t    running on one Virtuoso server instance).\n\t\n\t\n\t    The following are demo's main points.\n\t\n\t\n\t    Client uses a Username and password to digitally sign the\n\t\trequest from Token Issuer.\n\t    Token Issuer will check the signature and user credentials\n\t\tand then will issue security token to the client\n\t    The Token Issuer service uses a PL hook\n\t\tto return appropriate X.509 token\n\t    Client uses the returned token (from Token Issuer service) to\n\t\tmatch it against local key storage and to digitally sign the\n\t\tsecond request (to the Weblog service)\n\t    The Weblog service will just verify the signature\n\t\tand will return an echo of the client's request plus\n\t\tan random URL string and post id. (In the real world such service should add data into a Database keeping the blog posts)\n\t    The Weblog service will digitally sign the response before\n\t\tsending it to client.\n\t    To see request/response messages from/to Token Issuer or Web service\n\t      use the radio group buttons.\n      \n      \n\t  Note: In this example Token Issuer, Weblog service and client uses same X.509\n\t  certificate.\n      \n    " ;
	sioc:has_container	ns2:services ;
	sioc:description	"Exposing WS Trust SOAP Endpoints" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n\tPreliminaries\n\t\n\t    The WS Trust protocol is a SOAP based\n\t    secure service and client that can be used\n\t    to retrieve a security token (X.509 certificate or similar)\n\t    in order to be used for making secure operation with an\n\t    ultimate service in the client's operation.\n\t\n\t\n\t    In common scenario the client asks Token Issuer\n\t    for a security token. Then client uses token from\n\t    WS Trust response to perform second remote call\n\t    signed and/or encrypted to another service which\n\t    is a ultimate target service.\n\t    Usually Token Issuer, Client and Ultimate service are\n\t    located on different physical locations.\n\t\n    \n\tExample\n\t\n\t    Before running this demo make sure that WS-S-1 tutorial\n\t    is set-up and a valid X.509 certificate and corresponding private key\n\t    are imported (for server and client usage) via WS-S-1 example certificate\n\t    upload utility.\n\t\n\t\n\t    This example uses WS Trust client to\n\t    obtain X.509 security token from a Token Issuer service\n\t    and then it uses to make signed request to\n\t    dummy Weblog service. In real situation the Weblog service\n\t    instead of echoing a random URL would create an entry in the\n\t    user's blog.\n\t    Note that in that demo all operations are performed in context\n\t    of a same server (i.e. Token Issuer, Weblog service and client are\n\t    running on one Virtuoso server instance).\n\t\n\t\n\t    The following are demo's main points.\n\t\n\t\n\t    Client uses a Username and password to digitally sign the\n\t\trequest from Token Issuer.\n\t    Token Issuer will check the signature and user credentials\n\t\tand then will issue security token to the client\n\t    The Token Issuer service uses a PL hook\n\t\tto return appropriate X.509 token\n\t    Client uses the returned token (from Token Issuer service) to\n\t\tmatch it against local key storage and to digitally sign the\n\t\tsecond request (to the Weblog service)\n\t    The Weblog service will just verify the signature\n\t\tand will return an echo of the client's request plus\n\t\tan random URL string and post id. (In the real world such service should add data into a Database keeping the blog posts)\n\t    The Weblog service will digitally sign the response before\n\t\tsending it to client.\n\t    To see request/response messages from/to Token Issuer or Web service\n\t      use the radio group buttons.\n      \n      \n\t  Note: In this example Token Issuer, Weblog service and client uses same X.509\n\t  certificate.\n      \n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Add entity to UDDI" ;
	sioc:content	"\nExample\n\n    The example shows automatic convert demo..Suppliers to save_business UDDI query.\n    Use UD-S-2 to see the result.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Business Contact Registration in Virtuoso hosted UDDI registry" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n    The example shows automatic convert demo..Suppliers to save_business UDDI query.\n    Use UD-S-2 to see the result.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Display entry from UDDI server" ;
	sioc:content	"\nExample\n\n    Setup a URL to a UDDI server\n\tDefine a Name pattern (begin with)\n\tView the UDDI request\n\tGet the data from the server\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Querying Virtuoso hosted UDDI registry" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n    Setup a URL to a UDDI server\n\tDefine a Name pattern (begin with)\n\tView the UDDI request\n\tGet the data from the server\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Web services registration" ;
	sioc:content	"\nPreliminaries\n\n  The UDDI provides a flexible way to register any kind of\n  service.\n  The services in particular can be SOAP or WSDL web\n  services.\n\n\nSOAP and WSDL registration example\n\n  This example makes a business record, and will define a service for it.\n  The services can be provided by an organization (business).\n  Without a defined provider service, it cannot be registered separately.\n  Because there is no tModel for the service, one is provided\n  for SOAP classification (tm.xml).\n  Next step is to create a business description.(be.xml)\n  Then create a service description (bs.xml).\n  Then there is a binding (bnd.xml) of the service and business.\n  This binding has two templates:\n  \n    SOAP template for information via Web page\n    WSDL template for WSDL description of that service\n  \n  The example shows step by step for each template.\n\n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Step by step registration of SOAP services in Virtuoso hosted registry" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The UDDI provides a flexible way to register any kind of\n  service.\n  The services in particular can be SOAP or WSDL web\n  services.\n\n\nSOAP and WSDL registration example\n\n  This example makes a business record, and will define a service for it.\n  The services can be provided by an organization (business).\n  Without a defined provider service, it cannot be registered separately.\n  Because there is no tModel for the service, one is provided\n  for SOAP classification (tm.xml).\n  Next step is to create a business description.(be.xml)\n  Then create a service description (bs.xml).\n  Then there is a binding (bnd.xml) of the service and business.\n  This binding has two templates:\n  \n    SOAP template for information via Web page\n    WSDL template for WSDL description of that service\n  \n  The example shows step by step for each template.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Making and checking a Domain via Provider APIs" ;
	sioc:content	"\nExample\n\n  The SQL script makes a Virtuoso API functions to create and check domains.\n  The interface page has a test buttons which sends a REST request to the server.\n  The Service for testing will just return its own argument.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  The page shows the command and explains the manual operation for doing this from the admin interface.\n \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Exposing new domains" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The SQL script makes a Virtuoso API functions to create and check domains.\n  The interface page has a test buttons which sends a REST request to the server.\n  The Service for testing will just return its own argument.\n  At least 2 web threads are needed, so this should be noted before starting. An Error message is shown\n  if only one is available.\n  The page shows the command and explains the manual operation for doing this from the admin interface.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Checking if WebID and specific Public Key are in a relation" ;
	sioc:content	"\nExample\n\n  The service is an alternative to using SPARQL queries via the SPARQL protocol against Virtuoso endpoints re. WebID verification i.e., lookup a profile graph to see if WebID and specific Public Key are in a relation.\n  The webid_demo.vsp is a vsp page which implements WebID checking.\n  The webid_demo.php is a PHP page which implements WebID checking.\n  The webid_demo.html is a HTML (JS) page which implements WebID checking.\n \n" ;
	sioc:has_container	ns2:services ;
	sioc:description	"Checking WebID" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The service is an alternative to using SPARQL queries via the SPARQL protocol against Virtuoso endpoints re. WebID verification i.e., lookup a profile graph to see if WebID and specific Public Key are in a relation.\n  The webid_demo.vsp is a vsp page which implements WebID checking.\n  The webid_demo.php is a PHP page which implements WebID checking.\n  The webid_demo.html is a HTML (JS) page which implements WebID checking.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"HTML-to-Wireless" ;
	sioc:content	"\nPreliminaries\nTraditional HTML-based web pages are not intended for wireless viewing.\nHowever, with a little Virtuoso server-side scripting, you can turn any\nWAP-based wireless phone into a full HTML web browser!\n\nRunning the Demo on a WAP device\nTo access this application via WAP/WML, enter the following URL\ninto a WAP-enabled wireless device:\nhttp:///tutorial/apps/wa_b_1/html2wml.vsp\n\n\nRunning the Demo on a WAP emulator\n\nTo simulate viewing the output on a wireless device. Run the\nRunHtml2wml.html file.\nThen choose a web-based emulator from one below:\n\n\n  Wap.com -\n  This is the most accurate Java and web based emulator, almost to the point\n  of the definitive WAP SDK emulators from Openwave. However, its performance\n  is not always optimal.\n  \n\n  Wapsilon.com -\n  This is a reasonably accurate emulator, but the user interface handling is\n  not quite the same as a real WAP phone.\n  \n\n  Wapmore.com -\n  This is a PDA style emulator. Although its interface is a bit quirky, the\n  performance is reasonable.\n  \n\n  Gelon.net -\n  This is probably the fastest web-based WAP emulator; however, it sometimes\n  exhibits problems displaying WML forms.\n  \n\n  Download WAP SDK -\n  Our recommended option, this standard WAP SDK for emulators from\n  Openwave.com\n  (formerly Phone.com).\n  \n\n\n" ;
	sioc:has_container	ns2:wap ;
	sioc:description	"HTML-to-Wireless Tranformation" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\nTraditional HTML-based web pages are not intended for wireless viewing.\nHowever, with a little Virtuoso server-side scripting, you can turn any\nWAP-based wireless phone into a full HTML web browser!\n\nRunning the Demo on a WAP device\nTo access this application via WAP/WML, enter the following URL\ninto a WAP-enabled wireless device:\nhttp://<hostname>/tutorial/apps/wa_b_1/html2wml.vsp\n\n\nRunning the Demo on a WAP emulator\n\nTo simulate viewing the output on a wireless device. Run the\nRunHtml2wml.html file.\nThen choose a web-based emulator from one below:\n\n\n  Wap.com -\n  This is the most accurate Java and web based emulator, almost to the point\n  of the definitive WAP SDK emulators from Openwave. However, its performance\n  is not always optimal.\n  \n\n  Wapsilon.com -\n  This is a reasonably accurate emulator, but the user interface handling is\n  not quite the same as a real WAP phone.\n  \n\n  Wapmore.com -\n  This is a PDA style emulator. Although its interface is a bit quirky, the\n  performance is reasonable.\n  \n\n  Gelon.net -\n  This is probably the fastest web-based WAP emulator; however, it sometimes\n  exhibits problems displaying WML forms.\n  \n\n  Download WAP SDK -\n  Our recommended option, this standard WAP SDK for emulators from\n  Openwave.com\n  (formerly Phone.com).\n  \n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"WAP Phone Emulator" ;
	sioc:content	"\nPreliminaries\nThis application demonstrates the power of Virtuoso XSL-T by\ntransforming an XML file in real time into a wireless phone emulator,\nusing a simple XSL stylesheet. Although fuller-featured WAP emulators exist,\nthis demo serves to illustrate what can be achieved with a few lines of VSP\ncode and accompanying stylesheet. However, a more comprehensive and\nfuller-featured WAP emulator built around the same concepts may be\navailable soon.\n\nRunning the Demo on a WAP device\nTo access this application, click on 'Run' link below. \n" ;
	sioc:has_container	ns2:wap ;
	sioc:description	"WAP Phone Emulator" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\nThis application demonstrates the power of Virtuoso XSL-T by\ntransforming an XML file in real time into a wireless phone emulator,\nusing a simple XSL stylesheet. Although fuller-featured WAP emulators exist,\nthis demo serves to illustrate what can be achieved with a few lines of VSP\ncode and accompanying stylesheet. However, a more comprehensive and\nfuller-featured WAP emulator built around the same concepts may be\navailable soon.\n\nRunning the Demo on a WAP device\nTo access this application, click on 'Run' link below. \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"WAP based Email" ;
	sioc:content	"\nPreliminaries\nThought the only way to check your email on a wireless phone was via\nYahoo.com? This demo will illustrate how a few VSP scripts on a Virtuoso\nserver can provide a fully-functional wireless E-mail solution. Read messages\nfrom your POP-based email account from any WAP-enabled wireless device, or\nfrom the wireless phone emulators.\n\nRunning the Demo on a WAP device\nTo access this application via WAP/WML, enter the following URL\ninto a WAP-enabled wireless device:\nhttp:///tutorial/apps/wa_b_3/index.vsp\n\n\nEmail WAP Application files\n\n  index.vap - Main page that calls the other files.\n  signup.vsp - Code to register details about a new user.\n  login.vsp - Code to sign-in a registered user.\n  checkmail.vsp - Code to communicate with the POP3 account.\n  logout.vsp - Code to sign-out.\n\n\n\nRunning the Demo on a WAP emulator\n\nTo simulate viewing the output on a wireless device. Run the\nRunWapEmail.html file.\nThen choose a web-based emulator from one below:\n\n\n  Wap.com -\n  This is the most accurate Java and web based emulator, almost to the point\n  of the definitive WAP SDK emulators from Openwave. However, its performance\n  is not always optimal.\n  \n\n  Wapsilon.com -\n  This is a reasonably accurate emulator, but the user interface handling is\n  not quite the same as a real WAP phone.\n  \n\n  Wapmore.com -\n  This is a PDA style emulator. Although its interface is a bit quirky, the\n  performance is reasonable.\n  \n\n  Gelon.net -\n  This is probably the fastest web-based WAP emulator; however, it sometimes\n  exhibits problems displaying WML forms.\n  \n\n  Download WAP SDK -\n  Our recommended option, this standard WAP SDK for emulators from\n  Openwave.com\n  (formerly Phone.com).\n  \n\n\n" ;
	sioc:has_container	ns2:wap ;
	sioc:description	"WAP Phone E-mail Retrieval" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\nThought the only way to check your email on a wireless phone was via\nYahoo.com? This demo will illustrate how a few VSP scripts on a Virtuoso\nserver can provide a fully-functional wireless E-mail solution. Read messages\nfrom your POP-based email account from any WAP-enabled wireless device, or\nfrom the wireless phone emulators.\n\nRunning the Demo on a WAP device\nTo access this application via WAP/WML, enter the following URL\ninto a WAP-enabled wireless device:\nhttp://<hostname>/tutorial/apps/wa_b_3/index.vsp\n\n\nEmail WAP Application files\n\n  index.vap - Main page that calls the other files.\n  signup.vsp - Code to register details about a new user.\n  login.vsp - Code to sign-in a registered user.\n  checkmail.vsp - Code to communicate with the POP3 account.\n  logout.vsp - Code to sign-out.\n\n\n\nRunning the Demo on a WAP emulator\n\nTo simulate viewing the output on a wireless device. Run the\nRunWapEmail.html file.\nThen choose a web-based emulator from one below:\n\n\n  Wap.com -\n  This is the most accurate Java and web based emulator, almost to the point\n  of the definitive WAP SDK emulators from Openwave. However, its performance\n  is not always optimal.\n  \n\n  Wapsilon.com -\n  This is a reasonably accurate emulator, but the user interface handling is\n  not quite the same as a real WAP phone.\n  \n\n  Wapmore.com -\n  This is a PDA style emulator. Although its interface is a bit quirky, the\n  performance is reasonable.\n  \n\n  Gelon.net -\n  This is probably the fastest web-based WAP emulator; however, it sometimes\n  exhibits problems displaying WML forms.\n  \n\n  Download WAP SDK -\n  Our recommended option, this standard WAP SDK for emulators from\n  Openwave.com\n  (formerly Phone.com).\n  \n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Echo" ;
	sioc:content	"\n    Example\n    The example contains code for simple echo service.\n\tIt accepts a string as an input and echoes back to the client.\n\tSo it shows the core BPEL concepts for building services.\n    To build and run the example follow the steps bellow:\n\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n              Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the \"Load Deployment Descriptor URI\" field type 'http://host:port/BPELDemo/echo/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n" ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"Simple BPEL4WS process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    The example contains code for simple echo service.\n\tIt accepts a string as an input and echoes back to the client.\n\tSo it shows the core BPEL concepts for building services.\n    To build and run the example follow the steps bellow:\n\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n              Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the "Load Deployment Descriptor URI" field type 'http://host:port/BPELDemo/echo/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Fibonacci function" ;
	sioc:content	"\n    Example\n    The Fibonacci function calculates number based on following algorithm:\n    \n    \n\tint fi (int i)\n\t  {\n\t    if (i < 2)\n\t      return i;\n\t    return fi (i-1) + fi (i-2)\n\t  }\n\t\n    The example contains code for a simple Fibonacci function service.\n\tIt accepts an integer number as an input and calculates the Fibonacci number.\n\tThe process like the Fibonacci function does a recursive syncronous invocation of itself.\n    \n        The example is allowed with values less than 6. If is entered value greater then 6,\n        will be printed the message \"Entry values greater then 6 are not allowed!\"\n        and the input entry value will be initialized to 6.\n    \n    To build and run the example follow the steps bellow:\n\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n              Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the \"Process name\" field type 'Fi' in order the process to be invoked successfully.\n    In the \"Load Deployment Descriptor URI\" field type 'http://host:port/BPELDemo/fi/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n" ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"Fibonacci function BPEL4WS process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    The Fibonacci function calculates number based on following algorithm:\n    \n    \n\tint fi (int i)\n\t  {\n\t    if (i < 2)\n\t      return i;\n\t    return fi (i-1) + fi (i-2)\n\t  }\n\t\n    The example contains code for a simple Fibonacci function service.\n\tIt accepts an integer number as an input and calculates the Fibonacci number.\n\tThe process like the Fibonacci function does a recursive syncronous invocation of itself.\n    \n        The example is allowed with values less than 6. If is entered value greater then 6,\n        will be printed the message "Entry values greater then 6 are not allowed!"\n        and the input entry value will be initialized to 6.\n    \n    To build and run the example follow the steps bellow:\n\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n              Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the "Process name" field type 'Fi' in order the process to be invoked successfully.\n    In the "Load Deployment Descriptor URI" field type 'http://host:port/BPELDemo/fi/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Loan Flow" ;
	sioc:content	"\n    Example\n\n    This example needs BPEL4WS VAD package to be installed on the server, before trying it.\n\tTo learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n    \n    The example script creates services for Credit Rating, United Loan and Star Loan.\n    The WSDL descriptions for these services are available via CreditRating.vsp,\n\tUnitedLoan.vsp and StarLoan.vsp.\n    \n    On the initial load the BPEL LoanFlow process will be deployed.\n    The test client can be used to test the BPEL LoanFlow process.\n    \n      You can test the example using BPEL UI also by going to 'Processes' tab and\n      click \"Test\" in the listing. This goes to a page allowing you to enter a\n      start message for creating a new instance of this process.\n     \n\n" ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"LoanFlow process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n\n    This example needs BPEL4WS VAD package to be installed on the server, before trying it.\n\tTo learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n    \n    The example script creates services for Credit Rating, United Loan and Star Loan.\n    The WSDL descriptions for these services are available via CreditRating.vsp,\n\tUnitedLoan.vsp and StarLoan.vsp.\n    \n    On the initial load the BPEL LoanFlow process will be deployed.\n    The test client can be used to test the BPEL LoanFlow process.\n    \n      You can test the example using BPEL UI also by going to 'Processes' tab and\n      click "Test" in the listing. This goes to a page allowing you to enter a\n      start message for creating a new instance of this process.\n     \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SecLoan" ;
	sioc:content	"\n    Example\n    The example contains code for LoanFlow Using WS-Security.\n    \n\tThe following are requirments to the caller and the process:\n    \n    \n\tThe caller must supply a signed and encrypted SOAP message.\n\tProcess must reply from a separate HTTP connection to the endpoint designated by the  caller's ReplyTo WSA header.\n        The process' reply must contain a  signed and encrypted SOAP message.\n        The X.509 certificates must be used to sign the message.\n        The Session keys can be tripple-des or AES (128, 192 or 256 bit quality).\n        A Session key must be encrypted with the partner's RSA public key.\n        The test certificates from MS WSE 2.0 toolkit can be used.\n    \n    To build the example follow the steps bellow:\n    \n      This example needs BPEL4WS VAD package to be installed on the server, before trying it. To learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n      The example script creates services for Credit Rating, United Loan and Star Loan.\n      The WSDL descriptions for these services are available via CreditRating.vsp, UnitedLoan.vsp and StarLoan.vsp.\n      On the initial load the BPEL LoanFlow Using WS-Security process will be deployed.\n    \n    To run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      To enable debugging for the process with name 'SecLoanFlow' check the Debug checkbox in the listing.\n        This will cause all instances of the process to run in single-step mode,\n        pausing at each send or receive of a message. The debug console allows\n        interacting with instances in this mode.\n      \n      To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n    \n  " ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"LoanFlow process using WS-Security" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    The example contains code for LoanFlow Using WS-Security.\n    \n\tThe following are requirments to the caller and the process:\n    \n    \n\tThe caller must supply a signed and encrypted SOAP message.\n\tProcess must reply from a separate HTTP connection to the endpoint designated by the  caller's ReplyTo WSA header.\n        The process' reply must contain a  signed and encrypted SOAP message.\n        The X.509 certificates must be used to sign the message.\n        The Session keys can be tripple-des or AES (128, 192 or 256 bit quality).\n        A Session key must be encrypted with the partner's RSA public key.\n        The test certificates from MS WSE 2.0 toolkit can be used.\n    \n    To build the example follow the steps bellow:\n    \n      This example needs BPEL4WS VAD package to be installed on the server, before trying it. To learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n      The example script creates services for Credit Rating, United Loan and Star Loan.\n      The WSDL descriptions for these services are available via CreditRating.vsp, UnitedLoan.vsp and StarLoan.vsp.\n      On the initial load the BPEL LoanFlow Using WS-Security process will be deployed.\n    \n    To run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      To enable debugging for the process with name 'SecLoanFlow' check the Debug checkbox in the listing.\n        This will cause all instances of the process to run in single-step mode,\n        pausing at each send or receive of a message. The debug console allows\n        interacting with instances in this mode.\n      \n      To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"RMLoan" ;
	sioc:content	"\n    Example\n    The example contains code for Reliable Loan Flow.\n    \n\tInvokation of loan services must be done using WS-RM protocol and rules:\n    \n    \n\tThe caller must supply a valid WSA header 'ReplyTo' containing a valid response URL.\n\t\n           The Process must send a reply from a separate HTTP connection to the endpoint\n           designated by the caller's ReplyTo WSA header using WS-RM.\n        \n    \n    To build the example follow the steps bellow:\n    \n      This example needs BPEL4WS VAD package to be installed on the server, before trying it. To learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n      This example depends from the SecLoan example. Make sure there is initial load for this example.\n      The example script creates services for Credit Rating, United Loan and Star Loan.\n      The WSDL descriptions for these services are available via CreditRating.vsp, UnitedLoan.vsp and StarLoan.vsp.\n      On the initial load the BPEL Reliable LoanFlow process will be deployed.\n    \n    To run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      To enable debugging for the process with name 'SecLoanFlow' check the Debug checkbox in the listing.\n        This will cause all instances of the process to run in single-step mode,\n        pausing at each send or receive of a message. The debug console allows\n        interacting with instances in this mode.\n      \n      To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n    \n  " ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"Reliable Loan Flow process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    The example contains code for Reliable Loan Flow.\n    \n\tInvokation of loan services must be done using WS-RM protocol and rules:\n    \n    \n\tThe caller must supply a valid WSA header 'ReplyTo' containing a valid response URL.\n\t\n           The Process must send a reply from a separate HTTP connection to the endpoint\n           designated by the caller's ReplyTo WSA header using WS-RM.\n        \n    \n    To build the example follow the steps bellow:\n    \n      This example needs BPEL4WS VAD package to be installed on the server, before trying it. To learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n      This example depends from the SecLoan example. Make sure there is initial load for this example.\n      The example script creates services for Credit Rating, United Loan and Star Loan.\n      The WSDL descriptions for these services are available via CreditRating.vsp, UnitedLoan.vsp and StarLoan.vsp.\n      On the initial load the BPEL Reliable LoanFlow process will be deployed.\n    \n    To run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      To enable debugging for the process with name 'SecLoanFlow' check the Debug checkbox in the listing.\n        This will cause all instances of the process to run in single-step mode,\n        pausing at each send or receive of a message. The debug console allows\n        interacting with instances in this mode.\n      \n      To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"SecRMLoan" ;
	sioc:content	"\n    Example\n    This example is a combination of Secure and Reliable Loan Flow examples.\n    \n        The calls to the asynchronous services must be done via WS-RM protocol.\n    \n    \n\tThe calls to partners must be encrypted and signed using the rules:\n    \n    \n\tThe caller must supply a signed and encrypted SOAP message.\n\tThe process must reply from a separate HTTP connection to the endpoint designated by the caller's ReplyTo WSA header.\n        The process' reply must contain a signed and encrypted SOAP message.\n        X.509 certificates must be used to sign the message.\n        The session keys can be tripple-des or AES (128, 192 or 256 bit quality).\n        A Session key must be encrypted with the partner's RSA public key.\n        The test certificates from MS WSE 2.0 toolkit can be used.\n    \n    To build the example follow the steps bellow:\n    \n      This example needs BPEL4WS VAD package to be installed on the server, before trying it. To learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n      This example depends from the SecLoan and the RMLoan example. Make sure there are initial loads for these examples.\n      The example script creates services for Credit Rating, United Loan and Star Loan.\n      The WSDL descriptions for these services are available via CreditRating.vsp, UnitedLoan.vsp and StarLoan.vsp.\n      On the initial load the BPEL Secure and Reliable Loan Flow process will be deployed.\n    \n    To run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      To enable debugging for the process with name 'SecRMLoanFlow' check the Debug checkbox in the listing.\n        This will cause all instances of the process to run in single-step mode,\n        pausing at each send or receive of a message. The debug console allows\n        interacting with instances in this mode.\n      \n      To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n    \n  " ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"Secure and Reliable Loan Flow process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    This example is a combination of Secure and Reliable Loan Flow examples.\n    \n        The calls to the asynchronous services must be done via WS-RM protocol.\n    \n    \n\tThe calls to partners must be encrypted and signed using the rules:\n    \n    \n\tThe caller must supply a signed and encrypted SOAP message.\n\tThe process must reply from a separate HTTP connection to the endpoint designated by the caller's ReplyTo WSA header.\n        The process' reply must contain a signed and encrypted SOAP message.\n        X.509 certificates must be used to sign the message.\n        The session keys can be tripple-des or AES (128, 192 or 256 bit quality).\n        A Session key must be encrypted with the partner's RSA public key.\n        The test certificates from MS WSE 2.0 toolkit can be used.\n    \n    To build the example follow the steps bellow:\n    \n      This example needs BPEL4WS VAD package to be installed on the server, before trying it. To learn more about VAD please visit http://docs.openlinksw.com/virtuoso/VAD.html.\n      This example depends from the SecLoan and the RMLoan example. Make sure there are initial loads for these examples.\n      The example script creates services for Credit Rating, United Loan and Star Loan.\n      The WSDL descriptions for these services are available via CreditRating.vsp, UnitedLoan.vsp and StarLoan.vsp.\n      On the initial load the BPEL Secure and Reliable Loan Flow process will be deployed.\n    \n    To run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      To enable debugging for the process with name 'SecRMLoanFlow' check the Debug checkbox in the listing.\n        This will cause all instances of the process to run in single-step mode,\n        pausing at each send or receive of a message. The debug console allows\n        interacting with instances in this mode.\n      \n      To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Inventory Service" ;
	sioc:content	"\n      Example\n      \n\t  The demo is a service which is invoked on time\n\t  basis in order to update an inventory. This\n\t  demo using the Northwind demo Database as an\n\t  inventory.\n      \n      \n\t  The client generates a list of items that\n\t  are under 10 units using SQLX. This XML\n\t  document is sent to the inventory process\n\t  and will make new process instance.\n      \n      \ncreate procedure DB..update_inventory ()\n{\n  declare req any;\n  whenever not found goto nf;\n  -- the following statement generates an XML document using SQLX\n  --\n  -- the result would like :\n  -- 510...\n  --\n  select xmlelement(Items,\n  \t\txmlattributes ('http://temp.org' as xmlns),\n\t\txmlagg (\n\t\t  xmlelement (item,\n\t\t    xmlelement (ProductID, ProductID),\n\t\t    xmlelement (Quantity, UnitsInStock + 10)\n\t\t    ))) into req\n      from Demo..Products where UnitsInStock < 10 and Discontinued = 0;\n\n  -- call the process with generated XML document as a input parameter\n  soap_client (\turl=>'http://host:port/InventorySvc',\n      \t\toperation=>'initiate',\n\t\tparameters=>vector ('par0', req),\n\t\tsoap_action=>'initiate',\n\t\tstyle=>1\n      );\n\n  nf:\n  return;\n}\n\t  \n      \n\t  The process will loop over all items in input\n\t  and for each will ask for quote.\n\t  Also the quote service will return a list of\n\t  wholesalers and their prices. Then the process will\n\t  choose the best price and will make an order using specific\n\t  partner URL (this is simulated by appending a\n\t  URL parameter to the service URL).\n\t  When an order confirmation is received, the process\n\t  will update the inventory.\n      \n      \n\t  At the end of process it will sent an e-mail\n\t  to the pre-configured operator address.\n      \n      \n\t  The following code is a pseudo-code which describes the process flow:\n      \n      \n{\n  declare i, l int;\n  declare j, k, oid int;\n  declare in, out, ord any;\n\n  in = receive ();\n\n  l = length (in);\n  for (i = 0; i < l; i++)\n    {\n      declare q, best any;\n      q = getQuote (in[i]);\n      k = length (q);\n      for (j := 0; j < k; j++)\n        {\n          if (q.price < best.price)\n            best = q;\n        }\n      oid = newOrder (best.url, in[i].item, in[i].quantity, best.price);\n      update Demo.demo.Products set UnitsOnStock = UnitsOnStock + in[i].quantity where\n           ProductID = in[i].ProductID;\n    }\n   sendMail ('Inventory have been updated');\n}\n\t  \n      \n\t  To run the example follow the steps bellow:\n      \n\n    Load the initial setup file: 'store.sql'\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n              Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    In the \"Load Deployment Descriptor URI\" field type 'http://host:port/BPELDemo/sqlexec/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    Run via ISQL the DB..update_inventory () procedure.\n    Also the update_inventory procedure can be used as a scheduled task (see 'Virtuoso scheduler' section in the documentation for details).\n    \n\n" ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"Using SQL binding and SQLX to generate requests process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n      Example\n      \n\t  The demo is a service which is invoked on time\n\t  basis in order to update an inventory. This\n\t  demo using the Northwind demo Database as an\n\t  inventory.\n      \n      \n\t  The client generates a list of items that\n\t  are under 10 units using SQLX. This XML\n\t  document is sent to the inventory process\n\t  and will make new process instance.\n      \n      \ncreate procedure DB..update_inventory ()\n{\n  declare req any;\n  whenever not found goto nf;\n  -- the following statement generates an XML document using SQLX\n  --\n  -- the result would like :\n  -- <Items xmlns="http://temp.org"><Product><ProductID>5</ProductID><Quantity>10</Quantity></Product>...</Items>\n  --\n  select xmlelement(Items,\n  \t\txmlattributes ('http://temp.org' as xmlns),\n\t\txmlagg (\n\t\t  xmlelement (item,\n\t\t    xmlelement (ProductID, ProductID),\n\t\t    xmlelement (Quantity, UnitsInStock + 10)\n\t\t    ))) into req\n      from Demo..Products where UnitsInStock < 10 and Discontinued = 0;\n\n  -- call the process with generated XML document as a input parameter\n  soap_client (\turl=>'http://host:port/InventorySvc',\n      \t\toperation=>'initiate',\n\t\tparameters=>vector ('par0', req),\n\t\tsoap_action=>'initiate',\n\t\tstyle=>1\n      );\n\n  nf:\n  return;\n}\n\t  \n      \n\t  The process will loop over all items in input\n\t  and for each will ask for quote.\n\t  Also the quote service will return a list of\n\t  wholesalers and their prices. Then the process will\n\t  choose the best price and will make an order using specific\n\t  partner URL (this is simulated by appending a\n\t  URL parameter to the service URL).\n\t  When an order confirmation is received, the process\n\t  will update the inventory.\n      \n      \n\t  At the end of process it will sent an e-mail\n\t  to the pre-configured operator address.\n      \n      \n\t  The following code is a pseudo-code which describes the process flow:\n      \n      \n{\n  declare i, l int;\n  declare j, k, oid int;\n  declare in, out, ord any;\n\n  in = receive ();\n\n  l = length (in);\n  for (i = 0; i < l; i++)\n    {\n      declare q, best any;\n      q = getQuote (in[i]);\n      k = length (q);\n      for (j := 0; j < k; j++)\n        {\n          if (q.price < best.price)\n            best = q;\n        }\n      oid = newOrder (best.url, in[i].item, in[i].quantity, best.price);\n      update Demo.demo.Products set UnitsOnStock = UnitsOnStock + in[i].quantity where\n           ProductID = in[i].ProductID;\n    }\n   sendMail ('Inventory have been updated');\n}\n\t  \n      \n\t  To run the example follow the steps bellow:\n      \n\n    Load the initial setup file: 'store.sql'\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n              Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    In the "Load Deployment Descriptor URI" field type 'http://host:port/BPELDemo/sqlexec/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    Run via ISQL the DB..update_inventory () procedure.\n    Also the update_inventory procedure can be used as a scheduled task (see 'Virtuoso scheduler' section in the documentation for details).\n    \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"UseCases" ;
	sioc:content	"\n      Purpose\n      \n\t  This is a Technical Use Case as per OASIS MS01 document,\n\t  illustrating various options for data manipulation inside a BPEL process.\n      \n      The following situations are shown:\n      \n\t  MS01-1: Variable initialization.\n\t  MS01-2: Assignment of string, numeric, boolean and date values.\n\t  MS01-3: Assignment of variables by copying other variable's values.\n\t  MS01-4: Sample XPath calculations.\n\t  MS01-5&6: Working with array structures.\n      \n      \n\t  To run the example follow the steps bellow:\n      \n      \n        Load the initial setup file: 'MS01.sql'\n        Login into the BPEL UI via http://host:port/BPELGUI to test the processes.\n       \n    " ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"BPEL Data Manipulation Options processes" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n      Purpose\n      \n\t  This is a Technical Use Case as per OASIS MS01 document,\n\t  illustrating various options for data manipulation inside a BPEL process.\n      \n      The following situations are shown:\n      \n\t  MS01-1: Variable initialization.\n\t  MS01-2: Assignment of string, numeric, boolean and date values.\n\t  MS01-3: Assignment of variables by copying other variable's values.\n\t  MS01-4: Sample XPath calculations.\n\t  MS01-5&6: Working with array structures.\n      \n      \n\t  To run the example follow the steps bellow:\n      \n      \n        Load the initial setup file: 'MS01.sql'\n        Login into the BPEL UI via http://host:port/BPELGUI to test the processes.\n       \n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Java Execution" ;
	sioc:content	"\n    Example\n    This example demonstrates how the Java code can be embedded in a BPEL process.\n    \n    The example contains java code which gets data from BPEL variable, prints string to the console and returns string.\n    \n    To build and run the example follow the steps bellow:\n\n    Make sure system calls are enabled in virtuoso.ini (AllowOSCalls parameter).\n    Make sure CLASSPATH environment variable contains \"classlib\" entry.\n    Make sure you are running java enabled server (virtuoso-odbc-javavm-t or virtuoso-odbc-javavm-clr-t).\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    \n      From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n      Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the \"Load Deployment Descriptor URI\" field type 'http://host:port/BPELDemo/java_exec/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n" ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"Java Execution BPEL4WS process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    This example demonstrates how the Java code can be embedded in a BPEL process.\n    \n    The example contains java code which gets data from BPEL variable, prints string to the console and returns string.\n    \n    To build and run the example follow the steps bellow:\n\n    Make sure system calls are enabled in virtuoso.ini (AllowOSCalls parameter).\n    Make sure CLASSPATH environment variable contains "classlib" entry.\n    Make sure you are running java enabled server (virtuoso-odbc-javavm-t or virtuoso-odbc-javavm-clr-t).\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    \n      From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n      Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the "Load Deployment Descriptor URI" field type 'http://host:port/BPELDemo/java_exec/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	".NET Execution" ;
	sioc:content	"\n    Example\n    This example demonstrates how the C# code can be embedded in a BPEL process.\n    \n    The example contains .NET code which gets data from BPEL variable, prints string to the console and returns string.\n    \n    To build and run the example follow the steps bellow:\n    \n      \n        Initialize \"CLRAssembliesDir\" configuration field at BPEL UI 'Configuration' tab\n        with the directory name where the dlls from the distribution are located ( t.e. OpenLink.Data.VirtuosoClient.dll, virt_bpel4ws.dll etc).\n        If you have problems initializing this CLRAssembliesDir, ask your system administrator to initialize this directory for you\n        (and copy all needed DLLs there) or to tell you where this directory is located.\n      \n      Make sure you are running CLR or Mono enabled server (virtuoso-odbc-clr-t, virtuoso-odbc-mono-t, etc).\n      Login into the BPEL UI via http://host:port/BPELGUI.\n     \n       From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n       Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n     \n     For the given entry form in the \"Load Deployment Descriptor URI\" field type 'http://host:port/BPELDemo/clr_exec/bpel.xml'.\n     Choose the 'Import Process' button.\n     Choose the 'Compile process' button.\n     If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n     To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n   \n " ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	".NET Execution BPEL4WS process" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    This example demonstrates how the C# code can be embedded in a BPEL process.\n    \n    The example contains .NET code which gets data from BPEL variable, prints string to the console and returns string.\n    \n    To build and run the example follow the steps bellow:\n    \n      \n        Initialize "CLRAssembliesDir" configuration field at BPEL UI 'Configuration' tab\n        with the directory name where the dlls from the distribution are located ( t.e. OpenLink.Data.VirtuosoClient.dll, virt_bpel4ws.dll etc).\n        If you have problems initializing this CLRAssembliesDir, ask your system administrator to initialize this directory for you\n        (and copy all needed DLLs there) or to tell you where this directory is located.\n      \n      Make sure you are running CLR or Mono enabled server (virtuoso-odbc-clr-t, virtuoso-odbc-mono-t, etc).\n      Login into the BPEL UI via http://host:port/BPELGUI.\n     \n       From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n       Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n     \n     For the given entry form in the "Load Deployment Descriptor URI" field type 'http://host:port/BPELDemo/clr_exec/bpel.xml'.\n     Choose the 'Import Process' button.\n     Choose the 'Compile process' button.\n     If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n     To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n   \n \n " .
	rdf:type	foaf:Document ;
	dc:title	"processXSLT" ;
	sioc:content	"\n    Example\n    This example demonstrates how the XSLT styles can be used in BPEL script.\n    \n    The example contains invoking the processXSLT XPath function which transforms data from a BPEL variable.\n    \n    To build and run the example follow the steps bellow:\n\n    Load the initial setup file: ' processXSLT.sql'\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    \n      From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n      Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the \"Load Deployment Descriptor URI\" field type 'http://host:port/BPELDemo/processXSLT/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n" ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"XSLT processing example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    This example demonstrates how the XSLT styles can be used in BPEL script.\n    \n    The example contains invoking the processXSLT XPath function which transforms data from a BPEL variable.\n    \n    To build and run the example follow the steps bellow:\n\n    Load the initial setup file: ' processXSLT.sql'\n    Login into the BPEL UI via http://host:port/BPELGUI.\n    \n      From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n      Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n    \n    For the given entry form in the "Load Deployment Descriptor URI" field type 'http://host:port/BPELDemo/processXSLT/bpel.xml'.\n    Choose the 'Import Process' button.\n    Choose the 'Compile process' button.\n    If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n    To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"processXQuery" ;
	sioc:content	"\n    Example\n    This example demonstrates how the XQuery program can be used in a BPEL process.\n    \n    The example contains invoking the processXQuery XPath function which returns a result of XQuery program.\n    \n    To build and run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      \n        From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n        Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n      \n      For the given entry form in the \"Load Deployment Descriptor URI\" field type 'http://host:port/BPELDemo/processXQuery/bpel.xml'.\n      Choose the 'Import Process' button.\n      Choose the 'Compile process' button.\n      If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n      To test the process click \"Test\" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n      Enter \"2\" as id and \"Kathreen Smith\" as \"seller\" for the test form fields.\n    \n  " ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"XQuery processing example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    This example demonstrates how the XQuery program can be used in a BPEL process.\n    \n    The example contains invoking the processXQuery XPath function which returns a result of XQuery program.\n    \n    To build and run the example follow the steps bellow:\n    \n      Login into the BPEL UI via http://host:port/BPELGUI.\n      \n        From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n        Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n      \n      For the given entry form in the "Load Deployment Descriptor URI" field type 'http://host:port/BPELDemo/processXQuery/bpel.xml'.\n      Choose the 'Import Process' button.\n      Choose the 'Compile process' button.\n      If compilation succeeds, will go to the 'Processes' page where the process will be in the given processes list.\n      To test the process click "Test" in the listing. This goes to a page allowing you to enter a start message for creating a new instance of this process.\n      Enter "2" as id and "Kathreen Smith" as "seller" for the test form fields.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"processXSQL" ;
	sioc:content	"\n    Example\n    \n      This example demonstrates how the XSQL scripts can be used in a BPEL example.\n    \n    \n      The example contains the XSQL file selectCustomers.xsql which selects a customer by given SSN.\n    \n    \n      To build and run the example follow the steps bellow:\n    \n    \n      \n        Login into the BPEL UI via http://host:port/BPELGUI.\n      \n      \n        From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n        Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n      \n      \n        For the given entry form in the \"Load Deployment Descriptor URI\" field type\n        'http://host:port/BPELDemo/processXSQL/bpel.xml'.\n      \n      \n        Choose the 'Import Process' button.\n      \n      \n        Choose the 'Compile process' button.\n      \n      \n        If compilation succeeds, will go to the 'Processes' page where the process\n        will be in the given processes list.\n      \n      \n        To test the process click \"Test\" in the listing. This goes to a page\n        allowing you to enter a start message for creating a new instance of this process.\n      \n    \n  " ;
	sioc:has_container	ns2:bpeldemo ;
	sioc:description	"XSQL processing example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\n    Example\n    \n      This example demonstrates how the XSQL scripts can be used in a BPEL example.\n    \n    \n      The example contains the XSQL file selectCustomers.xsql which selects a customer by given SSN.\n    \n    \n      To build and run the example follow the steps bellow:\n    \n    \n      \n        Login into the BPEL UI via http://host:port/BPELGUI.\n      \n      \n        From the 'Home' tab page go to section 'Tasks' and click 'Upload Process' link.\n        Another way is to choose 'Processes' tab and go to the 'Process Upload' sub-tab.\n      \n      \n        For the given entry form in the "Load Deployment Descriptor URI" field type\n        'http://host:port/BPELDemo/processXSQL/bpel.xml'.\n      \n      \n        Choose the 'Import Process' button.\n      \n      \n        Choose the 'Compile process' button.\n      \n      \n        If compilation succeeds, will go to the 'Processes' page where the process\n        will be in the given processes list.\n      \n      \n        To test the process click "Test" in the listing. This goes to a page\n        allowing you to enter a start message for creating a new instance of this process.\n      \n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Making an Executable Directory" ;
	sioc:content	"\nPreliminaries\nIt is necessary to complete the configuration of the executable directory before any of the subsequent\ntutorials  will function. It is therefore important to follow these steps carefully before trying to run the\nvs_b_1.vsp file.\nThe example demonstrated here creates an executable directory depending on either tutorial_dav.vad package was installled\n(i.e. the tutorials are in the DAV repository) or the tutorial_filesystem.dav package ( the tutorials have FS location.)\n\n\nThese tutorials are designed for use on an OpenLink Virtuoso V3.0 VDBMS. Earlier versions will not work.\n\nLogin to the Conductor UI using the dba account.\n\n\nCreate the database user account vspdemo\n\n  Go to \"System Admin\" tab and then go to the \"User Accounts\" tab.\n  Click the \"Create New Account\" link.\n  Enter for Account Name \"vspdemo\" and a desired password with confirmation. Check the check-box for \"Allow SQL/ODBC Logins\".\n  Leave the rest of the fields at their default.\n  Press the \"Save\" button. You will see the vspdemo now listed under current user accounts.\n\n\nCheck tutorials type and path of installation (DAV or FS)\n\n  Go to \"Database\" tab and then go to the \"Interactive SQL\" tab.\n  Enter in the text area the following:\n\nselect TUTORIAL_VDIR_DIR();\n\n  \n  Click the \"Execute\" button.\n  The found result will be the tutorials Path location.\n  Click the button \"Return\".\n  Enter in the text area the following:\n\nselect TUTORIAL_IS_DAV();\n\n  \n  Click the \"Execute\" button.\n  The returned result will be the tutorials Type location:\n1 - tutorials are installed in DAV, or\n0 - tutorials are installed in the local FS.\n\n\nAllow VSP files to be run by vspdemo user with directory browsing allowed\n\n  Go to \"Web Application Server\" tab and then go to the \"Virtual Domains & Directories\" tab.\n  From the given list of HTTP Hosts click the icon in front of the Interface value.\n  Click the \"Add new directory\" link.\n  If tutorials Type location is FS, then choose the \"File System\" type and press the button\n\"Next>>\"; If tutorials Type location is DAV, then choose the \"WebDAV domain\" type and press the\nbutton \"Next>>\".\n  \n  Enter \"/vs_b_1\" for Path,\nEnter the tutorials Path location with \"/tutorial/web/\" at the end for physical path (for ex. /vad/vsp/tutorial/web/ or /DAV/VAD/tutorial/web/),\nselect \"vspdemo\" for the VSP user,\nselect \"Allow Directory Browsing\" checkbox and then press the \"Save Changes\" button.\n\nTo test the new directory: enter the \"http://host:port/vs_b_1\" in browser. For example\nhttp://localhost:8889 as the URL. If all is ok, the content of the web\ntutorial directory is shown.\n\nEquivalent SQL commands to achieve executable directory\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create the user \"vspdemo\"\n  \nSQL> create user vspdemo;\nSQL> user_set_qualifier ('vspdemo', 'vspdemo');\n  \n  Create the virtual directory with user for execution \"vspdemo\"\n  \nSQL> VHOST_REMOVE (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/vs_b_1');\nSQL> vhost_define (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/vs_b_1',\n     ppath=>TUTORIAL_VDIR_DIR() || '/tutorial/web/',vsp_user=>'vspdemo', is_brws=>1, is_dav=>TUTORIAL_IS_DAV());\n  \n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Making an executable directory in Virtuoso's Web server space." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\nIt is necessary to complete the configuration of the executable directory before any of the subsequent\ntutorials  will function. It is therefore important to follow these steps carefully before trying to run the\nvs_b_1.vsp file.\nThe example demonstrated here creates an executable directory depending on either tutorial_dav.vad package was installled\n(i.e. the tutorials are in the DAV repository) or the tutorial_filesystem.dav package ( the tutorials have FS location.)\n\n\nThese tutorials are designed for use on an OpenLink Virtuoso V3.0 VDBMS. Earlier versions will not work.\n\nLogin to the Conductor UI using the dba account.\n\n\nCreate the database user account vspdemo\n\n  Go to "System Admin" tab and then go to the "User Accounts" tab.\n  Click the "Create New Account" link.\n  Enter for Account Name "vspdemo" and a desired password with confirmation. Check the check-box for "Allow SQL/ODBC Logins".\n  Leave the rest of the fields at their default.\n  Press the "Save" button. You will see the vspdemo now listed under current user accounts.\n\n\nCheck tutorials type and path of installation (DAV or FS)\n\n  Go to "Database" tab and then go to the "Interactive SQL" tab.\n  Enter in the text area the following:\n\nselect TUTORIAL_VDIR_DIR();\n\n  \n  Click the "Execute" button.\n  The found result will be the tutorials Path location.\n  Click the button "Return".\n  Enter in the text area the following:\n\nselect TUTORIAL_IS_DAV();\n\n  \n  Click the "Execute" button.\n  The returned result will be the tutorials Type location:\n1 - tutorials are installed in DAV, or\n0 - tutorials are installed in the local FS.\n\n\nAllow VSP files to be run by vspdemo user with directory browsing allowed\n\n  Go to "Web Application Server" tab and then go to the "Virtual Domains & Directories" tab.\n  From the given list of HTTP Hosts click the icon in front of the Interface value.\n  Click the "Add new directory" link.\n  If tutorials Type location is FS, then choose the "File System" type and press the button\n"Next>>"; If tutorials Type location is DAV, then choose the "WebDAV domain" type and press the\nbutton "Next>>".\n  \n  Enter "/vs_b_1" for Path,\nEnter the tutorials Path location with "/tutorial/web/" at the end for physical path (for ex. /vad/vsp/tutorial/web/ or /DAV/VAD/tutorial/web/),\nselect "vspdemo" for the VSP user,\nselect "Allow Directory Browsing" checkbox and then press the "Save Changes" button.\n\nTo test the new directory: enter the "http://host:port/vs_b_1" in browser. For example\nhttp://localhost:8889 as the URL. If all is ok, the content of the web\ntutorial directory is shown.\n\nEquivalent SQL commands to achieve executable directory\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create the user "vspdemo"\n  \nSQL> create user vspdemo;\nSQL> user_set_qualifier ('vspdemo', 'vspdemo');\n  \n  Create the virtual directory with user for execution "vspdemo"\n  \nSQL> VHOST_REMOVE (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/vs_b_1');\nSQL> vhost_define (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/vs_b_1',\n     ppath=>TUTORIAL_VDIR_DIR() || '/tutorial/web/',vsp_user=>'vspdemo', is_brws=>1, is_dav=>TUTORIAL_IS_DAV());\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Syntax of a Page" ;
	sioc:content	"\nPreliminaries\n\n  The pages with active content are named Virtuoso Server Pages, or VSP in short.\n  These pages consist of Virtuoso PL and HTML code.\n  The Virtuoso Web server executes only files (resources) with the \".vsp\" extension.\n  The VSP file can contain VSP blocks and HTML blocks\n  The VSP block contains the PL code\n   \n    The  marks the end of a VSP block.\n   \n  The HTML block is everything outside of a VSP block.\n  The VSP shortcut in an HTML block is used to include value.\n   \n    The  marks the end of a VSP shortcut.  \n   \n\n\nExample\nThe demonstration page uses the 	rdf:type	foaf:Document ;
	dc:title	"Accessing Data in the Request" ;
	sioc:content	"\nPreliminaries\n\n    Data supplied to a VSP is normally posted from a form.\n    Pressing a form submit button causes the browser to pass the data to the server.\n    The form data may be encoded in two forms: www-url-encoded or multipart/form-data.\n\n\nProcessing of the form data in VSPs.\n\n  When the request arrives, the web server parses the request and creates three input arguments for VSP processing:\n  \n    path - array with path elements of the requested URL path. Ie. if the request is \"http://foo.bar/a/b/c\" then \"path\" argument will be a vector ('a','b','c').\n    params - array with name and value pairs of the passed form parameters\n    lines - the vector of HTTP request header lines\n  \n  The form data is held in the \"params\" argument.\n  The value of a named parameter can be extracted from the \"params\" array in two ways:\n    \n      Using the get_keyword function:\n         declare x varchar;\nx := get_keyword('fieldname', params, 'default value');\n      Using the {?'variable_name'} VSP shortcut.\n         x := {?'fieldname'};\n    \n\n\nForm example - A Simple Calculator.\nThe user can enter two numbers, and choose a desired operation.\nPressing the \"=\" button causes the form to be sent to the server. The VSP execution will show the result of\nthe calculation. This example uses the get_keyword function to retrieve the parameters.\n\nForm example - Insert table data\nThe second example demonstrates inserting the user entered form data into a table.\nThis example uses the {?''} shortcuts for accessing the form data. The data in the table will be shown\nbelow the form, ordered by date. You must run the sample SQL first to create the table.\n\nNote\nNote that both examples do not handle the SQL errors.\nThe handling of SQL errors in VSPs will be described in section \"VS-B-6\".\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"How to access form data." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n    Data supplied to a VSP is normally posted from a form.\n    Pressing a form submit button causes the browser to pass the data to the server.\n    The form data may be encoded in two forms: www-url-encoded or multipart/form-data.\n\n\nProcessing of the form data in VSPs.\n\n  When the request arrives, the web server parses the request and creates three input arguments for VSP processing:\n  \n    path - array with path elements of the requested URL path. Ie. if the request is "http://foo.bar/a/b/c" then "path" argument will be a vector ('a','b','c').\n    params - array with name and value pairs of the passed form parameters\n    lines - the vector of HTTP request header lines\n  \n  The form data is held in the "params" argument.\n  The value of a named parameter can be extracted from the "params" array in two ways:\n    \n      Using the get_keyword function:\n         declare x varchar;\nx := get_keyword('fieldname', params, 'default value');\n      Using the {?'variable_name'} VSP shortcut.\n         x := {?'fieldname'};\n    \n\n\nForm example - A Simple Calculator.\nThe user can enter two numbers, and choose a desired operation.\nPressing the "=" button causes the form to be sent to the server. The VSP execution will show the result of\nthe calculation. This example uses the get_keyword function to retrieve the parameters.\n\nForm example - Insert table data\nThe second example demonstrates inserting the user entered form data into a table.\nThis example uses the {?''} shortcuts for accessing the form data. The data in the table will be shown\nbelow the form, ordered by date. You must run the sample SQL first to create the table.\n\nNote\nNote that both examples do not handle the SQL errors.\nThe handling of SQL errors in VSPs will be described in section "VS-B-6".\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Emitting Output to the User Agent" ;
	sioc:content	"\nPreliminaries\n\nThe Virtuoso Web server writes the content that is to be sent into the internal string session.\nThe internal string session will be sent to the user-agent after VSP execution (if there is no unhandled SQL errors).\nThere is full control over an internal session. It can be cleared, filled and flushed.\nNote when flushing an internal session the task will be executed in background, and no output will be sent after this action.\nThe character data can be encoded in various ways. A default encoding (CharSet) can be defined in the database INI file\n\n\nHTTP session control functions\n\n  http() - writes a string into the internal string session without conversion.\n  http_value() - writes a string with escapes into the internal string session.\n  http_rewrite() - clears the internal string session\n  http_flush() - flushes the internal string to the user-agent and continues processing in background.\n   - a shortcut to write a variable (or function) from an HTML section.\n\n\nHTTP formatting and charset functions\n\n  sprintf() - the special codes %V and %U used for HTML and URL escaping respectively.\n  http_url() - converts argument to a URL escaping special characters. Result written to internal session.\n  http_value() - converts argument to HTML escaping special characters. Result written to internal session.\n  current_charset() - returns name of the current charset.\n\n\n\nExamples\n\n  Use of http().\n  Use of http_value().\n  Use of http_rewrite().\n  Use of http_url().\n  Use of  tags.\n  Use of sprintf().\n\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"How to send data to the user-agents" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\nThe Virtuoso Web server writes the content that is to be sent into the internal string session.\nThe internal string session will be sent to the user-agent after VSP execution (if there is no unhandled SQL errors).\nThere is full control over an internal session. It can be cleared, filled and flushed.\nNote when flushing an internal session the task will be executed in background, and no output will be sent after this action.\nThe character data can be encoded in various ways. A default encoding (CharSet) can be defined in the database INI file\n\n\nHTTP session control functions\n\n  http() - writes a string into the internal string session without conversion.\n  http_value() - writes a string with escapes into the internal string session.\n  http_rewrite() - clears the internal string session\n  http_flush() - flushes the internal string to the user-agent and continues processing in background.\n  <?=var ?> - a shortcut to write a variable (or function) from an HTML section.\n\n\nHTTP formatting and charset functions\n\n  sprintf() - the special codes %V and %U used for HTML and URL escaping respectively.\n  http_url() - converts argument to a URL escaping special characters. Result written to internal session.\n  http_value() - converts argument to HTML escaping special characters. Result written to internal session.\n  current_charset() - returns name of the current charset.\n\n\n\nExamples\n\n  Use of http().\n  Use of http_value().\n  Use of http_rewrite().\n  Use of http_url().\n  Use of <?= ?> tags.\n  Use of sprintf().\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Controlling the Response Header" ;
	sioc:content	"\nPreliminaries\n\nThe behavior of the user-agents (Eg. browser) depends on the server's HTTP response.\nThe HTTP responses are: positive (2xx), informative (1xx), redirection(3xx), client error(4xx), server error(5xx).\nThe Virtuoso Web server automatically generates positive, client error and server error codes.\nThe http_request_status() function overwrites the default response. Example:\nhttp_request_status ('HTTP/1.1 404 Not found');\nNote that the response line MUST begin with \"HTTP/1.1 \", and numeric code MUST be one described in RFC2616.\nSome responses require additional information in the HTTP response header.\nThe functions for setting the additional lines in a response header are:\n \n http_header() - accept a response header line(s) as string. If more than one line is supplied, they must be\n separated with  characters. Note that the string must always finish with  chars. Subsequent calls of this function replace the old response.\n http_header_get() - returns the HTTP response header currently defined. It is useful when you need to append\n more lines.\n \n\n\nRedirection example\nThe first example demonstrates a redirection to another page. It uses http_request_status() and http_header()\nfunctions to set redirection code 'HTTP/1.1 302 Found' and 'Location:' header line in the response.\n\nIf a document has moved to another url, it's possible to redirect using a meta tag within the \nof a page. However using the method in this example, the redirection can be dynamic and conditional.\n\n\nLoad random Images\nThe second example demonstrates loading random images onto a page.\nThree images are loaded into the page by calling the vsp to generate each image.\nEach image URL is made unique by including a pic parameter. This does not imply the images will\nbe different, however it stops the browser from reusing one image three times.\n\nThe image content is made by setting the 'Content-Type' header field of the response to the 'image/gif',\nthen returning a randomly chosen block of Gif data.\nA real world use for a random image, is to show an advertising banner graphic.\nRather than change the url for the banner, the actual image content is controlled.\nThis technique might also be useful for changing an appearance of a web page based on some\ncriteria such as if the user has membership access or the time of day is either day or night to show\na sun or moon image.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"How to control the HTTP response from VSP" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\nThe behavior of the user-agents (Eg. browser) depends on the server's HTTP response.\nThe HTTP responses are: positive (2xx), informative (1xx), redirection(3xx), client error(4xx), server error(5xx).\nThe Virtuoso Web server automatically generates positive, client error and server error codes.\nThe http_request_status() function overwrites the default response. Example:\nhttp_request_status ('HTTP/1.1 404 Not found');\nNote that the response line MUST begin with "HTTP/1.1 ", and numeric code MUST be one described in RFC2616.\nSome responses require additional information in the HTTP response header.\nThe functions for setting the additional lines in a response header are:\n \n http_header() - accept a response header line(s) as string. If more than one line is supplied, they must be\n separated with <CR><LF> characters. Note that the string must always finish with <CR><LF> chars. Subsequent calls of this function replace the old response.\n http_header_get() - returns the HTTP response header currently defined. It is useful when you need to append\n more lines.\n \n\n\nRedirection example\nThe first example demonstrates a redirection to another page. It uses http_request_status() and http_header()\nfunctions to set redirection code 'HTTP/1.1 302 Found' and 'Location:' header line in the response.\n\nIf a document has moved to another url, it's possible to redirect using a meta tag within the <head>\nof a page. However using the method in this example, the redirection can be dynamic and conditional.\n\n\nLoad random Images\nThe second example demonstrates loading random images onto a page.\nThree images are loaded into the page by calling the vsp to generate each image.\nEach image URL is made unique by including a pic parameter. This does not imply the images will\nbe different, however it stops the browser from reusing one image three times.\n\nThe image content is made by setting the 'Content-Type' header field of the response to the 'image/gif',\nthen returning a randomly chosen block of Gif data.\nA real world use for a random image, is to show an advertising banner graphic.\nRather than change the url for the banner, the actual image content is controlled.\nThis technique might also be useful for changing an appearance of a web page based on some\ncriteria such as if the user has membership access or the time of day is either day or night to show\na sun or moon image.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Error Recovery" ;
	sioc:content	"\nPreliminaries\n\nWhen processing some form data in VSPs, there may be errors in the PL code (for example due to deadlock condition).\nThe most popular way of catching the SQL errors is to declare an exception handler.\ndeclare error varchar;\nerror := null;\ndeclare exit handler for sqlstate '*', not found result { error := __SQL_MESSAGE; };\n {\n    -- some operation(s) that may cause a SQL error\n }\nif (error is not null)\n  -- print the error message\nTo simplify VSP production, the error handler can be written in a common file and included in each page.\nThe external file can be included using the following markup:\n\n\n\nDeadlock Example\nThe first example demonstrates the creation of a universal deadlock handler.\nIf this file is included in any VSP the deadlock condition will cause a retry up to 3 times on an\noperation that follows the handler. The VSP simulates the deadlock situation by signalling the error.\nThe error handler is therefore called.\n\nCalculator with error handler\nThe second example is the vs_b_3 Calculator example. In this example there is an added handler to trap\nerrors such as division by zero, and entering characters instead of numbers.\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Error handling in VSPs" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\nWhen processing some form data in VSPs, there may be errors in the PL code (for example due to deadlock condition).\nThe most popular way of catching the SQL errors is to declare an exception handler.\ndeclare error varchar;\nerror := null;\ndeclare exit handler for sqlstate '*', not found result { error := __SQL_MESSAGE; };\n {\n    -- some operation(s) that may cause a SQL error\n }\nif (error is not null)\n  -- print the error message\nTo simplify VSP production, the error handler can be written in a common file and included in each page.\nThe external file can be included using the following markup:\n<?include path_to_the_external_file.extension ?>\n\n\nDeadlock Example\nThe first example demonstrates the creation of a universal deadlock handler.\nIf this file is included in any VSP the deadlock condition will cause a retry up to 3 times on an\noperation that follows the handler. The VSP simulates the deadlock situation by signalling the error.\nThe error handler is therefore called.\n\nCalculator with error handler\nThe second example is the vs_b_3 Calculator example. In this example there is an added handler to trap\nerrors such as division by zero, and entering characters instead of numbers.\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"User Records" ;
	sioc:content	"\nUser record Example\nThe object of the exercise is to handle form data, and data held in a table.\nThis is achieved with 4 separate stages. Each stage has a separate file.\n\n  Create a user table with a login name, password, real name and address. The login name is the primary key. This table can be made with a SQL file.\n  Write an application which gets data from a form and inserts it into a table.\n  Write a form to prompt for login details and pass to the query page.\n  Write a form for querying the table based on the login name. The login name in the query form will be a SQL LIKE string.\n\nThis example would be used in web sites that have some form of membership to gain access\nto information.\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"VSP exercise to create user records" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nUser record Example\nThe object of the exercise is to handle form data, and data held in a table.\nThis is achieved with 4 separate stages. Each stage has a separate file.\n\n  Create a user table with a login name, password, real name and address. The login name is the primary key. This table can be made with a SQL file.\n  Write an application which gets data from a form and inserts it into a table.\n  Write a form to prompt for login details and pass to the query page.\n  Write a form for querying the table based on the login name. The login name in the query form will be a SQL LIKE string.\n\nThis example would be used in web sites that have some form of membership to gain access\nto information.\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Media Archive" ;
	sioc:content	"\nOverview\nThe media archive shall demonstrate a way to upload files and also to download them.\nThe web page shows the upload feature, and download list at the same time.\n\nUpload Media\n\n  The file upload form allows an arbitrary file to be browsed and uploaded.\n  The input control is of type FILE for the upload field.\n  The ENCTYPE of the form must be a \"multipart/form-data\", so that the uploaded file data and type (attr-file) is accessible to the VSP.\n\n\nDownload media\n\n  Display a list of stored files on a single page and have a download link to each.\n  The default name in the download box must be the original file name.\n  The INLINEFILE pseudo directory shall be used to set the original name of a file.\n  The \"Content-Type\" header must be set to original media type.\n  Note that INLINEFILE pseudo URL needs a parameter \"VSP\", this parameter MUST contain the target VSP link encoded as URL.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Creating a simple file storage system using an SQL table" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nOverview\nThe media archive shall demonstrate a way to upload files and also to download them.\nThe web page shows the upload feature, and download list at the same time.\n\nUpload Media\n\n  The file upload form allows an arbitrary file to be browsed and uploaded.\n  The input control is of type FILE for the upload field.\n  The ENCTYPE of the form must be a "multipart/form-data", so that the uploaded file data and type (attr-file) is accessible to the VSP.\n\n\nDownload media\n\n  Display a list of stored files on a single page and have a download link to each.\n  The default name in the download box must be the original file name.\n  The INLINEFILE pseudo directory shall be used to set the original name of a file.\n  The "Content-Type" header must be set to original media type.\n  Note that INLINEFILE pseudo URL needs a parameter "VSP", this parameter MUST contain the target VSP link encoded as URL.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Header Parsing Functions" ;
	sioc:content	"\nPreliminaries\n\n  The HTTP request header contains lines of request information.\n  Every user-agent (browser) sends at least one request line to the Web server.\n  The \"lines\" argument in VSPs is an array of the user-agent request lines.\n\n\nMethods for accessing the request parameters\n\n  A specific attribute can be accessed with the http_request_header() function.\n  The header lines can be accessed with aref() function.\n  Parsing the header line can be done with the split_and_decode() function.\n\n\nCookie Demo\nThis example shows how to set a cookie in the user-agent, and displaying a cookie string when retrieved. \n\n  Setting the cookie is done with the http_header() function. (see also:VS-B-5)\n  Retrieving the cookie string is done with http_request_header() function.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Header Parsing Functions (Cookie Example)" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The HTTP request header contains lines of request information.\n  Every user-agent (browser) sends at least one request line to the Web server.\n  The "lines" argument in VSPs is an array of the user-agent request lines.\n\n\nMethods for accessing the request parameters\n\n  A specific attribute can be accessed with the http_request_header() function.\n  The header lines can be accessed with aref() function.\n  Parsing the header line can be done with the split_and_decode() function.\n\n\nCookie Demo\nThis example shows how to set a cookie in the user-agent, and displaying a cookie string when retrieved. \n\n  Setting the cookie is done with the http_header() function. (see also:VS-B-5)\n  Retrieving the cookie string is done with http_request_header() function.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Simple VSPX controls" ;
	sioc:content	"\n    Preliminaries\n    \n    The framework named Virtuoso Server Pages Extensions (VSPX) is a set of widgets (controls)\n    which are executed on server side. The VSPX page itself is an active page which contains\n    XHTML, VSP and widget code.  The VSPX page like VSP is a server side executable, so in both cases the virtual\n    directory where pages are placed needs to be executable. For the details of virtual directory setup\n    please read VS-B-1.\n    \n    \n    It might appear that VSPX pages and VSP pages are similar, but in practice there are differences:\n    \n    \n      The content of a VSPX page must be well-formed XML (like XHTML), in contrast to a VSP page\n        where this is not mandatory.\n      VSPX pages have a container element named \"page\", VSP pages do not (they are processing instruction\n        based).\n      The controls and containers in the VSPX page are in a special name space:\n        \"http://www.openlinksw.com/vspx/\", we will alias it with the prefix \"vspx:\" for the controls in the rest\n        of the tutorials.\n      Any active content must be in vspx:page container, and no more than one vspx:page can be in a\n        separate VSPX source file.\n      The VSPX pages are compiled to a more complex structure than VSPs.\n      The processing model of VSPX pages have five phases on execution: initialization, data-binding,\n        post processing, pre-rendering and rendering. VSP only has pre-processing, and execution.\n\t\tFor more details please read the VSPX section in the Virtuoso server documentation.\n      The VSPX page may contain one or more controls, VSPs do not have components. Also each control\n        in the VSPX page (and page container itself) represents a user defined type (class).\n    \n    As VSPX pages may contain macros and may have a pre-processing XSL-T transformation, an intermediate\n      file will be generated in the same place where the source page is. Also the compilation will generate a SQL\n      script as a file before compilation of PL code in memory. These files will be explained later in the\n      VX-S-8 example.\n    Finally there are several notes about VSPX controls (widgets). They need to have unique names in the\n      page space, including the macro expanded ones. It is not mandatory for the page name to be unique in the\n      Web server space. All of the controls are represented by trees of class instances, where each member vc_children\n      contains instances to the children controls.\n  \n    Example\n    \n      The example shows a simple page containing a vspx:page container and basic controls: vspx:label, vspx:url\n      and vspx:include. The vspx:page container (as already discussed) can contain any executable content,\n      but it may not be the topmost element in the page as we may see in the source of simple.vspx page. It also\n      shows how VSP processing instructions can be nested in the VSPX page. On that point we need to say that a\n      good VSPX programming style is to use very minimal VSP code to get the benefit of widgets.\n    \n    \n    The rest of the controls used in this example can be placed in any other control or container allowing content.\n    The special case is vspx:include which we will discuss later.\n    \n    \n      The vspx:label is the simplest text label which can be data bound. The \"data bound\" term designates the ability\n      of the control to obtain a value (it may be constant or Virtuoso/PL expression) on data bind phase when the page\n      gets executed. The format attribute is used to render the data, so it depends on the data type of the control's\n      value. In practice it's a format string as in sprintf() function. In that example the first label has\n      string value and the format is '%s', but second one is integer and the format used is '%d'.\n    \n    \n      The vspx:url represents a HTML anchor, but value and url are data bind-able. We can talk about it as\n      an extended functionality of the vspx:label control.\n    \n    \n      The last one is a vspx:include control. This is not a control per se, it's rather a place where the\n      expanded content of another document will be placed before VSPX page compilation. In that way we can easily\n      re-use common code between different pages. In that particular case the included file is very simple,\n      but it can also be another VSPX page. With this approach VSPX pages have more complex ways to do macro\n      expansions which will be explained in detail in VX-S-8.\n    \n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Building a VSPX page" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Preliminaries\n    \n    The framework named Virtuoso Server Pages Extensions (VSPX) is a set of widgets (controls)\n    which are executed on server side. The VSPX page itself is an active page which contains\n    XHTML, VSP and widget code.  The VSPX page like VSP is a server side executable, so in both cases the virtual\n    directory where pages are placed needs to be executable. For the details of virtual directory setup\n    please read VS-B-1.\n    \n    \n    It might appear that VSPX pages and VSP pages are similar, but in practice there are differences:\n    \n    \n      The content of a VSPX page must be well-formed XML (like XHTML), in contrast to a VSP page\n        where this is not mandatory.\n      VSPX pages have a container element named "page", VSP pages do not (they are processing instruction\n        based).\n      The controls and containers in the VSPX page are in a special name space:\n        "http://www.openlinksw.com/vspx/", we will alias it with the prefix "vspx:" for the controls in the rest\n        of the tutorials.\n      Any active content must be in vspx:page container, and no more than one vspx:page can be in a\n        separate VSPX source file.\n      The VSPX pages are compiled to a more complex structure than VSPs.\n      The processing model of VSPX pages have five phases on execution: initialization, data-binding,\n        post processing, pre-rendering and rendering. VSP only has pre-processing, and execution.\n\t\tFor more details please read the VSPX section in the Virtuoso server documentation.\n      The VSPX page may contain one or more controls, VSPs do not have components. Also each control\n        in the VSPX page (and page container itself) represents a user defined type (class).\n    \n    As VSPX pages may contain macros and may have a pre-processing XSL-T transformation, an intermediate\n      file will be generated in the same place where the source page is. Also the compilation will generate a SQL\n      script as a file before compilation of PL code in memory. These files will be explained later in the\n      VX-S-8 example.\n    Finally there are several notes about VSPX controls (widgets). They need to have unique names in the\n      page space, including the macro expanded ones. It is not mandatory for the page name to be unique in the\n      Web server space. All of the controls are represented by trees of class instances, where each member vc_children\n      contains instances to the children controls.\n  \n    Example\n    \n      The example shows a simple page containing a vspx:page container and basic controls: vspx:label, vspx:url\n      and vspx:include. The vspx:page container (as already discussed) can contain any executable content,\n      but it may not be the topmost element in the page as we may see in the source of simple.vspx page. It also\n      shows how VSP processing instructions can be nested in the VSPX page. On that point we need to say that a\n      good VSPX programming style is to use very minimal VSP code to get the benefit of widgets.\n    \n    \n    The rest of the controls used in this example can be placed in any other control or container allowing content.\n    The special case is vspx:include which we will discuss later.\n    \n    \n      The vspx:label is the simplest text label which can be data bound. The "data bound" term designates the ability\n      of the control to obtain a value (it may be constant or Virtuoso/PL expression) on data bind phase when the page\n      gets executed. The format attribute is used to render the data, so it depends on the data type of the control's\n      value. In practice it's a format string as in sprintf() function. In that example the first label has\n      string value and the format is '%s', but second one is integer and the format used is '%d'.\n    \n    \n      The vspx:url represents a HTML anchor, but value and url are data bind-able. We can talk about it as\n      an extended functionality of the vspx:label control.\n    \n    \n      The last one is a vspx:include control. This is not a control per se, it's rather a place where the\n      expanded content of another document will be placed before VSPX page compilation. In that way we can easily\n      re-use common code between different pages. In that particular case the included file is very simple,\n      but it can also be another VSPX page. With this approach VSPX pages have more complex ways to do macro\n      expansions which will be explained in detail in VX-S-8.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Generic VSPX form controls" ;
	sioc:content	"\n    Simple form and field validation example\n    The vspx:form control represents scriptable container of a HTML form.\n    It may contains several other controls which are represented below. In the \n    form.vspx example the form contains two vspx:label, two vspx:text and vspx:button controls. \n    In that way vspx:form behaves as control and container, as it may contain other controls and have rendition.\n    The vspx:label controls are shown in that example again to see that these can be used as a child of any vspx: container. Also the values of vspx:label are data bound to the name of control and name of page class.  \n    \n    The vspx:text is a text input control which can accept data from user. It may have modifiers which only change appearance from text to password or hidden field. In that example the vspx:text controls are in their default form.\n    The vspx:button control is a generic scriptable button, which originates post events. In practice it renders as a submit button, but with modifiers it can appear as image or link, so in that cases client-side Java scripts are generated to allow posting.\n    The last in that example we should notice is vspx:validator components assigned to the vspx:text fields. These are used to perform server-side validation of data entered by user.\n    So in short the page will display two fields to enter a data, which must be integer numbers. Where the second one must be in the range from 10 to 20. If you enter a different value an error will appear.\n  \n    Check-box example\n    This example presents a scriptable check-box (vspx:check-box) and submit button which is modified to look-like as link. Changing a state of check-box and posting a form will change the value of the label at the bottom.\n  \n    Radio and radio group controls\n    The radio-button and radio-group represented in this example shows \n    usage of radio controls. The main difference in approach is using a container to designate group of radio boxes or to use attribute \"group-name\" to do that. These are used as a scriptable variant of radio button in HTML.\n    \n  \n    Select list example\n    This example shows the usage of select-list control, which is a VSPX analogue of the select control.\n    Its members must be pre-defined with vspx:item controls which are similar to \"option\" in HTML variant. \n    \n  \n    Text area example\n    Sometimes a free-form text needs to be entered in a forms, in that case (in HTML practice) textarea is used. In the VSPX world the scriptable variant of it is vspx:textarea. This example shows simple form allowing 50 chars at max to be entered.\n  \n    Inter-field form validation\n    As we noticed in the last and first example we have a vspx:validators to control the user input.\n    But they was per text field. What if we need to check two or more inputs against each other in some order? \n    In that case we can use the form validation. The date.vspx example shows two fields to be filled as date strings. \n    Each filed is tested to be valid date string, and finally if first date is below second the validation will be passed. This is done with validator assigned to the vspx:form control. The default values are initialized to be in incorrect order to see validation on first hit. \n    \n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Scriptable form and form controls" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Simple form and field validation example\n    The vspx:form control represents scriptable container of a HTML form.\n    It may contains several other controls which are represented below. In the \n    form.vspx example the form contains two vspx:label, two vspx:text and vspx:button controls. \n    In that way vspx:form behaves as control and container, as it may contain other controls and have rendition.\n    The vspx:label controls are shown in that example again to see that these can be used as a child of any vspx: container. Also the values of vspx:label are data bound to the name of control and name of page class.  \n    \n    The vspx:text is a text input control which can accept data from user. It may have modifiers which only change appearance from text to password or hidden field. In that example the vspx:text controls are in their default form.\n    The vspx:button control is a generic scriptable button, which originates post events. In practice it renders as a submit button, but with modifiers it can appear as image or link, so in that cases client-side Java scripts are generated to allow posting.\n    The last in that example we should notice is vspx:validator components assigned to the vspx:text fields. These are used to perform server-side validation of data entered by user.\n    So in short the page will display two fields to enter a data, which must be integer numbers. Where the second one must be in the range from 10 to 20. If you enter a different value an error will appear.\n  \n    Check-box example\n    This example presents a scriptable check-box (vspx:check-box) and submit button which is modified to look-like as link. Changing a state of check-box and posting a form will change the value of the label at the bottom.\n  \n    Radio and radio group controls\n    The radio-button and radio-group represented in this example shows \n    usage of radio controls. The main difference in approach is using a container to designate group of radio boxes or to use attribute "group-name" to do that. These are used as a scriptable variant of radio button in HTML.\n    \n  \n    Select list example\n    This example shows the usage of select-list control, which is a VSPX analogue of the select control.\n    Its members must be pre-defined with vspx:item controls which are similar to "option" in HTML variant. \n    \n  \n    Text area example\n    Sometimes a free-form text needs to be entered in a forms, in that case (in HTML practice) textarea is used. In the VSPX world the scriptable variant of it is vspx:textarea. This example shows simple form allowing 50 chars at max to be entered.\n  \n    Inter-field form validation\n    As we noticed in the last and first example we have a vspx:validators to control the user input.\n    But they was per text field. What if we need to check two or more inputs against each other in some order? \n    In that case we can use the form validation. The date.vspx example shows two fields to be filled as date strings. \n    Each filed is tested to be valid date string, and finally if first date is below second the validation will be passed. This is done with validator assigned to the vspx:form control. The default values are initialized to be in incorrect order to see validation on first hit. \n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Data-bound VSPX controls" ;
	sioc:content	"\n    Select list initialized from SQL select statement\n    \n    The power of VSPX controls is easy way to bind to a Database objects as tables.\n    In the selectdb.vspx file is shown an easy way to initialize a simple select list from database data. \n    This example shows Products from Nortwind database rendered as select list.\n    The focus on this control is vspx:data-list control. It's initialized with select statement,\n     so the key and value attributes are used to designate what to be used for the drop-down box.\n    \n  \n    Updating a Database table row via VSPX update form\n    \n    Beside showing a data in a form, the database data need to be changed via forms. \n    The most easy way to do that is to use vspx:form with modifier attribute \"type\" with value of 'update'.\n    The vspx:form[type='update'] used as container of few more elements:\n    \n    \n    vspx:key - binder to a specific row, can be one or more. Usually it's a primary key. Note that this is a not a control, it's a marker in the update form.\n    vspx:template[type='if-exists'] - this is a wrapper class for content to be shown under specific condition. In that case as if-not-exists template is not specified, content of this will be shown in both situations. In other words this example will show content of that template always. The difference will be in value of the fields inside it.\n    vspx:text - it's used to show the data on the row, and accept the data to be updated. These fields have attribute \"column\" which designate column to be used for data rendition and update. Actually they are inside a template, but logically they are linked to the update form.\n    vspx:button - this is a submit button used to submit the form. \n    \n    The example will:\n    \n \t\t\tinsert a record in Demo.demo.Customers table if CustomerID doesn'y exists \n \t\t\twill update the CompanyName column if CustomerID is set.\n    \n\n  \n    Updating a enumerated values in a Database table\n    To run this example we will first need to setup the initial state (using the link beside SQL script, see bellow). This action will cerate a simple table for the next experiment with update form. In some cases we need to enumerate values to the given column in Database table. In this example we will use a vspx:radio-button bound to the column to represent the data value and to allow it's modification to the some degree. (The degree is possible values allowed by group of radio-buttons).\n    \n    \n    In practice we are repeating the previous example but instead using of vspx:text to enter the data , we will use a vspx:radio-button for the second column. The pane at the bottom of demo page shows the result of update, clicking a link of a 'e-id' will load appropriate record to the update form. The button is used to update the data row as in previous example.\n    \n  \n    Simple scroll-able edit-able data grid (vspx:data-set)\n    The most complex control used to view and modify the data in a Database tables is vspx:data-set.\n    This control represents a result set from a SQL select statement as a table (or some other form depending of templates used) and allows scrolling, editing, inserting or deleting a row. In practice it's a combination of scroll-able grid plus one or two update forms. In the example data_set.vspx is shown navigation over Northwind's Customers table. So the following should be noticed in the demo source:\n    \n    \n    The vspx:data-set contains a two simple templates for the header and footer.\n    The middle template is special denoted by \"repeat\" value of \"type\" attribute, it's used to render the row in a grid, form to insert, update form in place of a row in a focus and for case of empty result.\n    The repeat template contains four templates for each case as discussed above\n    The template[if-not-exists] will be rendered when no data found\n    The template[edit] will be displayed when edit button is selected\n    The template[add] will be always displayed, if specified\n    The template[browse] is a one per row to show the content on each row\n    The buttons for scrolling as [ds]_next and [ds]_prev must be defined with these suffixes.\n    The above applies to [ds]_edit, [ds]_delete and [ds]_select. In other words some buttons in data-set must have special names.\n    \n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Linking a DB data into a VSPX controls" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Select list initialized from SQL select statement\n    \n    The power of VSPX controls is easy way to bind to a Database objects as tables.\n    In the selectdb.vspx file is shown an easy way to initialize a simple select list from database data. \n    This example shows Products from Nortwind database rendered as select list.\n    The focus on this control is vspx:data-list control. It's initialized with select statement,\n     so the key and value attributes are used to designate what to be used for the drop-down box.\n    \n  \n    Updating a Database table row via VSPX update form\n    \n    Beside showing a data in a form, the database data need to be changed via forms. \n    The most easy way to do that is to use vspx:form with modifier attribute "type" with value of 'update'.\n    The vspx:form[type='update'] used as container of few more elements:\n    \n    \n    vspx:key - binder to a specific row, can be one or more. Usually it's a primary key. Note that this is a not a control, it's a marker in the update form.\n    vspx:template[type='if-exists'] - this is a wrapper class for content to be shown under specific condition. In that case as if-not-exists template is not specified, content of this will be shown in both situations. In other words this example will show content of that template always. The difference will be in value of the fields inside it.\n    vspx:text - it's used to show the data on the row, and accept the data to be updated. These fields have attribute "column" which designate column to be used for data rendition and update. Actually they are inside a template, but logically they are linked to the update form.\n    vspx:button - this is a submit button used to submit the form. \n    \n    The example will:\n    \n \t\t\tinsert a record in Demo.demo.Customers table if CustomerID doesn'y exists \n \t\t\twill update the CompanyName column if CustomerID is set.\n    \n\n  \n    Updating a enumerated values in a Database table\n    To run this example we will first need to setup the initial state (using the link beside SQL script, see bellow). This action will cerate a simple table for the next experiment with update form. In some cases we need to enumerate values to the given column in Database table. In this example we will use a vspx:radio-button bound to the column to represent the data value and to allow it's modification to the some degree. (The degree is possible values allowed by group of radio-buttons).\n    \n    \n    In practice we are repeating the previous example but instead using of vspx:text to enter the data , we will use a vspx:radio-button for the second column. The pane at the bottom of demo page shows the result of update, clicking a link of a 'e-id' will load appropriate record to the update form. The button is used to update the data row as in previous example.\n    \n  \n    Simple scroll-able edit-able data grid (vspx:data-set)\n    The most complex control used to view and modify the data in a Database tables is vspx:data-set.\n    This control represents a result set from a SQL select statement as a table (or some other form depending of templates used) and allows scrolling, editing, inserting or deleting a row. In practice it's a combination of scroll-able grid plus one or two update forms. In the example data_set.vspx is shown navigation over Northwind's Customers table. So the following should be noticed in the demo source:\n    \n    \n    The vspx:data-set contains a two simple templates for the header and footer.\n    The middle template is special denoted by "repeat" value of "type" attribute, it's used to render the row in a grid, form to insert, update form in place of a row in a focus and for case of empty result.\n    The repeat template contains four templates for each case as discussed above\n    The template[if-not-exists] will be rendered when no data found\n    The template[edit] will be displayed when edit button is selected\n    The template[add] will be always displayed, if specified\n    The template[browse] is a one per row to show the content on each row\n    The buttons for scrolling as [ds]_next and [ds]_prev must be defined with these suffixes.\n    The above applies to [ds]_edit, [ds]_delete and [ds]_select. In other words some buttons in data-set must have special names.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Order Entry Form using VSPX controls" ;
	sioc:content	"\nExample\n\n  The form accepts data for entering an order into the demo database.\n  The arguments contain the customer id, item to order and quantity.\n  The web page will take the data and execute a procedure via custom on-post handler.\n  It will display the status of the execution.\n \n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Order Entry Form" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample\n\n  The form accepts data for entering an order into the demo database.\n  The arguments contain the customer id, item to order and quantity.\n  The web page will take the data and execute a procedure via custom on-post handler.\n  It will display the status of the execution.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"XForms 1.0 rendering" ;
	sioc:content	"\n    Preliminaries\n    \n\tThe VSPX (Virtuoso Server Pages Extensions) framework allows \n\tform controls to be rendered as XForms 1.0 components. \n\tThis approach take an advantage to check input field's data-type \n\tand to restrict value using XML-Schema constraints. Thus \n        it's possible to make user agent performs input validation \n        before sending a data back to server.\t\n\tIt's IMPORTANT that this approach is only possible with browsers\n\tthat have a plug-in or natively supports XForms 1.0.\n    \n\nVSPX to XForms input rendering\n\n    This example works with IE6 or greater with FormsPlayer installed.\n    \n    The example shows turning on the flag for XForms rendering : \"connection_set ('RenderXForms', 1)\"\n    In the simple form all generic input controls are represented.\n    When submit is performed, data as XML document will be sent back to server and \n\twill be prepared on server side as well-known 'params' array.\n    \n\n\n    As can be seen the XForms rendering do not require any changes to existing VSPX pages (except logic to turn it on).\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Rendering VSPX form controls as XForms 1.0 components" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Preliminaries\n    \n\tThe VSPX (Virtuoso Server Pages Extensions) framework allows \n\tform controls to be rendered as XForms 1.0 components. \n\tThis approach take an advantage to check input field's data-type \n\tand to restrict value using XML-Schema constraints. Thus \n        it's possible to make user agent performs input validation \n        before sending a data back to server.\t\n\tIt's IMPORTANT that this approach is only possible with browsers\n\tthat have a plug-in or natively supports XForms 1.0.\n    \n\nVSPX to XForms input rendering\n\n    This example works with IE6 or greater with FormsPlayer installed.\n    \n    The example shows turning on the flag for XForms rendering : "connection_set ('RenderXForms', 1)"\n    In the simple form all generic input controls are represented.\n    When submit is performed, data as XML document will be sent back to server and \n\twill be prepared on server side as well-known 'params' array.\n    \n\n\n    As can be seen the XForms rendering do not require any changes to existing VSPX pages (except logic to turn it on).\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"XML data binding" ;
	sioc:content	"\n    Preliminaries\n    Usually data-bound controls as data-list, data-set etc. are \n\tusing a relational data (from tables, local or remote). But in some cases data\n\tis available as XML, which is most convenient to use as such instead of \n\tfilling and using an intermediate table as data source. \n\tFor this cases VSPX components (which allows data-binding) supports special \n\tset of attributes (see documentation for details). With these attributes \n  it is possible to bind XML data to the control's value, row-set etc.  \t\n    \n\n    Repeatable content based on XML data\n    The following approaches are demonstrated: \n\n    Binding a XML data to VSPX components, instead of using relational data\n    Using XML manipulation routines to insert update or delete \n    XML data.\n\n\n    In details example itself shows:\n\n\n    Filling a select list from XML document\n    Filling a repeatable control (data-set) with XML data.\n    Custom ordering functionality in repeatable control, using XML manipulation routines.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Using XML data for VSPX data-binding" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Preliminaries\n    Usually data-bound controls as data-list, data-set etc. are \n\tusing a relational data (from tables, local or remote). But in some cases data\n\tis available as XML, which is most convenient to use as such instead of \n\tfilling and using an intermediate table as data source. \n\tFor this cases VSPX components (which allows data-binding) supports special \n\tset of attributes (see documentation for details). With these attributes \n  it is possible to bind XML data to the control's value, row-set etc.  \t\n    \n\n    Repeatable content based on XML data\n    The following approaches are demonstrated: \n\n    Binding a XML data to VSPX components, instead of using relational data\n    Using XML manipulation routines to insert update or delete \n    XML data.\n\n\n    In details example itself shows:\n\n\n    Filling a select list from XML document\n    Filling a repeatable control (data-set) with XML data.\n    Custom ordering functionality in repeatable control, using XML manipulation routines.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"VSPX tree control" ;
	sioc:content	"\n    Vertical oriented tree\n    \n    To display any data which can be represented as tree hierarchy,\n    the vspx:tree control can be used.  In it's forms it may be represented as \n    vertical or horizontal one. The following example show directory structure of the \n    VSPX tutorials on local file system.  \n    \n    \n    The vspx:tree control have three important attributes:\n    \n    \n      root - This is a name of PL procedure which must return nodes under root of tree\n      child-function - This evaluated on a node must return children nodes or empty if it's a leaf\n      start-path - This expression or constant is passed to the root function\n    \n    In our example the root and child functions returns a array of strings per directory or file, the '.' and '..' are omitted. In interest also are two special containers and one place-holder:\n    \n      leaf-template - the content of this template will be instantiated and rendered when current position in the tree is a leaf.\n      node-template - this will be instantiated and rendered on nodes, per each node. The place of next node is designated with \"node\" placeholder.\n      node - place-holder to mark-up place where child content must be instantiated.\n    \n    In that control like as in data-set may have special button suffixed with '[name of tree control]_toggle'. This will be rendered as other submit buttons (in our case it have image appearance), but it will have special function to expand or collapse the branch.\n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Directory tree browser" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Vertical oriented tree\n    \n    To display any data which can be represented as tree hierarchy,\n    the vspx:tree control can be used.  In it's forms it may be represented as \n    vertical or horizontal one. The following example show directory structure of the \n    VSPX tutorials on local file system.  \n    \n    \n    The vspx:tree control have three important attributes:\n    \n    \n      root - This is a name of PL procedure which must return nodes under root of tree\n      child-function - This evaluated on a node must return children nodes or empty if it's a leaf\n      start-path - This expression or constant is passed to the root function\n    \n    In our example the root and child functions returns a array of strings per directory or file, the '.' and '..' are omitted. In interest also are two special containers and one place-holder:\n    \n      leaf-template - the content of this template will be instantiated and rendered when current position in the tree is a leaf.\n      node-template - this will be instantiated and rendered on nodes, per each node. The place of next node is designated with "node" placeholder.\n      node - place-holder to mark-up place where child content must be instantiated.\n    \n    In that control like as in data-set may have special button suffixed with '[name of tree control]_toggle'. This will be rendered as other submit buttons (in our case it have image appearance), but it will have special function to expand or collapse the branch.\n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"VSPX tab control" ;
	sioc:content	"\n    Example\n    The example presents vspx:tab control. It's used to show simultaneously content of one child container at time. The child container must be vspx:template, they are used to encapsulate other controls. The \"style\" attribute on \"tab\" controls designate automatic generation of select list to control switching between templates.\n    In interest is also \"initial-active\" attribute, this is used to activate one of templates initially. \n    The value of that attribute needs to be the name of the template to be activated on first go.\n    \n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Tab desk" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Example\n    The example presents vspx:tab control. It's used to show simultaneously content of one child container at time. The child container must be vspx:template, they are used to encapsulate other controls. The "style" attribute on "tab" controls designate automatic generation of select list to control switching between templates.\n    In interest is also "initial-active" attribute, this is used to activate one of templates initially. \n    The value of that attribute needs to be the name of the template to be activated on first go.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"VSPX login control" ;
	sioc:content	"\n    Login example\n    The vspx:login is a special control, it may occur inside VSPX page only once. In it's representation it may be a visual or it may be a hidden depending of intended purpose. \n    The purposes of that control are two: to verify login credentials and to ask user to enter a login.\n    On pages that are authorized the control is hidden, but in case login fails, redirect will be made to a page which will ask for login. Reasonable question is what kind of authorization is supported? The answer is: HTTP Digest, URL poisoning and with Cookies. As Digest and Cookie are not well supported in world of browsers the most effective way is URL poisoning.  \n    \n    \n    The attributes on vspx:login control are: \n    \n    \n      mode - designate type of authorization : \"digest\", \"url\" or \"cookie\". In out example it would be the \"url\"\n      realm - this is a unique string within applications space. This is used to distinguish logins from one application to other. In other words: area of usability of performed login.\n      user-password - name of PL function. This function is used when the mode is \"digest\". As digest do not send clear-text passwords this is used to retrieve from some source the password on server side.\n      user-password-check - this is PL function which is used to check password for given user. It's used when \"cookie\" and \"url\" authorization is performed.\n    \n    In our example the setup script defines both functions: for digest and URL poisoning, so as exercise the type can be changed to \"digest\" and appropriate attribute to be set. \n    Also please note that digest on Netscape (up to 7.0) or Mozilla browsers will not function properly as they have a defect in digest handling. But anyway on IE5.0 or greater this can be experimented.\n    \n    The following children elements are interesting:\n    \n      template[if-no-login] - the content of it will be displayed when login failed. It may have special attribute \"redirect\" which will cause redirect to another page.\n      template[if-login] - the content will be shown if request is authorized.\n      login-form - this is a special form to ask user for entering the credentials. It may have defaults, but special content is also possible as in that example.\n      \n    \n    As note we should say that login-form contains special buttons and fields named \"username\", \"password\" and \"login\". These are used to represent custom login form. These must be with the exactly that names. And one vspx:button with special function - \"logout\", it is used to terminate the current session. The logout button may appear in any place of login control but it's usually in if-login template.\n    Finally we should notice that when login control is used the connection variables and persistent page variables can be used. (for more details see vspx:variable and connection_set () , conenction_get () functions)\n    \n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Simple login dialog" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Login example\n    The vspx:login is a special control, it may occur inside VSPX page only once. In it's representation it may be a visual or it may be a hidden depending of intended purpose. \n    The purposes of that control are two: to verify login credentials and to ask user to enter a login.\n    On pages that are authorized the control is hidden, but in case login fails, redirect will be made to a page which will ask for login. Reasonable question is what kind of authorization is supported? The answer is: HTTP Digest, URL poisoning and with Cookies. As Digest and Cookie are not well supported in world of browsers the most effective way is URL poisoning.  \n    \n    \n    The attributes on vspx:login control are: \n    \n    \n      mode - designate type of authorization : "digest", "url" or "cookie". In out example it would be the "url"\n      realm - this is a unique string within applications space. This is used to distinguish logins from one application to other. In other words: area of usability of performed login.\n      user-password - name of PL function. This function is used when the mode is "digest". As digest do not send clear-text passwords this is used to retrieve from some source the password on server side.\n      user-password-check - this is PL function which is used to check password for given user. It's used when "cookie" and "url" authorization is performed.\n    \n    In our example the setup script defines both functions: for digest and URL poisoning, so as exercise the type can be changed to "digest" and appropriate attribute to be set. \n    Also please note that digest on Netscape (up to 7.0) or Mozilla browsers will not function properly as they have a defect in digest handling. But anyway on IE5.0 or greater this can be experimented.\n    \n    The following children elements are interesting:\n    \n      template[if-no-login] - the content of it will be displayed when login failed. It may have special attribute "redirect" which will cause redirect to another page.\n      template[if-login] - the content will be shown if request is authorized.\n      login-form - this is a special form to ask user for entering the credentials. It may have defaults, but special content is also possible as in that example.\n      \n    \n    As note we should say that login-form contains special buttons and fields named "username", "password" and "login". These are used to represent custom login form. These must be with the exactly that names. And one vspx:button with special function - "logout", it is used to terminate the current session. The logout button may appear in any place of login control but it's usually in if-login template.\n    Finally we should notice that when login control is used the connection variables and persistent page variables can be used. (for more details see vspx:variable and connection_set () , conenction_get () functions)\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"VSPX  browse button control" ;
	sioc:content	"\n    Example\n    This example repeats the VX-S-3(data-set),\n    but it also introduce the vspx:button with special functions browse and select.\n   These buttons are to make inter-page communication, in our case to establish the foreign key relation ship between Products and Categories tables from Northwind demo database.\n    \n    The browse button represents a HTML button which will pop-up the window to make selection.\n    The special attributes selector and child-window-options are used to indicate which link should be used for pop-up and how to display the child browser window.\n    \n    The selector window (child) is also an data-set over Categories table and contains special button with name of data-set control suffixed with '_select'. This is a Java script button which will return back to parent window the selected data and will close the window after selection is made.\n    \n    Both buttons have as children elements vspx:field, these are markers to the buttons which control value and must be used to link both pages. The name attribute of these is the same of the control which needs to be selected or filled with the data. In that way this is a exception of unique names in the page.\n    Please note that both controls instruct VSPX compiler to add client-side Java script functions to maintain functionality. Hence disabling the Java script on browser will made these to stop working.\n    \n    In our example the discussed functionality is demonstrated with buttons Browse in rows to insert and when do an update of products page. Hitting on one of these will pop-up a window to select appropriate foreign key value.\n    \n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Pop-up select list" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Example\n    This example repeats the VX-S-3(data-set),\n    but it also introduce the vspx:button with special functions browse and select.\n   These buttons are to make inter-page communication, in our case to establish the foreign key relation ship between Products and Categories tables from Northwind demo database.\n    \n    The browse button represents a HTML button which will pop-up the window to make selection.\n    The special attributes selector and child-window-options are used to indicate which link should be used for pop-up and how to display the child browser window.\n    \n    The selector window (child) is also an data-set over Categories table and contains special button with name of data-set control suffixed with '_select'. This is a Java script button which will return back to parent window the selected data and will close the window after selection is made.\n    \n    Both buttons have as children elements vspx:field, these are markers to the buttons which control value and must be used to link both pages. The name attribute of these is the same of the control which needs to be selected or filled with the data. In that way this is a exception of unique names in the page.\n    Please note that both controls instruct VSPX compiler to add client-side Java script functions to maintain functionality. Hence disabling the Java script on browser will made these to stop working.\n    \n    In our example the discussed functionality is demonstrated with buttons Browse in rows to insert and when do an update of products page. Hitting on one of these will pop-up a window to select appropriate foreign key value.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"VSPX controls" ;
	sioc:content	"\n    Examples\n  All the standard VSPX base controls (including but not limited to \n  buttons, drop-down lists and tab controls etc) are listed in the table below with \n  invocation and source code revealing hyperlinks.  The pages source code of each \n  control is optionally vieweable by clicking the filename hyperlink in the \n  \"View Source\" column.   To execute each of these vspx pages click on the  \n  \"run\" hyperlink  in the \"Action\" column.\n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Collection of VSPX controls" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Examples\n  All the standard VSPX base controls (including but not limited to \n  buttons, drop-down lists and tab controls etc) are listed in the table below with \n  invocation and source code revealing hyperlinks.  The pages source code of each \n  control is optionally vieweable by clicking the filename hyperlink in the \n  "View Source" column.   To execute each of these vspx pages click on the  \n  "run" hyperlink  in the "Action" column.\n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"VSPX macros" ;
	sioc:content	"\n    Example\n    In the first example of this section VX-S-1 we mentioned that except vspx:include there is more powerful feature for macro expansion. This feature is explained here. The idea is to have two more source files named style and decoration. They are assigned to the target page via vspx:page attributes \"decor\" and \"style\" respectively.\n    The way these are working is the following: before any compilation phase the decor file will be expanded with page itself (see placeholder element). After that the style will be applied and result will be saved in an intermediary file named as original with .vspx-m. As a last step of process would be the page compilation of the intermediary file. This step will generate also a SQL script for page class and it's member functions definitions. The last step of page compilation is execution of the .vspx-sql script and hence creation of objects into the server memory.\n    \n    The example extends the formsty.vspx page with expansion of formdecor.vspx file and make rendition before compilation with formsty.xsl. In that way we can make similar pages with very simple structure, which are with same style and appearance. Also we can divide VSPX page design from functionality.\n  " ;
	sioc:has_container	ns2:web ;
	sioc:description	"Using macro expansion" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Example\n    In the first example of this section VX-S-1 we mentioned that except vspx:include there is more powerful feature for macro expansion. This feature is explained here. The idea is to have two more source files named style and decoration. They are assigned to the target page via vspx:page attributes "decor" and "style" respectively.\n    The way these are working is the following: before any compilation phase the decor file will be expanded with page itself (see placeholder element). After that the style will be applied and result will be saved in an intermediary file named as original with .vspx-m. As a last step of process would be the page compilation of the intermediary file. This step will generate also a SQL script for page class and it's member functions definitions. The last step of page compilation is execution of the .vspx-sql script and hence creation of objects into the server memory.\n    \n    The example extends the formsty.vspx page with expansion of formdecor.vspx file and make rendition before compilation with formsty.xsl. In that way we can make similar pages with very simple structure, which are with same style and appearance. Also we can divide VSPX page design from functionality.\n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Mapping Requests to Resources" ;
	sioc:content	"\nListening Interface Concepts\n\n  A single Virtuoso server can accept HTTP requests on multiple interfaces.\n  Listening interfaces are defined via a virtual directory mechanism (not based on INI setting).\n  Virtual directory operation can be stopped or started without restarting the server engine.\n  The request accepted on a given interface can be processed in a separate Web space.\n\n\nVirtual Host\n\n  The term Virtual Host refers to the practice of maintaining more than one server on one machine, as differentiated\nby their apparent host name. For example, it is often desirable for companies sharing a web server to have their\nown domains, with web servers accessible as www.company1.com and www.company2.com, without requiring the user to\nknow any extra path information. The Virtual host can be IP-based or non-IP.\n  The IP-based (named in this document as multihosting) refers to the practice of making one machine listen on\ndifferent interfaces and respond with different pages.\n  The non-IP (named virtual hosting) refers to the practice where one machine is allocated more than one DNS\nalias. The web content served can then be based on the alias that the client contacted, as identified by the\n'Host' HTTP header field.\n  A single Virtuoso server can map requests into multiple spaces of web pages based on the interface to\n  which the requests come (multihosting) or on the Host HTTP/1.1 header (virtual hosting).\n  A single physical interface can map multiple virtual hosts.\n  The virtual host name must be defined also in Domain Name Server as an alias of the official host name.\n\n\nAttributes\n\n  Logical Path - The path part from URL which user-agent wants.\n  Mapped Path - Defacto location of requested Web resource.\n  Is in DAV - The Virtuoso server has space for Distributed Authoring & Versioning (DAV see: rfc2518 for details) under \"/DAV\" URL. The logical path can me mapped in to this space.\n  Default page - The name of page or resource on Web server to show if a directory/folder is requested. It applies to the entire subdirectory tree.\n  Is browseable - If no default page specified or page does not exist, then show directory content. Warning: This setting can raise security problems, because all directory content will be shown.\n\n\nSecurity\n\n  The Web server has access to the file system directory (see ServerRoot INI setting) using the privileges\n\tof the user who is running it.\n  Access to the WebDAV repository can be restricted to only special accounts, as each resource/folder can\n   have different permissions applied.\n  Execution in a mapped path can be enabled/disabled.\n  Basic and Digest HTTP authentication schemes can be used.\n  HTTPS listeners can be started.\n  User-agent's certificate can be requested and checked.\n\n\nAuthentication Function\n\n  An application dependant PL function for HTTP authentication can be defined for each path mapping.\n  The authentication function can be used to restore session variables.\n  The built-in authentication functions can be used.\n\n\nRequest Postprocessing Function\n\n  An application dependant PL function can be defined for each path mapping to store the session variables\n  (in session table).\n\n\nDatabase User Accounts for execution of active content\n\n  Database User Account for VSP: For each path mapping, a different Database account can be supplied.\n  The VSP will be executed on behalf of this account.\n  Database user account for SOAP: For each path mapping, the SOAP calls can be assign to a different Database\n  account. The WSDL schema will show only PL procedures granted to this account.\n\n\nExample Listen host & Virtual host mappings\nIt is possible to have a mapping in the file system /www1/ for  http://www.a.com/ requests.\n    In this case we will specify the listen host www.a.com (the port default is 80), logical path / and\n\tphysical location /www1/.\nIn some cases more than one web server is needed on the same machine. A second DNS alias www.b.com can\n\tbe routed to the www.a.com. A mapping for this alias can then be: listen host is again www.a.com but virtual host is\n\twww.b.com and physical location can be a /www2/ under HTTP root directory. When a User-Agent requests the\n\thttp://www.b.com/ it will send a 'Host' header field, in this field value will be 'www.b.com'. The web server will\n\tfind a second map and will try to process the pages under /www2/.\n\nFinding the closest applicable mapping\nIts possible to define more than one mapping for one virtual/listen host combination. In this case the closest\nmatch to the request is used. For example with the following mappings:\n\nLogical PathPhysical Path\nwww.a.com//www/a\nwww.a.com/a/www/b\n\nGets the following mapping:\n\nRequestPhysical Path\nhttp://www.a.com/a//www/b\nhttp://www.a.com/other/www/a/other\n\nThe Web server will find the closest path match when processing the logical to physical mapping.\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"General information about the virtual host/directory mechanism" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nListening Interface Concepts\n\n  A single Virtuoso server can accept HTTP requests on multiple interfaces.\n  Listening interfaces are defined via a virtual directory mechanism (not based on INI setting).\n  Virtual directory operation can be stopped or started without restarting the server engine.\n  The request accepted on a given interface can be processed in a separate Web space.\n\n\nVirtual Host\n\n  The term Virtual Host refers to the practice of maintaining more than one server on one machine, as differentiated\nby their apparent host name. For example, it is often desirable for companies sharing a web server to have their\nown domains, with web servers accessible as www.company1.com and www.company2.com, without requiring the user to\nknow any extra path information. The Virtual host can be IP-based or non-IP.\n  The IP-based (named in this document as multihosting) refers to the practice of making one machine listen on\ndifferent interfaces and respond with different pages.\n  The non-IP (named virtual hosting) refers to the practice where one machine is allocated more than one DNS\nalias. The web content served can then be based on the alias that the client contacted, as identified by the\n'Host' HTTP header field.\n  A single Virtuoso server can map requests into multiple spaces of web pages based on the interface to\n  which the requests come (multihosting) or on the Host HTTP/1.1 header (virtual hosting).\n  A single physical interface can map multiple virtual hosts.\n  The virtual host name must be defined also in Domain Name Server as an alias of the official host name.\n\n\nAttributes\n\n  Logical Path - The path part from URL which user-agent wants.\n  Mapped Path - Defacto location of requested Web resource.\n  Is in DAV - The Virtuoso server has space for Distributed Authoring & Versioning (DAV see: rfc2518 for details) under "/DAV" URL. The logical path can me mapped in to this space.\n  Default page - The name of page or resource on Web server to show if a directory/folder is requested. It applies to the entire subdirectory tree.\n  Is browseable - If no default page specified or page does not exist, then show directory content. Warning: This setting can raise security problems, because all directory content will be shown.\n\n\nSecurity\n\n  The Web server has access to the file system directory (see ServerRoot INI setting) using the privileges\n\tof the user who is running it.\n  Access to the WebDAV repository can be restricted to only special accounts, as each resource/folder can\n   have different permissions applied.\n  Execution in a mapped path can be enabled/disabled.\n  Basic and Digest HTTP authentication schemes can be used.\n  HTTPS listeners can be started.\n  User-agent's certificate can be requested and checked.\n\n\nAuthentication Function\n\n  An application dependant PL function for HTTP authentication can be defined for each path mapping.\n  The authentication function can be used to restore session variables.\n  The built-in authentication functions can be used.\n\n\nRequest Postprocessing Function\n\n  An application dependant PL function can be defined for each path mapping to store the session variables\n  (in session table).\n\n\nDatabase User Accounts for execution of active content\n\n  Database User Account for VSP: For each path mapping, a different Database account can be supplied.\n  The VSP will be executed on behalf of this account.\n  Database user account for SOAP: For each path mapping, the SOAP calls can be assign to a different Database\n  account. The WSDL schema will show only PL procedures granted to this account.\n\n\nExample Listen host & Virtual host mappings\nIt is possible to have a mapping in the file system /www1/ for  http://www.a.com/ requests.\n    In this case we will specify the listen host www.a.com (the port default is 80), logical path / and\n\tphysical location /www1/.\nIn some cases more than one web server is needed on the same machine. A second DNS alias www.b.com can\n\tbe routed to the www.a.com. A mapping for this alias can then be: listen host is again www.a.com but virtual host is\n\twww.b.com and physical location can be a /www2/ under HTTP root directory. When a User-Agent requests the\n\thttp://www.b.com/ it will send a 'Host' header field, in this field value will be 'www.b.com'. The web server will\n\tfind a second map and will try to process the pages under /www2/.\n\nFinding the closest applicable mapping\nIts possible to define more than one mapping for one virtual/listen host combination. In this case the closest\nmatch to the request is used. For example with the following mappings:\n\nLogical PathPhysical Path\nwww.a.com//www/a\nwww.a.com/a/www/b\n\nGets the following mapping:\n\nRequestPhysical Path\nhttp://www.a.com/a//www/b\nhttp://www.a.com/other/www/a/other\n\nThe Web server will find the closest path match when processing the logical to physical mapping.\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Examples of Mapping" ;
	sioc:content	"\nPreliminaries\n\n  The virtual path can be defined to have a default page.\n  The default page will be displayed if no file is requested.\n  Sub directories of the defined mapping, inherit the default page name mapping.\n  The particular URL can be retrieved with integrated HTTP client as a string.\n  The integrated HTTP client can be invoked with the http_get() function. \n\n\nExample description\n\n  This example defines a virtual directory with a default dynamic page.\n  A URL is prompted for. If it is found then the header and content is loaded and displayed.\n  An error is reported if the URL cannot be found.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Creating a virtual directory with default page" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The virtual path can be defined to have a default page.\n  The default page will be displayed if no file is requested.\n  Sub directories of the defined mapping, inherit the default page name mapping.\n  The particular URL can be retrieved with integrated HTTP client as a string.\n  The integrated HTTP client can be invoked with the http_get() function. \n\n\nExample description\n\n  This example defines a virtual directory with a default dynamic page.\n  A URL is prompted for. If it is found then the header and content is loaded and displayed.\n  An error is reported if the URL cannot be found.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Examples of Mapping" ;
	sioc:content	"\nPreliminaries\n\n  The Virtuoso Web server can act as a proxy server for HTTP requests.\n  If request from a user-agent is a proxy request, then the Web server will try to retrieve the URL, and will send the response and entity body back to the user-agent.\n  The virtual directory mapping can be setup when physical location is a Web server. The local URL will then be treated by the Web server as a proxy request.\n\nLogin to the Conductor UI using the dba account.\n\nExample virtual directory setup to another HTTP server\n\n  Go to \"Web Application Server\" tab and then go to the \"Virtual Domains & Directories\" tab.\n  From the given list of HTTP Hosts click the icon infront of the Interface value.\n  Click the \"Add new directory\" link.\n  Choose the \"Proxy server\" type and press the button \"Next>>\".\n  Enter \"/proxy\" for Virtual directory path, \"http://[desired_host:port]/\" for Proxy to, and then press the \"Save Changes\" button.\n\nTo test the new directory: enter the \"http://your_host:port/proxy\" in browser.\nIf all is ok, the content of the web tutorial directory is shown.\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create the virtual directory with physical path \"http://host:port/\"\n  \nSQL> vhost_define (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/proxy',ppath=>'http://host:port/');\n  \n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Creating a virtual directory to proxy to another server" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The Virtuoso Web server can act as a proxy server for HTTP requests.\n  If request from a user-agent is a proxy request, then the Web server will try to retrieve the URL, and will send the response and entity body back to the user-agent.\n  The virtual directory mapping can be setup when physical location is a Web server. The local URL will then be treated by the Web server as a proxy request.\n\nLogin to the Conductor UI using the dba account.\n\nExample virtual directory setup to another HTTP server\n\n  Go to "Web Application Server" tab and then go to the "Virtual Domains & Directories" tab.\n  From the given list of HTTP Hosts click the icon infront of the Interface value.\n  Click the "Add new directory" link.\n  Choose the "Proxy server" type and press the button "Next>>".\n  Enter "/proxy" for Virtual directory path, "http://[desired_host:port]/" for Proxy to, and then press the "Save Changes" button.\n\nTo test the new directory: enter the "http://your_host:port/proxy" in browser.\nIf all is ok, the content of the web tutorial directory is shown.\n\nEquivalent SQL commands to above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Create the virtual directory with physical path "http://host:port/"\n  \nSQL> vhost_define (vhost=>'*ini*',lhost=>'*ini*',lpath=>'/proxy',ppath=>'http://host:port/');\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Examples of Mapping" ;
	sioc:content	"\nPreliminaries\n\n  Space on the Web server can be explicitly mapped for SSL (HTTPS) connections.\n  To start HTTPS listener, the server needs a valid certificate and private key pair.\n\n\nUsing the Virtual Directories UI\n\n  Login to the Conductor UI using the dba account.\n  Go to \"Web Application Server\" tab and then go to the \"Virtual Domains & Directories\" tab.\n  In the empty fields below the list of HTTP Listeners enter:\n  In the \"HTTP Host\" field the qualified name of the host.\n  In the \"Interface\" field the qualified name of the interface to listen to.\n  In the \"Port\" field the port number to listen on.\n  Press the \"Add\" button.\n  Define the HTTP root location of this host. The root location can be mapped in file system, DAV or proxy server. In this example we will define a map in filesystem.\n  Click the icon in front of the Interface value.\n   Click the \"Add new directory\" link.\n  Create a \"/ssl\" directory under the HTTPServer ServerRoot directory. This directory will be used to create the new mapping.\n  Choose the \"File System\" type and press the button 'Next>>'.\n  Enter for \"Path\" \"/ssl\" and enter \"/ssl/\" (or select this directory with \"Browse\" button) in the \"Physical path\" location.\n  If you wish to make entire site to be executable specify the VSP user. (See also: VS-B-1 example)\n  Select the \"SSL\" as \"Security method\"\n  Enter for authentication options the files for the certificate and the private key of the server\n\nhttps_cert=PATH_TO_THE_CERTIFICATE;\nhttps_key=PATH_TO_THE_PRIVATE_KEY;\n\n  Press the \"Save Changes\" button.\n  If needed, more path mapping can be added to that defined.\n  To test the definition enter http://[yourhost:port]/ in location box of your browser.\n\n\nEquivalent SQL commands for above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Define a virtual directory mapping for the host alias:\n\nSQL> vhost_define (vhost=>'[yourhost]:4333',lhost=>'[yourhost]:4333',\n                      lpath=>'/',ppath=>'/ssl/', def_page=>'index.html',\n\t\t      is_brws=>1, sec=>'SSL',\n\t\t      auth_opts=>vector ('https_cert','PATH_TO_THE_CERTIFICATE',\n\t\t\t'https_key','PATH_TO_THE_PRIVATE_KEY'));\n\nNote that in the sample SQL script, 'localhost' is used instead of 'yourhost'. This MUST be replaced with the official host name. Also needs certificate an private keys to be in place, before trying this example; PATH_TO_THE_CERTIFICATE and PATH_TO_THE_PRIVATE_KEY MUST be replaced with actual path to these files.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Setting up a Secure Directory" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  Space on the Web server can be explicitly mapped for SSL (HTTPS) connections.\n  To start HTTPS listener, the server needs a valid certificate and private key pair.\n\n\nUsing the Virtual Directories UI\n\n  Login to the Conductor UI using the dba account.\n  Go to "Web Application Server" tab and then go to the "Virtual Domains & Directories" tab.\n  In the empty fields below the list of HTTP Listeners enter:\n  In the "HTTP Host" field the qualified name of the host.\n  In the "Interface" field the qualified name of the interface to listen to.\n  In the "Port" field the port number to listen on.\n  Press the "Add" button.\n  Define the HTTP root location of this host. The root location can be mapped in file system, DAV or proxy server. In this example we will define a map in filesystem.\n  Click the icon in front of the Interface value.\n   Click the "Add new directory" link.\n  Create a "/ssl" directory under the HTTPServer ServerRoot directory. This directory will be used to create the new mapping.\n  Choose the "File System" type and press the button 'Next>>'.\n  Enter for "Path" "/ssl" and enter "/ssl/" (or select this directory with "Browse" button) in the "Physical path" location.\n  If you wish to make entire site to be executable specify the VSP user. (See also: VS-B-1 example)\n  Select the "SSL" as "Security method"\n  Enter for authentication options the files for the certificate and the private key of the server\n\nhttps_cert=PATH_TO_THE_CERTIFICATE;\nhttps_key=PATH_TO_THE_PRIVATE_KEY;\n\n  Press the "Save Changes" button.\n  If needed, more path mapping can be added to that defined.\n  To test the definition enter http://[yourhost:port]/ in location box of your browser.\n\n\nEquivalent SQL commands for above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Define a virtual directory mapping for the host alias:\n\nSQL> vhost_define (vhost=>'[yourhost]:4333',lhost=>'[yourhost]:4333',\n                      lpath=>'/',ppath=>'/ssl/', def_page=>'index.html',\n\t\t      is_brws=>1, sec=>'SSL',\n\t\t      auth_opts=>vector ('https_cert','PATH_TO_THE_CERTIFICATE',\n\t\t\t'https_key','PATH_TO_THE_PRIVATE_KEY'));\n\nNote that in the sample SQL script, 'localhost' is used instead of 'yourhost'. This MUST be replaced with the official host name. Also needs certificate an private keys to be in place, before trying this example; PATH_TO_THE_CERTIFICATE and PATH_TO_THE_PRIVATE_KEY MUST be replaced with actual path to these files.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Examples of Mapping" ;
	sioc:content	"\nPreliminaries\n\n  The Web server can be setup to check the HTTPS client certificate\n  The HTTPS client must have installed a X.509 certificate.\n\n\nUsing the Virtual Directories UI\n\n  Login to the Conductor UI using the dba account.\n  Go to \"Web Application Server\" tab and then go to the \"Virtual Domains & Directories\" tab.\n   In the empty fields below the list of HTTP Listeners enter:\n  In the \"HTTP Host\" field the qualified name of the host.\n  In the \"Interface\" field the qualified name of the interface to listen to.\n  In the \"Port\" field the port number to listen on.\n  Press the \"Add\" button.\n  Define the HTTP root location of this host. The root location can be mapped in file system, DAV or proxy. This example uses the filesystem.\n  Create a \"/ssl_cv\" directory under the HTTPServer ServerRoot directory. This will be used for the new mapping.\n  Click the icon in front of the Interface value.\n  Click the \"Add new directory\" link.\n  Choose the \"File System\" type and press the button 'Next>>'.\n  Enter for \"Path\" \"/ssl_cv\" and enter \"/ssl_cv/\" (or select with \"Browse\" button this directory) in the \"Physical path\" location.\n  If you wish to make entire site to be executable specify the VSP user. (See also: VS-B-1 example)\n  Select the \"SSL\" as \"Security method\"\n  Enter for authentication options the files for the certificate and the private key of the server:\n\nhttps_cert=PATH_TO_THE_CERTIFICATE;\nhttps_key=PATH_TO_THE_PRIVATE_KEY;\nhttps_cv=PATH_TO_THE_CA_LIST;\nhttps_cv_depth=2;\n\n  Press the \"Save Changes\" button.\n  If needed, more path mapping can be added to the defined.\n  To test the definition enter http://[yourhost:port]/ in location box of your browser.\n\n\nEquivalent SQL commands for above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Define a virtual directory mapping for the host alias:\nSQL> vhost_define (vhost=>'[yourhost]:4334',lhost=>'[yourhost]:4334',\n             lpath=>'/',ppath=>'/ssl_cv/', def_page=>'index.html',\n\t\t     is_brws=>1, sec=>'SSL',\n\t\t     auth_opts=>vector ('https_cert','PATH_TO_THE_CERTIFICATE',\n\t\t\t 'https_key','PATH_TO_THE_PRIVATE_KEY', 'https_cv', 'PATH_TO_THE_CA_LIST',\n\t\t\t 'https_cv_depth', 1));\n  Note that in the sample SQL script, 'localhost' is used instead of 'yourhost'. This can be replaced with the official host name.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Using the HTTPS client certificates" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The Web server can be setup to check the HTTPS client certificate\n  The HTTPS client must have installed a X.509 certificate.\n\n\nUsing the Virtual Directories UI\n\n  Login to the Conductor UI using the dba account.\n  Go to "Web Application Server" tab and then go to the "Virtual Domains & Directories" tab.\n   In the empty fields below the list of HTTP Listeners enter:\n  In the "HTTP Host" field the qualified name of the host.\n  In the "Interface" field the qualified name of the interface to listen to.\n  In the "Port" field the port number to listen on.\n  Press the "Add" button.\n  Define the HTTP root location of this host. The root location can be mapped in file system, DAV or proxy. This example uses the filesystem.\n  Create a "/ssl_cv" directory under the HTTPServer ServerRoot directory. This will be used for the new mapping.\n  Click the icon in front of the Interface value.\n  Click the "Add new directory" link.\n  Choose the "File System" type and press the button 'Next>>'.\n  Enter for "Path" "/ssl_cv" and enter "/ssl_cv/" (or select with "Browse" button this directory) in the "Physical path" location.\n  If you wish to make entire site to be executable specify the VSP user. (See also: VS-B-1 example)\n  Select the "SSL" as "Security method"\n  Enter for authentication options the files for the certificate and the private key of the server:\n\nhttps_cert=PATH_TO_THE_CERTIFICATE;\nhttps_key=PATH_TO_THE_PRIVATE_KEY;\nhttps_cv=PATH_TO_THE_CA_LIST;\nhttps_cv_depth=2;\n\n  Press the "Save Changes" button.\n  If needed, more path mapping can be added to the defined.\n  To test the definition enter http://[yourhost:port]/ in location box of your browser.\n\n\nEquivalent SQL commands for above\n\n  Connect to the Virtuoso server via ISQL utility as DBA user.\n  Define a virtual directory mapping for the host alias:\nSQL> vhost_define (vhost=>'[yourhost]:4334',lhost=>'[yourhost]:4334',\n             lpath=>'/',ppath=>'/ssl_cv/', def_page=>'index.html',\n\t\t     is_brws=>1, sec=>'SSL',\n\t\t     auth_opts=>vector ('https_cert','PATH_TO_THE_CERTIFICATE',\n\t\t\t 'https_key','PATH_TO_THE_PRIVATE_KEY', 'https_cv', 'PATH_TO_THE_CA_LIST',\n\t\t\t 'https_cv_depth', 1));\n  Note that in the sample SQL script, 'localhost' is used instead of 'yourhost'. This can be replaced with the official host name.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Examples of Mapping" ;
	sioc:content	"\nPreliminaries\n\n  The Web server can listen on multiple physical interfaces.\n  Requests for each interface can be dispatched to a separate directory.\n\n\nUsing the Virtual Directories UI\n\n  Login to the Conductor UI using the dba account.\n  Go to \"Web Application Server\" tab and then go to the \"Virtual Domains & Directories\" tab.\n  In the empty fields below the list of HTTP Listeners enter:\n  In the \"HTTP Host\" field the qualified name of the host.\n  In the \"Interface\" field the qualified name of the interface to listen to.\n  In the \"Port\" field the port number to listen on.\n  Press the \"Add\" button.\n  Create a \"/www2\" directory under the HTTPServer ServerRoot directory. This will be used for the new mapping.\n  Click the icon in front of the Interface value.\n  Click the \"Add new directory\" link.\n  Choose the \"File System\" type and press the button \"Next>>\".\n  Enter for \"Path\" \"/www2\" and enter \"/www2/\" (or select with \"Browse\" button the same directory) in the \"Physical path\" location.\n  To give execute permission, specify the VSP user. (See also: VS-B-1 example)\n  Press the \"Save Changes\" button.\n  Repeat this setup for another interface, directing to a different path (for example WebDAV repository).\n\n\nTesting the Virtual Directories\n\n  To test the definition enter http://[first_interface:port]/ in location box of your browser. After this try http://[second_interface:port]/\n  Note that you may test this using official host name and localhost. The local loopback is also a possibility for a second interface.\n\n\nEquivalent SQL commands for above\n\n  Connect to the Virtuoso server via ISQL utility as the DBA user.\n  Define a virtual directory mapping for the host alias:\n     \nSQL> vhost_define (vhost=>'[first interface]:4444',lhost=>'[first interface]:4444',\n                      lpath=>'/',ppath=>'/www2/', def_page=>'index.html', is_brws=>1);\nSQL> vhost_define (vhost=>'[second interface]:4444',lhost=>'[first interface]:4444',\n                      lpath=>'/',ppath=>'/DAV/', is_dav=>1, def_page=>'index.html', is_brws=>1);\n     \n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Multiple interfaces setup" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The Web server can listen on multiple physical interfaces.\n  Requests for each interface can be dispatched to a separate directory.\n\n\nUsing the Virtual Directories UI\n\n  Login to the Conductor UI using the dba account.\n  Go to "Web Application Server" tab and then go to the "Virtual Domains & Directories" tab.\n  In the empty fields below the list of HTTP Listeners enter:\n  In the "HTTP Host" field the qualified name of the host.\n  In the "Interface" field the qualified name of the interface to listen to.\n  In the "Port" field the port number to listen on.\n  Press the "Add" button.\n  Create a "/www2" directory under the HTTPServer ServerRoot directory. This will be used for the new mapping.\n  Click the icon in front of the Interface value.\n  Click the "Add new directory" link.\n  Choose the "File System" type and press the button "Next>>".\n  Enter for "Path" "/www2" and enter "/www2/" (or select with "Browse" button the same directory) in the "Physical path" location.\n  To give execute permission, specify the VSP user. (See also: VS-B-1 example)\n  Press the "Save Changes" button.\n  Repeat this setup for another interface, directing to a different path (for example WebDAV repository).\n\n\nTesting the Virtual Directories\n\n  To test the definition enter http://[first_interface:port]/ in location box of your browser. After this try http://[second_interface:port]/\n  Note that you may test this using official host name and localhost. The local loopback is also a possibility for a second interface.\n\n\nEquivalent SQL commands for above\n\n  Connect to the Virtuoso server via ISQL utility as the DBA user.\n  Define a virtual directory mapping for the host alias:\n     \nSQL> vhost_define (vhost=>'[first interface]:4444',lhost=>'[first interface]:4444',\n                      lpath=>'/',ppath=>'/www2/', def_page=>'index.html', is_brws=>1);\nSQL> vhost_define (vhost=>'[second interface]:4444',lhost=>'[first interface]:4444',\n                      lpath=>'/',ppath=>'/DAV/', is_dav=>1, def_page=>'index.html', is_brws=>1);\n     \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Control of the Web Request Log" ;
	sioc:content	"\nPreliminaries\n\n  It is possible to log HTTP requests.\n  The log file can be analyzed with the Conductor UI, such as the Analog utility, going to the \"System Admin\" tab, then to the \"Monitor\" tab and then to the \"Log Viewer\" sub-tab.\n  HTTP logging is enabled by setting the HTTPLogFile parameter in the [HTTPServer] section of the database INI file.\n  The HTTPLogFile must be set to the path of the HTTP server log. For example:\n    [HTTPServer]\n ....\nHTTPLogFile   = ./http.log\n ....\n\n\nLog file format\nCLIENT_IP AUTH_TYPE AUTH_ID [DD/MMM/YYYY:HH:MM:SS +ZZZZ] \"HTTP REQUEST\" HTTP_RESPONSE CONTENT_LENGTH\nHere is an example:\n127.0.0.1 Basic test_user [02/May/2001:11:05:25 +0200] \"GET / HTTP/1.0\" 200 2186\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"HTTP requests logging" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  It is possible to log HTTP requests.\n  The log file can be analyzed with the Conductor UI, such as the Analog utility, going to the "System Admin" tab, then to the "Monitor" tab and then to the "Log Viewer" sub-tab.\n  HTTP logging is enabled by setting the HTTPLogFile parameter in the [HTTPServer] section of the database INI file.\n  The HTTPLogFile must be set to the path of the HTTP server log. For example:\n    [HTTPServer]\n ....\nHTTPLogFile   = ./http.log\n ....\n\n\nLog file format\nCLIENT_IP AUTH_TYPE AUTH_ID [DD/MMM/YYYY:HH:MM:SS +ZZZZ] "HTTP REQUEST" HTTP_RESPONSE CONTENT_LENGTH\nHere is an example:\n127.0.0.1 Basic test_user [02/May/2001:11:05:25 +0200] "GET / HTTP/1.0" 200 2186\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Basics" ;
	sioc:content	"\nPreliminaries\n\n    The HTTP protocol does not define a session management\n    To make a HTTP session few options are possible:\n\t\n\t    To set a cookie, but this feature is not supported in all browsers.\n\t    To use the opaque value of the digest authentication, it is also not supported in all user-agents\n\t    The most common way for doing this is to pass an URL variable (http://host:port/path?variable=value) to keep the session id; this is usually named \"URL-poisoning\".\n\t\n    \n    The Virtuoso HTTP session management consists of functions for session variables manipulation and an ability to define a pre- and post-processing function. \n    Also there is pre-defined table WS.WS.SESSION, which could be used in various applications to keep session data.  \n    There are special functions to store/retrieve/restore a variables into the memory. These can be used to persist/restore the session variables.  \n\nFor more details see: Session Management section in Virtuoso HTTP Server documentation.\n\n\nSession Table\nThe Virtuoso server offers a built-in session table. Application developers can also use their own table.\n\nCREATE TABLE WS.WS.SESSION (\n  S_ID                        varchar,      -- session id\n  S_EXPIRE                    datetime,     -- when it expires\n  S_VARS                      long varchar, -- serialized value of session variables\n  S_REQUEST_UNDER_RELOGIN     long varchar, -- serialized value of request status upon re-login detected \n  S_REALM                     varchar,      -- authentication realm   \n  S_IS_DIGEST                 integer,      -- flag for digest authentication \n  S_DOMAIN                    varchar,      -- authentication domain  \n  S_NONCE                     varchar,      -- nonce value\n  S_OPAQUE                    varchar,      -- opaque value\n  S_STALE                     varchar,      -- stale value\n  S_QOP                       varchar,      -- qop value\n  S_ALGORITHM                 varchar,      -- algorithm name\n  S_NC                        integer,      -- nonce count \n  primary key (S_REALM, S_ID))\n\n\nSession Table handling\nTo set, clear, or preset the in-memory based session table, the following functions are available.\n\n    connection_set() - sets the connection variable.\n    connection_get() - get a connection variable state.\n    connection_vars() - get all connection variables.\n    connection_vars_set() - clear and set the session variables.\n    connection_is_dirty() - indicate state of the session variables (whether changed during the session).\n\n\n    Common Web application framework\n    \n\tThe next examples demonstrates this three techniques for passing the session id to the VSPs\n\tEvery application have a startup page with links to login and register a new account\n\tOnce registered or logged in, the user will be redirected to the default page, that retrieves a session and variable increase it.\n\tAlso they have a authentication hook and post processing hook. These PL hooks are used to restore and save respectively the session variables.\n\tThe sessions are kept in the WS.WS.SESSION table. Note that not all columns are used in particular application. The full set of columns are used only in session with digest authentication example.\n    \n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Introduction to HTTP session management" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n    The HTTP protocol does not define a session management\n    To make a HTTP session few options are possible:\n\t\n\t    To set a cookie, but this feature is not supported in all browsers.\n\t    To use the opaque value of the digest authentication, it is also not supported in all user-agents\n\t    The most common way for doing this is to pass an URL variable (http://host:port/path?variable=value) to keep the session id; this is usually named "URL-poisoning".\n\t\n    \n    The Virtuoso HTTP session management consists of functions for session variables manipulation and an ability to define a pre- and post-processing function. \n    Also there is pre-defined table WS.WS.SESSION, which could be used in various applications to keep session data.  \n    There are special functions to store/retrieve/restore a variables into the memory. These can be used to persist/restore the session variables.  \n\nFor more details see: Session Management section in Virtuoso HTTP Server documentation.\n\n\nSession Table\nThe Virtuoso server offers a built-in session table. Application developers can also use their own table.\n\nCREATE TABLE WS.WS.SESSION (\n  S_ID                        varchar,      -- session id\n  S_EXPIRE                    datetime,     -- when it expires\n  S_VARS                      long varchar, -- serialized value of session variables\n  S_REQUEST_UNDER_RELOGIN     long varchar, -- serialized value of request status upon re-login detected \n  S_REALM                     varchar,      -- authentication realm   \n  S_IS_DIGEST                 integer,      -- flag for digest authentication \n  S_DOMAIN                    varchar,      -- authentication domain  \n  S_NONCE                     varchar,      -- nonce value\n  S_OPAQUE                    varchar,      -- opaque value\n  S_STALE                     varchar,      -- stale value\n  S_QOP                       varchar,      -- qop value\n  S_ALGORITHM                 varchar,      -- algorithm name\n  S_NC                        integer,      -- nonce count \n  primary key (S_REALM, S_ID))\n\n\nSession Table handling\nTo set, clear, or preset the in-memory based session table, the following functions are available.\n\n    connection_set() - sets the connection variable.\n    connection_get() - get a connection variable state.\n    connection_vars() - get all connection variables.\n    connection_vars_set() - clear and set the session variables.\n    connection_is_dirty() - indicate state of the session variables (whether changed during the session).\n\n\n    Common Web application framework\n    \n\tThe next examples demonstrates this three techniques for passing the session id to the VSPs\n\tEvery application have a startup page with links to login and register a new account\n\tOnce registered or logged in, the user will be redirected to the default page, that retrieves a session and variable increase it.\n\tAlso they have a authentication hook and post processing hook. These PL hooks are used to restore and save respectively the session variables.\n\tThe sessions are kept in the WS.WS.SESSION table. Note that not all columns are used in particular application. The full set of columns are used only in session with digest authentication example.\n    \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Basics" ;
	sioc:content	"\nThe default URL poisoning scheme\n\n  There is an authentication function that restores the session variables from a session table.\n  There is a post processing function to save the session variables into a session table.\n  An authentication function will try to get a URL parameter named \"sid\", if there is a session table row corresponding to it.\n  The state of session variables is read into memory with connection_vars_set().\n  The post processing function updates the session table, saving all session variables available with connection_vars().\n\n\nExample Description\n\n  Using the built-in session table this web application saves the state between sessions.\n  It has a front page with a two links \"register\" and \"login\".\n  The register page will ask for the user id and for a password.\n  The login page will ask for user id and password which are checked against an application dependant users table.\n  Both pages will do a redirect message with the newly generated session id, to the default application page.\n  The application pages (except front, login and register pages) can be placed under a separate directory.\n  The directory containing the VSP application must be setup as executable with authentication and post processing hooks defined.\n  The redirection to the application pages is made with URL parameter \"sid\" (the session id).\n  The session id must be transferred between pages for the restoration of session variables.\n  Each load of the default application page will restore the session variables, and will display the number increased by one.\n  If the session expires, a redirect to the login page will be performed.\n\n\nStep by step overview\n\nThe following sections describe the complete set of steps to make the application work.\nMost of this details also apply to the cookie and digest examples.\n\n\nAuthentication hook\n\n  The authentication hook will get the 'sid' parameter using the get_keyword().\n  If there is no row in the session table, it redirects to the login page.\n  If a row exists, then increase the expiry time, and restore the session variables with connection_vars_set().\n  If the authentication hook gets a 'logoff', then the session record is removed from the session table.\n  The browser is redirected to the login page.\n\n\nPost processing function\n\n  The 'sid' is read from session variables using connection_get(), as this is faster than from the URL parameters.\n Check for change of the session variables with connection_is_dirty().\n  If there is a change then serialize and store them into the session table. All variables are read with connection_vars().\n  At the end of the post-processing hook clear the in-memory variables to avoid reading from other HTTP client by using connection_vars_set(null).\n\n\nLogin, Default & Registration pages\n\n  The login page will check user & password against user-defined table (APP_USER) and if it matches, the new session will be created.\n  When starting a new session, the 'sid' connection variable is also setup to be available in the post-processing hook.\n  After a new session is done, there is a redirect using the header 'Location' to the default page.\n  Note the Location URL contains the 'sid' parameter' (see line 61 of vs_u_2.sql)\n  When the default page is called the authentication hook is already executed and session variables are in memory.\n  Therefore it is only necessary to get with connection_get() and set (if needed) with connection_set().\n  In this example, there is a 'ctr' variable that is a counter. It increases with each page reload.\n  The logout link passes another URL parameter 'logoff', this is also handled in the authentication hook.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Url poisoning example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nThe default URL poisoning scheme\n\n  There is an authentication function that restores the session variables from a session table.\n  There is a post processing function to save the session variables into a session table.\n  An authentication function will try to get a URL parameter named "sid", if there is a session table row corresponding to it.\n  The state of session variables is read into memory with connection_vars_set().\n  The post processing function updates the session table, saving all session variables available with connection_vars().\n\n\nExample Description\n\n  Using the built-in session table this web application saves the state between sessions.\n  It has a front page with a two links "register" and "login".\n  The register page will ask for the user id and for a password.\n  The login page will ask for user id and password which are checked against an application dependant users table.\n  Both pages will do a redirect message with the newly generated session id, to the default application page.\n  The application pages (except front, login and register pages) can be placed under a separate directory.\n  The directory containing the VSP application must be setup as executable with authentication and post processing hooks defined.\n  The redirection to the application pages is made with URL parameter "sid" (the session id).\n  The session id must be transferred between pages for the restoration of session variables.\n  Each load of the default application page will restore the session variables, and will display the number increased by one.\n  If the session expires, a redirect to the login page will be performed.\n\n\nStep by step overview\n\nThe following sections describe the complete set of steps to make the application work.\nMost of this details also apply to the cookie and digest examples.\n\n\nAuthentication hook\n\n  The authentication hook will get the 'sid' parameter using the get_keyword().\n  If there is no row in the session table, it redirects to the login page.\n  If a row exists, then increase the expiry time, and restore the session variables with connection_vars_set().\n  If the authentication hook gets a 'logoff', then the session record is removed from the session table.\n  The browser is redirected to the login page.\n\n\nPost processing function\n\n  The 'sid' is read from session variables using connection_get(), as this is faster than from the URL parameters.\n Check for change of the session variables with connection_is_dirty().\n  If there is a change then serialize and store them into the session table. All variables are read with connection_vars().\n  At the end of the post-processing hook clear the in-memory variables to avoid reading from other HTTP client by using connection_vars_set(null).\n\n\nLogin, Default & Registration pages\n\n  The login page will check user & password against user-defined table (APP_USER) and if it matches, the new session will be created.\n  When starting a new session, the 'sid' connection variable is also setup to be available in the post-processing hook.\n  After a new session is done, there is a redirect using the header 'Location' to the default page.\n  Note the Location URL contains the 'sid' parameter' (see line 61 of vs_u_2.sql)\n  When the default page is called the authentication hook is already executed and session variables are in memory.\n  Therefore it is only necessary to get with connection_get() and set (if needed) with connection_set().\n  In this example, there is a 'ctr' variable that is a counter. It increases with each page reload.\n  The logout link passes another URL parameter 'logoff', this is also handled in the authentication hook.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Basics" ;
	sioc:content	"\nPreliminaries\n\n    The cookies can be used to keep session id between two HTTP requests.\n    If the target browser can work with cookies, this method can be used instead of URL poisoning.\n\n\nSession state in a cookie example\n\n    On login or register, the set-cookie header writes a new session id.\n    The authentication function extracts the cookie value from the HTTP header.\n    If the session id is not valid, then the browser is redirected to the login page.\n    The post processing function is the same as in URL poisoning example.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Cookie example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n    The cookies can be used to keep session id between two HTTP requests.\n    If the target browser can work with cookies, this method can be used instead of URL poisoning.\n\n\nSession state in a cookie example\n\n    On login or register, the set-cookie header writes a new session id.\n    The authentication function extracts the cookie value from the HTTP header.\n    If the session id is not valid, then the browser is redirected to the login page.\n    The post processing function is the same as in URL poisoning example.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Basics" ;
	sioc:content	"\nPreliminaries\n\n    The Digest HTTP authentication can have the attributes kept between sessions.\n    If the target browser supports the Digest authentication, the opaque attribute can be used for the session id.\n    The Virtuoso server has a predefined authentication hook for digest authentication.\n    Digest authentication is held in WS.WS.DIGEST_AUTH.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Digest example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n    The Digest HTTP authentication can have the attributes kept between sessions.\n    If the target browser supports the Digest authentication, the opaque attribute can be used for the session id.\n    The Virtuoso server has a predefined authentication hook for digest authentication.\n    Digest authentication is held in WS.WS.DIGEST_AUTH.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Basics" ;
	sioc:content	"\nPreliminaries\n\n  The Virtuoso Web server can be set up for HTTPS listening, for increased security.\n  Passing the session id as a cookie or a URL parameter over HTTP connection is not secure.\n\n\nExample\nThis example uses the most common URL poisoning over SSL connection.\n\n\n  This example repeats the example VS-U-2, but result of VSP pages is transferred over SSL.\n  Make sure that files containing server\n  certificate/key data exists in the server working directory. The\n  following files are required for the example:\n  \n    virtuoso_cert.pem - server certificate \n    virtuoso_key.pem - server private key \n  \n  \n  The example script defines and starts a HTTPS server on port 4333.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"SSL example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The Virtuoso Web server can be set up for HTTPS listening, for increased security.\n  Passing the session id as a cookie or a URL parameter over HTTP connection is not secure.\n\n\nExample\nThis example uses the most common URL poisoning over SSL connection.\n\n\n  This example repeats the example VS-U-2, but result of VSP pages is transferred over SSL.\n  Make sure that files containing server\n  certificate/key data exists in the server working directory. The\n  following files are required for the example:\n  \n    virtuoso_cert.pem - server certificate \n    virtuoso_key.pem - server private key \n  \n  \n  The example script defines and starts a HTTPS server on port 4333.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Exercises" ;
	sioc:content	"\nCursor state examples\n\n  These examples have a scrollable page for browsing user records.\n  Each uses a PL scrollable cursor, and keeps the bookmark in the session state.\n  Data is taken from the demo database tables.\n  These examples demonstrate static, keyset and dynamic cursors.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"How to maintain a cursor state" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nCursor state examples\n\n  These examples have a scrollable page for browsing user records.\n  Each uses a PL scrollable cursor, and keeps the bookmark in the session state.\n  Data is taken from the demo database tables.\n  These examples demonstrate static, keyset and dynamic cursors.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Using XSLT to Format Output" ;
	sioc:content	"\nExample\nThis example renders XML with XSLT, and demonstrates the following:\n\n  Shows the style sheet in a database table as well as in the file system.\n  Shows use of the http_xslt() function to process XML with an XSL.\n  Resolving the stylesheet reference, e.g. virt://, DAV resident sheets.\n  Changing the stylesheet and when the sheet changes it is automatically detected.\n  Affecting the output character set.\n  Specifying parameters to the output xslt run.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Using XSLT to Format Output" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample\nThis example renders XML with XSLT, and demonstrates the following:\n\n  Shows the style sheet in a database table as well as in the file system.\n  Shows use of the http_xslt() function to process XML with an XSL.\n  Resolving the stylesheet reference, e.g. virt://, DAV resident sheets.\n  Changing the stylesheet and when the sheet changes it is automatically detected.\n  Affecting the output character set.\n  Specifying parameters to the output xslt run.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Using XSLT to Format Output" ;
	sioc:content	"\nXSLT Example\n\n  This example uses an XSLT to customize a view of a table.\n  The XSL demonstrates xsl:output to create the output.\n  The http_xslt() does not make the XSL-T transformation. It only registers the content as XML\n  such that when the document is requested by the client, the server will transform it with XSL-T.\n\n\nExample explained\n\n  string_output () - creates a string session.\n  select ... for xml auto element - Is the SQL/XML query over target table(s).\n  xml_auto() - This executes the above query, and stores the resultant XML document (entities) in the string session allocated by string_output().\n  string_output_string() - converts the string session to 'normal' string.\n  http_xslt()  - defines the XSL-T stylesheet for transformation of the XML content, which is stored in internal string session of the Web server.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Using XSLT to Format Output" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nXSLT Example\n\n  This example uses an XSLT to customize a view of a table.\n  The XSL demonstrates xsl:output to create the output.\n  The http_xslt() does not make the XSL-T transformation. It only registers the content as XML\n  such that when the document is requested by the client, the server will transform it with XSL-T.\n\n\nExample explained\n\n  string_output () - creates a string session.\n  select ... for xml auto element - Is the SQL/XML query over target table(s).\n  xml_auto() - This executes the above query, and stores the resultant XML document (entities) in the string session allocated by string_output().\n  string_output_string() - converts the string session to 'normal' string.\n  http_xslt()  - defines the XSL-T stylesheet for transformation of the XML content, which is stored in internal string session of the Web server.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Using xslt() in VSPs" ;
	sioc:content	"\nExample\n\n  This example displays user data using XSLT to customize the look.\n  The result is the same as in VS-X-2, but XSL-T transformation is done in the VSP.\n  The http_xslt() can be replaced (for main functionality) by the following:\n    \n      xml_tree_doc() over an XML document\n      xslt() with XSL-T stylesheet URI and result from xml_tree_doc()\n      http_value() with result from xslt()\n    \n  The above describes the steps that the web server makes in the VSP execution when http_xslt() is called.\n   This is not a direct equivalent, because Content-Type is not manipulated, as it is with http_xslt().\n   This means that web server can setup a Content-Type if it's not specified, otherwise it is specified in xsl:output element.\n   The same is true for encoding. If it is necessary to manipulate content-type with xsl:output, then use xml_tree_doc_media_type() to retrieve the media type from the XML entity, produced from xml-tree_doc(), and manually set 'Content-Type' header with http_header().\n   The above steps are useful for VSP&XSLT understanding, but in practice the http_xslt() is more suitable.\n   The http_xslt() is most appropriate if all content that produces a VSP should be transformed.\n\n   In the case where a piece of XML data is to be inserted in the middle of the HTML part of VSP, it cannot be done with http_xslt(). It may only be done with the step-by-step way above.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"An alternative of the http_xslt()" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample\n\n  This example displays user data using XSLT to customize the look.\n  The result is the same as in VS-X-2, but XSL-T transformation is done in the VSP.\n  The http_xslt() can be replaced (for main functionality) by the following:\n    \n      xml_tree_doc() over an XML document\n      xslt() with XSL-T stylesheet URI and result from xml_tree_doc()\n      http_value() with result from xslt()\n    \n  The above describes the steps that the web server makes in the VSP execution when http_xslt() is called.\n   This is not a direct equivalent, because Content-Type is not manipulated, as it is with http_xslt().\n   This means that web server can setup a Content-Type if it's not specified, otherwise it is specified in xsl:output element.\n   The same is true for encoding. If it is necessary to manipulate content-type with xsl:output, then use xml_tree_doc_media_type() to retrieve the media type from the XML entity, produced from xml-tree_doc(), and manually set 'Content-Type' header with http_header().\n   The above steps are useful for VSP&XSLT understanding, but in practice the http_xslt() is more suitable.\n   The http_xslt() is most appropriate if all content that produces a VSP should be transformed.\n\n   In the case where a piece of XML data is to be inserted in the middle of the HTML part of VSP, it cannot be done with http_xslt(). It may only be done with the step-by-step way above.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"DAV Security Model" ;
	sioc:content	"\nPreliminaries\n\n  A resource has a group and an owner user, just like files in a Unix file system.\n  A resource has flags determining the read, write, and execute privileges of it's owner,\n  other members of the owner's group, and all other users on it.\n  Additionally it has a free text indexing flag.\n  Collections are resources also. These have the same flags but the free text index\n  flag is treated differently.\n  DAV server asks for authentication in the following situations:\n    \n      on the read operation if URL is not public readable\n      on the write operations if URL is not public writable\n\t\n  The read operations are GET, POST, PROPFIND, HEAD\n  The write operations are LOCK, PUT, MOVE, COPY, DELETE, PROPPATCH\n  The Webdav admin account has full access rights to the Webdav repository, regardless of privilege flags.\n  The server will try to match the user to resource owner, second match to the group ownership,\n  and last to the additional groups membership.\n  If the URL is public readable, the request will be processed without asking for authentication.\n  The special flag in permissions can be set to the no-index, index, index recursively.\n  On resources, the last two settings act in the same way: if the resource is a text document,\n  the content will be free text indexed, otherwise not.\n  On collections, the 'no-index' will stop indexing of all direct and indirect members.\n  The 'index this' flag will cause indexing only over direct members (resources).\n  The 'index recursively' will allow free-text indexing of all direct and indirect members.\n  The values indicated in the WebDAV content management UI are N, T and R for the no-index, index, index recursively respectively.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"DAV Maintenance & Security" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  A resource has a group and an owner user, just like files in a Unix file system.\n  A resource has flags determining the read, write, and execute privileges of it's owner,\n  other members of the owner's group, and all other users on it.\n  Additionally it has a free text indexing flag.\n  Collections are resources also. These have the same flags but the free text index\n  flag is treated differently.\n  DAV server asks for authentication in the following situations:\n    \n      on the read operation if URL is not public readable\n      on the write operations if URL is not public writable\n\t\n  The read operations are GET, POST, PROPFIND, HEAD\n  The write operations are LOCK, PUT, MOVE, COPY, DELETE, PROPPATCH\n  The Webdav admin account has full access rights to the Webdav repository, regardless of privilege flags.\n  The server will try to match the user to resource owner, second match to the group ownership,\n  and last to the additional groups membership.\n  If the URL is public readable, the request will be processed without asking for authentication.\n  The special flag in permissions can be set to the no-index, index, index recursively.\n  On resources, the last two settings act in the same way: if the resource is a text document,\n  the content will be free text indexed, otherwise not.\n  On collections, the 'no-index' will stop indexing of all direct and indirect members.\n  The 'index this' flag will cause indexing only over direct members (resources).\n  The 'index recursively' will allow free-text indexing of all direct and indirect members.\n  The values indicated in the WebDAV content management UI are N, T and R for the no-index, index, index recursively respectively.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"DAV Properties" ;
	sioc:content	"\nDAV properties\nEvery collection resource has standard (computed) properties, and can have user-defined properties.\n\n\nComputed Properties\nThe computed properties are set by DAV server. The user-agents do not handle it. The computed resources are\nin the DAV name space. The computed properties are:\n\n  creationdate (#PCDATA) - when created\n  getcontentlength (#PCDATA) - length of the content\n  getcontenttype (#PCDATA) - mime type of the content\n  getetag (#PCDATA) - Etag of the resource\n  getlastmodified (#PCDATA) - when the resource is modified\n  lockdiscovery (activelock)*  - active lock information\n  resourcetype ANY - type of the resource (applicable only for collections)\n  supportedlock (lockentry)* - what lock supported\n\n\n\nUser Defined Properties\n\n  For other application specific purposes the PROPPATCH request can be used to set other properties.\n  The Virtuoso WebDAV server process by special way the following properties.\n  xml-sql - text of the SQL query to produce an XML document.\n  xml-sql-root - the root element name of the produced XML document.\n  xml-stylesheet  - the URL of the associated XSL-T style-sheet.\n  xml-sql-dtd - the external DTD link or 'on' in case of inline DTD.\n  xml-sql-schema - the external XMLSchema link.\n  xper - persistent XML storage.\n\n\n\nProperty handling\n\n  If an XML document has a property xml-stylesheet, then the retrieved content \n     will be transformed and sent instead of the original document content.\n  The xml-sql and xml-sql-root work together. If the resource has these properties,\n     and the content length is 0, then WebDAV server will execute the SQL query (see xml_auto()),\n    and the generated XML document will be sent to the user-agent.\n  If no xml-sql-root is associated, then the root element will be defaulted to the 'document'.\n  The xper property signals to the server that each member of the collection must be stored as XML persistent.\n  If the xper property is removed from a collection, then each currently stored persistent XML \n      document will revert to a normal text/xml at the next update. Each xper property will be removed.\n\n\n\nExample PROPFIND Request\n\n   PROPFIND /DAV/images/davadmin.jpg HTTP/1.1\n   Host: localhost:6666\n   Content-Type: text/xml\n   Depth: 1\n   Content-Length: 269\n   Authorization: \n\n   \n   \n   \n   \n   \n   \n   \n   \n \n\n\nResponse\n\n   HTTP/1.1 207 Multi-Status\n   Server: Virtuoso\n   Content-type: text/xml; charset=\"utf-8\"\n   Content-Length: 652\n   \n   \n   \n   \n   /DAV/images/davadmin.jpg\n   \n   \n   5725\n   Mon, 14 May 2001 13:26:54 GMT\n   \n   \n   HTTP/1.1 200 OK\n   \n   \n   \n   \n   \n   \n   HTTP/1.1 404 Not Found\n   \n   \n   \n\n\n\nExample PROPPATCH Request\n\n   PROPPATCH /bar.html HTTP/1.1\n   Host: www.foo.com\n   Content-Type: text/xml; charset=\"utf-8\"\n   Content-Length: xxxx\n\n   \n   \n     \n          \n               \n                    Jim Whitehead\n                    Roy Fielding\n               \n          \n     \n     \n          \n     \n   \n\n\n\nResponse\n\n   HTTP/1.1 207 Multi-Status\n   Content-Type: text/xml; charset=\"utf-8\"\n   Content-Length: xxxx\n\n   \n   \n     \n          http://www.foo.com/bar.html\n          \n               \n               HTTP/1.1 424 Failed Dependency\n          \n          \n               \n               HTTP/1.1 409 Conflict\n          \n     \n   \n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"DAV properties - PROPFIND and PROPPATCH" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nDAV properties\nEvery collection resource has standard (computed) properties, and can have user-defined properties.\n\n\nComputed Properties\nThe computed properties are set by DAV server. The user-agents do not handle it. The computed resources are\nin the DAV name space. The computed properties are:\n\n  creationdate (#PCDATA) - when created\n  getcontentlength (#PCDATA) - length of the content\n  getcontenttype (#PCDATA) - mime type of the content\n  getetag (#PCDATA) - Etag of the resource\n  getlastmodified (#PCDATA) - when the resource is modified\n  lockdiscovery (activelock)*  - active lock information\n  resourcetype ANY - type of the resource (applicable only for collections)\n  supportedlock (lockentry)* - what lock supported\n\n\n\nUser Defined Properties\n\n  For other application specific purposes the PROPPATCH request can be used to set other properties.\n  The Virtuoso WebDAV server process by special way the following properties.\n  xml-sql - text of the SQL query to produce an XML document.\n  xml-sql-root - the root element name of the produced XML document.\n  xml-stylesheet  - the URL of the associated XSL-T style-sheet.\n  xml-sql-dtd - the external DTD link or 'on' in case of inline DTD.\n  xml-sql-schema - the external XMLSchema link.\n  xper - persistent XML storage.\n\n\n\nProperty handling\n\n  If an XML document has a property xml-stylesheet, then the retrieved content \n     will be transformed and sent instead of the original document content.\n  The xml-sql and xml-sql-root work together. If the resource has these properties,\n     and the content length is 0, then WebDAV server will execute the SQL query (see xml_auto()),\n    and the generated XML document will be sent to the user-agent.\n  If no xml-sql-root is associated, then the root element will be defaulted to the 'document'.\n  The xper property signals to the server that each member of the collection must be stored as XML persistent.\n  If the xper property is removed from a collection, then each currently stored persistent XML \n      document will revert to a normal text/xml at the next update. Each xper property will be removed.\n\n\n\nExample PROPFIND Request\n\n   PROPFIND /DAV/images/davadmin.jpg HTTP/1.1\n   Host: localhost:6666\n   Content-Type: text/xml\n   Depth: 1\n   Content-Length: 269\n   Authorization: \n\n   <?xml version="1.0" encoding="utf-8"?>\n   <propfind xmlns="DAV:"><prop>\n   <getcontentlength xmlns="DAV:"/>\n   <getlastmodified xmlns="DAV:"/>\n   <displayname xmlns="DAV:"/>\n   <executable xmlns="http://apache.org/dav/props/"/>\n   <resourcetype xmlns="DAV:"/>\n   </prop></propfind>\n \n\n\nResponse\n\n   HTTP/1.1 207 Multi-Status\n   Server: Virtuoso\n   Content-type: text/xml; charset="utf-8"\n   Content-Length: 652\n   \n   <?xml version="1.0" encoding="utf-8"?>\n   <D:multistatus xmlns:D="DAV:">\n   <D:response xmlns:lp0="DAV:" xmlns:i0="DAV:">\n   <D:href>/DAV/images/davadmin.jpg</D:href>\n   <D:propstat>\n   <D:prop>\n   <lp0:getcontentlength>5725</lp0:getcontentlength>\n   <lp0:getlastmodified>Mon, 14 May 2001 13:26:54 GMT</lp0:getlastmodified>\n   <D:resourcetype/>\n   </D:prop>\n   <D:status>HTTP/1.1 200 OK</D:status>\n   </D:propstat>\n   <D:propstat>\n   <D:prop>\n   <i0:displayname/>\n   <i0:executable/>\n   </D:prop>\n   <D:status>HTTP/1.1 404 Not Found</D:status>\n   </D:propstat>\n   </D:response>\n   </D:multistatus>\n\n\n\nExample PROPPATCH Request\n\n   PROPPATCH /bar.html HTTP/1.1\n   Host: www.foo.com\n   Content-Type: text/xml; charset="utf-8"\n   Content-Length: xxxx\n\n   <?xml version="1.0" encoding="utf-8" ?>\n   <D:propertyupdate xmlns:D="DAV:"\n   xmlns:Z="http://www.w3.com/standards/z39.50/">\n     <D:set>\n          <D:prop>\n               <Z:authors>\n                    <Z:Author>Jim Whitehead</Z:Author>\n                    <Z:Author>Roy Fielding</Z:Author>\n               </Z:authors>\n          </D:prop>\n     </D:set>\n     <D:remove>\n          <D:prop><Z:Copyright-Owner/></D:prop>\n     </D:remove>\n   </D:propertyupdate>\n\n\n\nResponse\n\n   HTTP/1.1 207 Multi-Status\n   Content-Type: text/xml; charset="utf-8"\n   Content-Length: xxxx\n\n   <?xml version="1.0" encoding="utf-8" ?>\n   <D:multistatus xmlns:D="DAV:"\n   xmlns:Z="http://www.w3.com/standards/z39.50">\n     <D:response>\n          <D:href>http://www.foo.com/bar.html</D:href>\n          <D:propstat>\n               <D:prop><Z:Authors/></D:prop>\n               <D:status>HTTP/1.1 424 Failed Dependency</D:status>\n          </D:propstat>\n          <D:propstat>\n               <D:prop><Z:Copyright-Owner/></D:prop>\n               <D:status>HTTP/1.1 409 Conflict</D:status>\n          </D:propstat>\n     </D:response>\n   </D:multistatus>\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"DAV Properties" ;
	sioc:content	"\nPreliminaries\n\n  The SQL query can be transformed into an XML document with xml_auto() for example.\n  The SQL/XML documents are automatically generated resources, based on a SQL query.\n  Two types of SQL/XML documents can be defined in the WebDAV repository:\n  Persistent documents and Immediate transformation.\n\n\nPersistent Documents\nThe persistent SQL/XML documents have the same behavior as text/xml documents:\n\n  They have a mime type of text/xml, and have a content.\n  The content can be refreshed with a scheduled event.\n  The content is free-text indexed\n\n\nImmediate Transformation\nThe SQL/XML documents with immediate transformation are formed as they are requested.\n\n  The content is empty\n  Hence the content is not free-text indexed\n\n\nProperties\n\n  Both resources have a property xml-sql. The value of the property is the SQL query string.\n  If content length is zero and the xml-sql property is set, then the server will do an immediate transformation.\n  Both resources have xml-sql-root, xml-sql-dtd, and xml-sql-schema properties (see also vs-d-2).\n\n\nSQL/XML resource example\nThe example SQL script creates a few SQL/XML resources.\nClick here for resources made in /DAV/vs_d_3/\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"SQL/XML documents in DAV" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The SQL query can be transformed into an XML document with xml_auto() for example.\n  The SQL/XML documents are automatically generated resources, based on a SQL query.\n  Two types of SQL/XML documents can be defined in the WebDAV repository:\n  Persistent documents and Immediate transformation.\n\n\nPersistent Documents\nThe persistent SQL/XML documents have the same behavior as text/xml documents:\n\n  They have a mime type of text/xml, and have a content.\n  The content can be refreshed with a scheduled event.\n  The content is free-text indexed\n\n\nImmediate Transformation\nThe SQL/XML documents with immediate transformation are formed as they are requested.\n\n  The content is empty\n  Hence the content is not free-text indexed\n\n\nProperties\n\n  Both resources have a property xml-sql. The value of the property is the SQL query string.\n  If content length is zero and the xml-sql property is set, then the server will do an immediate transformation.\n  Both resources have xml-sql-root, xml-sql-dtd, and xml-sql-schema properties (see also vs-d-2).\n\n\nSQL/XML resource example\nThe example SQL script creates a few SQL/XML resources.\nClick here for resources made in /DAV/vs_d_3/\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"DAV Special URI's" ;
	sioc:content	"\nWebDAV parameters\nThe WebDAV server has the following special URL parameters:\n\n  XPATH - the XPATH query to perform against the existing XML document\n  set_tag - the root XML element (default is 'document')\n  result_tag - the elements tag\n\n\nPreparation\nThis example uses the SQL/XML documents generated by VS-D-3.\n\nExample with result_tag\nFrom within a browser do an XPATH query for a subset of attributes. Use the following URL:\nhttp://host:port/DAV/vs_d_3/URLMultiTable.xml?XPATH=/root/Customers/@CustomerID&result_tag=id\nOr click this relative link.\n\nExpected result with result_tag\nFor browsers such as Opera and Netscape, view the source of the result page to see the XML.\nFor browsers capable of rendering the XML, such as Internet Explorer 5+, the XML result will\nbe shown.\nThis excerpt from the expected output shows the xml document containing the CustomerID only:\n\n\n   \n   \n   \n   ALFKI\n   \n   ANATR\n   \n   ANTON\n   \n   AROUT\n   \n   BERGS\n   \n   BLAUS\n   \n   BLONP\n   \n   BOLID\n   \n   BONAP\n   ...\n   \n\n\nExample with set_tag\nSimilar to previous example, but replacing result_tag with the set_tag parameter. Enter this URL into a browser:\n\nhttp://host:port/DAV/vs_d_3/URLMultiTable.xml?XPATH=/root/Customers[@CustomerID+like+'A*']/@CustomerID&set_tag=id\nOr click this relative link.\n\nNote: the XPATH queries can only be performed against the persistent storage.\n\nExpected result with set_tag\n\n \n \n ALFKIANATRANTONAROUT\n\n\nExample with set_tag and result_tag\nSimilar to previous example, but adding result_tag parameter. Enter this URL into a browser:\n\nhttp://host:port/DAV/vs_d_3/URLMultiTable.xml?XPATH=/root/Customers[@CustomerID+like+'A*']/@CustomerID&set_tag=id&result_tag=p\nOr click this relative link.\n\nNote: the XPATH queries can only be performed against the persistent storage.\n\nExpected result with set_tag and result_tag\n\n \n \n
\nALFKI
\n
\nANATR
\n
\nANTON
\n
\nAROUT
\n\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"DAV Special URI's" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nWebDAV parameters\nThe WebDAV server has the following special URL parameters:\n\n  XPATH - the XPATH query to perform against the existing XML document\n  set_tag - the root XML element (default is 'document')\n  result_tag - the elements tag\n\n\nPreparation\nThis example uses the SQL/XML documents generated by VS-D-3.\n\nExample with result_tag\nFrom within a browser do an XPATH query for a subset of attributes. Use the following URL:\nhttp://host:port/DAV/vs_d_3/URLMultiTable.xml?XPATH=/root/Customers/@CustomerID&result_tag=id\nOr click this relative link.\n\nExpected result with result_tag\nFor browsers such as Opera and Netscape, view the source of the result page to see the XML.\nFor browsers capable of rendering the XML, such as Internet Explorer 5+, the XML result will\nbe shown.\nThis excerpt from the expected output shows the xml document containing the CustomerID only:\n\n\n   <?xml version="1.0" encoding="ISO-8859-1"?>\n   <document>\n   <id>\n   ALFKI</id>\n   <id>\n   ANATR</id>\n   <id>\n   ANTON</id>\n   <id>\n   AROUT</id>\n   <id>\n   BERGS</id>\n   <id>\n   BLAUS</id>\n   <id>\n   BLONP</id>\n   <id>\n   BOLID</id>\n   <id>\n   BONAP</id>\n   ...\n   </document>\n\n\nExample with set_tag\nSimilar to previous example, but replacing result_tag with the set_tag parameter. Enter this URL into a browser:\n\nhttp://host:port/DAV/vs_d_3/URLMultiTable.xml?XPATH=/root/Customers[@CustomerID+like+'A*']/@CustomerID&set_tag=id\nOr click this relative link.\n\nNote: the XPATH queries can only be performed against the persistent storage.\n\nExpected result with set_tag\n\n <?xml version="1.0" encoding="ISO-8859-1"?>\n <id>\n ALFKIANATRANTONAROUT</id>\n\n\nExample with set_tag and result_tag\nSimilar to previous example, but adding result_tag parameter. Enter this URL into a browser:\n\nhttp://host:port/DAV/vs_d_3/URLMultiTable.xml?XPATH=/root/Customers[@CustomerID+like+'A*']/@CustomerID&set_tag=id&result_tag=p\nOr click this relative link.\n\nNote: the XPATH queries can only be performed against the persistent storage.\n\nExpected result with set_tag and result_tag\n\n <?xml version="1.0" encoding="ISO-8859-1"?>\n <id>\n<p>\nALFKI</p>\n<p>\nANATR</p>\n<p>\nANTON</p>\n<p>\nAROUT</p>\n</id>\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"DAV Free Text Index" ;
	sioc:content	"\nReal time index mode\n\n  The WebDAV content is free-text indexed on all documents with a text content.\n  The documents may have their indexing disabled by turning off the indexing flag. (see DAV security)\n  By default the WebDAV content is in real time mode. That means after insert/update/delete\n  the content immediately will be indexed.\n  The real time mode will update the free text index as soon as the indexed resources change.\n  Advantage is that a text search query can be performed immediately after an action.\n  This will however take substantially longer if any significant number\n  of resources are regularly updated.\n\n\nBatch Mode indexing\n\n  In this mode, changes of the WebDAV content are logged for later indexing.\n  The index is updated periodically, at approximately the specified period (in minutes),\n  if allowed by other background tasks.\n  The index refresh period is a scheduled event period to refresh the free-text index in batch mode.\n  To switch between modes in the Conductor UI, go to the \"Web Application Server\" tab, then go to the \"Content Management\" tab and then go to the \"Text Triggers\" sub-tab.\n  This can also be achieved using a sql command. For example to turn batch mode on for 7 minute updates use:\n\n  SQL> DB.DBA.vt_batch_update ('WS.WS.SYS_DAV_RES', 'ON', 7);\n\n\n\nExample\nThe demonstration allows the mode to be switched. Resource content can be created and tested.\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"DAV Free Text Index : general" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nReal time index mode\n\n  The WebDAV content is free-text indexed on all documents with a text content.\n  The documents may have their indexing disabled by turning off the indexing flag. (see DAV security)\n  By default the WebDAV content is in real time mode. That means after insert/update/delete\n  the content immediately will be indexed.\n  The real time mode will update the free text index as soon as the indexed resources change.\n  Advantage is that a text search query can be performed immediately after an action.\n  This will however take substantially longer if any significant number\n  of resources are regularly updated.\n\n\nBatch Mode indexing\n\n  In this mode, changes of the WebDAV content are logged for later indexing.\n  The index is updated periodically, at approximately the specified period (in minutes),\n  if allowed by other background tasks.\n  The index refresh period is a scheduled event period to refresh the free-text index in batch mode.\n  To switch between modes in the Conductor UI, go to the "Web Application Server" tab, then go to the "Content Management" tab and then go to the "Text Triggers" sub-tab.\n  This can also be achieved using a sql command. For example to turn batch mode on for 7 minute updates use:\n\n  SQL> DB.DBA.vt_batch_update ('WS.WS.SYS_DAV_RES', 'ON', 7);\n\n\n\nExample\nThe demonstration allows the mode to be switched. Resource content can be created and tested.\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Content Types and Names" ;
	sioc:content	"\nPreliminaries\n\n  The user-agents (browsers) may supply the content-type for an uploaded resource.\n  A resource in the WebDAV repository can have a supplied content-type associated to the resource.\n  If the content type is not supplied, the WebDAV server does a mapping from file extension to mime type.\n  Mapping table is held in WS.WS.SYS_DAV_RES_TYPES and used by http_mime_type() function.\n  Using Conductor UI can be defined additional MIME type: Go to the \"Web Application Server\" tab, then go to the \"Content Management\" tab and then go to the \"Resource Types\" sub-tab. Here press the \"Create New Type\" button.\n\n\nMime lookup example\nThe example requests a file, then the name of the file will be matched against the mime types table. The resulting mime type is displayed.\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Mapping between resource content types, and name extensions" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The user-agents (browsers) may supply the content-type for an uploaded resource.\n  A resource in the WebDAV repository can have a supplied content-type associated to the resource.\n  If the content type is not supplied, the WebDAV server does a mapping from file extension to mime type.\n  Mapping table is held in WS.WS.SYS_DAV_RES_TYPES and used by http_mime_type() function.\n  Using Conductor UI can be defined additional MIME type: Go to the "Web Application Server" tab, then go to the "Content Management" tab and then go to the "Resource Types" sub-tab. Here press the "Create New Type" button.\n\n\nMime lookup example\nThe example requests a file, then the name of the file will be matched against the mime types table. The resulting mime type is displayed.\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"DAV Tables" ;
	sioc:content	"\nDAV Tables\n\nThe WebDAV DB schema is detailed in the vs_d_7.sql that creates each table.\nThe schema is available from a shipped database, as it is automactically\ngenerated if it does not exist.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Complete description for all DAV tables" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nDAV Tables\n\nThe WebDAV DB schema is detailed in the vs_d_7.sql that creates each table.\nThe schema is available from a shipped database, as it is automactically\ngenerated if it does not exist.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Exercises" ;
	sioc:content	"\nExample of making XML reports in DAV\n\n  The example makes XML reports on the Demo database and inserts them into a user's DAV folder.\n  The application will take a user registration, and make a DAV account\n  Enter parameters for a query, e.g. product group for tracking sales\n  A resulting XML report is put in the user's created DAV collection.\n  Once the report is made a HTTP redirect occurs to the new resource.\n  Note that the login for DAV will be different from the application's login. This is OK in this context.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Simple DAV Report Generation" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nExample of making XML reports in DAV\n\n  The example makes XML reports on the Demo database and inserts them into a user's DAV folder.\n  The application will take a user registration, and make a DAV account\n  Enter parameters for a query, e.g. product group for tracking sales\n  A resulting XML report is put in the user's created DAV collection.\n  Once the report is made a HTTP redirect occurs to the new resource.\n  Note that the login for DAV will be different from the application's login. This is OK in this context.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Control Web server threads" ;
	sioc:content	"\nPreliminaries\n\n  The HTTP requests are processed by HTTP server threads.\n  The HTTP threads are configurable in the INI file. Hence they are a limited number.\n  A VSP execution can run in the background by using http_flush().\n  Pending HTTP requests can be monitored (including the background tasks).\n  Pending HTTP requests can be aborted with http_kill().\n\n\nThread killing example\n\nRun the long_task.vsp to start a thread that takes a long time.\nThis will start another thread to run vs_c_1_sample_1.vsp\nAll pending tutorial HTTP requests will be listed.\nThe long_task thread can then be killed by using the link.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Web server threads monitor" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The HTTP requests are processed by HTTP server threads.\n  The HTTP threads are configurable in the INI file. Hence they are a limited number.\n  A VSP execution can run in the background by using http_flush().\n  Pending HTTP requests can be monitored (including the background tasks).\n  Pending HTTP requests can be aborted with http_kill().\n\n\nThread killing example\n\nRun the long_task.vsp to start a thread that takes a long time.\nThis will start another thread to run vs_c_1_sample_1.vsp\nAll pending tutorial HTTP requests will be listed.\nThe long_task thread can then be killed by using the link.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Importing Web Content" ;
	sioc:content	"\nImporting Web Content\nDefault traversal algorithm of the web robot.\n\n  Keep into the queue only the start link\n  Get the oldest entry from the queue (for the given target) and mark as 'pending'\n  Retrieve the link\n  Parse the page and extract the URLs\n  Apply the \"Traverse and do not traverse\" rules\n  Insert the new entries in the queue\n  Mark queue entry as 'retrieved'\n  Repeat from step 2, if there are more 'waiting' entries, otherwise finish\n\n\nTraverse and do not traverse links\n\n  Traverse - this is a semicolon separated string which contains the path masks\n    (the like predicate chars are applicable). Any link that matches any of these\n    masks will be added to the queue for processing, but only if it doesn't match the\n    do not traverse masks.\n   \n  Do not traverse - the format of the string is the same (semicolon separated),\n    but the masks mean the opposite. If any link matches the rule it will be skipped from processing.\n\n\nTables of the Web Robot\n\n-- Target site definition\ncreate table WS.WS.VFS_SITE (\n    VS_DESCR    varchar,    -- human readable description\n    VS_HOST     varchar,    -- target host name\n    VS_URL      varchar,    -- start URL path\n    VS_INX      varchar (5),-- reserved\n    VS_OWN      integer,    -- local WebDAV owner of the retrieved content\n    VS_ROOT     varchar,    -- local WebDAV collection destination\n    VS_NEWER    datetime,   -- update only newer than (this date)\n    VS_DEL      varchar,    -- delete local resource if removal on target detected\n    VS_FOLLOW   varchar,    -- walk on this links\n    VS_NFOLLOW  varchar,    -- do not walk on this links\n    VS_SRC      varchar,    -- retrieve images\n    VS_OPTIONS  varchar,    -- if target wants authentication the uid/pwd are stored\n    VS_METHOD   varchar,    -- use WebDAV or traditional HTTP method\n    VS_OTHER    varchar,    -- walk on foreign links\n    primary key (VS_HOST, VS_ROOT));\ncreate index VS_HOST_ROOT on WS.WS.VFS_SITE (VS_HOST, VS_URL, VS_ROOT)\n;\n\n-- Queue table\ncreate table WS.WS.VFS_QUEUE (\n    VQ_HOST     varchar,    -- target host name\n    VQ_TS       datetime,    -- date and time of adding into the queue\n    VQ_URL      varchar,    -- target URL path\n    VQ_ROOT     varchar,    -- local WebDAV folder destination\n    VQ_STAT     varchar (15),    -- status\n    VQ_OTHER    varchar,    -- retrieved from other site\n    primary key (VQ_HOST, VQ_URL, VQ_ROOT));\ncreate index VQ_HOST_ROOT_STAT on WS.WS.VFS_QUEUE (VQ_HOST, VQ_ROOT, VQ_STAT);\ncreate index VQ_HOST_ROOT on WS.WS.VFS_QUEUE (VQ_HOST, VQ_ROOT);\ncreate index VQ_HOST_TIME on WS.WS.VFS_QUEUE (VQ_HOST, VQ_ROOT, VQ_TS);\ncreate index VQ_TS on VFS_QUEUE (VQ_TS)\n;\n\n\n-- Retrieved URLs table\ncreate table WS.WS.VFS_URL (\n    VU_HOST     varchar,    -- target host name\n    VU_URL      varchar,    -- retrieved URL path\n    VU_ROOT     varchar,    -- local WebDAV folder destination\n    VU_CHKSUM   varchar,    -- content checksum\n    VU_ETAG     varchar,    -- target's ETag\n    VU_CPTIME   datetime,   -- retrieval date and time\n    VU_OTHER    varchar,    -- retrieved from other site\n    primary key (VU_HOST, VU_URL, VU_ROOT));\ncreate index VU_HOST_ROOT on WS.WS.VFS_URL (VU_HOST, VU_ROOT)\n;\n\n\nHooks for Parametizing the Web Robot\n\nThe custom queue hook can be used to extract next entry from the robot's queue and\nfollow a custom algorithm. The prototype of the hook is:\n\n\ncreate procedure\nDB.DBA.VFS_HOOK (in host varchar, in collection varchar, out url varchar, in data any)\n{\n  -- choose an entry from queue (may use the user-specific date passed as 'data' variable)\n  -- mark as 'pending'\n  -- set the 'url' from the chosen entry\n  -- return 1 on success or 0 if no more entries\n}\n;\n\n\nWeb Index Example\n\n  Example does a breadth first traversal of all reachable sites.\n  To actually get some links retrieved change all the occurences of www.foo.bar to a site of your choice.\n  The site to process are separately maintained in an 'interesting sites' list.\n  The example runs on multiple threads.\n  The interface can start n threads running the robot.\n  There is a web page showing the running status, e.g. number of pages fetched in the last minute.\n  A stop button will kill http threads running the web robot.\n  Important: The example requires a license to run, due to multiple web threads.\n\n" ;
	sioc:has_container	ns2:web ;
	sioc:description	"Importing Web Content" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nImporting Web Content\nDefault traversal algorithm of the web robot.\n\n  Keep into the queue only the start link\n  Get the oldest entry from the queue (for the given target) and mark as 'pending'\n  Retrieve the link\n  Parse the page and extract the URLs\n  Apply the "Traverse and do not traverse" rules\n  Insert the new entries in the queue\n  Mark queue entry as 'retrieved'\n  Repeat from step 2, if there are more 'waiting' entries, otherwise finish\n\n\nTraverse and do not traverse links\n\n  Traverse - this is a semicolon separated string which contains the path masks\n    (the like predicate chars are applicable). Any link that matches any of these\n    masks will be added to the queue for processing, but only if it doesn't match the\n    do not traverse masks.\n   \n  Do not traverse - the format of the string is the same (semicolon separated),\n    but the masks mean the opposite. If any link matches the rule it will be skipped from processing.\n\n\nTables of the Web Robot\n\n-- Target site definition\ncreate table WS.WS.VFS_SITE (\n    VS_DESCR    varchar,    -- human readable description\n    VS_HOST     varchar,    -- target host name\n    VS_URL      varchar,    -- start URL path\n    VS_INX      varchar (5),-- reserved\n    VS_OWN      integer,    -- local WebDAV owner of the retrieved content\n    VS_ROOT     varchar,    -- local WebDAV collection destination\n    VS_NEWER    datetime,   -- update only newer than (this date)\n    VS_DEL      varchar,    -- delete local resource if removal on target detected\n    VS_FOLLOW   varchar,    -- walk on this links\n    VS_NFOLLOW  varchar,    -- do not walk on this links\n    VS_SRC      varchar,    -- retrieve images\n    VS_OPTIONS  varchar,    -- if target wants authentication the uid/pwd are stored\n    VS_METHOD   varchar,    -- use WebDAV or traditional HTTP method\n    VS_OTHER    varchar,    -- walk on foreign links\n    primary key (VS_HOST, VS_ROOT));\ncreate index VS_HOST_ROOT on WS.WS.VFS_SITE (VS_HOST, VS_URL, VS_ROOT)\n;\n\n-- Queue table\ncreate table WS.WS.VFS_QUEUE (\n    VQ_HOST     varchar,    -- target host name\n    VQ_TS       datetime,    -- date and time of adding into the queue\n    VQ_URL      varchar,    -- target URL path\n    VQ_ROOT     varchar,    -- local WebDAV folder destination\n    VQ_STAT     varchar (15),    -- status\n    VQ_OTHER    varchar,    -- retrieved from other site\n    primary key (VQ_HOST, VQ_URL, VQ_ROOT));\ncreate index VQ_HOST_ROOT_STAT on WS.WS.VFS_QUEUE (VQ_HOST, VQ_ROOT, VQ_STAT);\ncreate index VQ_HOST_ROOT on WS.WS.VFS_QUEUE (VQ_HOST, VQ_ROOT);\ncreate index VQ_HOST_TIME on WS.WS.VFS_QUEUE (VQ_HOST, VQ_ROOT, VQ_TS);\ncreate index VQ_TS on VFS_QUEUE (VQ_TS)\n;\n\n\n-- Retrieved URLs table\ncreate table WS.WS.VFS_URL (\n    VU_HOST     varchar,    -- target host name\n    VU_URL      varchar,    -- retrieved URL path\n    VU_ROOT     varchar,    -- local WebDAV folder destination\n    VU_CHKSUM   varchar,    -- content checksum\n    VU_ETAG     varchar,    -- target's ETag\n    VU_CPTIME   datetime,   -- retrieval date and time\n    VU_OTHER    varchar,    -- retrieved from other site\n    primary key (VU_HOST, VU_URL, VU_ROOT));\ncreate index VU_HOST_ROOT on WS.WS.VFS_URL (VU_HOST, VU_ROOT)\n;\n\n\nHooks for Parametizing the Web Robot\n\nThe custom queue hook can be used to extract next entry from the robot's queue and\nfollow a custom algorithm. The prototype of the hook is:\n\n\ncreate procedure\nDB.DBA.VFS_HOOK (in host varchar, in collection varchar, out url varchar, in data any)\n{\n  -- choose an entry from queue (may use the user-specific date passed as 'data' variable)\n  -- mark as 'pending'\n  -- set the 'url' from the chosen entry\n  -- return 1 on success or 0 if no more entries\n}\n;\n\n\nWeb Index Example\n\n  Example does a breadth first traversal of all reachable sites.\n  To actually get some links retrieved change all the occurences of www.foo.bar to a site of your choice.\n  The site to process are separately maintained in an 'interesting sites' list.\n  The example runs on multiple threads.\n  The interface can start n threads running the robot.\n  There is a web page showing the running status, e.g. number of pages fetched in the last minute.\n  A stop button will kill http threads running the web robot.\n  Important: The example requires a license to run, due to multiple web threads.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Blog application" ;
	sioc:content	"\nOverview\n\nThe application allow users to post messages to a Weblog servers using XML-RPC protocol.\nIt can work locally where as server is used one running the application.\nAlso it demonstrate usage of VSPX calendar, dataset and login controls.\nThe demo also shows usage of blogger API.\n\n\nApplication pages\nThe application has the following pages:\n\nLogin \n \n  This page allow existing Web users to login to the application. \n  Furthermore these credentials will be used to authenticate against Weblog server. \n  When user is authenticated the request will be redirected to the home page.\n  \n  \n Configuration\n  \n \n  This page is accessible via \"Settings\" link of home page (see below). \n  It allows users to configure parameters for blogger API request as \"appkey\", \"blogID\" and target server endpoint.\n  It's vital for application to set these properly before trying any aother action on home page.\n  \n  \n Home\n \n  This page allows users to enter a new message, to edit an existing or see in archive organized by date.\n  To look at the archive calendar control is used for navigation. Please note that this application limits number of messages shown at screen for brevity; so as exercise it can be edited to show number of messages entered on that page in special box.  \n  \n\n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Blog application" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\nOverview\n\nThe application allow users to post messages to a Weblog servers using XML-RPC protocol.\nIt can work locally where as server is used one running the application.\nAlso it demonstrate usage of VSPX calendar, dataset and login controls.\nThe demo also shows usage of blogger API.\n\n\nApplication pages\nThe application has the following pages:\n\nLogin \n \n  This page allow existing Web users to login to the application. \n  Furthermore these credentials will be used to authenticate against Weblog server. \n  When user is authenticated the request will be redirected to the home page.\n  \n  \n Configuration\n  \n \n  This page is accessible via "Settings" link of home page (see below). \n  It allows users to configure parameters for blogger API request as "appkey", "blogID" and target server endpoint.\n  It's vital for application to set these properly before trying any aother action on home page.\n  \n  \n Home\n \n  This page allows users to enter a new message, to edit an existing or see in archive organized by date.\n  To look at the archive calendar control is used for navigation. Please note that this application limits number of messages shown at screen for brevity; so as exercise it can be edited to show number of messages entered on that page in special box.  \n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Weblog Bridge" ;
	sioc:content	"\nExample\n\nThe demo shows a way to replicate a blog messages to multiple destinations.\nThe destinations are configurable via \"Blogger Brigde\" link of blogging page.\nA destination server *MUST* support one of following APIs: blogger, metaWeblog or Movable Type.\nTo select a blog from target the URL, Username and password must be entered before \"Fetch\" button clicked.\nYou may choose one of BLOGs listed in pop-up window.\nOnce you have defined a Bridge target, you can verify the bridging with post via main page.\nNote that bridge will post the messages with it's own application key ; so that message will not be replicated. if you are choosed the same server and blog, messages will appear twise as original will be replicated.\n\n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Synchronizing local Blog storage with multiple Blog servers via Blogger APIs" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\nExample\n\nThe demo shows a way to replicate a blog messages to multiple destinations.\nThe destinations are configurable via "Blogger Brigde" link of blogging page.\nA destination server *MUST* support one of following APIs: blogger, metaWeblog or Movable Type.\nTo select a blog from target the URL, Username and password must be entered before "Fetch" button clicked.\nYou may choose one of BLOGs listed in pop-up window.\nOnce you have defined a Bridge target, you can verify the bridging with post via main page.\nNote that bridge will post the messages with it's own application key ; so that message will not be replicated. if you are choosed the same server and blog, messages will appear twise as original will be replicated.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Making a dynamic blog posts" ;
	sioc:content	"\nOverview\n\n    This demo makes a Weblog and posts into it using Metaweblog API two dynamic posts\n    The dynamic posts contains XML template(s) which will be executed at render time.\n    The first post makes a SQL quesry on Demo Database table 'Shippers' and inserts a table\n\tinto the user's weblog.\n    \n    The second post contains a XML Template containing a XQuery statement.\n\tIt will render a table containing names from simple opml.xml file.\n     The following is a post content containing a XML Template with SQL Query:\n\t\n\t    \n\t    \n\t\t\n\t\t    select 1 as tag , null as parent, CompanyName as [tr!1!td!element]\n\t\t    from Demo.demo.Shippers\n\t\t    for xml explicit\n\t\t\n\t    
\n\t    \n\t\n    \n      The following is a post content containing a XML Template with XQuery:\n\t\n\t    \n\t    
\n\t\t\n\t\t    \n\t\t\t{ for $o in document (\"opml.xml\")//outline\n\t\t\t   return { string ($o/@text) }\n\t\t\t}\n\t\t    \n\t\t    ]]>\n\t\t\n\t    
\n\t    \n\t\n    \n    The result from execution can be seen at http://host:port/weblog/bloguser/bloguser-blog-0.\n\tNote that demo's initial state MUST be set before hitting this link.\n    \n\n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Making a dynamic blog posts using XML templates" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\nOverview\n\n    This demo makes a Weblog and posts into it using Metaweblog API two dynamic posts\n    The dynamic posts contains XML template(s) which will be executed at render time.\n    The first post makes a SQL quesry on Demo Database table 'Shippers' and inserts a table\n\tinto the user's weblog.\n    \n    The second post contains a XML Template containing a XQuery statement.\n\tIt will render a table containing names from simple opml.xml file.\n     The following is a post content containing a XML Template with SQL Query:\n\t\n\t    \n\t    <table border="1">\n\t\t<sql:query xmlns:sql="urn:schemas-openlink-com:xml-sql" >\n\t\t    select 1 as tag , null as parent, CompanyName as [tr!1!td!element]\n\t\t    from Demo.demo.Shippers\n\t\t    for xml explicit\n\t\t</sql:query>\n\t    </table>\n\t    \n\t\n    \n      The following is a post content containing a XML Template with XQuery:\n\t\n\t    \n\t    <div>\n\t\t<sql:xquery  xmlns:sql="urn:schemas-openlink-com:xml-sql"\n\t\t    sql:context="http://localhost:8890/tutorial/apps/blog_query/">\n\t\t    <![CDATA[\n\t\t    <table border="1">\n\t\t\t{ for $o in document ("opml.xml")//outline\n\t\t\t   return <tr><td>{ string ($o/@text) }</td></tr>\n\t\t\t}\n\t\t    </table>\n\t\t    ]]>\n\t\t</sql:xquery>\n\t    </div>\n\t    \n\t\n    \n    The result from execution can be seen at http://host:port/weblog/bloguser/bloguser-blog-0.\n\tNote that demo's initial state MUST be set before hitting this link.\n    \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Application \"Forums\"" ;
	sioc:content	"\nOverview\n\n\nThe \"Forums\" is a World Wide Web application for posting, reading and searching of messages.\nIt is developed under Virtuoso VDBMS using Virtuoso Server Pages (VSP) and server-side XSL-T\ntransformation.\nThe messages are classified by interest to forums and sub-forums.\nThe posting is allowed only for the registered users. The registration is done by registration form.\nEvery registered user can create  a new theme, post messages to an existing theme or reply to a message.\nUnregistered users can search and browse and read the existing themes and messages.\nVSP is used to produce an XML document. This is then transformed to HTML using server side XSL-T transformation.\nThe design and functionality of this application are separate. The design and appearance of the application depends only on the XSL-T style-sheets.\nSession management is based on URL (poisoning) and persistent HTTP session variables.\nThe messages are stored in the Database as XML documents, with a text index over them.\n\n\nApplication pages\nThe application has the following pages:\n\nhome.vsp - the main page:\nShows the forums with the following information:\n\nForums: name of the forum with link to the relevant sub-forums.\nTotal: total of the messages for this forum;\nNew: new messages for the current forum for the last one day;\nLast msg.: last inserted message to the forum;\nTotal users: the count of all users at the current moment who are registered at the forums;\nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\n\n\n\nsubforums.vsp - Shows the sub-forums of the current forum with the following information:\n\n\nSubforum: name of the sub-forum with link to the relevant themes.\nTotal: total of the messages for this forum;\nNew: new messages for the current forum for the last one day;\nLast msg.: last inserted message to the forum;\nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\nForums path: links to the home page and to the forum to which belong the current sub-forums;\n\n\n\n\n forum.vsp - Shows themes of the current sub-forum with the following information:\n\n\nTheme: name of the theme with link to its messages.\nTotal: total of the messages for this theme;\nNew: new messages for the current theme for the last one day;\nLast msg.: last inserted message to the theme;\nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\nForums path: links to the home page, to the forum and to the sub-forum to which belong the current themes;\n\n\n\n\n thread.vsp - Shows the messages of the current theme with the following information:\n\n\nMessage: name of the messages with link to its properties / text, author / and when the link is activated, the same page is present, but with the tree of the messages for which the current message is parent.\nAuthor: the name of the author, posted the current messages;\nDate of inserting: date of posting the messages; \nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\nForums path: links to the home page, to the forum and to the sub-forum to which belong the current message, also for the current messages which is parent for the other messages, its name is only presented, and lower you go in the tree, you can go back using this path.\n\n\n\n\nRemarks\n\nIf you are not logged in, you can go on all the pages of the site, but if you want to insert new theme, or new message, you have to login, and automatically the login page is displayed. When you are successfully login, you go directly   to the form for inserting messages/themes.\n\n If you aren't logged-in, the name anonymous is displayed, instead of your email, if you were logged in.\n\nWhen you use the search option, you can search in 3 main parts:\n\n Theme title: title of message which is title of theme;\n Message title: title of message which has theme as parent theme;\n Message body: body of the messages which has as a parent different themes;\n\n\nWhen the search result is displayed, there info how many hits are found, and the result are displayed as following:\nMessage title: the title of the current message / when you search in message body, its title is displayed /;\nTime: date of inserting of the message or theme;\nAuthor: the author of the message or the theme;\nHome: link to the home page;\nUser info: if logged in, then the current email, otherwise anonymous.\n\n\nInstallation\n\n  Copy /forums and /xslt to the HTTP ServerRoot\n  Execute def.sql script via isql tool with dba privileges. Example:\n   \n   [isql tool directory]\\isql [server ip or hostname]:[port] dba dba\n\n   Connected to OpenLink Virtuoso VDBMS\n   Driver: 02.10.2018 OpenLink Virtuoso ODBC Driver\n   OpenLink Interactive SQL (Virtuoso), version 0.9849b.\n   Type HELP; for help and EXIT; to exit.\n   SQL>load c:\\temp\\def.sql;\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n   \n   Important: Make sure there are no errors.\n   \n\n   Execute func.sql script. Example:\n  \n   SQL>load c:\\temp\\func.sql;\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n \n Important: Make sure there are no errors.\nCheck the installation:\n  \n   http://[server ip or hostname]:[port]/forums/home.vsp\n  \n\n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Application \"Forums\"" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\nOverview\n\n\nThe "Forums" is a World Wide Web application for posting, reading and searching of messages.\nIt is developed under Virtuoso VDBMS using Virtuoso Server Pages (VSP) and server-side XSL-T\ntransformation.\nThe messages are classified by interest to forums and sub-forums.\nThe posting is allowed only for the registered users. The registration is done by registration form.\nEvery registered user can create  a new theme, post messages to an existing theme or reply to a message.\nUnregistered users can search and browse and read the existing themes and messages.\nVSP is used to produce an XML document. This is then transformed to HTML using server side XSL-T transformation.\nThe design and functionality of this application are separate. The design and appearance of the application depends only on the XSL-T style-sheets.\nSession management is based on URL (poisoning) and persistent HTTP session variables.\nThe messages are stored in the Database as XML documents, with a text index over them.\n\n\nApplication pages\nThe application has the following pages:\n\nhome.vsp - the main page:\nShows the forums with the following information:\n\nForums: name of the forum with link to the relevant sub-forums.\nTotal: total of the messages for this forum;\nNew: new messages for the current forum for the last one day;\nLast msg.: last inserted message to the forum;\nTotal users: the count of all users at the current moment who are registered at the forums;\nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\n\n\n\nsubforums.vsp - Shows the sub-forums of the current forum with the following information:\n\n\nSubforum: name of the sub-forum with link to the relevant themes.\nTotal: total of the messages for this forum;\nNew: new messages for the current forum for the last one day;\nLast msg.: last inserted message to the forum;\nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\nForums path: links to the home page and to the forum to which belong the current sub-forums;\n\n\n\n\n forum.vsp - Shows themes of the current sub-forum with the following information:\n\n\nTheme: name of the theme with link to its messages.\nTotal: total of the messages for this theme;\nNew: new messages for the current theme for the last one day;\nLast msg.: last inserted message to the theme;\nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\nForums path: links to the home page, to the forum and to the sub-forum to which belong the current themes;\n\n\n\n\n thread.vsp - Shows the messages of the current theme with the following information:\n\n\nMessage: name of the messages with link to its properties / text, author / and when the link is activated, the same page is present, but with the tree of the messages for which the current message is parent.\nAuthor: the name of the author, posted the current messages;\nDate of inserting: date of posting the messages; \nOptions: Login if the user is already registered in the forums;\nRegistration: to add a new user;\nSearch: to search in the messages;\nForums path: links to the home page, to the forum and to the sub-forum to which belong the current message, also for the current messages which is parent for the other messages, its name is only presented, and lower you go in the tree, you can go back using this path.\n\n\n\n\nRemarks\n\nIf you are not logged in, you can go on all the pages of the site, but if you want to insert new theme, or new message, you have to login, and automatically the login page is displayed. When you are successfully login, you go directly   to the form for inserting messages/themes.\n\n If you aren't logged-in, the name anonymous is displayed, instead of your email, if you were logged in.\n\nWhen you use the search option, you can search in 3 main parts:\n\n Theme title: title of message which is title of theme;\n Message title: title of message which has theme as parent theme;\n Message body: body of the messages which has as a parent different themes;\n\n\nWhen the search result is displayed, there info how many hits are found, and the result are displayed as following:\nMessage title: the title of the current message / when you search in message body, its title is displayed /;\nTime: date of inserting of the message or theme;\nAuthor: the author of the message or the theme;\nHome: link to the home page;\nUser info: if logged in, then the current email, otherwise anonymous.\n\n\nInstallation\n\n  Copy /forums and /xslt to the HTTP ServerRoot\n  Execute def.sql script via isql tool with dba privileges. Example:\n   \n   [isql tool directory]\\isql [server ip or hostname]:[port] dba dba\n\n   Connected to OpenLink Virtuoso VDBMS\n   Driver: 02.10.2018 OpenLink Virtuoso ODBC Driver\n   OpenLink Interactive SQL (Virtuoso), version 0.9849b.\n   Type HELP; for help and EXIT; to exit.\n   SQL>load c:\\temp\\def.sql;\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n   \n   Important: Make sure there are no errors.\n   \n\n   Execute func.sql script. Example:\n  \n   SQL>load c:\\temp\\func.sql;\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n   . . .\n   Done. -- 20 msec.\n \n Important: Make sure there are no errors.\nCheck the installation:\n  \n   http://[server ip or hostname]:[port]/forums/home.vsp\n  \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Blog application" ;
	sioc:content	"\nExample\n\nThe application allow users to retreive a RSS2 documents and render as Weblog.\nThe RSS2 file will be transformed to a Updategram and stored in a local table.\nAlso it demonstrates the usage of VSPX calendar used for navigation.\nThe application contains a simple RSS2 generator, used to present a BLOG data on local server.\nThe data on local server can be entered using the BLOG application\n\n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Consuming a RSS2 feeds" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\nExample\n\nThe application allow users to retreive a RSS2 documents and render as Weblog.\nThe RSS2 file will be transformed to a Updategram and stored in a local table.\nAlso it demonstrates the usage of VSPX calendar used for navigation.\nThe application contains a simple RSS2 generator, used to present a BLOG data on local server.\nThe data on local server can be entered using the BLOG application\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Editing the Demo Database data" ;
	sioc:content	"\n      Simple application to edit countries data from Demo Database\n      The following approaches are demonstrated: \n      \n\t  Listing the data with data-set\n\t  Editing the data with form controls\n\t  inline images in from blob data\n      \n      \n\t  In details example itself shows:\n      \n      \n\t  How to build simple application to list a data.\n\t  To edit and add strings and large objects.\n      \n  " ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Using VSPX controls to edit the Demo Database data" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n      Simple application to edit countries data from Demo Database\n      The following approaches are demonstrated: \n      \n\t  Listing the data with data-set\n\t  Editing the data with form controls\n\t  inline images in from blob data\n      \n      \n\t  In details example itself shows:\n      \n      \n\t  How to build simple application to list a data.\n\t  To edit and add strings and large objects.\n      \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Making XML Reports" ;
	sioc:content	"\nXML report example\n\n  The example shows a sales report by customer and product category for a given time period.\n  The FOR XML and XSLT is used to render it.\n  A form is used to define start and end dates.\n  The data is taken from the demo tables.\n  This is an example of xml_auto() on a vsp page with an xslt template.\n  It shows how xml_auto_dtd(), and xml_auto_schema() can be used to describe the output.\n\n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Making simple XML report" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nXML report example\n\n  The example shows a sales report by customer and product category for a given time period.\n  The FOR XML and XSLT is used to render it.\n  A form is used to define start and end dates.\n  The data is taken from the demo tables.\n  This is an example of xml_auto() on a vsp page with an xslt template.\n  It shows how xml_auto_dtd(), and xml_auto_schema() can be used to describe the output.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Making XML Reports" ;
	sioc:content	"\nInline DTD XML report\n\n  The example shows a sales report by customer and product category for a given period of time.\n  The FOR XML and XSLT is used to render it.\n  A form is used to define start and end dates.\n  The data is taken from the demo tables.\n  This is an example of xml_auto() on a vsp page with an xslt template.\n  It shows how xml_auto_dtd(), and xml_auto_schema() can be used to describe the output.\n\n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"Inline DTD example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\nInline DTD XML report\n\n  The example shows a sales report by customer and product category for a given period of time.\n  The FOR XML and XSLT is used to render it.\n  A form is used to define start and end dates.\n  The data is taken from the demo tables.\n  This is an example of xml_auto() on a vsp page with an xslt template.\n  It shows how xml_auto_dtd(), and xml_auto_schema() can be used to describe the output.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"XML for Analysis" ;
	sioc:content	"\nExample\n\nThe Virtuoso server can act as XML for Analysis (XMLA) tabular data provider.\nXML for Analysis is a SOAP based XML API, \ndesigned specifically for data access interaction between a \nclient application and a data provider working over the Web. \nThe client application can do discovery of data provider information \nand execute of SQL statements. The result sets from server to client can be \nMultidimensonal and Tabular, at current state only Tabular is supported.\nTo setup an virtual directory to act as XMLA data provider, it needs to be \ndefined as SOAP one and Discover and Execute procedures needs to be granted to the \nuser account for SOAP execution.\n\n\n The example shows how SOAP enabled virtual directory can be exposed for XMLA.\n The SQL statements for setting up the virtual directory are shown in the .sql file\n In addition to the virtual directory setup, there is a grant to the Northwind Customers table \n to be able to invoke select on that table via Execute method.\n \n The example XMLA client is a simplest browser of XMLA provider\n It allows to browse the data, do execute of SQL statements and such\n To try the example do load the script, start the VSP example and follow the steps\n \n" ;
	sioc:has_container	ns2:web2 ;
	sioc:description	"XML for Analysis" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nThe Virtuoso server can act as XML for Analysis (XMLA) tabular data provider.\nXML for Analysis is a SOAP based XML API, \ndesigned specifically for data access interaction between a \nclient application and a data provider working over the Web. \nThe client application can do discovery of data provider information \nand execute of SQL statements. The result sets from server to client can be \nMultidimensonal and Tabular, at current state only Tabular is supported.\nTo setup an virtual directory to act as XMLA data provider, it needs to be \ndefined as SOAP one and Discover and Execute procedures needs to be granted to the \nuser account for SOAP execution.\n\n\n The example shows how SOAP enabled virtual directory can be exposed for XMLA.\n The SQL statements for setting up the virtual directory are shown in the .sql file\n In addition to the virtual directory setup, there is a grant to the Northwind Customers table \n to be able to invoke select on that table via Execute method.\n \n The example XMLA client is a simplest browser of XMLA provider\n It allows to browse the data, do execute of SQL statements and such\n To try the example do load the script, start the VSP example and follow the steps\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Making a freetext trigger" ;
	sioc:content	"\nExample\n\nThis example adds an XML content trigger to the data of XS-S-1.\nThe main features of this example are:\n\n  Display a list of documents held in a table.\n  Add a new document or delete an existing one.\n  Define a trigger.\n  Show the hits found by the triggers.\n\n\nDocument upload and list page\n\n  The URI for the document is entered, and the system goes to retrieve it using xml_uri_get().\n  The document is inserted into a table.\n  If the document is HTML it is converted to XHTML with xml_tree() HTML mode.\n  If the HTML is not in a valid format or the document at the URI is not found, an error is reported.\n  There is a list of the rows in the documents table.\n  Each row has a delete button, to remove the document.\n\n\nTrigger definition page\n\n  The triggers page allows triggers to be added and deleted. When a trigger is deleted the\n   hits are also deleted.\n  Some pre-existing triggers look for text of specific tags in the XS-S-1 material.\n\n\nHits page\n\n  The hits are listed on this page.\n  The hits page has a delete all button, to remove the hits.\n\n" ;
	sioc:has_container	ns2:xmlxslt ;
	sioc:description	"Freetext triggers example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nExample\n\nThis example adds an XML content trigger to the data of XS-S-1.\nThe main features of this example are:\n\n  Display a list of documents held in a table.\n  Add a new document or delete an existing one.\n  Define a trigger.\n  Show the hits found by the triggers.\n\n\nDocument upload and list page\n\n  The URI for the document is entered, and the system goes to retrieve it using xml_uri_get().\n  The document is inserted into a table.\n  If the document is HTML it is converted to XHTML with xml_tree() HTML mode.\n  If the HTML is not in a valid format or the document at the URI is not found, an error is reported.\n  There is a list of the rows in the documents table.\n  Each row has a delete button, to remove the document.\n\n\nTrigger definition page\n\n  The triggers page allows triggers to be added and deleted. When a trigger is deleted the\n   hits are also deleted.\n  Some pre-existing triggers look for text of specific tags in the XS-S-1 material.\n\n\nHits page\n\n  The hits are listed on this page.\n  The hits page has a delete all button, to remove the hits.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Encodings in HTTP, XML XSL-T" ;
	sioc:content	"\nTreatment of the  notation\n\n  Each external parsed entity may begin with a text declaration:\n    \n  Each external parsed entity in an XML document may use a different encoding for its characters. \n  The encoding declaration instructs the XML parser which encoding to use to parse the entity.\n    encoding=\"encoding name\"\n\n\nThe xsl:output element's options\n\n  The xml output method outputs the result tree as a well-formed XML external general parsed entity. \n  The html output method outputs the result tree as HTML.\n  The text output method outputs the result tree by outputting the string-value of every text node in the\n    result tree in document order without any escaping.\n\n\nParsing the XML documents with specified encoding\n\n  If the encoding is specified in the XML document (in xml header), it is used.\n  If not in the document, but in \"default encoding\" argument, then the argument's value is used.\n  If no argument, the session should be used only for HTML, but for XMLs the standard requires UTF-8.\n  So when a tree comes from xslt the xsl:output is reflected there for use when serializing.\n\n\nExamples\n\n  The example in the SQL script demonstrates using the encodings and languages with free-text search over indexed data.\n  The first example accepts text from the user and maps this to any selected encoding and returns the text in another encoding. The selection box of input and output encodings is used to transfer the narrow character data.\n  The second example sends the text of the XS-S-1 data to the user agent in a selectable encoding, using an XSL-T transformation.\n  The last example shows how the text can be effected by the HTTP 'Content-Type' header defining the charset.\n  In this example current charset is set with 'set charset=...' statement. This invokes sending a 'charset' mime attribute to the user-agent.\n\n" ;
	sioc:has_container	ns2:xmlxslt ;
	sioc:description	"Encodings in HTTP, XML XSL-T" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nTreatment of the <?xml > notation\n\n  Each external parsed entity may begin with a text declaration:\n    <?xml versioninfo encoding_declaration >\n  Each external parsed entity in an XML document may use a different encoding for its characters. \n  The encoding declaration instructs the XML parser which encoding to use to parse the entity.\n    encoding="encoding name"\n\n\nThe xsl:output element's options\n\n  The xml output method outputs the result tree as a well-formed XML external general parsed entity. \n  The html output method outputs the result tree as HTML.\n  The text output method outputs the result tree by outputting the string-value of every text node in the\n    result tree in document order without any escaping.\n\n\nParsing the XML documents with specified encoding\n\n  If the encoding is specified in the XML document (in xml header), it is used.\n  If not in the document, but in "default encoding" argument, then the argument's value is used.\n  If no argument, the session should be used only for HTML, but for XMLs the standard requires UTF-8.\n  So when a tree comes from xslt the xsl:output is reflected there for use when serializing.\n\n\nExamples\n\n  The example in the SQL script demonstrates using the encodings and languages with free-text search over indexed data.\n  The first example accepts text from the user and maps this to any selected encoding and returns the text in another encoding. The selection box of input and output encodings is used to transfer the narrow character data.\n  The second example sends the text of the XS-S-1 data to the user agent in a selectable encoding, using an XSL-T transformation.\n  The last example shows how the text can be effected by the HTTP 'Content-Type' header defining the charset.\n  In this example current charset is set with 'set charset=...' statement. This invokes sending a 'charset' mime attribute to the user-agent.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"DTD validation" ;
	sioc:content	"\nExample\n\n  This sample uses the DTDs generated based on FOR XML query to verify another FOR XML query result.\n  The interface allows selection of a query for the DTD and a query for the XML document.\n  The interface has check boxes controlling each aspect of DTD validation \n            (see the documentation about each of them).\n  The submit button combines the DTD and the XML document, \n            verifies them and produces a result page showing the error messages.\n\n" ;
	sioc:has_container	ns2:xmlxslt ;
	sioc:description	"DTD Validation example" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nExample\n\n  This sample uses the DTDs generated based on FOR XML query to verify another FOR XML query result.\n  The interface allows selection of a query for the DTD and a query for the XML document.\n  The interface has check boxes controlling each aspect of DTD validation \n            (see the documentation about each of them).\n  The submit button combines the DTD and the XML document, \n            verifies them and produces a result page showing the error messages.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Processing a large XML files" ;
	sioc:content	"\nPreliminaries\n\n  The PL varchar variable has a limit of 10Mb.\n  This means that variables that may contains a large document for XML processing cannot keep over 10Mb data.\n  Using a temp file with xml_persistent does not have this limit.\n  The xml_persistent() can process the large documents using the temporary file for storing the data.\n\n\nCaution: Paths used in that sample are evaluted in the server file system. \nSpecify correct server filesystem paths. \n\nExample\n\n  The example converts a file to persistent XML and back to a file.\n  The file is then traversed by XSLT and the result is stored into a string output.\n  This is then stored into a file.\n  The input of the sheet is checked against a DTD.\n  The page shows these steps and the lengths of the files and intermediate data.\n  The data is an excerpt of dmoz with some extra repetition to make 5MB of data.\n    This is not itself above the varchar limit but is large enough for this example.\n  The results can be seen in the result file in the directory.\n  The vsp page will show fragments of the data, e.g. part of the first subtree.\n\n" ;
	sioc:has_container	ns2:xmlxslt ;
	sioc:description	"XML persistent storage" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:55 GMT" ;
	content:encoded	"\nPreliminaries\n\n  The PL varchar variable has a limit of 10Mb.\n  This means that variables that may contains a large document for XML processing cannot keep over 10Mb data.\n  Using a temp file with xml_persistent does not have this limit.\n  The xml_persistent() can process the large documents using the temporary file for storing the data.\n\n\nCaution: Paths used in that sample are evaluted in the server file system. \nSpecify correct server filesystem paths. \n\nExample\n\n  The example converts a file to persistent XML and back to a file.\n  The file is then traversed by XSLT and the result is stored into a string output.\n  This is then stored into a file.\n  The input of the sheet is checked against a DTD.\n  The page shows these steps and the lengths of the files and intermediate data.\n  The data is an excerpt of dmoz with some extra repetition to make 5MB of data.\n    This is not itself above the varchar limit but is large enough for this example.\n  The results can be seen in the result file in the directory.\n  The vsp page will show fragments of the data, e.g. part of the first subtree.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"RDF NET" ;
	sioc:content	"\nExample\n\n    RDF NET\n\n\n\n RDF NET\n \n" ;
	sioc:has_container	ns2:rdf ;
	sioc:description	"RDF NET" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n    RDF NET\n\n\n\n RDF NET\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SPARQL Query on PHP ODBC Hosting Demo" ;
	sioc:content	"\n    PHP script calling ODBC\n    \n      This demo shows simple ODBC functions being used in a PHP script:\n      odbc_connect(), odbc_exec(), odbc_result_all() and odbc_tables().\n    \n    \n      The demo makes sparql queries on Virtuoso's RDF database using \"sparql select\" syntax.\n      The data is loaded on tutorial vad installation time by the sparql_demo.\n    \n  " ;
	sioc:has_container	ns2:rdf ;
	sioc:description	"Demonstrates the use of a PHP script hosted in Virtuoso to execute\nSPARQL queries against Virtuoso's RDF Triplestore. Note, this demo leverages\nPHP's ODBC based data access layer and Virtuoso's ability to execute SPARQL\nvia its SQL query processor." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    PHP script calling ODBC\n    \n      This demo shows simple ODBC functions being used in a PHP script:\n      odbc_connect(), odbc_exec(), odbc_result_all() and odbc_tables().\n    \n    \n      The demo makes sparql queries on Virtuoso's RDF database using "sparql select" syntax.\n      The data is loaded on tutorial vad installation time by the sparql_demo.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"RDF data import on PHP ODBC Hosting Demo" ;
	sioc:content	"\n    PHP page invoking the SPARQL sponger\n    \n      This demo demonstrates the use of PHP script hosted in Virtuoso to import\n      RDF data using SPARQL sponger. Note, this demo leverages\n      PHP's ODBC based data access layer and Virtuoso's ability to execute SPARQL\n      via its SQL query processor.\n    \n    \n        This demo presents a PHP form to the user to enter a URL.\n        The form action (buton click) will perform import of RDF data.\n        Note: this tutorial is limitied to no more than 10 MB files to be imported.\n\tAlso note that pinging the service is not needed if [SPARQL] INI section has\n\tPingService = http://rpc.pingthesemanticweb.com/ setting.\n    \n  " ;
	sioc:has_container	ns2:rdf ;
	sioc:description	"Demonstrates the use of a PHP script hosted in Virtuoso to import\n    RDF data using SPARQL sponger. Note, this demo leverages\n    PHP's ODBC based data access layer and Virtuoso's ability to execute SPARQL\n    via its SQL query processor." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    PHP page invoking the SPARQL sponger\n    \n      This demo demonstrates the use of PHP script hosted in Virtuoso to import\n      RDF data using SPARQL sponger. Note, this demo leverages\n      PHP's ODBC based data access layer and Virtuoso's ability to execute SPARQL\n      via its SQL query processor.\n    \n    \n        This demo presents a PHP form to the user to enter a URL.\n        The form action (buton click) will perform import of RDF data.\n        Note: this tutorial is limitied to no more than 10 MB files to be imported.\n\tAlso note that pinging the service is not needed if [SPARQL] INI section has\n\tPingService = http://rpc.pingthesemanticweb.com/ setting.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Importing RDF data using SPARQL query" ;
	sioc:content	"\n    VSPX page invoking the SPARQL sponger\n    \n       This demo presents a VSPX-based form for entering an URL. The form's\n       submit (button click) will perform a SPARQL query with sponge parameters and\n       will ping pingthesemanticweb.com upon success.\n    \n    \n\tNote that pinging the service is not needed if [SPARQL] INI section have\n\tPingService = http://rpc.pingthesemanticweb.com/ setting.\n    \n  " ;
	sioc:has_container	ns2:rdf ;
	sioc:description	"RDF data import using SPARQL sponger." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    VSPX page invoking the SPARQL sponger\n    \n       This demo presents a VSPX-based form for entering an URL. The form's\n       submit (button click) will perform a SPARQL query with sponge parameters and\n       will ping pingthesemanticweb.com upon success.\n    \n    \n\tNote that pinging the service is not needed if [SPARQL] INI section have\n\tPingService = http://rpc.pingthesemanticweb.com/ setting.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"RDF Cartridges" ;
	sioc:content	"\n    Concept\n    \n      RDF cartridges provide a modular approach to RDF oriented entity extraction and ontology mapping\n      as part of a Linked Data production pipeline. Typical sources include (X)HTML pages, images,\n      Office documents and PDF documents amongst others.\n    \n    \n      Cartridges expose their functionality to service consumers via the Virtuoso Sponger (\"Sponger\"),\n      a middleware layer that extracts and delivers RDF to other Virtuoso components such as the Web\n      Crawler and SPARQL Query Process. In addition it is directly exposed as a REST-style Web Service\n      for external applications and services to exploit.\n    \n    \n      A Cartridges is comprised of an initialization PL procedure (hook) and an entity extractor and mapper.\n      The entity extractor and mapping component can be developed using PL, C or any external language\n      supported by Virtuoso via the Virtuoso Server Extensions APIs.\n    \n    \n      Once the cartridge has been developed, it is plugged into the Virtuoso Sponger by adding a record\n      to the table DB.DBA. DB.DBA.SYS_RDF_MAPPERS.\n    \n    How Cartridges Work:\n  \n    SPARQL Query Processing\n    \n      When a SPARQL query is dispatched to Virtuoso, it invokes the Sponger during the act of\n      graph or resource URI dereferencing i.e. it actually crawls the Web, locates a resource via\n      it's URI/IRI (using a variety of RDF discovery heuristics), and then differences the data that\n      the URI exposes. If RDF is discovered, the cartridges play no role. On the other hand, if RDF\n      isn't discovered the Sponger will look in the DB.DBA.SYS_RDF_MAPPERS table (in RM_ID order),\n      and for every matching URI or MIME type pattern (depending on RM_TYPE column value) it will\n      invoke the associated cartridge by invoking the hook procedure. If the hook returns zero the\n      next cartridge will be tried. If the result is negative the process stops, instructing the\n      SPARQL engine that nothing was retrieved. If the result is positive the process stops, this\n      time instructing the SPARQL engine that RDF data was successfully retrieved.\n    \n  \n    PL hook requirements\n    \n      Every PL function used to plug a cartridge into the SPARQL engine must have the following parameter signature:\n    \n    \n      \n        in graph_iri varchar: the local storage graph IRI\n      \n      \n\tin new_origin_uri varchar: target information resource URI\n      \n      \n        in destination varchar: the target graph IRI\n      \n      \n        inout content any: the content of the information resource retrieved for dispatch to the Sponger\n      \n      \n        inout async_queue any: an asynchronous queue, can be used for background processing (if required)\n      \n      \n        inout ping_service any: the value in the [SPARQL] section of a Virtuoso instance (i.e PingService? INI parameter) which is enables RDF triple propagation and notification to pinger services such as http://pingthesemanticweb.com\n      \n      \n        inout api_key any: a plain text id single key value or serialized vector of keys, basically the value of RM_KEY column of the DB.DBA.SYS_RDF_MAPPERS table, which is used for handling of API keys for 3rd party Web Services.\n      \n    \n    \n      Note: the names of the parameters are not important, but their order and presence are vital.\n    \n  \n    Implementation\n    \n      In the example script we implement a basic cartridge which maps a text/plain mime type to an\n      imaginary ontology, which extends the class Document from FOAF with properties 'txt:UniqueWords?'\n      and 'txt:Chars', where the prefix 'txt:' we specify as 'urn:txt:v0.0:'.\n    \n    \n      To test the cartridge we just use /sparql endpoint with option 'Retrieve remote RDF data for\n      all missing source graphs' to execute:\n    \n    \n      select * from  where { ?s ?p ?o }\n    \n    \n      It is important that the SPARQL_SPONGE role needs to be granted to \"SPARQL\" user account (or any\n      other account bound to SPARQL functionality) in order to enable persistence to local storage.\n    \n    \n      If the above is set correctly then you can just hit this link.\n    \n    \n      More complex examples can be found in the rdf_cartridges package implementation.\n    \n  " ;
	sioc:has_container	ns2:rdf ;
	sioc:description	"This article explains how to develop and test a custom RDF Cartridge." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Concept\n    \n      RDF cartridges provide a modular approach to RDF oriented entity extraction and ontology mapping\n      as part of a Linked Data production pipeline. Typical sources include (X)HTML pages, images,\n      Office documents and PDF documents amongst others.\n    \n    \n      Cartridges expose their functionality to service consumers via the Virtuoso Sponger ("Sponger"),\n      a middleware layer that extracts and delivers RDF to other Virtuoso components such as the Web\n      Crawler and SPARQL Query Process. In addition it is directly exposed as a REST-style Web Service\n      for external applications and services to exploit.\n    \n    \n      A Cartridges is comprised of an initialization PL procedure (hook) and an entity extractor and mapper.\n      The entity extractor and mapping component can be developed using PL, C or any external language\n      supported by Virtuoso via the Virtuoso Server Extensions APIs.\n    \n    \n      Once the cartridge has been developed, it is plugged into the Virtuoso Sponger by adding a record\n      to the table DB.DBA. DB.DBA.SYS_RDF_MAPPERS.\n    \n    How Cartridges Work:\n  \n    SPARQL Query Processing\n    \n      When a SPARQL query is dispatched to Virtuoso, it invokes the Sponger during the act of\n      graph or resource URI dereferencing i.e. it actually crawls the Web, locates a resource via\n      it's URI/IRI (using a variety of RDF discovery heuristics), and then differences the data that\n      the URI exposes. If RDF is discovered, the cartridges play no role. On the other hand, if RDF\n      isn't discovered the Sponger will look in the DB.DBA.SYS_RDF_MAPPERS table (in RM_ID order),\n      and for every matching URI or MIME type pattern (depending on RM_TYPE column value) it will\n      invoke the associated cartridge by invoking the hook procedure. If the hook returns zero the\n      next cartridge will be tried. If the result is negative the process stops, instructing the\n      SPARQL engine that nothing was retrieved. If the result is positive the process stops, this\n      time instructing the SPARQL engine that RDF data was successfully retrieved.\n    \n  \n    PL hook requirements\n    \n      Every PL function used to plug a cartridge into the SPARQL engine must have the following parameter signature:\n    \n    \n      \n        in graph_iri varchar: the local storage graph IRI\n      \n      \n\tin new_origin_uri varchar: target information resource URI\n      \n      \n        in destination varchar: the target graph IRI\n      \n      \n        inout content any: the content of the information resource retrieved for dispatch to the Sponger\n      \n      \n        inout async_queue any: an asynchronous queue, can be used for background processing (if required)\n      \n      \n        inout ping_service any: the value in the [SPARQL] section of a Virtuoso instance (i.e PingService? INI parameter) which is enables RDF triple propagation and notification to pinger services such as http://pingthesemanticweb.com\n      \n      \n        inout api_key any: a plain text id single key value or serialized vector of keys, basically the value of RM_KEY column of the DB.DBA.SYS_RDF_MAPPERS table, which is used for handling of API keys for 3rd party Web Services.\n      \n    \n    \n      Note: the names of the parameters are not important, but their order and presence are vital.\n    \n  \n    Implementation\n    \n      In the example script we implement a basic cartridge which maps a text/plain mime type to an\n      imaginary ontology, which extends the class Document from FOAF with properties 'txt:UniqueWords?'\n      and 'txt:Chars', where the prefix 'txt:' we specify as 'urn:txt:v0.0:'.\n    \n    \n      To test the cartridge we just use /sparql endpoint with option 'Retrieve remote RDF data for\n      all missing source graphs' to execute:\n    \n    \n      select * from <URL-of-a-txt-file> where { ?s ?p ?o }\n    \n    \n      It is important that the SPARQL_SPONGE role needs to be granted to "SPARQL" user account (or any\n      other account bound to SPARQL functionality) in order to enable persistence to local storage.\n    \n    \n      If the above is set correctly then you can just hit this link.\n    \n    \n      More complex examples can be found in the rdf_cartridges package implementation.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"RDF Cartridges" ;
	sioc:content	"\n    Setting up server\n    \n\tThis tutorial explain steps to use the Python language to extend the Virtuoso Sponger.\n    \n    \n\tThe server must have installed latest Python hosting plugin. When it is installed and registered in the configuration file \n\ta new function python_exec will be available for developers. \t\n    \n    \n\tSetup the Virtuoso server INI to include python module\n    \n    \n\t[Plugins]\n\tLoadPath = ../lib\n\tLoad1    = Hosting, hosting_python.so\n\t...\n    \n    \n\tThe python_exec takes following arguments:\n    \n    \n\t\n\t    code - a string containing the Python code\n\t\n\t\n\t    function_name - a string containing the name of Python function to be executed\n\t\n\t\n\t    param1 : a string containing first parameter\n\t\n\t\n\t    param2 : a string containing second parameter\n\t\n\t\n\t    as many parameters as Python function has\n\t\n    \n    \n\tThe Python based function must return a single string value.\n    \n  \n    Setting up environment\n    \n\tBefore to write cartridge you need to setup Python environment. To do this you need to download and install rdflib, pyRDFa. \n\tRead the pyRDFa paper for what additional libraries are needed. \n    \n    \n\tIf your Python installation have Zope support, you should disable the zope interfaces in rdflib. This is needed because Python C-API expirence problems when using sub modules within C code. In order to disable you can comment out following lines in [rdflib_home]/rdflib/__init__.py : \n    \n    \n    36 #from rdflib.interfaces import IIdentifier, classImplements\n    37 #classImplements(URIRef, IIdentifier)\n    38 #classImplements(BNode, IIdentifier)\n    39 #classImplements(Literal, IIdentifier)\n    \n\nthen do:\n\n    \n    perl setup.py build\n    perl setup.py --user install\n    \n  \n    RDF Cartridge implementation notes\n    \n\tThe implementation consist of two steps:\n    \n    \n\t\n\t    Make a copy of the localRDFa.py and use as template to run pyRDFa extractor over single string stream. \n\t    The details can be seen in source of pyRDFa.py code attached to this tutorial.\n\t\n\t\n\t    Make a Virtuoso/PL based stored procedure to call the Pyhton based extractor. The source of this function can be seen in rdf_cartridge.sql script.\n\t\n    \n    \n\tThe stored procedure is used to do two main operations: to call 'processString' Python function inside pyRDFa.py script and to load the result in the Virtuoso RDF store.\n    \n    \n\tAnother important item is to register the cartridge with Sponger. this is done by insert statement into DB.DBA.SYS_RDF_MAPPERS table.\n\tNote that in this example the new cartridge will be disabled if you run that code, if you want to enable and test the cartridge the flag in RM_ENABLED column must be 1. or enable the crtridge via conductor.\n    \n  " ;
	sioc:has_container	ns2:rdf ;
	sioc:description	"This article explains how to implement a Python based RDFa Cartridge based on pyRDFa library." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Setting up server\n    \n\tThis tutorial explain steps to use the Python language to extend the Virtuoso Sponger.\n    \n    \n\tThe server must have installed latest Python hosting plugin. When it is installed and registered in the configuration file \n\ta new function python_exec will be available for developers. \t\n    \n    \n\tSetup the Virtuoso server INI to include python module\n    \n    \n\t[Plugins]\n\tLoadPath = ../lib\n\tLoad1    = Hosting, hosting_python.so\n\t...\n    \n    \n\tThe python_exec takes following arguments:\n    \n    \n\t\n\t    code - a string containing the Python code\n\t\n\t\n\t    function_name - a string containing the name of Python function to be executed\n\t\n\t\n\t    param1 : a string containing first parameter\n\t\n\t\n\t    param2 : a string containing second parameter\n\t\n\t\n\t    as many parameters as Python function has\n\t\n    \n    \n\tThe Python based function must return a single string value.\n    \n  \n    Setting up environment\n    \n\tBefore to write cartridge you need to setup Python environment. To do this you need to download and install rdflib, pyRDFa. \n\tRead the pyRDFa paper for what additional libraries are needed. \n    \n    \n\tIf your Python installation have Zope support, you should disable the zope interfaces in rdflib. This is needed because Python C-API expirence problems when using sub modules within C code. In order to disable you can comment out following lines in [rdflib_home]/rdflib/__init__.py : \n    \n    \n    36 #from rdflib.interfaces import IIdentifier, classImplements\n    37 #classImplements(URIRef, IIdentifier)\n    38 #classImplements(BNode, IIdentifier)\n    39 #classImplements(Literal, IIdentifier)\n    \n\nthen do:\n\n    \n    perl setup.py build\n    perl setup.py --user install\n    \n  \n    RDF Cartridge implementation notes\n    \n\tThe implementation consist of two steps:\n    \n    \n\t\n\t    Make a copy of the localRDFa.py and use as template to run pyRDFa extractor over single string stream. \n\t    The details can be seen in source of pyRDFa.py code attached to this tutorial.\n\t\n\t\n\t    Make a Virtuoso/PL based stored procedure to call the Pyhton based extractor. The source of this function can be seen in rdf_cartridge.sql script.\n\t\n    \n    \n\tThe stored procedure is used to do two main operations: to call 'processString' Python function inside pyRDFa.py script and to load the result in the Virtuoso RDF store.\n    \n    \n\tAnother important item is to register the cartridge with Sponger. this is done by insert statement into DB.DBA.SYS_RDF_MAPPERS table.\n\tNote that in this example the new cartridge will be disabled if you run that code, if you want to enable and test the cartridge the flag in RM_ENABLED column must be 1. or enable the crtridge via conductor.\n    \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Using HTTP client to perform FOAF+SSL connection" ;
	sioc:content	"\nExample\n\nIn order to have the rest of examples of this section working, the following steps must be performed.\n\n\n    \n\tSetup the ODS and Policy Manager packages.\n    \n    \n\tFollow instructions on Setting-Up issuer CA\n    \n    \n\tFollow instructions on Virtuoso Authentication Server UI\n    \n    \n\tIn above step register your WebID with secure SPARQL endpoint. Note: \"sparql-ssl\" endpoint is alias of \"sparql-webid\" endpoint.\n    \n    \n\tExport your certificate and key containing the WebID mentioned before from browsers key store as PKCS#12 package.\n    \n    \n\tRun the register_cert.vsp to import your key into Virtuoso Server PKI repository. \n    \n    \n\tRun the foaf_ssl_client.vsp.\n    \n\n" ;
	sioc:has_container	ns2:rdf ;
	sioc:description	"Using HTTP client to perform FOAF+SSL connection" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\nIn order to have the rest of examples of this section working, the following steps must be performed.\n\n\n    \n\tSetup the ODS and Policy Manager packages.\n    \n    \n\tFollow instructions on Setting-Up issuer CA\n    \n    \n\tFollow instructions on Virtuoso Authentication Server UI\n    \n    \n\tIn above step register your WebID with secure SPARQL endpoint. Note: "sparql-ssl" endpoint is alias of "sparql-webid" endpoint.\n    \n    \n\tExport your certificate and key containing the WebID mentioned before from browsers key store as PKCS#12 package.\n    \n    \n\tRun the register_cert.vsp to import your key into Virtuoso Server PKI repository. \n    \n    \n\tRun the foaf_ssl_client.vsp.\n    \n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SMTP client" ;
	sioc:content	"\nExample\n\n  This example uses the smtp_send() function for sending emails.\n  The demo page accepts mail server address, sender, recipient and message body.\n  The 'Send' button causes the composed simple email message to be sent to the mail server.\n \n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Simple mail composer" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example uses the smtp_send() function for sending emails.\n  The demo page accepts mail server address, sender, recipient and message body.\n  The 'Send' button causes the composed simple email message to be sent to the mail server.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"SMTP local mailer" ;
	sioc:content	"\nInstallation instructions\n\nThe Virtuoso server can store the incoming mail into the database using it's own local mailer implementation.\nThe following sections detail the configuration of each type of mail environment.\n\n\nReplacing procmail as default handler in sendmail configurations\n\nCopy virt_mail to /usr/bin/virt_mail\nCopy odbc_mail.default.ini to /etc/odbc_mail.ini\n    IMPORTANT: Make sure /etc/odbc_mail.ini is NOT GROUP/WORLD writable,\n    otherwise virt_mail will fail to run.\n    \n\nEdit /etc/odbc_mail.ini and change the login settings to match your\ncurrent database installation.\n \nIf you don't have or want to use procmail, comment out the \"Fallback\"\nsetting in the [Deliver] section.\n\nEdit /etc/sendmail.cf. Change:\n  Mlocal,\tP=/usr/bin/procmail, F=lsDFMAw5:/|@qSPfhn9, S=10/30, R=20/40,\n\t\t  T=DNS/RFC822/X-Unix,\n\t\t  A=procmail -Y -a $h -d $u\n\ninto:\n  Mlocal,\tP=/usr/bin/virt_mail, F=lsDFMA5:/|@qSPhn9,\n\t\tS=10/30, R=20/40, T=DNS/RFC822/X-Unix,\n\t\tA=virt_mail -c /etc/odbc_mail.ini -l $u -s $g\n\nNOTE: The changes to the F= setting involve removing both the 'w' and 'f' flags.\n\nThe removal of the 'w' flag affects lookups in /etc/passwd, which are no\nlonger required if all mail drops go into the database.\nThe default ini file is set up to maildrop to procmail, which will perform\nthis check correctly.\n\n\nPer-user database maildrops under sendmail\n\nCopy odbc_mail.default.ini to ~the_user_name/.odbc_mail.ini\nIMPORTANT: Make sure the .odbc_mail.ini is NOT GROUP/WORLD writable,\notherwise virt_mail will fail to run.\nPut at the end of ~the_user_name/.procmailrc something like:\n:0:\n| /usr/bin/virt_mail -c .odbc_mail.ini -l the_user_name\n\nreplacing the_user_name with the user you're setting up.\n\nNote: the '-l ..' parameter is used to relate the local recipient to\nthe database user for which the maildrop is done. See the remarks in\nthe odbc_mail.default.ini file.\n\nAdjust the parameters in .odbc_mail.ini to match your configuration\n\nIMPORTANT - also disable Fallback delivery in .odbc_mail.ini\nComment out the \"Fallback =\" entry in the .odbc_mail.ini\nor set it to something that doesn't involve procmail.\nOtherwise, this could lead to drop loops.\n\n\n\nPer-user database maildrops under qmail\n\n\nCopy odbc_mail.default.ini to ~the_user_name/.odbc_mail.ini\nIMPORTANT: Make sure the .odbc_mail.ini is NOT GROUP/WORLD writable,\notherwise virt_mail will fail to run.\n\nIf you're setting up a .qmail, simply do something like\n| /usr/bin/virt_mail -m qmail -c .odbc_mail.ini\n\nIf you're setting up .qmail-default or .qmail-,\nmake sure you adjust the RemovePrefix accordingly in the odbc_mail.ini.\n\nThis also works if a single user is receiving mail for an entire\n(virtual) domain.\n\nIf you want to configure qmail so that user 'db' gets all mail for\nexample.com, do this:\n \n  Create a new user db in /etc/passwd etc.\n  Remove example.com from /var/qmail/control/locals\n  Add to /var/qmail/controls/virtualdomains:\nexample.com:db\n  Adjust /var/qmail/users/assign accordingly:\n\t=db:db::::::\n\t+db-:db::::-::\n  or run\n  qmail-pw2u < /etc/passwd > /var/qmail/users/assign\n  then run qmail-newu and restart qmail\n  In ~db/.qmail-default, put:\n| /usr/bin/virt_mail -m qmail -c .odbc_mail.ini\n  In .odbc_mail.ini, set RemovePrefix=db-\nNow, mail to info@example.com will be delivered to the qmail alias\ndb-info@example.com and is stored into the database for user 'info'.\n  \n\nAdjust the parameters in .odbc_mail.ini to match your configuration\n\n\nPer-user database maildrops under courier\n\nCopy odbc_mail.default.ini to ~the_user_name/.odbc_mail.ini\nIMPORTANT: Make sure the .odbc_mail.ini is NOT GROUP/WORLD writable,\notherwise virt_mail will fail to run.\n\nIf you're setting up a .courier, simply do something like\n| /usr/bin/virt_mail -mcourier -c .odbc_mail.ini\n\nIf you're setting up .courier-default or .courier-,\nmake sure you adjust the RemovePrefix accordingly in the .odbc_mail.ini.\n\nNote 1: Although courier is very similar to qmail in this respect,\nit is different from qmail in how it handles exit codes.\nIf you use -mqmail while running under courier, you'll get the wrong\nexit codes, so mail is bounced instead of retried.\n\nNote 2: If delivering to multiple recipients in a .courier file,\nmake sure the virt_mail is specified first. This is because if the\nvirt_mail fails with a temporary error, the other recipients will\nget another drop when courier re-attempts to deliver the mail.\nRight:\n| /usr/bin/virt_mail -mcourier -c .odbc_mail.ini\n./Maildir\nWrong:\n./Maildir\n| /usr/bin/virt_mail -mcourier -c .odbc_mail.ini\n\nAdjust the parameters in .odbc_mail.ini to match your configuration\n\n\nEXIM\nHere are code snippets for Exim that perform maildrops into the odbc database.\n\n## IN TRANSPORT SECTION\n\n# Delivers into the database\nodbc:\n  driver = pipe\n  command = /usr/bin/virt_mail \\\n\t-c /etc/odbc_mail.ini \\\n\t-s \"${if def:return_path{$return_path}{MAILER-DAEMON}}\" \\\n\t-l \"$local_part\"\n  user = USERNAME\n  return_path_add\n  delivery_date_add\n  prefix =\n  suffix =\n  temp_errors = 73 : 74 : 75\n  return_fail_output\n\n# NOTE: Make sure the USERNAME in the 'user = USERNAME' setting matches\n# the owner of /etc/odbc_mail.ini, because this file must have mode 0600.\n# Consider creating a new user account for this delivery only.\n# You should specify 'user = root' here only if Fallback delivery is\n# configured in /etc/odbc_mail.ini (for procmail fallback delivery\n# for instance)\n\n\n## IN DIRECTORS SECTION\n\n# Attempts delivery of all mail into the database\nto_db:\n  driver = smartuser\n  transport = odbc\n  require_files = /etc/odbc_mail.ini\n  #\n  # uncomment line below to deliver all mail to db-XXX into the database, for any\n  # value of XXX. For this to work, set \"RemovePrefix = db-\" in\n  # the [Translate] section in /etc/odbc_mail.ini\n  #prefix = db-\n \n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Storing incoming mail into the DataBase" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nInstallation instructions\n\nThe Virtuoso server can store the incoming mail into the database using it's own local mailer implementation.\nThe following sections detail the configuration of each type of mail environment.\n\n\nReplacing procmail as default handler in sendmail configurations\n\nCopy virt_mail to /usr/bin/virt_mail\nCopy odbc_mail.default.ini to /etc/odbc_mail.ini\n    IMPORTANT: Make sure /etc/odbc_mail.ini is NOT GROUP/WORLD writable,\n    otherwise virt_mail will fail to run.\n    \n\nEdit /etc/odbc_mail.ini and change the login settings to match your\ncurrent database installation.\n \nIf you don't have or want to use procmail, comment out the "Fallback"\nsetting in the [Deliver] section.\n\nEdit /etc/sendmail.cf. Change:\n  Mlocal,\tP=/usr/bin/procmail, F=lsDFMAw5:/|@qSPfhn9, S=10/30, R=20/40,\n\t\t  T=DNS/RFC822/X-Unix,\n\t\t  A=procmail -Y -a $h -d $u\n\ninto:\n  Mlocal,\tP=/usr/bin/virt_mail, F=lsDFMA5:/|@qSPhn9,\n\t\tS=10/30, R=20/40, T=DNS/RFC822/X-Unix,\n\t\tA=virt_mail -c /etc/odbc_mail.ini -l $u -s $g\n\nNOTE: The changes to the F= setting involve removing both the 'w' and 'f' flags.\n\nThe removal of the 'w' flag affects lookups in /etc/passwd, which are no\nlonger required if all mail drops go into the database.\nThe default ini file is set up to maildrop to procmail, which will perform\nthis check correctly.\n\n\nPer-user database maildrops under sendmail\n\nCopy odbc_mail.default.ini to ~the_user_name/.odbc_mail.ini\nIMPORTANT: Make sure the .odbc_mail.ini is NOT GROUP/WORLD writable,\notherwise virt_mail will fail to run.\nPut at the end of ~the_user_name/.procmailrc something like:\n:0:\n| /usr/bin/virt_mail -c .odbc_mail.ini -l the_user_name\n\nreplacing the_user_name with the user you're setting up.\n\nNote: the '-l ..' parameter is used to relate the local recipient to\nthe database user for which the maildrop is done. See the remarks in\nthe odbc_mail.default.ini file.\n\nAdjust the parameters in .odbc_mail.ini to match your configuration\n\nIMPORTANT - also disable Fallback delivery in .odbc_mail.ini\nComment out the "Fallback =" entry in the .odbc_mail.ini\nor set it to something that doesn't involve procmail.\nOtherwise, this could lead to drop loops.\n\n\n\nPer-user database maildrops under qmail\n\n\nCopy odbc_mail.default.ini to ~the_user_name/.odbc_mail.ini\nIMPORTANT: Make sure the .odbc_mail.ini is NOT GROUP/WORLD writable,\notherwise virt_mail will fail to run.\n\nIf you're setting up a .qmail, simply do something like\n| /usr/bin/virt_mail -m qmail -c .odbc_mail.ini\n\nIf you're setting up .qmail-default or .qmail-<some_alias_name>,\nmake sure you adjust the RemovePrefix accordingly in the odbc_mail.ini.\n\nThis also works if a single user is receiving mail for an entire\n(virtual) domain.\n\nIf you want to configure qmail so that user 'db' gets all mail for\nexample.com, do this:\n \n  Create a new user db in /etc/passwd etc.\n  Remove example.com from /var/qmail/control/locals\n  Add to /var/qmail/controls/virtualdomains:\nexample.com:db\n  Adjust /var/qmail/users/assign accordingly:\n\t=db:db:<uid>:<gid>:<home>:::\n\t+db-:db:<uid>:<gid>:<home>:-::\n  or run\n  qmail-pw2u < /etc/passwd > /var/qmail/users/assign\n  then run qmail-newu and restart qmail\n  In ~db/.qmail-default, put:\n| /usr/bin/virt_mail -m qmail -c .odbc_mail.ini\n  In .odbc_mail.ini, set RemovePrefix=db-\nNow, mail to info@example.com will be delivered to the qmail alias\ndb-info@example.com and is stored into the database for user 'info'.\n  \n\nAdjust the parameters in .odbc_mail.ini to match your configuration\n\n\nPer-user database maildrops under courier\n\nCopy odbc_mail.default.ini to ~the_user_name/.odbc_mail.ini\nIMPORTANT: Make sure the .odbc_mail.ini is NOT GROUP/WORLD writable,\notherwise virt_mail will fail to run.\n\nIf you're setting up a .courier, simply do something like\n| /usr/bin/virt_mail -mcourier -c .odbc_mail.ini\n\nIf you're setting up .courier-default or .courier-<some_alias_name>,\nmake sure you adjust the RemovePrefix accordingly in the .odbc_mail.ini.\n\nNote 1: Although courier is very similar to qmail in this respect,\nit is different from qmail in how it handles exit codes.\nIf you use -mqmail while running under courier, you'll get the wrong\nexit codes, so mail is bounced instead of retried.\n\nNote 2: If delivering to multiple recipients in a .courier file,\nmake sure the virt_mail is specified first. This is because if the\nvirt_mail fails with a temporary error, the other recipients will\nget another drop when courier re-attempts to deliver the mail.\nRight:\n| /usr/bin/virt_mail -mcourier -c .odbc_mail.ini\n./Maildir\nWrong:\n./Maildir\n| /usr/bin/virt_mail -mcourier -c .odbc_mail.ini\n\nAdjust the parameters in .odbc_mail.ini to match your configuration\n\n\nEXIM\nHere are code snippets for Exim that perform maildrops into the odbc database.\n\n## IN TRANSPORT SECTION\n\n# Delivers into the database\nodbc:\n  driver = pipe\n  command = /usr/bin/virt_mail \\\n\t-c /etc/odbc_mail.ini \\\n\t-s "${if def:return_path{$return_path}{MAILER-DAEMON}}" \\\n\t-l "$local_part"\n  user = USERNAME\n  return_path_add\n  delivery_date_add\n  prefix =\n  suffix =\n  temp_errors = 73 : 74 : 75\n  return_fail_output\n\n# NOTE: Make sure the USERNAME in the 'user = USERNAME' setting matches\n# the owner of /etc/odbc_mail.ini, because this file must have mode 0600.\n# Consider creating a new user account for this delivery only.\n# You should specify 'user = root' here only if Fallback delivery is\n# configured in /etc/odbc_mail.ini (for procmail fallback delivery\n# for instance)\n\n\n## IN DIRECTORS SECTION\n\n# Attempts delivery of all mail into the database\nto_db:\n  driver = smartuser\n  transport = odbc\n  require_files = /etc/odbc_mail.ini\n  #\n  # uncomment line below to deliver all mail to db-XXX into the database, for any\n  # value of XXX. For this to work, set "RemovePrefix = db-" in\n  # the [Translate] section in /etc/odbc_mail.ini\n  #prefix = db-\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Text triggers notification" ;
	sioc:content	"\nExample\n\n  The SMTP client function can be used for automatic responses and notifications for DB events.\n  The example shows mail delivery code for the hit notifications on the text triggers in DAV.\n  When a free-text trigger query is defined to make an email notification, the trigger will have an email address stored in the column TTH_NOTIFY of the HITS table.\n  The notification is a separate procedure that opens a cursor over the hits table. For every non-empty recipient, a message is sent.\n  Note that in this example the mail server passed to the smtp_send() is null.\n  This means that the default mail server from virtuoso.ini will be used for making the SMTP connection.\n \n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Using the SMTP client function for free-text triggers notification" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The SMTP client function can be used for automatic responses and notifications for DB events.\n  The example shows mail delivery code for the hit notifications on the text triggers in DAV.\n  When a free-text trigger query is defined to make an email notification, the trigger will have an email address stored in the column TTH_NOTIFY of the HITS table.\n  The notification is a separate procedure that opens a cursor over the hits table. For every non-empty recipient, a message is sent.\n  Note that in this example the mail server passed to the smtp_send() is null.\n  This means that the default mail server from virtuoso.ini will be used for making the SMTP connection.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Mail notification" ;
	sioc:content	"\nExample\n\n  The example shows an automatic reply to the sender.\n  If the message contains a valid XML structure describing the order SOAP request,\n  it will add the order to the demo tables and reply with a success message.\n  If there is no valid structure, it will reply with a failure notice.\n  The web page contains configuration instructions.\n  It is possible to define the mail account on the server for processing these messages.\n\nAn example SMTP send command is :\n\n\nsmtp_send (\n  null,\n  'imitko@localhost',\n  'dav@localhost' ,\n  'Subject: SOAPMethodName: #new_order\\r\\n\\r\\n\n  \n  \n      \n        \n          <_CustomerID>CENTC\n          <_EmployeeID>1\n          <_ShipVia>3\n          <_RequiredDate>2001-05-31\n          <_ProductID>26\n          <_Quantity>1\n          <_Discount>0.300000\n        \n      \n  '\n);\n\n\n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Automatic reply to mail message" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The example shows an automatic reply to the sender.\n  If the message contains a valid XML structure describing the order SOAP request,\n  it will add the order to the demo tables and reply with a success message.\n  If there is no valid structure, it will reply with a failure notice.\n  The web page contains configuration instructions.\n  It is possible to define the mail account on the server for processing these messages.\n\nAn example SMTP send command is :\n\n\nsmtp_send (\n  null,\n  'imitko@localhost',\n  'dav@localhost' ,\n  'Subject: SOAPMethodName: #new_order\\r\\n\\r\\n\n  <?xml version=\\'1.0\\' ?>\n  <SOAP:Envelope\n    xmlns:xsi=\\'http://www.w3.org/1999/XMLSchema-instance\\'\n    xmlns:xsd=\\'http://www.w3.org/1999/XMLSchema\\'\n    xmlns:SOAP=\\'urn:schemas-xmlsoap-org:soap.v1\\'\n    xmlns:dt=\\'urn:schemas-microsoft-com:datatypes\\'>\n      <SOAP:Body>\n        <new_order>\n          <_CustomerID>CENTC</_CustomerID>\n          <_EmployeeID>1</_EmployeeID>\n          <_ShipVia>3</_ShipVia>\n          <_RequiredDate>2001-05-31</_RequiredDate>\n          <_ProductID>26</_ProductID>\n          <_Quantity>1</_Quantity>\n          <_Discount>0.300000</_Discount>\n        </new_order>\n      </SOAP:Body>\n  </SOAP:Envelope>'\n);\n\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"MIME messages" ;
	sioc:content	"\nExample\n\n  This example renders a MIME tree as HTML.\n  The messages are from a designated POP server.\n  The retrieved messages are stored into a local table without deleting from the origin server.\n  The web page has a function for clearing the operation.\n\n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Rendering MIME message as HTML" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  This example renders a MIME tree as HTML.\n  The messages are from a designated POP server.\n  The retrieved messages are stored into a local table without deleting from the origin server.\n  The web page has a function for clearing the operation.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"MIME messages" ;
	sioc:content	"\nExample\n\n  The example builds a multipart MIME message and sends it to an external mailbox.\n  The page will accept the recipient, text and a single file upload.\n  It will make these into a MIME message to be sent.\n  The mail server is specified on the form.\n \n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Creating a simple MIME message" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The example builds a multipart MIME message and sends it to an external mailbox.\n  The page will accept the recipient, text and a single file upload.\n  It will make these into a MIME message to be sent.\n  The mail server is specified on the form.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"POP3 server" ;
	sioc:content	"\nExample\n\n  The example inserts data into the tables used by the local POP3 server, including user accounts.\n  Data imported from another POP3 server is made available.\n \n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Storing mails in local POP3 server" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nExample\n\n  The example inserts data into the tables used by the local POP3 server, including user accounts.\n  Data imported from another POP3 server is made available.\n \n\n " .
	rdf:type	foaf:Document ;
	dc:title	"NNTP get messages" ;
	sioc:content	"\nPreliminaries\nThe nntp_get() function can read the following information:\n\n  List of news groups on a server.\n  Length and Range of message numbers within a group.\n  Message headers.\n  Message body can be read with nntp_get() or nntp_id_get().\n\n\nNewsgroup message read example\n\n    Display group list from an external NNTP server.\n    Display last 20 message headers from the selected newsgroup.\n    Display any selected message using nntp_get() or nntp_id_get().\n\n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Get messages from NNTP server" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nPreliminaries\nThe nntp_get() function can read the following information:\n\n  List of news groups on a server.\n  Length and Range of message numbers within a group.\n  Message headers.\n  Message body can be read with nntp_get() or nntp_id_get().\n\n\nNewsgroup message read example\n\n    Display group list from an external NNTP server.\n    Display last 20 message headers from the selected newsgroup.\n    Display any selected message using nntp_get() or nntp_id_get().\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"NNTP messages" ;
	sioc:content	"\nNewsgroup message write example\n\n    The example builds an NNTP message and sends it to an external NNTP server.\n    The form accepts the news server, newsgroup name and message body.\n\n" ;
	sioc:has_container	ns2:intprot ;
	sioc:description	"Creating a simple NNTP message" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\nNewsgroup message write example\n\n    The example builds an NNTP message and sends it to an external NNTP server.\n    The form accepts the news server, newsgroup name and message body.\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"IBuySpy application" ;
	sioc:content	"\nOverview\n\nThe goal of that demo is to demonstrate ability of Virtuoso server to host ASP.NET projects\nThe IBuySpy application is ASP.NET based solution for making a portal applications\nThe demo uses Virtuoso as hosting environment and Database back-end\nIt may re-configured easy to use MS SQL server as back-end\nThe Database connection options are two\nVirtuoso .NET client\nVirtuoso OLEDB provider\n\n\nInstallation\n\n\n \n\nThis demo can be started only on Virtuoso server running over Windows OS environment\nIf you are going to try application using MS SQL Server back-end, the IBuySpy application must be downloaded from www.ibuyspy.com and installed.\nThe Mobile Internet Toolkit (MMIT 1.0), available from www.asp.net must be installed.\nGo to the folder vsp/IBuySpy under installation directory and unpack one of the .ZIP archives, depending of provider type : OLEDB or .NET provider. Please note that Store application is available only with .NET provider only.\nThe content of archive must be extracted under vsp/IBuySpy, so if all is ok the PortalCSVS subdirectory must appear.\nIf you are not running Virtuoso demo instance, the supplied SQL scripts must be loaded via ISQL tool using DBA account. In this case also needs to define a virtual directory pointing to the (HTTP root)/IBuySpy/PortalCSVS and (HTTP root)/IBuySpy/StoreCSVS. (See web applications tutorial how to make a executable virtual directory) \n\nIf you are running Virtuoso demo instance, the scripts are already loaded and virtual directory is created. \nEdit the Web.config file under vsp/IBuySpy/PortalCSV directory and change the address of Virtuoso server location (host name and ODBC/SQL port) in the appSettings section, key=\"ConnectionString\" element \nThe Portal application Web UI is accessible through the http://[host:port]/PortalCSVS/\nAlso the Store application Web UI is accessible through the http://[host:port]/StoreCSVS/\n\n" ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Running ASPX based applications" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\nOverview\n\nThe goal of that demo is to demonstrate ability of Virtuoso server to host ASP.NET projects\nThe IBuySpy application is ASP.NET based solution for making a portal applications\nThe demo uses Virtuoso as hosting environment and Database back-end\nIt may re-configured easy to use MS SQL server as back-end\nThe Database connection options are two\nVirtuoso .NET client\nVirtuoso OLEDB provider\n\n\nInstallation\n\n\n \n\nThis demo can be started only on Virtuoso server running over Windows OS environment\nIf you are going to try application using MS SQL Server back-end, the IBuySpy application must be downloaded from www.ibuyspy.com and installed.\nThe Mobile Internet Toolkit (MMIT 1.0), available from www.asp.net must be installed.\nGo to the folder vsp/IBuySpy under installation directory and unpack one of the .ZIP archives, depending of provider type : OLEDB or .NET provider. Please note that Store application is available only with .NET provider only.\nThe content of archive must be extracted under vsp/IBuySpy, so if all is ok the PortalCSVS subdirectory must appear.\nIf you are not running Virtuoso demo instance, the supplied SQL scripts must be loaded via ISQL tool using DBA account. In this case also needs to define a virtual directory pointing to the (HTTP root)/IBuySpy/PortalCSVS and (HTTP root)/IBuySpy/StoreCSVS. (See web applications tutorial how to make a executable virtual directory) \n\nIf you are running Virtuoso demo instance, the scripts are already loaded and virtual directory is created. \nEdit the Web.config file under vsp/IBuySpy/PortalCSV directory and change the address of Virtuoso server location (host name and ODBC/SQL port) in the appSettings section, key="ConnectionString" element \nThe Portal application Web UI is accessible through the http://[host:port]/PortalCSVS/\nAlso the Store application Web UI is accessible through the http://[host:port]/StoreCSVS/\n\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"PetShop application" ;
	sioc:content	"\nOverview\n\nThe PetShop application developed by Microsoft using ASP .Net and C# used in this tutorial is another demonstration of Virtuoso's ability to host ASP .Net projects.   This ASP .Net data driven shopping cart application for browsing and adopting Pets utilizes Virtuoso's 3rd Party hosting feature as well as the Virtuoso database as the data store. \n\n\nThis demonstration is completely configurable and can be modified easily to change the data store to Microsoft SQL Server.\n\n\n\nPrerequisites\nThe following prerequisites should be used to make sure your computer has the appropriate operating system and software to demonstrate the PetShop application using Virtuoso running on the Windows.\n\n Windows 2000/XP\n Virtuoso Universal Servers Microsoft ASP .Net enabled binary\n Microsoft ASP .Net Framework SDK\n\n\nInstallation and Configuration\n\nThis demonstration is based on the Virtuoso Universal Server running in a Windows operating system environment and includes configuration steps to run the PetShop application.   If you have installed the demonstration database and have an environment already running the Virtuoso demo instance, the SQL scripts and configuration files are already loaded and the virtual directory has been created as part of the installation.\n\n\nIf you are not running in this environment perform the following steps to demonstrate the PetShop Application\n\n \n\nIn the folder vsp/Petshop under the Virtuoso Universal Server installation directory unpack and extract the OLEDB the .ZIP archive.\n\nRegister the PetShop.Components.dll as COM object using regsvcs utility, which is required to start the application.\n\nCreate the PetShop database schemas (MSPetShop and MSPetShopOrders), including tables and stored procedures and populate the databases using the following supplied SQL scripts located in the PetShop\\DatabaseScripts\\SQL subdirectory.  These scripts can be loaded using the OpenLink Virtuoso Interactive SQL Interface (ISQL) tool available from the OpenLink Virtuoso start menu using the DBA account.\n\nCreateDBLogin1.sql\nCreateTables1.sql\nCreateTables2.sql\nLoadTables1.sql\n\n\n Define a new virtual directory pointing to the (HTTP root)/PetShop/Web. (For instructions on creating an executable virtual directory see the Web applications tutorials (LINK))\n\n Edit two connection strings in Web.config file which is located under the vsp/PetShop/Web directory.  Add two entries with same values for the address set to the Virtuoso server location (host name and ODBC/SQL port), the account and password (UID and PWD) and the change the name of each of the databases; one for \"MSPetShop\" and one for MSPetShopOrders the appSettings section, key=\"ConnectionString\" element\n\n                Example:\n                 \n                \n                \n\t\t\n\n\nOnce configured, the PetShop application Web UI will be accessible from the URL http://[host:port]/PetShop/\n\n\n\nConfiguration Options\nDatabase\n\nThe PetShop application is designed to be configurable and is easily modified.   Should you choose to switch the database data store to Microsoft SQL Server, you will need to install the complete PetShop application, which can be downloaded from http://www.gotdotnet.com/team/compare/petshop.aspx.\n \nLimits/Restrictions\n\nIn Virtuoso, the PetShop application is available only with .NET provider.\n" ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Running ASPX based applications" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\nOverview\n\nThe PetShop application developed by Microsoft using ASP .Net and C# used in this tutorial is another demonstration of Virtuoso's ability to host ASP .Net projects.   This ASP .Net data driven shopping cart application for browsing and adopting Pets utilizes Virtuoso's 3rd Party hosting feature as well as the Virtuoso database as the data store. \n\n\nThis demonstration is completely configurable and can be modified easily to change the data store to Microsoft SQL Server.\n\n\n\nPrerequisites\nThe following prerequisites should be used to make sure your computer has the appropriate operating system and software to demonstrate the PetShop application using Virtuoso running on the Windows.\n\n Windows 2000/XP\n Virtuoso Universal Servers Microsoft ASP .Net enabled binary\n Microsoft ASP .Net Framework SDK\n\n\nInstallation and Configuration\n\nThis demonstration is based on the Virtuoso Universal Server running in a Windows operating system environment and includes configuration steps to run the PetShop application.   If you have installed the demonstration database and have an environment already running the Virtuoso demo instance, the SQL scripts and configuration files are already loaded and the virtual directory has been created as part of the installation.\n\n\nIf you are not running in this environment perform the following steps to demonstrate the PetShop Application\n\n \n\nIn the folder vsp/Petshop under the Virtuoso Universal Server installation directory unpack and extract the OLEDB the .ZIP archive.\n\nRegister the PetShop.Components.dll as COM object using regsvcs utility, which is required to start the application.\n\nCreate the PetShop database schemas (MSPetShop and MSPetShopOrders), including tables and stored procedures and populate the databases using the following supplied SQL scripts located in the PetShop\\DatabaseScripts\\SQL subdirectory.  These scripts can be loaded using the OpenLink Virtuoso Interactive SQL Interface (ISQL) tool available from the OpenLink Virtuoso start menu using the DBA account.\n\nCreateDBLogin1.sql\nCreateTables1.sql\nCreateTables2.sql\nLoadTables1.sql\n\n\n Define a new virtual directory pointing to the (HTTP root)/PetShop/Web. (For instructions on creating an executable virtual directory see the Web applications tutorials (LINK))\n\n Edit two connection strings in Web.config file which is located under the vsp/PetShop/Web directory.  Add two entries with same values for the address set to the Virtuoso server location (host name and ODBC/SQL port), the account and password (UID and PWD) and the change the name of each of the databases; one for "MSPetShop" and one for MSPetShopOrders the appSettings section, key="ConnectionString" element\n\n                Example:\n                 \n                <add key="ConnString1" value="HOST=localhost:1112;UID=petshop;PWD=password;Database=MSPetShop" />\n                <add key="ConnString2"value="HOST=localhost:1112;UID=petshop;PWD=password;Database=MSPetShopOrders" />\n\t\t\n\n\nOnce configured, the PetShop application Web UI will be accessible from the URL http://[host:port]/PetShop/\n\n\n\nConfiguration Options\nDatabase\n\nThe PetShop application is designed to be configurable and is easily modified.   Should you choose to switch the database data store to Microsoft SQL Server, you will need to install the complete PetShop application, which can be downloaded from http://www.gotdotnet.com/team/compare/petshop.aspx.\n \nLimits/Restrictions\n\nIn Virtuoso, the PetShop application is available only with .NET provider.\n\n " .
	rdf:type	foaf:Document ;
	dc:title	"Integrating Common Language Runtime Objects with Virtuoso" ;
	sioc:content	"\n    Overview\n    This tutorial demonstrates Web Services hosted on Virtuoso.  The \n\tWeb Service was created using MS Visual Studio. \n    \n    Prerequisites\n    The following prerequisites ensure the usability of these tutorial demos on Windows\n\nWindows\n   \n     .NET Runtime and Frameworks\n     .Net Runtime and Framework SDK (if you seek to write your own \n\t Objects for integration with Virtuoso)\n     Virtuoso Universal Server for Windows with .NET CLR Hosting\n     \n\n    \n    Tutorial Example\n\n  Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the \"Set Initial State\" link which registers the two C# classes \n within Virtuoso.  Click on the \"ho_s_12.sql\" link to see the code behind this step.\n Click on the \"Run\" links to execute the demos.\n\n\nDemo Breakdown\n\n\n \"ho_s_12.sql\" performs the following steps:\n  \n   Defines a Virtual Directory called \"asmx_tutorial\".  \n   Imported WSDL to define types needed for virtuoso soap client.\n   Defines a procedure to return soap cal result using previously defined types.\n  \n\n The \"asmx_tutorial.vsp\" shows all end-points URLs defined from the Web Service.\n\n    " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Hosting .Net Web Services in Virtuoso." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    Overview\n    This tutorial demonstrates Web Services hosted on Virtuoso.  The \n\tWeb Service was created using MS Visual Studio. \n    \n    Prerequisites\n    The following prerequisites ensure the usability of these tutorial demos on Windows\n\nWindows\n   \n     .NET Runtime and Frameworks\n     .Net Runtime and Framework SDK (if you seek to write your own \n\t Objects for integration with Virtuoso)\n     Virtuoso Universal Server for Windows with .NET CLR Hosting\n     \n\n    \n    Tutorial Example\n\n  Please follow the steps below to maximize the value of this tutorial:\n\n\n Click on the "Set Initial State" link which registers the two C# classes \n within Virtuoso.  Click on the "ho_s_12.sql" link to see the code behind this step.\n Click on the "Run" links to execute the demos.\n\n\nDemo Breakdown\n\n\n "ho_s_12.sql" performs the following steps:\n  \n   Defines a Virtual Directory called "asmx_tutorial".  \n   Imported WSDL to define types needed for virtuoso soap client.\n   Defines a procedure to return soap cal result using previously defined types.\n  \n\n The "asmx_tutorial.vsp" shows all end-points URLs defined from the Web Service.\n\n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Basic ASP.NET Hosting Demo" ;
	sioc:content	"\n    Overview\n    The HO-S-6 tutorial shows all the ASP.NET standard \n    controls hosted inside Virtuoso's DAV repository and accessible via its HTTP server.\n\n    Prerequisites\n\n  The following prerequisites should be used to ensure that your computer \n  has the appropriate operating system and software to run the Virtuoso 3rd \n  Party Hosting HO-S-6 tutorial on Windows 2000, XP or operating systems \n  capable of running Mono. Windows or Linux\n\n\n  Virtuoso Universal with support for Microsoft .NET and  Mono Hosting enabled.  \n  Microsoft .NET Runtime or Mono Runtime  \n  Microsoft .NET  Frameworks (specifically ASP.NET) or Mono's ASP.NET Frameworks (this is part of the Mono bundle included in the Virtuoso installer)  \n\n\n    Tutorial Example\n\n  All the standard ASP.NET base controls (including but not limited to \n  buttons, drop-down lists and tab controls etc) are listed in a table with \n  invocation and source code revealing hyperlinks.  The C# source code of each \n  control is   optionally vieweable by clicking the  matching hyperlink in the \n  \"View Source\" column.   To execute each of these aspx pages click on the  \n  \"run\" hyperlink  in the \"Action\" column.\n\n  For troubleshooting tips, refer to the \"Environment Setup\" \n  section in \"Runtime hosting\" chapter of the Virtuoso documentation. \n\n  " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Hosting standard ASP.NET controls within Virtuoso." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    Overview\n    The HO-S-6 tutorial shows all the ASP.NET standard \n    controls hosted inside Virtuoso's DAV repository and accessible via its HTTP server.\n\n    Prerequisites\n\n  The following prerequisites should be used to ensure that your computer \n  has the appropriate operating system and software to run the Virtuoso 3rd \n  Party Hosting HO-S-6 tutorial on Windows 2000, XP or operating systems \n  capable of running Mono. Windows or Linux\n\n\n  Virtuoso Universal with support for Microsoft .NET and  Mono Hosting enabled.  \n  Microsoft .NET Runtime or Mono Runtime  \n  Microsoft .NET  Frameworks (specifically ASP.NET) or Mono's ASP.NET Frameworks (this is part of the Mono bundle included in the Virtuoso installer)  \n\n\n    Tutorial Example\n\n  All the standard ASP.NET base controls (including but not limited to \n  buttons, drop-down lists and tab controls etc) are listed in a table with \n  invocation and source code revealing hyperlinks.  The C# source code of each \n  control is   optionally vieweable by clicking the  matching hyperlink in the \n  "View Source" column.   To execute each of these aspx pages click on the  \n  "run" hyperlink  in the "Action" column.\n\n  For troubleshooting tips, refer to the "Environment Setup" \n  section in "Runtime hosting" chapter of the Virtuoso documentation. \n\n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"DataGrid ASP.NET Hosting Demo" ;
	sioc:content	"\n    Overview\n    This tutorial is a demonstration of how Virtuoso hosts the ASP.NET  and ADO.NET Frameworks as implemented by Microsoft.NET and Mono. The demo consists of a DataGrid control which uses ADO.NET and Virtuoso's managed Data Provider to retrieve data from the local Virtuoso database hosting this tutorial application. \n    \n    Prerequisites\n    The following prerequisites should be used to ensure computer has the appropriate operating system and software to run the Virtuoso 3rd Party Hosting HO-S-7 tutorial on Windows 2000, XP or operating systems capable of running Mono.\n    (See the Mono project home page for information regarding Mono developed by Ximian). \n\n\n  Virtuoso Universal Servers Microsoft ASP .Net or Mono ECMA-CLI enabled binary   \n  CLR from Microsoft ASP .Net Framework SDK \n  Review the documentation on CLR Hosting setup in the Runtime Hosting, chapter 15 of the Virtuoso documentation\n\n\n    \n    Tutorial Example\n\n  The HO-S-7 tutorial uses the C# bound .aspx page to demonstrate\n  data retrieval via ADO.NET, and data display using the standard ASP.NET DataGrid control. \n  The source code for the DataGrid control (\"VirtSample.aspx\") is\n  viewable  by clicking the associated hyperlink in the \"View Source\" column, and\n  can be executed by clicking  the \"Run\" hyperlink in the \"Action\" column..\n\nNotes\nIn this tutorial, the data provider being used is the Virtuoso.NET managed provider, which is installed as part of the Virtuoso installation process.   To run this tutorial, the demo instance requires an Access Control List file modification (in this case the .INI file associated with the demo database instance); this involves adding a section-key-value to \"DirsAllowed\" section-key that points to the location of the  OpenLink.Data.Virtuoso.dll assembly (which hosts the managed data provider)  \nSimply append  the file reference \"../bin/OpenLink.Data.Virtuoso.dll\" to the last entry for the section-key  \"DirsAllowed\". If you have changed the password for \"demo\" SQL account (you are encouraged to do this at installation time), you will need to Edit the connection string in the Web.config file associated with this application domain and change the password (PWD) in key=\"ConnectionString\" element which is part of the appSettings section,\ne.g.:\n\nThe Web.config file is located in one of the following locations depending on the CLR being used for the demonstration\n\n [http_root]/vad/vsp/tutorial/hosting/ho_s_7/Web.config if you are using server hosting MS.NET CLR.\n mono/lib/mono/machine.config if you are using server-hosting ECMA-CLI (Mono).\n\n\nFor troubleshooting tips, refer to the \"Environment Setup\" section in \"Runtime Hosting\", chapter 15 in the Virtuoso documentation. \n\n\n  " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"A databound ASP.NET page hosted within Virtuoso's\n    WebDAV repository" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    Overview\n    This tutorial is a demonstration of how Virtuoso hosts the ASP.NET  and ADO.NET Frameworks as implemented by Microsoft.NET and Mono. The demo consists of a DataGrid control which uses ADO.NET and Virtuoso's managed Data Provider to retrieve data from the local Virtuoso database hosting this tutorial application. \n    \n    Prerequisites\n    The following prerequisites should be used to ensure computer has the appropriate operating system and software to run the Virtuoso 3rd Party Hosting HO-S-7 tutorial on Windows 2000, XP or operating systems capable of running Mono.\n    (See the Mono project home page for information regarding Mono developed by Ximian). \n\n\n  Virtuoso Universal Servers Microsoft ASP .Net or Mono ECMA-CLI enabled binary   \n  CLR from Microsoft ASP .Net Framework SDK \n  Review the documentation on CLR Hosting setup in the Runtime Hosting, chapter 15 of the Virtuoso documentation\n\n\n    \n    Tutorial Example\n\n  The HO-S-7 tutorial uses the C# bound .aspx page to demonstrate\n  data retrieval via ADO.NET, and data display using the standard ASP.NET DataGrid control. \n  The source code for the DataGrid control ("VirtSample.aspx") is\n  viewable  by clicking the associated hyperlink in the "View Source" column, and\n  can be executed by clicking  the "Run" hyperlink in the "Action" column..\n\nNotes\nIn this tutorial, the data provider being used is the Virtuoso.NET managed provider, which is installed as part of the Virtuoso installation process.   To run this tutorial, the demo instance requires an Access Control List file modification (in this case the .INI file associated with the demo database instance); this involves adding a section-key-value to "DirsAllowed" section-key that points to the location of the  OpenLink.Data.Virtuoso.dll assembly (which hosts the managed data provider)  \nSimply append  the file reference "../bin/OpenLink.Data.Virtuoso.dll" to the last entry for the section-key  "DirsAllowed". If you have changed the password for "demo" SQL account (you are encouraged to do this at installation time), you will need to Edit the connection string in the Web.config file associated with this application domain and change the password (PWD) in key="ConnectionString" element which is part of the appSettings section,\ne.g.:\n<add key="ConnectionString" value="HOST=localhost:1112;UID=demo;PWD=demo;Database=demo" />\nThe Web.config file is located in one of the following locations depending on the CLR being used for the demonstration\n\n [http_root]/vad/vsp/tutorial/hosting/ho_s_7/Web.config if you are using server hosting MS.NET CLR.\n mono/lib/mono/machine.config if you are using server-hosting ECMA-CLI (Mono).\n\n\nFor troubleshooting tips, refer to the "Environment Setup" section in "Runtime Hosting", chapter 15 in the Virtuoso documentation. \n\n\n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"PHP ODBC Hosting Demo" ;
	sioc:content	"\n    PHP script calling ODBC\n\n  \n  This demo shows simple ODBC functions being used in a PHP script:\nodbc_connect(), odbc_exec(), odbc_result_all() and odbc_tables().\n  \n\n\nThe WebCalendar application is an Open-Source implementation of\na multi-user web-calendar in PHP, released under the terms of the\nGPL;\nthe project homepage is hosted\non SourceForge.net. We include it\nhere as an example of how to take an existing PHP application designed\nto run with Apache against mysql, postgresql or ODBC database\nbackends, and host it within Virtuoso.\n\n\nThe default username and password are admin/admin.\n\nThe \"Set the initial state\" SQL files must be executed prior to running the demo.\nThe file create_local_dsn.sql will create a local DSN named \"Local Virtuoso Tutorial HO-S-30\", which will be used \nfor connecting the database.\n\n\n  \n  For troubleshooting please read the \"Environment Setup\" section in \"Runtime hosting\" chapter from documentation.\n  \n  \n  " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Use of ODBC from within a PHP script hosted in Virtuoso" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    PHP script calling ODBC\n\n  \n  This demo shows simple ODBC functions being used in a PHP script:\nodbc_connect(), odbc_exec(), odbc_result_all() and odbc_tables().\n  \n\n\nThe WebCalendar application is an Open-Source implementation of\na multi-user web-calendar in PHP, released under the terms of the\nGPL;\nthe project homepage is hosted\non SourceForge.net. We include it\nhere as an example of how to take an existing PHP application designed\nto run with Apache against mysql, postgresql or ODBC database\nbackends, and host it within Virtuoso.\n\n\nThe default username and password are admin/admin.\n\nThe "Set the initial state" SQL files must be executed prior to running the demo.\nThe file create_local_dsn.sql will create a local DSN named "Local Virtuoso Tutorial HO-S-30", which will be used \nfor connecting the database.\n\n\n  \n  For troubleshooting please read the "Environment Setup" section in "Runtime hosting" chapter from documentation.\n  \n  \n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"Integrating Perl Scripts with Virtuoso" ;
	sioc:content	"\n    Overview\n  The following tutorial demonstrates how Virtuoso can be extended \n  through the use of Perl.\n  The demonstrations in this section highlight transparent integration \n  (hosting) between Virtuoso and the Perl Runtime. \n  \n    Prerequisites\n  The following prerequisites ensure the usability of these tutorial demos on any platform with a Perl runtime:\n\n    Perl 5.6 or higher for UNIX platforms or ActivePerl 5.8 or higher for Windows platforms\n    The DBI and DBD::ODBC Perl modules MUST be installed in order to run second example. (reffer to your Perl distribution documentation how to install them if they are not already installed)\n  Perl should be compiled with -Dusemultiplicity\n  Virtuoso Universal Server with Perl Runtime Hosting module\n \n\n    Tutorial Example\nThe following tutorial shows how Perl scripts using CGI.pm are executed within Virtuoso HTTP server. \nPlease follow the steps below to maximize the value of this tutorial:\n\n  Click on the \"Run\" links to actually experience the demo\n\n\n    " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Using Perl code to extend Virtuoso." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    Overview\n  The following tutorial demonstrates how Virtuoso can be extended \n  through the use of Perl.\n  The demonstrations in this section highlight transparent integration \n  (hosting) between Virtuoso and the Perl Runtime. \n  \n    Prerequisites\n  The following prerequisites ensure the usability of these tutorial demos on any platform with a Perl runtime:\n\n    Perl 5.6 or higher for UNIX platforms or ActivePerl 5.8 or higher for Windows platforms\n    The DBI and DBD::ODBC Perl modules MUST be installed in order to run second example. (reffer to your Perl distribution documentation how to install them if they are not already installed)\n  Perl should be compiled with -Dusemultiplicity\n  Virtuoso Universal Server with Perl Runtime Hosting module\n \n\n    Tutorial Example\nThe following tutorial shows how Perl scripts using CGI.pm are executed within Virtuoso HTTP server. \nPlease follow the steps below to maximize the value of this tutorial:\n\n  Click on the "Run" links to actually experience the demo\n\n\n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Integrating Python Scripts with Virtuoso" ;
	sioc:content	"\n    Overview\n  The following tutorial demonstrates how Virtuoso can be extended \n  through the use of Python.\n  The demonstrations in this section highlight transparent integration \n  (hosting) between Virtuoso and the Python Runtime. \n  \n    Prerequisites\n  The following prerequisites ensure the usability of these tutorial demos on any platform with a Python runtime:\n\n  Python 2.2\n  Python should be compiled to have lybpython2.2 as a shared object\n  Python should be compiled with -DWITH_THREADS\n  Virtuoso Universal Server with Python Runtime Hosting module\n \n\n    Tutorial Example\nThe following tutorial shows how Python scripts using cgi.py are executed within Virtuoso HTTP server. \nPlease follow the steps below to maximize the value of this tutorial:\n\n  Click on the \"Run\" links to actually experience the demo\n\n\n    " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Using Python code to extend Virtuoso." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    Overview\n  The following tutorial demonstrates how Virtuoso can be extended \n  through the use of Python.\n  The demonstrations in this section highlight transparent integration \n  (hosting) between Virtuoso and the Python Runtime. \n  \n    Prerequisites\n  The following prerequisites ensure the usability of these tutorial demos on any platform with a Python runtime:\n\n  Python 2.2\n  Python should be compiled to have lybpython2.2 as a shared object\n  Python should be compiled with -DWITH_THREADS\n  Virtuoso Universal Server with Python Runtime Hosting module\n \n\n    Tutorial Example\nThe following tutorial shows how Python scripts using cgi.py are executed within Virtuoso HTTP server. \nPlease follow the steps below to maximize the value of this tutorial:\n\n  Click on the "Run" links to actually experience the demo\n\n\n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Integrating Ruby Scripts with Virtuoso" ;
	sioc:content	"\n    Overview\n  The following tutorial demonstrates how Virtuoso can be extended \n  through the use of Ruby.\n  The demonstrations in this section highlight transparent integration \n  (hosting) between Virtuoso and the Ruby Runtime. \n  \n    Prerequisites\n  The following prerequisites ensure the usability of these tutorial demos on any platform with a Ruby runtime:\n\n  Ruby 1.8.2 or higher\n  Ruby should be compiled to have libruby.1.8 as a shared object\n  Virtuoso Universal Server with Ruby Runtime Hosting module\n \n\n    Tutorial Example\nThe following tutorial shows how Ruby scripts using cgitest.rb are executed within Virtuoso HTTP server. \nPlease follow the steps below to maximize the value of this tutorial:\n\n  Click on the \"Run\" links to actually experience the demo\n\n\n    " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Using Ruby code to extend Virtuoso." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    Overview\n  The following tutorial demonstrates how Virtuoso can be extended \n  through the use of Ruby.\n  The demonstrations in this section highlight transparent integration \n  (hosting) between Virtuoso and the Ruby Runtime. \n  \n    Prerequisites\n  The following prerequisites ensure the usability of these tutorial demos on any platform with a Ruby runtime:\n\n  Ruby 1.8.2 or higher\n  Ruby should be compiled to have libruby.1.8 as a shared object\n  Virtuoso Universal Server with Ruby Runtime Hosting module\n \n\n    Tutorial Example\nThe following tutorial shows how Ruby scripts using cgitest.rb are executed within Virtuoso HTTP server. \nPlease follow the steps below to maximize the value of this tutorial:\n\n  Click on the "Run" links to actually experience the demo\n\n\n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Basic JSP Hosting Demo" ;
	sioc:content	"\n    Overview\n    The HO-S-17 tutorial shows JSP hosting.\n\n    Prerequisites\n\n  *\n\n\n  *\n\n\n    Tutorial Example\n\n  To execute each of these jps pages click on the \"run\" hyperlink  in the \"Action\" column.\n\n  For troubleshooting tips, refer to the \"Environment Setup\" \n  section in \"Runtime hosting\" chapter of the Virtuoso documentation. \n\n  " ;
	sioc:has_container	ns2:apps ;
	sioc:description	"Hosting JSP controls within Virtuoso." ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:52 GMT" ;
	content:encoded	"\n    Overview\n    The HO-S-17 tutorial shows JSP hosting.\n\n    Prerequisites\n\n  *\n\n\n  *\n\n\n    Tutorial Example\n\n  To execute each of these jps pages click on the "run" hyperlink  in the "Action" column.\n\n  For troubleshooting tips, refer to the "Environment Setup" \n  section in "Runtime hosting" chapter of the Virtuoso documentation. \n\n  \n " .
	rdf:type	foaf:Document ;
	dc:title	"W3C XML Query Workgroup Testsuite" ;
	sioc:content	"" ;
	sioc:has_container	ns2:xmlapps ;
	sioc:description	"W3C XML Query Workgroup Testsuite" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"" .
	rdf:type	foaf:Document ;
	dc:title	"SPARQL Query Language" ;
	sioc:content	"\n    Tutorial Description\n\n\t  The following tutorial depends on the sparql_demo_dav.vad package, which is preinstalled in the demo db. \n\t  If you are running demo database or have installed sparql_demo_dav.vad package try this link /sparql_demo/. \n\t  If not run your demo db and point your browser to http://[host]:[port]/sparql_demo/\n    " ;
	sioc:has_container	ns2:linkeddata ;
	sioc:description	"SPARQL Query Language Demo" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:54 GMT" ;
	content:encoded	"\n    Tutorial Description\n\n\t  The following tutorial depends on the sparql_demo_dav.vad package, which is preinstalled in the demo db. \n\t  If you are running demo database or have installed sparql_demo_dav.vad package try this link /sparql_demo/. \n\t  If not run your demo db and point your browser to http://[host]:[port]/sparql_demo/\n    \n " .
	rdf:type	foaf:Document ;
	dc:title	"Linked Data" ;
	sioc:content	"\n    Concept\n    \n      This demonstration guides you through the process of \n      creating presence on the Semantic Web by creating a Linked Data URI. \n      There are simple instructions:\n    \n    \n      \n        Downloading Virtuoso (Commercial or Open Source)\n      \n      \n        Download and install Virtuoso installation archives\n      \n      \n        Download and install OpenLink Data Spaces (ODS) installation packages (VADs)\n      \n      \n        Start with OpenLink Virtuoso\n      \n      \n        Build OpenLink Virtuoso\n      \n      \n        OpenLink Virtuoso User Guide\n      \n    \n  \n     Simple steps registering ODS user\n     \n       Go to ODS Framework\n       Click Sign Up\n       Register either using the sample form or with existing OpenID\n     \n     Import data to your ODS profile using the \"Import\" feature\n     \n        Go to Edit profile\n        Open Import page\n        Enter FOAF Url or choose LDAP server\n     \n     Import RSS Feed in your Dataspace\n     \n        Go to Feed Manager\n        Click Admnistration\n        Click  Subscribe\n     \n     \n        Now view the link: http://[host:port]/dataspace/person/[username]\n     \n  " ;
	sioc:has_container	ns2:linkeddata ;
	sioc:description	"Getting Yourself a Linked Data URI in 5 minutes or less" ;
	dcterms:created_at	"Fri, 27 Dec 2019 14:12:53 GMT" ;
	content:encoded	"\n    Concept\n    \n      This demonstration guides you through the process of \n      creating presence on the Semantic Web by creating a Linked Data URI. \n      There are simple instructions:\n    \n    \n      \n        Downloading Virtuoso (Commercial or Open Source)\n      \n      \n        Download and install Virtuoso installation archives\n      \n      \n        Download and install OpenLink Data Spaces (ODS) installation packages (VADs)\n      \n      \n        Start with OpenLink Virtuoso\n      \n      \n        Build OpenLink Virtuoso\n      \n      \n        OpenLink Virtuoso User Guide\n      \n    \n  \n     Simple steps registering ODS user\n     \n       Go to ODS Framework\n       Click Sign Up\n       Register either using the sample form or with existing OpenID\n     \n     Import data to your ODS profile using the "Import" feature\n     \n        Go to Edit profile\n        Open Import page\n        Enter FOAF Url or choose LDAP server\n     \n     Import RSS Feed in your Dataspace\n     \n        Go to Feed Manager\n        Click Admnistration\n        Click  Subscribe\n     \n     \n        Now view the link: http://[host:port]/dataspace/person/[username]\n     \n  \n " .