Name Parse Ambiguity
We explore how Business Validation PDPs improve business information through the implementation of the OriginalInput rule in scenarios where parse ambiguities or exceptions arise.
Parse Ambiguity
When the input such as "The trustee for Richard Patrick," is tokenized by the parser into separate entities like "The" and "Richard Patrick," there's a risk that the input might erroneously use trust name "Richard Patrick" for business validation. However, "The trustee for Richard Patrick" stands as an independent entity. In such cases Business Validation PDPs mitigates these parse ambiguities by utilizing the "OriginalInput" match rule.
Sample Business Data in HELLO_BUSINESS_INDEX
Company1: The trustee for Richard Patrick Eisele
bn: 78485861784
Company2: Richard Patrick
bn: 23897996450
{
"ciqPartyRelationshipDocument": {
"options": {
"originalInput": "The trustee for RICHARD PATRICK",
"exposeAttributes": "7"
},
"parties": [
{
"pdpchangeContext": {},
"companyName": {
"companyName": "The",
"personalName": false,
"organisationalName": true,
"nameQuality": 3
},
"relationshipLabel": "organisation1",
"customAttributes": {
"business_name": "The Trustee for Richard Patrick Eisele",
"business_tax_status_from_date": "19000101",
"business_display_name": "The Trustee for Richard Patrick Eisele",
"business_ver_code": "OriginalInput_1_0.125",
"business_name_entity_type": "MN",
"business_bn": "78485861784",
"business_entity_type_ind": "DES",
"business_postcode": "7330",
"business_bn_status_from_date": "20200112",
"business_entity_type_text": "Deceased Estate",
"business_country": "au",
"business_month_in_business": "48",
"business_last_updated_date": "20200203",
"business_bn_status": "ACT",
"business_tax_status": "NON",
"business_state": "TAS"
},
"containedInParties": true,
"locationInParties": 1
},
{
"pdpchangeContext": {},
"relationshipLabel": "person1",
"personName": {
"fullName": "RICHARD PATRICK",
"personalName": true,
"firstName": "RICHARD",
"lastName": "PATRICK",
"organisationalName": false,
"nameQuality": 4
},
"containedInParties": true,
"locationInParties": 2
}
],
"numberOfParties": 2
},
"relationships": [
{
"from": "organisation1",
"to": "person1",
"title": "trust",
"arcrole": "http://www.msi.com.au/relationships/trust"
}
]
}Parse Exception
There are numerous cases where alphanumeric business names, trading names, or other names lack identifiable company terms like (PTY LTD etc.) leading to parsing failures.
In such cases , there is a configuration that can be tweaked through $HARMONY_HOME/config/harmony_scrubbing_descriptor.xml to surpass the parse failure and feed original input as is to Business Validation PDP.
Default configuration is false
<h:passthrough-name-on-parse-failure>false</h:passthrough-name-on-parse-failure>
Response using the default passthrough-name-on-parse-failure as false.
Response after the passthrough-name-on-parse-failure is set to true.
Last updated