rdfapi-php-interest

[Rdfapi-php-interest] Integration of the RAP database schema in our wiki engine (WikiNi)

[Charles N. <cha...@ne...>]

Hi,

We would like to add triples to our wiki engine, to extend the data=20
model without extending the SQL model. Thus, external developpers, for=20
example, would be able to write plug-ins without modifying the SQL model.

I looked for a database schema to store the triples and found RAP=20
schema. If I understand, it seems to be good for us, except :
-- the "namespace" table : which seem to be no use for us
-- the "model" table : idem
-- and of course, the "modelID" field in the "statements" table

If we would use RAP schema, we could also use some of tools : to=20
import/export datas, for example.

I would like to know what are the consequencies to drop "namespace" and=20
"model" tables : for RAP use ? for our wiki engine ? I am not sure to=20
understand quite well the notion of "model"... I guess RAP tools won't=20
work whithout it but I didn't understand why this notion is useful for RA=
P.

I will pay attention to all remarks or ideas about adding a triplestore=20
in a wiki in general.
(see, in franch,=20
http://www.wikini.net/wakka.php?wiki=3DDiscussionsModeleDeDonneesEvolutif=
 )

Regards,
Charles N=E9pote
http://www.wikini.net/

[Rdfapi-php-interest] Integration of the RAP database schema in our wiki engine (WikiNi)

[Chris B. <bi...@gm...>]

Hi Charles,

your ideas of extending your wiki with a triple store sounds very =
similar to
a paper Gregory Todd Williams has submitted to our SFSW workshop. The =
paper
is currently under reviewing, so I can't send it to you, but maybe =
Gregory
will send it to you directly if you ask him.

Abstract of the paper:

MT-Redland: An RDF Storage Backend for
Movable Type
Gregory Todd Williams
gr...@ev...
Abstract. Existing content management systems and weblogging tools
are based on rigid database designs that suffer from a lack of =
flexibility
in
the face of an ever increasing need for new types of structured data and
metadata. By modifying these systems to use RDF as the native storage
format, they may be easily extended in ways unimagined by the original
designers. I present just such a system, a combination of the Movable
Type weblogging tool and the Redland RDF Application Framework,
showing examples of how the system can more easily adapt to diverse
semantic annotation needs.


Comments on the RAP db schema:

The namespace table is used for being able to serialize RDF models with =
the
same namespace prefixes as used by the original models having been read =
in.

The model table is used to store the base uris of the different models =
(if I
remember right, Radek?).

We will definitfly keep both in RAP, but maybe you don't want to use =
them in
your application. More information about relational schema for storing =
RDF
data is found in:

http://www.w3.org/2001/sw/Europe/reports/scalable_rdbms_mapping_report/ =
and
http://www.w3.org/2001/sw/Europe/events/20031113-storage/

I really like the idea of extending existing systems with RDF =
capabilities.
Please keep us informed on how your efforts are developing.

Chris


--=20
Chris Bizer
Freie Universit=E4t Berlin
Phone: +49 30 838 54057
Mail: ch...@bi...
Web: www.bizer.de

-----Urspr=FCngliche Nachricht-----
Von: rdf...@li...
[mailto:rdf...@li...] Im Auftrag von
Charles Nepote
Gesendet: Dienstag, 26. April 2005 00:48
An: rdf...@li...
Betreff: [Rdfapi-php-interest] Integration of the RAP database schema in =
our
wiki engine (WikiNi)

Hi,

We would like to add triples to our wiki engine, to extend the data=20
model without extending the SQL model. Thus, external developpers, for=20
example, would be able to write plug-ins without modifying the SQL =
model.

I looked for a database schema to store the triples and found RAP=20
schema. If I understand, it seems to be good for us, except :
-- the "namespace" table : which seem to be no use for us
-- the "model" table : idem
-- and of course, the "modelID" field in the "statements" table

If we would use RAP schema, we could also use some of tools : to=20
import/export datas, for example.

I would like to know what are the consequencies to drop "namespace" and=20
"model" tables : for RAP use ? for our wiki engine ? I am not sure to=20
understand quite well the notion of "model"... I guess RAP tools won't=20
work whithout it but I didn't understand why this notion is useful for =
RAP.

I will pay attention to all remarks or ideas about adding a triplestore=20
in a wiki in general.
(see, in franch,=20
http://www.wikini.net/wakka.php?wiki=3DDiscussionsModeleDeDonneesEvolutif=
 )

Regards,
Charles N=E9pote
http://www.wikini.net/



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=3Dick
_______________________________________________
Rdfapi-php-interest mailing list
Rdf...@li...
https://lists.sourceforge.net/lists/listinfo/rdfapi-php-interest

Re: [Rdfapi-php-interest] Integration of the RAP database schema in our wiki engine (WikiNi)

[Gunnar A. G. <ggr...@cs...>]

The model table (paradigm?) allows you to have seperate collections of=20
triples. For instance, if you had multiple wikis on the same server, or=20
if different plugins wanted separate "storage" areas. You can think of=20
it as another layer of division below mysql (or whatever) databases=20
(mysql, test, etc).

I've not written any of the RAP Db stuff, but I doubt it will work=20
without the models/namespace table.

Could you not keep the tables, and if you really have no use for models=20
just make sure all your triples are in the same model? You migth find=20
that models are very helpful when you come to designing/implementing=20
stuff with this.

AND if you keep them you get the added bonus of being able to export all=20
your data as RDF! :)

There is a database admin tool included with the RAP download, this can=20
be used to inspect/edit/export/import etc.

Have fun!

- Gunnar

Charles Nepote wrote:
> Hi,
>=20
> We would like to add triples to our wiki engine, to extend the data=20
> model without extending the SQL model. Thus, external developpers, for=20
> example, would be able to write plug-ins without modifying the SQL mode=
l.
>=20
> I looked for a database schema to store the triples and found RAP=20
> schema. If I understand, it seems to be good for us, except :
> -- the "namespace" table : which seem to be no use for us
> -- the "model" table : idem
> -- and of course, the "modelID" field in the "statements" table
>=20
> If we would use RAP schema, we could also use some of tools : to=20
> import/export datas, for example.
>=20
> I would like to know what are the consequencies to drop "namespace" and=
=20
> "model" tables : for RAP use ? for our wiki engine ? I am not sure to=20
> understand quite well the notion of "model"... I guess RAP tools won't=20
> work whithout it but I didn't understand why this notion is useful for =
RAP.
>=20
> I will pay attention to all remarks or ideas about adding a triplestore=
=20
> in a wiki in general.
> (see, in franch,=20
> http://www.wikini.net/wakka.php?wiki=3DDiscussionsModeleDeDonneesEvolut=
if )
>=20
> Regards,
> Charles N=E9pote
> http://www.wikini.net/
>=20
>=20
>=20
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_ide95&alloc_id=14396&op=CCk
> _______________________________________________
> Rdfapi-php-interest mailing list
> Rdf...@li...
> https://lists.sourceforge.net/lists/listinfo/rdfapi-php-interest

--=20
Gunnar AAstrand Grimnes
-----------------------
Room 312, Computing Science Dept.
University of Aberdeen
Aberdeen
AB24 3UE

Mobile: (+44) (0) 7950 251379

Email: ggr...@cs...
WWW: http://www.csd.abdn.ac.uk/~ggrimnes