Dear all,
I have a question about the XLE transfer system. Let me know in case I need to send this to another distribution list (parsem?)
Since I haven't followed the development for some years now, I am unsure whether some functionality may have been added or workarounds been found regarding the following aspects.
1. marking and repeatedly executing a block of transfer rules that have to be executed in sequence:
we have a set of rules A that need to be executed in sequence, repeatedly. The number of loops needed is not known and can differ (only an upper limit could be estimated).
- Can we place the block of rules A in a file that can then repeatedly called/inserted? How would we state that?
2. Controlling the number of times such a block of rules needs to be processed repeatedly. We could formulate a rule set or an external procedure that executes a test each time a rule produces a new set of facts, and checks for equality of two subsets.
Is there a way to execute such a test and if the condition is met, stop the repeated execution of the rule block?
In essence, what we would like to achieve:
- A sequence A of transfer rules that continuously rewrite the input, and that can be called repeatedly, without leaving the transfer process (I/O would be too coslty). - Each rule application in A executes a termination condition. - This termination condition either needs to be defined as an external prolog procedure (procedural attachment) or would require several rule applications in a specified order.
I am aware of the limitations of the system that make such a scenario difficult, but I wonder whether you can advise me on - what are the limits of using procedural attachments (we would need check two subsets of facts for identity) - how possibly to employ "stop" in such a scenario - how to effectivly call an identical rule set repeatedly (by listing individual calls to an externally stored rule set of specified length?) - any private knowledge of how to circumvent the difficulty
Thanks a lot for your help!
Best regards, Anette
PS: we are currently still using a release of 2010 (xle-2010-10-06), but could switch versions, of course.