OSDE
The OpenLink Structured Data Editor
OSDE, the OpenLink Structured Data Editor, is a tool for creating and editing structured data using RDF Language statements/triples, through many web browsers.
OSDE enables creation and editing of data using abstract subject → predicate → object or entity → attribute → value notation.
OSDE currently ingests RDF from documents serialized as RDF-Turtle, JSON-LD, and RDF/XML.
Once constructed or edited, data can be saved to local or remote storage, or directly copied, as RDF-Turtle documents.
Full RDF-Turtle document access requires that HTTP-accessible host servers support at least one of the following open standards —
Data stored as RDF-Turtle documents can be further transformed to other formats (JSON-LD, CSV, OData, Microdata, RDF/XML, RDF/JSON, etc.) using a variety of transformation tools and services.
Note: Safari 9.1.2 and earlier have an issue with memory consumption; this is resolved by updating to Safari Technology Preview, Release 10, of 2016-08-03 (requires OS X 10.11.4 or later).
The World Wide Web (or simply, the Web) was originally conceived as a Read-and-Write medium, but even now, with user-created content filling many web surfers' screens, most usage remains Read-Only.
OSDE bolsters the growing Write dimension by letting users create structured data using the familiar File Create → Save → Share pattern, without forcing a document storage location, i.e., documents created with OSDE may be stored to the desktop or to virtually anywhere in the cloud.
en
” in
the lang
field, when prompted.)Metaphorically, as in the real-word —
Somewhat more elaborately —
You can get started by creating a brand new document or applying edits to an existing document.
Start OSDE with a New Document.
From the Action menu, select Input Turtle Directly. Paste or type your Turtle, and click Import.
Inspect and/or edit the imported data in Statements view.
Inspect and/or edit the imported data in Entities (Subjects) view.
Inspect and/or edit the imported data in Attributes (Predicates) view.
Inspect and/or edit the imported data in Values (Objects) view.
Here are a couple of silent screencasts showing OSDE in action, through loose coupling to the OpenLink Structured Data Sniffer (OSDS), which exposes OSDE as its Annotation feature.
OpenLink RDF Editor Demo -- Open Data Flow
OSDS & OSDE Integration Demo — Beyond Bookmarking Annotation Feature
If you don't have an existing OSDE instance, deployment takes just a few simple steps, which vary with your HTTP server.
rdf_editor_dav.vad
).rdf_editor_pkg.zip
).unzip rdf_editor_pkg.zip -d [PATH]
/rdf-edtor
) with RDF Editor to the server configuration.[APACHE HOME]/bin/httpd
http://localhost:[port]/rdf-editor/index.html
unzip rdf_editor_pkg.zip -d [IIS Root Path]
http://localhost:[port]/rdf-editor/index.html
node.js http-server
(a simple, zero-configuration
command-line http server) globally, so that it may be run from the command line:
npm install http-server -g
unzip rdf_editor_pkg.zip -d [RDF Editor Path]
http-server [RDF Editor Path]/rdf-editor [options]
http://localhost:[port]/index.html
[TOMCAT HOME]/bin/startup
unzip rdf_editor_pkg.zip -d [TOMCAT HOME]/webapps/Root
http://localhost:[port]/rdf-editor/index.html
rdf_editor_dav.vad
.
rdf_editor_dav.vad
package for your version of
Virtuoso from our
repository.cname
is the
{hostname}:{port-number}
at which your Virtuoso instance is listening.
http://{cname}/rdf-editor/index.html
http://{cname}/rdf-editor/index.html
, and expose the physical location you chose
for the extraction.You can use an XHR-oriented parameterized URL to load the Editor with a number of UI choices already made. Several examples follow the parameter details, all based on the URI Template —
http://{cname}/rdf-editor/#/editor(?uri,ioType,saveDocument,newDocument,view,newStatement,statement:subject,
statement:predicate,statement:object)
newDocument
—
Drops current OSDE content before next action. Optional values:
true
or false
.
uri
—
URL encoded
URI of the resource to be opened by OSDE.
view
—
The editor view is identified by one of the following values:
statements
or triples
—
The default view.
Always valid.
entities
or subjects
—
The default view when statement:subject
is set.
Invalid when statement:predicate
or statement:object
is set.
attributes
or predicates
—
The default view when statement:predicate
is set.
Invalid when statement:subject
or statement:object
is set.
values
or objects
—
The default view when statement:object
is set.
Invalid when statement:subject
or statement:predicate
is set.
newStatement
—
The editor will be opened in 'new statement' state.
statement:subject
—
URL encoded
URI value to be initially used as the subject of new statements. If the view parameter
is omitted, the editor is opened in Subjects view. When this parameter is used,
the enabled values for the view parameter are statements
and
subjects
.
statement:predicate
—
URL encoded
URI value to be initially used as the predicate of new statements. If the view parameter
is omitted, the editor is opened in Predicates view. When this parameter is used,
the enabled values for the view parameter are statements
and
predicates
.
statement:object
—
URL encoded
URI value to be initially used as the object of new statements. If the view parameter
is omitted, the editor is opened in Objects view. When this parameter is used,
the enabled values for the view parameter are statements
and
objects
.
uri
—
URL encoded
URI of the resource to be written by OSDE.
ioType
—
Protocol to use to access the target resource. Optional values:
webdav
—
The document will be accessed using WebDAV protocol ldp
—
The document will be accessed using LDP protocol sparql
—
The document will be accessed using SPARQL protocol http
—
The document will be accessed using HTTP protocol sparqlEndpoint
—
URL encoded
URI that identifies SPARQL endpoint to be used when source document content is identified
by a SPARQL CONSTRUCT
or DESCRIBE
query results URL
saveDocument
—
Save current content to document identified by the Document URI. Optional values:
true
or false
Place Editor in 'New Document' state with current Entity identified by
<http://dbpedia.org/resource/DBpedia>
as the Entity of the initial EAV Statement, using 'Statements' view —
Place Editor in 'New Document' state with current Entity identified by
<http://dbpedia.org/resource/DBpedia>
as the Entity of the initial EAV Statement, using 'Entities' view —
Place Editor in 'New Document' state with current Entity identified by
<http://www.w3.org/1999/02/22-rdf-syntax-ns#type>
as the Attribute of the initial EAV Statement, using 'Attributes' view —
Place Editor in 'New Document' state with current Value identified by
"Initial Value"
as the Value of the initial EAV Statement, using 'Values' view —
Opens up the Description of <https://dbpedia.org/resource/DBpedia>
in the Editor, using the default EAV 'Statements' view —
Opens up the Description of <https://dbpedia.org/resource/DBpedia>
in the Editor, using the default EAV 'Statements' view —
Opens up <https://dbpedia.org/ontology/Company>
in the Editor, using the default Statements view —
http://linkeddata.uriburner.com/rdf-editor/#/editor?uri=http:%2F%2Fdbpedia.org%2Fontology%2FCompany
Opens up <https://s3.amazonaws.com/webid-sandbox/Profile/Basic-Identity-Claims-And-Profile-Document.ttl>
in the Editor, using Statements view, with
<http://dbpedia.org/resource/DBpedia>
set as the Entity of an additional Statement —
This somewhat cryptic error message results from a complex set of web browser and web server behaviors and design choices. If you encounter a message like this, please see our detailed discussion of Cross-Origin Resource Sharing (CORS) Errors.