The following is an extract from a thread at msnusers.com/biztalkservers... Charles Young explains with great clarity the subtle differences in the rules engine parsing of facts expressed using XPath Selector and XPath Field combinations (or “facts” and “slots”); This causes so much confusion. The rules engine works by asserting 'facts' into its working memory. A 'fact' is some object, and therefore contains fields, commonly called 'slots' in the world of rule engines. The ......
The more I work with the Rules API the more I'm convinced that the Vocabulary element was only created for the BRC. The most generous I can be is that someone came up with a good idea for the BRC and "retrofitted" it for the API. There are two reasons for this; The API is unsupported and undocumented. The BRL (Business Rules Language) can function happily without it - in fact a rule can reference directly the document element / .NET method etc. If you take a look at the following two bites from the ......
Has anybody seen a Vocabulary API for the rule engine? No? That's probably because it seems to either be on its way out or never made it in the first place. According to the BizTalk SDK "The following objects are exposed by Microsoft(r) BizTalk(r) Server 2004, but are not used in BizTalk Server programming." These include the following from the Microsoft.RuleEngine Namespace Vocabulary VocabularyDefinition VocabularyDefinitionDictionary VocabularyDictionary VocabularyInfo VocabularyInfoCollection ......