The rest of the data immediately follow it. Where "" is an integer value specifying the number of bytes in the block of data following it. The block can be either compressed or uncompressed, but by default it is uncompressed (compression is global to the file and marked by an attribute on the VTKFile element).Ī block representing a data array without compression has this format: Each DataArray's data are stored in a contiguous block. An offset of "0" means the first character after the underscore. The value in the "offset" attribute is the file offset in bytes beyond the leading underscore. In this document we assume the raw encoding because it is simpler.ĭataArray elements elsewhere in the file reference the AppendedData section like this: The AppendedData section CDATA can be base-64 encoded to produce a fully valid XML file, but may also be left raw. Extra whitespace AFTER the data has no effect. This character separates whitespace to its left from the data to its right.
Note the literal underscore ('_') at the beginning of the data. A file with an AppendedData element has this form: The appended data section is stored in an XML element just before the end of the file. If no such attribute is specified (as in version 0.1) the header type is UInt32. The header-type specified may be either " UInt32" or " UInt64" and indicates the integer type used in binary data headers (see below). The byte-order specified may be either " LittleEndian" or " BigEndian" and indicates the byte order used for any binary data in the file.įile format version 1.0 supports an additional VTKFile attribute: The version number is specific to each type of data set represented in the file.įor normal (non-composite) data set types possible version numbers are: For more information, see Unregister a Machineįor each of the child tags under the tag,Īdditional tags are used to identify specific elements of information.The top-level document element of any VTK XML file is called "VTKFile": For more information, see Delete a Client Identity Information for deleting client identities.
#Format xml file update#
For more information, see Update a Client Identity Information for modifying or disabling client identities. For more information, see Create a Client Identity
Information for creating client identities. For more information, see Read a Client Identity List For more information, see Retrieve a Single Client Identity
#Format xml file license#
Regarding configuration settings for the local Sentinel License For more information, see Generating C2V Files and Fingerprint Files. Regarding the local Sentinel License Managerįingerprint of the machine. Regarding current sessions for a specific protection key Regarding the local Sentinel License Manager. For more information, see Format XML Tags for Protection Keys
(The retrieved information is arranged under the parent tag.) (No additional child tags are availableįor the format of the XML for information to be retrieved. Scope tags can be used to set the scope for the information to be retrieved.įor certain child tags, the scope is not relevant and Scope tags shouldįormat XML tags are also used by the function to label the retrieved information.Īnd relevant Scope tags are described in the table that follows.Īdmin API session context. The Format XML tags that you specify (and their arrangement) determine both which items of information are retrieved by the function and the manner in which the retrieved information is arranged.įor each child tag (described in the table below), specific Field to specify the data that should be retrieved by the function.
0 kommentar(er)
