ZZ/OSS Wiki - Distributed Digital Object

The DistributedDigitalObject (DDO) approach is a generic framework based on a URI composed of a addressing scheme (something like the IP address of digital resources) and the resource identifier. It is not bound to a specific application (e.g. Conesys), instead it could be useful in many circumstances.

The general DDO syntax is:

ddo:[network_ID].[website_ID].[repository_ID]/[resource_ID]

For example: The "examples network" comprises several websites of companies, organisations, etc. Let's give the example network the ID "1" and start building our DDO:

ddo:1

We go on and identify a resource published on the example.com Web site. This Web site is being assigned the ID "3":

ddo:1.3

The resource we identify is published in a repository with the ID "5" which is a collection of online tutorials:

ddo:1.3.5

A specific tutorial itself might have the ID "34":

ddo:1.3.5/34

A DDO leaves it up to you, what you do with the ressource identifier part. You could create a DDO along the lines of:

ddo:1.3.5/http://www.example.com/index.html

The first part holds the DDO routing information ("1.3.5") to resolve the actual location of the object, the second part identifies the resource ("http://www.example.com/index.html"), which is a URL in this case. Now that you use a DDO to identify a URL, you can move around the content of index.html within a content network.

To make the peer-to-peer content syndication work, each website that participates in one or several content networks, must have the relevant look-up lists available to resolve the DDO addressing part. This means, resolving the network ID, community aka Web site ID, and repository ID to a physical location, i.e. a URL.

As you can imagine, Conesys does not only have to know where to find the digital object, but also how to connect to the repository that stores the resource. Therefore, the repositories repository (which is a collection of data about repositories) provides connector parameters for each remote and local repository.

The DDO approach does not rely on a certain protocol, instead, it is a generic framework for identification and distribution of digital objects. In Conesys, we implemented a ConesysConnector system that wraps several protocols/APIs (like PEAR::DB, PEAR::SOAP, ...). Of course, the actual implementation is up to the concrete application and not bound to the way how Conesys implements DDOs. Nevertheless, Conesys serves as the reference implementation of DDOs

-- SandroZic

PHP Warnings

lib/WikiUser.php:50: Notice[8]: Only variables should be assigned by reference

lib/pear/DB/common.php:741: Notice[8]: Only variable references should be returned by reference

lib/Template.php:220: Notice[8]: Only variables should be assigned by reference

lib/Template.php:106: Notice[8]: Only variables should be assigned by reference

lib/Template.php:107: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'body'?)(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'body'?)(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'top'?)(In template 'body'?)(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'top'?)(In template 'body'?)(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

lib/pear/DB/common.php(In template 'navbar'?)(In template 'top'?)(In template 'body'?)(In template 'html'?):741: Notice[8]: Only variable references should be returned by reference

lib/Template.php(In template 'body'?)(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'body'?)(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'browse'?)(In template 'body'?)(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'browse'?)(In template 'body'?)(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'actionbar'?)(In template 'browse'?)(In template 'body'?)(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'actionbar'?)(In template 'browse'?)(In template 'body'?)(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'body'?)(In template 'html'?):106: Notice[8]: Only variables should be assigned by reference

lib/Template.php(In template 'body'?)(In template 'html'?):107: Notice[8]: Only variables should be assigned by reference

Page Execution took 0.113 seconds