[JemBlog-Develop] flurry

[Danny A. <dan...@vi...>]

Sorry, I should have said - there isn't much difference between what I put
in the CVS and the zip of a few weeks back, I think the only real change was
to swap 'name' for 'key' in the FeatureSet vocabulary.

Also sorry about missing the last load of posts, some quick thoughts :

re. Synchronizing CVS  -  as the JemBlog stuff was in my main tree, I've got
an Ant script to copy the source to another directory before doing a
separate build, for the initial cvs import I've used a copy from there. I
should use the sourceforge cvs as the main repository for this stuff, so
I'll probably just remove it from the local server completely, though I'll
definitely have to look at CVSup first (thanks).

re. Input Templates - yes! great idea. Leigh mentions XForms + RDF - that
sounds very like the XUL stuff. One thing that's high on my to-do list for
Ideagraph is a general-purpose Swing form for RDF, where all you might know
is that e.g. it's a literal or resource (I guess Leigh has been exactly
there with the FOAF-a-matic). I suppose we need to be able to make an
appropriate form whether we're looking through a browser or local
app...D'oh! I missed Steve's later post - I'd better have a think & read the
doc at HP.

re. Haystack - that project's been around without a release for as long as I
can remember, though they do now have screenshots so I guess they must be
progressing. I still wouldn't gamble too much on it being released before
Chandler ;-)

re. Jemblog feedback - ('canned' methods to access DC properties), couple of
specifics: "Where do you stop?" - I'd say at the edge of what people are
commonly using in RSS feeds. "Isn't it better to use a more generic method:
eg getPropertyValues(name)?" - this nicely highlights one of what I see as
the justifications for JemBlog. I think the canned methods remove any doubt
someone who is unfamiliar with RDF (but maybe has used RSS) might feel. Jena
already has the generic methods, but anyone that has only been using e.g.
rsslibj is in for a shock when they see the Jena API. Another minor point is
that it should make it easier to enforce some of the RSS rules for
mandatory/one-only elements.

Cheers,
Danny.


----

http://dannyayers.com