A Data Space is an atomic point of presence in cyberspace (Internet, Web, Blogosphere, Wikisphere, etc.) for interacting with Data, Information, Knowledge, and Services. Its content may be imported from, or simply point to data in, other Data Spaces. In all cases the content is either transient (generated "on the fly") or persistent (supported by cache synchronization schemes).
Data Spaces are fundamentally problem-domain-specific database applications. They offer functionality that you would instinctively expect of a database (e.g., ACID data management) with the additional benefit of being data-model- and query-language-agnostic. Data Spaces are for the most part DBMS Engine and Data Access Middleware hybrids, in the sense that ownership and control of data is inherently loosely-coupled.
Data Spaces are inherently more flexible, as they support multiple data models and data representation formats. Content management systems do not possess the same degree of dexterity over data models and data representations.
A Data Space cannot dictate the perception of its content. For instance, what I may consider as knowledge relative to my Data Space may not be the case to a remote client that interacts with it from a distance. Thus, defining my Data Space as Knowledgebase, purely, introduces constraints that reduce its broader effectiveness to third party clients (applications, services, users, etc.). A Knowledgebase is based on a Graph Data Model resulting in significant impedance for clients that are built around alternative models. To reiterate, Data Spaces support multiple data models.
They are an essential part of the burgeoning Data Web / Semantic Web. In short, they will take us from data "Mash-ups" (combining web accessible data that exists without integration and repurposing in mind) to "Mesh-ups" (combining web accessible data that exists with integration and repurposing in mind).
My Blog Data Space:
Some of RDF Data Sets exposed via My Data Spaces:
There are several, classifiable by query method available:
More information you can find here.
OAuth is an open protocol to allow secure API authentication in a simple and standard method from desktop and web applications.
OAuth allows the user to grant access to their private resources on one site (the Service Provider), to another site (called Consumer). OAuth is about giving access to your information without sharing all of your identity.
In ODS you can setup Application OAuth keys from Settings->OAuth keys. There you can select Application name from the drop-down list and click the "Generate Keys" button. As result for the selected application will be shown the generated Token and Secrete values.
More information you can find here.
MOAT (Meaning Of A Tag) provides a Semantic Web framework to publish semantically-annotated content from free-tagging.
MOAT Server is a application that serves tag meanings (in HTML, JSON or RDF/XML, using content negotiation for any Tag you request.
In ODS logged in as administrator, at Site Settings->Web Application Configuration you can define MOAT server with server URL and server key.
More information you can find here.
In ODS logged in as regular user, at Settings->Content Tagging Settings you can add new rules for which defined tagging rules is used the MAOT feature for importing meanings.
More information you can find here.
Your own ODS Data Space Personal URI is valid for linking to/from any Linked Data service.
More information you can find here.
The settings for <a>++ links can be changed in ODS Framework UI->user name->Edit My Profile->Personal page, drop-down list "Show <a>++ links". The options scope is:
More information you can find here.
Virtuoso offers a short way to view ODS user's WebDAV? file content. All you need to do is for existing ODS user to access the following url:
http://host:port/~<odsuser>/<name of the file>.
You can browse the ODS user's WebDAV? Public folder by accessing the following url:
http://host:port/~<ods-user>/Public.
For ex.: http://demo.openlinksw.com/Public
Yadis is an authentication service discovery protocol allowing Compliant Clients (identity consumers or member-sites) to deductively determine authentication protocol options available from a service provider.
The ODS Yadis URL is:
http://host:port/dataspace/[your-ods-username]
More information you can find here.
OpenID? is an open, decentralized system for user-centric digital identity. It works on the concept that anyone can identify themselves on the Internet the same way websites do - with a URI (sometimes called a URL or web address, somewhat inaccurately).
ODS supports the OpenID? Authentication 1.1 and registration extension 1.0. ODS includes OpenID? Server and client side implemented in the weblogs comments using AJAX. When posting a comment, a Web Site url is needed to be entered in order to be verified the authentication against a Server that supports OpenID?. The implementation code is located in the openid.js and openid.sql files from the ODS package.
To see how it works, perform the steps from Weblog example.
In ODS you can share your contacts, bookmarks, files and folders, calendar event and tasks. For more information see here.
In ODS you can publish your contacts, bookmarks, files and folders, calendar event and tasks. For more information see here.
Yes, ODS users can perform SPARUL over the SPARQL protocol after authentication at the http://host:port/sparql-auth endpoint. For more information you can see here.
Virtuoso supports OpenID2?. You can register ODS user using OpenID2? Url. A sample tutorial can be found here.
When querying a data space via SPARQL you need to be aware of the target data sources which take the form of information resource (web doc) URLs or internal RDF Store Graph IRIs.
In ODS, when you create an account, you end up with a personal identifier (also known as a Web ID or Personal URI).
The personal identifier is associated with an information resource that takes the form of a FOAF based profile page.
Thus, if you want to query you own data space you simply need to aim you SPARQL queries at your FOAF profile page URL which takes the form: http://
On the other hand you can also SPARQL across the entire collection of public data hosted by an ODS instance if you scope your queries to the ODS data space Graph IRI: http://
You achieve the SPARQL scope via:
With the recent support of WebID?, the ACL capabilities of the ODS instance and its SPARQL endpoint goes beyond explicit ODS membership. Thus, if someone has a URI bound to a self-certified certificate where the public key component is written to their FOAF profile page, such individuals will also have SPARQL access to shared resources via an HTTPS based SPARQL endpoint.
See more information for ODS SPARQL OAuth.
Yes. The ODS package contains OpenSocial? data APIs about people and activities. More information and sample examples you can find here.
Yes. Check out our Generate an X.509 Certificate hosted WebID Guide. Additional information and sample examples you can find here.
Yes. This feature now is offered from the Virtuoso Authentication Server UI?. More information and sample scenario you can find here.
Detailed Information and sample examples you can find here.
Find more details how to configure Virtuoso+ODS instance as an X.509 Certificate Authority and HTTPS listener.