<!doctype linuxdoc system>
<article>
<title>Donantonio, an architecture for automated electronic publishing (draft)
<author>Ismael Olea &nl; <url url="mailto:olea@hispalinux.es">
<Date> v0.01 1999-09-02

<abstract>
The very basic ideas for an architecture for publishing and
maintaining  all kind e-libraries using known standards as XML, RDF,
Dublin Core, etc.
</abstract>

<sect>Introduction<p> 

Please read the introducction about a global document project and the technologies involved 
see the document «Electronic libraries: documentation technology».

<descrip>
<tag/tecnologia-doc-es/ the Spanish version.
<tag/tecnologia-doc-en/ the English version.
</descrip>

<sect>Donantonio design<p>

<sect1>basic planning <p>
<itemize>
<item>based on true free software, using the GPL license or compatible if it's possible;
<item>open especifications clearly documented;
<item>based on true standards as RFC's, ISO and 3WC standards.
<item>simple, modular and flexible to become the layer for distributed applications
</itemize>

<sect1>The design goals are:<p>

<itemize>
<item>automatic publishing;
<item>distributed publishing along the Net;
<item>distributed publishing ¿responsabilidad?;
<item>automated and programmable view organization ---system and user---;
<item>mirroring facilities;
<item>automatic updating facilities;
<item>flexible relations between <bf/Donantonio/ agents.
</itemize>

<sect1>Necessary elements (some of them):<p>

<itemize>
<item>meta-data declaration conforming a normalized schema (description);
<item>the file as the atomic transfer data unit;
<item>use of internet file transfer protocols;
<item>simple and flexible query system (¿SQL?).
</itemize>

<sect>Architecture versus application.<p>

This paper is focused in architecture only. The idea is to design a set of 
conventions and rules to build a working environment to develop applied 
publishing tools.

For this cause I'll try not to say too much about the Metalab/LDP publishing
system. Indeed, the designing work for these appliances will help to refine
Donantonio to get a multi true purpose and generalized architecture.


<sect>Donantonio definitions
<p>
<sect1>Elements
<p>
<descrip>
	<tag/Resource/  file or a document located via an URL.
	<tag/Description/ a RDF file meta-data, located via an URL.
	<tag/Repository/ collection of resources or collection of  resources' instances.
	<tag/Library/ collection of descriptions or collection of descriptions' instances.
</descrip>

<sect1>Agent tasks
<p>
These tasks aren't completely defined yet.
<descrip>
	<tag/Server/software acting as a server 
	<tag/Client/software acting as a client
	<tag/Proxy/Proxy between two servers or between a server and a client
</descrip>

<sect1>Actions
<p>
These are the "atomic actions":

<descrip>
	<tag/Resource download/ the act of downloading a resource referred by
an URL via an Internet transfer protocol.
	<tag/Resource mirroring/the act of mirroring (and sincronicing) a
resource referred by an URL via an Internet transfer protocol.
	<tag/Description download/ the act of downloading a description
referred by an URL via an Internet transfer protocol.
	<tag/Description mirroring/ the act of mirroring (and sincronicing)
a description referred by an URL via an Internet transfer protocol.
	<tag/Petition/ a query on a transport layer (mime+http??).
	<tag/Answer/ of a query on a transport layer (mime+http??). It can contains a view.

</descrip>

And these are the "composed actions"
<descrip>
	<tag/Library mirroring/ TACA
	<tag/Repository mirroring/ TACA
	<tag/Distributed query/ TACA
</descrip>

<sect1>Relations
<p>
<descrip>
	<tag/Projection/ relational representation in SQL language of a RDF schema.
	<tag/Query/ SQL query to a projection.
	<tag/View/ a set of one or more description Urls.
</descrip>

<sect>The Donantonio metaphor
<p>
<sect1>The astral metaphor
<p>
An incomplete metaphor of the things Donantonio could support is the 
"astral metaphor".

If we believe to some astrologists, the physical body has an astral body 
(the soul). In some circumstances the soul can travel without its physical 
body. But soul and body are linked with a silver bow. The astral body (the
 soul) can travel to any place of the world and ever is linked to his body,
 which is still sleeping somewhere on the Earth. But if the silver bow get 
broken, the soul is not linked to its body anymore. It's the death for its 
body.

<sect1>Equivalence between Donantonio metaphor and the astral metaphor
<p>
For Donantonio thinking, documents are the body, descriptions are the astral 
bodies of its documents and are linked to it by a URL. If the link get broken
the description lost all is usefulness and the documents die forgotten in somebody
hard disk.

The principal idea is that while resources are sleeping in some place, their souls 
(meta-data descriptions) are traveling along the world, being processed and shared 
between Donantonio applications. Donantonio add the ubiquity faculty letting several 
duplicated souls for a only resource.

The soul's movememt capabilities are configured by the relations between agents. Movement
makes happen in the form of actions, performed by agents. 

<sect1>Practical consequences
<p>
<itemize>

<item>Resources had fixed publishing points (one or many) referenced
by a URL.

<item>A resource never travel across the net.

<item>A resource can be downloaded. The downloaded resource is an
instance of the resource and it hasn't bibliographic relevance.

<item>Descriptions had a one and only fixed publishing point
referenced by a URL.

<item>Descriptions instances can travel across the net to by archived
or processed. A description instance has bibliographic relevance
while they had a valid link with their master description.

<item>A repository can be a Donantonio repository while all its
resources had its description in a Donantonio application somewhere
in the net.

<item>A Donantonio library is a true library while all its
descriptions or descriptions instances are valid (they refer to their
own resources).

<item>It's too easy to replicate libraries only replicating its
descriptions files. A way to distribute load distributing server
accesses.

<item>The way for building indexing clusters or indexing servers
trees is distributing the descriptions their self between the
servers. An information petition on one of the servers (the cluster
case) or in the main server (the tree case) is distributed to the
others with a Donantonio query. Them, the systems acts as one only
server.

<item>Descriptions can be grouped into views with SQL queries and
explicit Urls.

<item>A distributed/monolithic library can be replicated with only a
query (a view) into a monolithic mirror or with several well designed
queries (several views) into a net of servers.

<item>The resources referenced by a library (or many libraries) can
be instanced locally (cached) with views and URL downloads.

</itemize>




<sect>Who's Don Antonio?
<p>

Don Antonio is the librarian of the high school were I had my
bachelor degree.

I like this name because it's different and sounds funny :-)

<sect>Bibliography
<p>
<itemize>
<item>XML
<item>DC
<item>RFC 2413 (DC)
<item>RDF
<item>Los de la clasificacion automatica.
<item>URL de LuCAS
<item>de insflug
<item>de Ofelia
<item>del borrador del libro de estilo de Insflug
<item>al glosario de LuCAS
<item> ldp-core.dtd: http://casbah.org/cgi-bin/cvsweb.cgi/XML/DTDs/ldpCoreMetaML.dtd
Creada por Kendall Clark en XML. Se supone un paso previo a la
versión RDF.

</itemize>

<sect>Change-log
<p>

v0.0, first release in English

</article>

