Re: FM+SGML Enhancement Request No. 3

[Marcus Carr <mrc@xxxxxxxxxxxxxx>]

Dan Emory wrote:

> ENHANCING THE POWER OF READ/WRITE RULES
> THE PROBLEM: In the existing read/write rules, there are no mechanisms for
> evaluating the context of an element, or the value of an element attribute,
> and then specifying the import or export action to be taken based on the
> evaluation outcome.
>
> THE PROPOSED SOLUTION: The addition to the read/write rules of a conditional
> processing construct, combined with the ability to declare and set
> semi-persistent read/write rules variables, would aliminate most of the
> problems that must now be resolved by developing expensive (and difficult to
> modify) import/export API clients using the FDK.

I'm not sure that moving functionality from the FDK to the read/write rules is going
to result in a net simplification - in some cases, I'm fairly sure that the opposite
would be true. I see the read/write rules as being somewhat the domain of the
"technical user", but the FDK as being well and truly "programmer/developer"
territory. Why do you feel that this is unsatisfactory?


--
Regards,

Marcus Carr                      email:  mrc@allette.com.au
___________________________________________________________________
Allette Systems (Australia)      www:    http://www.allette.com.au
___________________________________________________________________
"Everything should be made as simple as possible, but not simpler."
       - Einstein



** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **