Virtuoso 6.2
-- New Features
Virtuoso 6.2 introduces a major number of enhancements to
areas including:
Linked Data
Deployment
Feature |
Description |
Benefit |
Automatic Deployment |
Linked Data Pages are now automatically published
for every Virtuoso Data Object; users need only load
their data into the RDF Quad Store. |
Handcrafted URL-Rewrite Rules are no longer
necessary. |
HTTP Metadata
Enhancements |
HTTP Link: header is used to transfer
vital metadata (e.g., relationships between a
Descriptor Resource and its Subject) from HTTP Servers
to User Agents. |
Enables HTTP-oriented tools to work with such
relationships and other metadata. |
HTML Metadata Embedding |
HTML resource <head /> and
<link /> elements and their
@rel attributes are used to transfer vital
metadata (e.g., relationships between a Descriptor
Resource and its Subject) from HTTP Servers to User
Agents. |
Enables HTML-oriented tools to work with such
relationships and other metadata. |
Hammer Stack Auto-Discovery
Patterns |
HTML resource <head /> section
and <link /> elements, the HTTP
Link: header, and XRD-based
"host-meta" resources collectively provide
structured metadata about Virtuoso hosts, associated
Linked Data Spaces, and specific Data Items
(Entities). |
Enables humans and machines to easily distinguish
between Descriptor Resources and their Subjects,
irrespective of URI scheme. |
Linked Data
Middleware
Feature |
Description |
Benefit |
New Sponger Cartridges |
New cartridges (data access and transformation
drivers) for Twitter, Facebook, Amazon, eBay, LinkedIn,
and others. |
Enable users and user agents to deal with the
Sponged data spaces as though they were named graphs in
a quad store, or tables in an RDBMS. |
New Descriptor Pages |
HTML-based descriptor pages are automatically
generated. |
Descriptor subjects, and the constellation of
navigable attribute-and-value pairs that constitute
their descriptive representation, are clearly
identified. |
Automatic Subject Identifier
Generation |
De-referenceable data object identifiers are
automatically created. |
Removes tedium and risk of error associated with
nuance-laced manual construction of identifiers. |
Support for OData, JSON,
RDFa |
Additional data representation and serialization
formats associated with Linked Data. |
Increases flexibility and interoperability. |
Data
Virtualization
Feature |
Description |
Benefit |
Materialized RDF Views |
RDF Views over ODBC/JDBC Data Sources can now
(optionally) keep the Quad Store in sync with the RDBMS
data source. |
Enables high-performance Faceted Browsing while
remaining sensitive to changes in the RDBMS data
sources. |
CSV-to-RDF
Transformation |
Wizard-based generation of RDF Linked Data from CSV
files. |
Speeds deployment of data which may only exist in
CSV form as Linked Data. |
Transparent Data Access
Binding |
SPASQL (SPARQL Query Language integrated into SQL)
is usable over ODBC, JDBC, ADO.NET, OLEDB, or XMLA
connections. |
Enables Desktop Productivity Tools to transparently
work with any blend of RDBMS and RDF data sources. |
Dynamic
Data Exchange & Data Replication
Feature |
Description |
Benefit |
Quad Store to Quad Store
Replication |
High-fidelity graph-data replication between one or
more database instances. |
Enables a wide variety of deployment
topologies. |
Delta Engine |
Automated generation of deltas at the
named-graph-level, matches transactional replication
offered by the Virtuoso SQL engine. |
Brings RDF replication on par with SQL
replication. |
PubSubHubbub Support |
Deep integration within Quad Store as an optional
mechanism for shipping deltas. |
Enables push-based data replication across a
variety of topologies. |
Security
Feature |
Description |
Benefit |
WebID support at the DBMS
core |
Use WebID protocol for low-level ACL-based
protection of database objects (RDF or Relational) and
Web Services. |
Enables application of sophisticated security and
data access policies to Web Services (e.g., SPARQL
endpoint) and actual DBMS objects. |
Webfinger |
Supports using mailto: and
acct: URIs in the context of WebID and
other mechanisms, when domain holders have published
necessary XRDS resources. |
Enables more intuitive identification of people and
organizations. |
Fingerpoint |
Similar to Webfinger but does not require XRDS
resources; instea,d it works directly with SPARQL
endpoints exposed using auto-discovery patterns in the
<head /> section of HTML
documents. |
Enables more intuitive identification of people and
organizations. |