Service Call Flow

UI to Server

1. The user configures the Find Connections dialog in the graphmart editor (FindGraphmartConnections component).
2. On save, the UI calls graphmartService.findLinks(requestData, { progress: true }).
3. The findLinks function serializes the parameters into an RDF request graph and invokes the semantic service at:

``` http://cambridgesemantics.com/services/GraphConnectionMagicService#findLinks ```

5. The server-side GraphConnectionMagicService.findLinks() method deserializes the request and delegates to findConnections().

Server Processing

1. findConnections() opens a transaction, validates the graphmart, and sets up progress tracking.

2. A GraphConnectionsFinder subclass is instantiated by ConnectionFinderFactory based on the strategyType:

• Exact Match → ExactMatchConnectionFinder

• Fuzzy Match"` → FuzzyConnectionFinder

• Regex Match"` → RegexConnectionsFinder

4. processReductionStrategies() runs the discovery phase — collecting classes, properties, existing links, and ontology mappings.

5. processLinkedClassPairs() creates the pivot layer, iterates class pairs, finds the best match for each, creates the link ontology and transform steps, and generates the response.

6. The pivot layer is cleaned up and the graphmart is refreshed.