RE: [JemBlog-Develop] Input Templates

[Cayzer, S. <Ste...@hp...>]

What a coincidence!
I am thinking along exactly the same lines at the moment in HPs semantic
blogging project [1].

I am implementing (well, about to implement) a 'metadata edit module' that
allows a user to enter/edit metadata about an item. The idea is that the
metadata is taken from a user supplied schema - and what is more, that the
metadata edit form doesn't have to display all the schema elements, it is
configurable (per user) just like the standard MT entry form.

My idea at the moment is to store a (per user) configuration file (in RDF of
course) which specifies these preferences.
It will look something like what you suggest, except that I would be
slightly less fine grain about the display options.
For example, I might specify 'maximum expected size'  for a literal, and
also a filename which contains a controlled vocabulary to fields such as
topic. But try to leave fine grain UI configurations to the dialog builder.

Which brings me to Haystack. HP have quite close relationships with
Haystack, I have not seen it in action but have read the papers carefully.
They do *very* fine grain UI control, which is conceptually attractive but
computationally expensive (1M triples to specify a startup screen). In our
'eperson' work[2] we tried to steer a middle road, and I'd like to try the
same tack here.

One thing I'm not sure about is whether to implement the dialog builder in
perl or as a servlet. I'm tending towards the latter, partly because it
integrates better with Jena, partly because it appears that doing it in perl
will require hacking the core MT scripts (which I'm loath to do, I want this
to be easily deployable) and partly because I'm still a beginner in perl
(mind you I'm not that hot on servlets either ;-)). Opinions welcome.

Oh and one last thing. I promised Danny ages ago that I'd look at JemBlog, I
have, it looks nice though I haven't used it as such. I hope though, that my
work will contribute something to the project, in terms of ideas if not
actual code.

If anyone's interested, I'm writing some design documents and can circulate
them to the list.

Cheers

Steve

[1] http://www-uk.hpl.hp.com/people/steve_cayzer/semblog.htm
[2] http://www.hpl.hp.com/semweb/e-person.htm


-----Original Message-----
From: Ian Davis [mailto:ia...@in...]
Sent: 18 March 2003 17:24
To: jem...@li...
Subject: [JemBlog-Develop] Input Templates



One thing that annoys me about Moveable Type is that the input form is
limited to the fields that the developer thinks I'll need and has
coded support for in the back-end. With an RDF back-end it should be
possible handle all kinds of data at the front-end.

We should define Input Templates that describe the fill-in fields
required to create an instance of a particular class. The simplest
template would define the fields for an rss:Item, i.e. title,
description and link.

This could be described in RDF, e.g. (made up on the spot - no deep
thought behind this)


<rdf:RDF ...>
  <ui:Template>
    <ui:class rdf:resource="http://purl.org/rss/1.0/item" />
    <ui:title>New RSS Item</ui:title>
    <rdf:Seq>
      <rdf:li>
        <ui:Field>
          <ui:classProperty
            rdf:resource="http://purl.org/rss/1.0/title" />
          <ui:cols>40</ui:cols>
          <ui:rows>1</ui:rows>
          <ui:multiline>false</ui:multiline>
        </ui:Field>
      </rdf:li>
    </rdf:Seq>
  </ui:Template>
</rdf:RDF>

What do you think?



- Ian <ia...@in...>
"One never notices what has been done; one can only see what remains to be
done."



-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? 
You could win a Tablet PC. Get a free Tablet PC hat just for playing. 
What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en
_______________________________________________
JemBlog-Develop mailing list
Jem...@li...
https://lists.sourceforge.net/lists/listinfo/jemblog-develop