Similar to FileAnalysisResponseMessageJson but using n-quads as serialization format.

interface FileAnalysisResponseMessageNQuads {
    cfg?: string;
    format: "n-quads";
    id: undefined | string;
    results: {
        dataflow: string;
        normalize: string;
        parse: string;
    };
    type: "response-file-analysis";
}

Hierarchy (view full)

Hierarchy-Diagram

UML class diagram of FileAnalysisResponseMessageNQuads

Properties

cfg?: string

FileAnalysisResponseMessageJson#cfg

format: "n-quads"
id: undefined | string

The id that links a request with its responses, it is up to the calling client to make sure it is unique. However, the client does not have to pass the id if it does not need to link the request with its response. The id is always undefined if the message is unprompted (e.g., with hello) or the id unknown.

results: {
    dataflow: string;
    normalize: string;
    parse: string;
}

FileAnalysisResponseMessageJson#results

type: "response-file-analysis"

The at this time unknown type