Topic Map Fragment Extraction Tool

Description

Fragment creates little topic maps out of big ones. It does this by applying a simple fragment extraction algorithm to a selected topic in the input topic map(s). This algorithm extracts a subset of the input by copying all topics (and associations) with-in a specified 'distance' of the selected topic. The fragment thus created is a copy of the objects contained in the input - the input is not modified by this operation.

Usage

or, if using the scripts provided in the bin directory:

Options

-O | --object {object_id}

Specifies the unique object identifier of the topic to be the center of the fragment.

-I | --subject-indicator {subject_indiciator}

Specifies the subject indicator URI of the topic to be the center of the fragment. {subject_indiciator} must be a valid URI.

-S | --subject {subject}

Specifies the subject URI of the topic to be the center of the fragment. {subject} must be a valid URI.

code>-r | --radius {radius}

Specifies the 'radius' of the output fragment to be created. A value of 0 results in just the center topic being completely copied. A value of 1 results in the center topic and all topics which are associated with it or used to type or scope the topic or its characteristics being completely copied. The higher the radius, the more topics and associations will be completely copied. To maintain the semantics of the input topic map, other topics may be partially copied in such a way that if the fragment were to be merged again with the input source(s), those partially copied topics would be merged into the originals.

-o | --output {output_file_name}

Specifies the name of file to which the fragment should be written. If this option is omitted, then the fragment will be written to the standard output.

-b | --baseuri {output_uri}

Specifies the base URI of the topic map fragment generated. {output_uri} must be a valid URI. Note, this option does not specify where the file is to be written, just what the value of its xml:base attribute should be.

--no-mergemap

Specifies that the processor should not merge in topic maps specified in mergeMap directives in the input topic map(s).

--no-mergeref

Specifies that the processor should not merge in topic maps which contain topics referenced by the input topic map(s).

-c | --consistent

Specifies that the output topic map fragment should be made "consistent" according to the rules of XTM 1.0 before being written.