[RDF] Re: RDF

[Jonas Liljegren]

Ok. Here is some comments on your points.

I have already taken this into consideration while I wrote
http://www.uxn.nu/wraf/


On Tue, 8 Aug 2000, Stefan Andersson wrote:

> Web Resource Application Framework (WRAF) key features:
>=20
> WRAF is primarily designed as a platform for:
> =B7 Data-driven web applications with complex class hierarchies and
> inter-resource relations, such as metadata repositories, topic
> communities and intranets.

Resource is an RDF term.  I would say inter-object relations.

The list of intended uses is a important point for the presentation of
Wraf, and shoud be expanded upon.

 - Metadata repositories  (examples?)

 - Topic communities  (what is that exactly?)

 - Intranets  (examples?)

We should compile a list of possible uses.  I add this task at SF (under
Documentation tasks).


> =B7 Applications collecting, processing and presenting information from
> many sources, distributed over many processes.

Or distrebuted over many domains from diffrent organizations.

> =B7 Intelligent agents and robots.

How intelligent? ;)


> =B7 Dynamic content, where the content selection and presentation is a
> result of complex dependencies.

Yes. Examples would be good.


> WRAF offers=20
> =B7 an consistent interface to and between multiple information sources
> =B7 the possibility of rich data and metadata modeling through inheritanc=
e
> =B7 an open, standardized and extensible way of describing and exchanging
> resources, inter- as well as intraorganizational.

The resource exchange is going to take much work.  The goal is that the
process will be cumulative. That is: that it will be possible to extend
and grow the system without the old definitions becomming a burden.  That
is at least my vision.

> =B7 a framework for RAD (Rapid Application Development) and realtime
> system extension through schema remodeling.

Yes.


> WRAF is built upon

Here we go...

> =B7 RDF, an open W3C (WWW Consortium) standard for distributed resource
> modelling through DLG (Directed Labeled Graphs).

Ok.

> =B7 RDF-Schema, the W3C standard for schema modelling under RDF

RDF-Schema is a candidate recommendation. This means that there is still
time for the W3C members to comment on this thing. W3C wan't to see a few
real implementations in order to be satisfied with RDFS.


> =B7 RDF-XML, the W3C standard for expressing RDF data in XML.

This is called the RDF Syntax.


> =B7 RDF QDS, an query definition schema modelled in RDF.

This is post 1.0


> =B7 RDF SDS - The Serialisation Definition Schema is used to describe
> transformations between a RDF DLG and serialized formats, such as
> RDF-XML, native XML, [X]HTML, WML, et.c.

Ok.  I wonder if maby its best to have some sort of template system in
combination with SDS? You still want to do some form of layout.

Should we realy go for a system like SmartWorks?


> =B7 WRAF XML SDS - A base SDS for expressing RDF as XML
> =B7 WRAF [X]HTML SDS - A base SDS for expressing RDF resources as [X]HTML

This is also two diffrent contexts. Either you wan't to transfer the
requested information (XML) or you wan't to present the information.  For
information presentation, there will be a lot of supporting style and
markers and things.

I would like to see some more details on this.

In any case. SDS is post 1.0


> =B7 RDF DB - An interface for storing and retrieving RDF DLG in relationa=
l
> databases

It's currently named org.cpan.RDF.Interface.DBI.V01 :-)  I was trying to
think of some global way of naming CPAN modules. Come to think of
Java. :-I  The name (resource URI) will of course change.


> =B7 WRAF API - The core functionality, exposing RDF models and interfaces=
=2E

Ok.

> WRAF IE - The Inference Engine enables applications that do not share
> data definitions to identify and bridge RDF Schema incompatibilities.

That's new.   - I'm planning for alias functionality.  In addition to
thet: We will have som rule set that can create new statements based on
other statements. And the new statements will be dependent on the
old. (Publish subscribe..)

But that will come later. (After 1.0)


> Currently, all functionality is implemented as an UNIX service deamon
> with a cgi/mod_perl client.

It will be. :)  We prototype worked that way. But there is no reason to
start using the deamon before the cache functionality is in place.

(Ok. This points was about describing Wraf.  I just takeing the
opportunity to talk about the development.)


> The RDF, RDF-XML and RDF-Schema are open W3C standards. The RDF DB, WRAF
> API and WRAF IE are open source as per GNU Public License, and will be
> given to CPAN upon completion. The RDF QDS and SDS will be submitted as
> standards proposals upon completion.

Isn't this a little ambitious?

If can find financial support, I bet that Meta Matrix would like to help
out here.


--=20
/ Jonas  -  http://jonas.liljegren.org/myself/en/index.html