DSPro Message Metadata

Every message being added to DSPro needs to have a metadata that describes its content. The message metadata can be submitted to DSPro either as a XML document matching the appropriate schema (see next section), or as an attribute-value list. DSPro supports a set of default attributes, and the custom extra attributes specified during DSPro configuration, or by using the -metadataExtraAttribute command line switch when running DSPro (see the DSPro Configuration page).

• Application_Metadata: an application-defined metadata that can be embedded in the DSPro metadata. The application metadata is opaque for DSPro, however, because the DSPro metadata is expressed in XML, the application metadata should not contain symbols that are included in the XML language. It is therefore recommended that the application metadata is encoded (for instance using a base 64 encoding) to some appropriate format.
• Application_Metadata_Format: it should contain the necessary information to allow the applications to correctly decode and parse the application metadata.
• Message_ID: the DSPro ID that identifies the metadata message within DSPro. This field is set by DSPro.
• Refers_To: the DSPro ID of the data message that the metadata describes. If set to , it means that the metadata is also the data. This field is set by DSPro.
• Referred_Data_Object_Id: a publishing-application-defined identifier for the object. This field is set by DSPro.
• Referred_Data_Instance_Id: a publishing-application-defined identifier for the object's instance. This field is set by DSPro.
• Prev_Msg_ID: the DSPro ID of the metadata message that was pushed to the node prior to the metadata being notified. This field is set by DSPro.
• Node_Type: the type of the node.
• Data_Content: a description of the content of the data.
• Classification: the classification of the data (top secret, secret, confidential, ...)
• Data_Format: the MIME type of the data message.
• Left_Upper_Latitude: Left upper latitude of the area for which the IO is relevant
• Right_Lower_Latitude: Left upper longitude of the area for which the IO is relevant
• Left_Upper_Longitude: Right upper latitude of the area for which the IO is relevant
• Right_Lower_Longitude: Right upper longitude of the area for which the IO is relevant
• Pedigree: the list of nodes the metadata traversed before reached the current node. This field is set by DSPro.
• Importance: a publishing-application-defined value of importance for the data message. It ranges from 1 to 5.
• Location: descriptive information on the location where the data message was generated.
• Receiver_Time_Stamp: the time when the current node received the metadata message. This field is set by DSPro
• Source_Realiability: Reliability at the source of the IO (1-10)
• Node_Type: Usually contains the military standard code
• ComputedVOI: The VoI of the IO that was computed for the metadata (in the peerNodeId1,Voi1;peerNodeId2,Voi2 format). This field is set by DSPro.
• Source: the node ID of the node generating the message. This field is set by DSPro.
• Source_Time_Stamp: the time when the source node generated the metadata message. This field is set by DSPro.
• Expiration_Time: the time before which the data message is considered relevant.
• Relevant_Missions: the mission for which the data message is considered relevant.
• Target_ID: The Id (node id, user id, ...) for whom the IO is relevant.
• Target_Role: The role for which the IO is relevant.
• Target_Team: The id of the team for which the IO is relevant.
• Relevant_Mission: The mission for which the IO is relevant.
• Data_Content: It is usually set to the filename or callsign of the published IO.