RE: Architectural Forms, separation of formatting and loose-leaf management

["Jordi Mulet" <jmulet@xxxxxxxxxx>]

>[Paul Prescod on Wed, 06 May 1998 09:22:07 -0400]


>>> It will be necessary to define property sets and grove plans for the
>>> Layout scheme and Page scheme, doesn't ? Is there any working experience
>>> on this topic ? ( PDF, Quark, FrameMaker,...)
>>
>> If anyone has defined grove plans for a layout-based language, it would
be
>> Peter Newcomb at TechnoTeacher, but he may not have got around to doing
so
>> yet. (so many grove plans, so little time)

>I'm afraid I've not yet done any _real_ work on these sorts of
>property sets, though I have studied the problem to some extent.
>Basically, it comes down to deciding what level of detail you want to
>include, and that comes down to deciding upon what applications you
>intend to use the groves for.  If you don't want to make such
>presuppositions, you can build a "complete" property set, as was done
>with SGML and HyTime, where _everything_ is included in the property
>set, and then grove plans are used to describe subsets needed for
>specific applications.

We are interested in a loose-leaf management system with the ability to cope
with the updates of the new SGML estructured information to the layout
output.
Also we must think about our legacy publications ( Quark, PageMaker) and how
to translate the basic page information to the new system.


>It seems likely that a complete property set for something like PDF
>will be extremely complex and difficult to maintain, especially if
>you're not Adobe.  However, a generic page- and/or layout- based
>property set that could work for a range of page description languages
>might be both easier to develop and ultimately more useful.

We have thought the PDF is a good format to store our Graphic/ Page Database
because it would be easy to build a Printing On Demand system without
problems in the future. We don't know if really we will need a complete
property set for PDF because probably we also will need to locate each SGML
original element within the correct page.
We don't want an automatic loose-leaf pagination system. The layout updates
and customizations surely will be realized by a typesetting person  ( Quark,
Frame,....) but we want to control the updates in the final layout and pages
to simplify the layout process.

How would be a approximated cost of GroveMinder and property sets for PDF
and layout schemes ? We would need 50 sites licenses and one
developer/customization license.
When will be available a stable subset of this library to evaluate its
functionality and how much would be its cost ?

Best regards,

Jordi Mulet



 DSSSList info and archive:  http://www.mulberrytech.com/dsssl/dssslist