Re: [Hypercontent-developer] HyperContent 2.0 status

[Jack P. <jac...@gm...>]

Thanks, Alex.

My thinking is that I have a need that goes beyond uPortal, so I
thought I'd start with standalone HyperContent, meaning 2.0.

I suppose there is some benefit, however, in starting with 1.4

I'll look at it. Particularly, I'll try to come up to speed on the
editors you mention. I suspect, however, that there are some
requirements for a topic map engine, quite possibly TM4J, though TM4J
would need to be integrated with the backside used in HyperContent. I
have a few ideas of my own on knowledge datastores, and will need to
think all this through in the context of HyperContent.

Thanks
Jack

On Thu, 2 Sep 2004 13:31:23 -0400, Alex Vigdor <av...@co...> wrote:
> Jack,
>         Depending exactly what you intend to do, I might recommend
> implementing it in HyperContent 1.4.  Are you specifically interested
> in generating a topic map for a web site to be managed in HyperContent?
>   If so, you could accomplish that in the current release and fairly
> painlessly migrate it into 2.0 down the road.  HyperContent supports
> RDF metadata; you could implement topics in the Dublin Core Subject
> field (no Java coding required), or you could develop a small editor to
> manage a custom topic metadata grammar (some Java coding required, to a
> well defined API which will unfortunately be changing a bit in v2).
> Producing the topical map could then be implemented as a combination of
> XML includes and XSL processing to group related materials together.
> HyperContent's design allows you to implement quite complex, custom web
> site features with little to no Java coding, once you grok the power of
> XML includes combined with XSLT.  The XML Includes allow you to pull
> all data and/or metadata out of your repository into a single XML
> document for XSL processing.
> 
> Alex
> 
> 
> 
> On Sep 2, 2004, at 1:10 PM, Jack Park wrote:
> 
> > Thanks Alex.
> >
> > I plan to look at the code in terms of adding a topic map as a
> > navigational system to the architecture. It's pretty clear I'll need
> > to ask a few questions along the way.
> >
> > The first one is: how soon a build.xml?
> >
> > Many thanks.
> > Jack
> >