Announce: RDF::RDFa::Template 0.04

[Kjetil Kjernsmo]

Hi again!

I've been working for a long time on a simple templating language for RDFa. 
I started to outline the ideas last year at
http://www.kjetil.kjernsmo.net/software/rat/

It was a bit of discussion in various places, but I decided to code rather 
than talk to come up with a simple implementation to illustrate some of the 
ideas. So now, I have just uploaded file

    RDF-RDFa-Template-0.04.tar.gz

which has entered CPAN as

  file: $CPAN/authors/id/K/KJ/KJETILK/RDF-RDFa-Template-0.04.tar.gz
  size: 30300 bytes
   md5: 76f2f5c340230f36936ed77d856f35fa

This is an early alpha, and it is limited in functionality compared to the 
above vision. Please see the short-term TODO-list below. I'm just going to 
work on this if there is actual interest for it though. :-)

You can take it for a spin: In the examples/ directory in the distribution, 
there is a script called  demoserver.pl and if you run this, it will set up 
a very simple HTTP server that can process and serve files from the 
directory it is in. Thus, if you run this server and go to 
http://localhost:8080/dbpedia-mustang-range.input.xhtml
you will see it actually querying DBPedia to find the range of the Cessna 
Citation Mustang very light jet. :-) Contributions of more examples would 
be appreciated. 

The next step now is to document how non-Perlers would install this module 
and run this script by just using cpanmin.us. Once I have that working, I 
will announce it to the RDFa community.

Now, time to have a look at the TODO-list:

* Support for queries with multiple solutions is essential, but not yet 
implemented.
* Multiple queries in a single template is not tested.
* Prefixes are hardcoded. In the finished system, the XML namespace 
prefixes must not be hardcoded, but namespace URIs must be used instead. 
This is not there yet. Thus, you need to use rat and sub like in the 
examples.
* The attribute that sets the graph name is hardcoded to g:graph or 
{http://example.org/graph#}graph. This will be up to the author to select 
and pass as doc_graph for each unit. Thus, this must change.
* The RDF objects are checked for variables, which is contained in XML 
Literals. Only the first child is used, this may not be reliable.
* DTD information is not prefixed to the result document.
* The system doesn't follow OOP best practices in many places, as instance 
variables are accessed directly rather than using methods. Pretty nasty, it 
is, but it will be corrected.
* Consider using just one namespace.

Cheers,

Kjetil
-- 
Kjetil Kjernsmo
kjetil at kjernsmo.net
http://www.kjetil.kjernsmo.net/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.perlrdf.org/pipermail/dev/attachments/20100406/9a668857/attachment.pgp>