s1kd-defaults Description khzae.net khzae.net All Add --xml-catalog parser option. The s1kd-defaults tool generates a basic .defaults file for a new CSDB, which is used by several of the other s1kd-tools to determine default values for S1000D metadata. It also provides a way to convert between the simple text and XML formats of the .defaults, .dmtypes and .fmtypes files. s1kd-defaults [-DdFfisth?] [-b <BREX>] [-j <map>] [-n <name> -v <value> ...] [-o <dir>] [<file>...] -b, --brex <BREX> Use the specified BREX data module to build the .defaults and .dmtypes files. This can be used both when initializing a new CSDB (-i) or either file can be generated from a BREX data module separately. -D, --dmtypes Convert a .dmtypes file. -d, --defaults Convert a .defaults file. -F, --fmtypes Convert a .fmtypes file. -f, --overwrite Overwrite the existing file after conversion. -h, -?, --help Show help/usage message. -i, --init Initialize a new CSDB by generating the .defaults, .dmtypes and .fmtypes files in the current directory. -J, --dump-brexmap Dump the default .brexmap file to stdout. -j, --brexmap <map> Use a custom .brexmap file to map a BREX DM to a .defaults or .dmtypes file. -n, --name <name> The name of a specific default key to set a value for. The value must be specified after this option with -v. Multiple pairs of -n and -v can be specified to set multiple default values. -o, --dir <dir> Initialize or manage configuration files in <dir> instead of the current directory. If <dir> does not exist, it will be created. -s, --sort Sort the entries alphabetically for either file/output format. -t, --text Output using the simple text format. Otherwise, the XML format is used by default. -v, --value <value> The new value to set for the default key specified with -n. This option must be specified after -n. --version Show version information. <file>... Names of files to convert. If none are specified, the default names of .defaults (for the -d option), .dmtypes (for the -D option) or .fmtypes (for the -F option) in the current directory are used. In addition, the following options allow configuration of the XML parser: --dtdloadLoad the external DTD.--hugeRemove any internal arbitrary parser limits.--netAllow network access to load external DTD and entities.--noentResolve entities.--parser-errorsEmit errors from parser.--parser-warningsEmit warnings from parser.--xincludeDo XInclude processing.--xml-catalog <file>Use an XML catalog when resolving entities. Multiple catalogs may be loaded by specifying this option multiple times. This file specifies a mapping between BREX structure object rules and .defaults and .dmtypes files. The path to an object can be written in many different ways in a BREX rule, so the .brexmap file allows any project's BREX to be used to generate these files without having to modify the BREX data module itself. By default, the program will search for a file named .brexmap in the current directory and parent directories, but any file can be specified using the -j option. If there is no .brexmap file and the -j option is not specified, a default mapping will be used. Example of .brexmap file: <brexMap> <dmtypes path="//@infoCode"/> <default path="//@languageIsoCode" ident="languageIsoCode"/> <default path="//@countryIsoCode" ident="countryIsoCode"/> </brexMap> More exact matches can be made by using the attribute id on the <dmtypes> or <default> elements. This overrides the path attribute, and will only match a BREX rule with the specified ID. $ mkdir mycsdb $ cd mycsdb $ s1kd-defaults -i $ mkdir mycsdb $ cd mycsdb $ s1kd-defaults -ti $ s1kd-defaults > custom-defaults.xml $ s1kd-defaults -df $ s1kd-defaults -dts custom-defaults.txt $ s1kd-defaults -df -n issue -v 5.0