Back to Basics 6 – Always Check your Parse

This is of course connected to the previous remarks about constructing phrases with booleans or non-booleans. But I would like to take a moment to go a little further and remind those of you starting out of the importance of the parsing process. In some ways, the old Version 10 user experience, where the parsing engine results were popped up in Word directly, when you validated / compiled your work, was easier to explain. It oriented users towards the idea of checking the parse straight away:

opa-10-select-parse

In the above example, everything is fine. But the process was useful when the writer had failed to be clear in their ideas, because at least then the Select Parse window showed there might be a bit of a problem right after we clicked the button:

opa-10-select-parse-double-list

So in the case above, we can see that there are two verbs in our made-up phrase, and the parser has flagged that to us. In Version 12, the validation process no longer shows the dialog above – te process is largely silent and transparent. I can see this as a benefit in terms of experience but it takes away the immediate sense of checking the text and parse. To get the same sort of information you have to go into the Attribute list in the Data tab, double-click the Attribute and then click the Change button shown below:

opa-12-edit-attribute-parses

I just think that it could be a little easier for users to find. But I’m just a slow learner. I would however say that this deserves to be in our top ten of back to basics items, since checking the parse and verifying the coherence of the generated text is something to get used to very early on. And it is valid for any language that is supported by Oracle Policy Modeler.

A quick thank you

While I am writing this, I want to thank all our readers and happily report that we have just gone past the 100 post mark. Here’s to the next 100!

Until the next time, take care!