The message type is a dot-delimited null-terminated string that defines the contents, meaning, and intended consumers of the message. An example is:
The message type must always begin with a protocol component and can be followed by more specific subtype information. From the perspective of NFP providers, only the protocol component needs to be parsed out and evaluated by the provider. The rest can be opaque and need only be used for matching published messages with subscribers.
The protocol component of the message type is defined as everything before the first dot in the message type, or the entire string if it contains no dots. As an example, the highlighted portion of Windows
.contoso.com:t shows the protocol component.
The protocol component is a standardized unique string that defines the primary level of branching for provider message handling. The string is case-sensitive. The parameter indicates to the NFP provider what the contents of messageData are as well as what protocol to use when transmitting the message.
A message intended to be transmitted or received over NFC would use the “NDEF” protocol and messageData should be assumed to already be formatted according to a specific NDEF standard.
All NFP providers are required to support the “Windows” protocol. When “Windows” is specified, messageData is formatted so that Windows can decode and understand the message. However, messageData is not encoded to any NFP technology standards. The NFP provider will need to wrap the message parameters in the appropriate protocol headers so that it can be transmitted to a receiver on a Windows device.
The protocol component corresponds to standardized types that the NFP provider understands and supports. An NFP provider must return an error when the caller specifies a protocol that the driver is not expecting. This avoids confusion among callers about why a message is not encoded to the expected protocol.
The maximum length of the Protocol component is 250 characters (not including the dot or NULL terminator).
The subtype component of messageType is defined as everything after the first dot. As an example, the highlighted portion of
Windows.contoso.com:t shows the subtype component.
The subtype component may be defined by Windows or by apps. The NFP provider should use it to deliver messages only to subscribers of the specified messageType.
The subtype string is case-sensitive and describes the contents of the message.
Providers MUST, at a minimum, support the following characters; for published types, limiting use to the following characters is RECOMMENDED:
Plus the following non-alphanumeric characters:
- . _~ : / ? # [ ] @ ! $ & ‘ ( ) * + , ; = %
For the “Windows” protocol, the subtype string should follow the URI naming scheme. This allows two different implementers to create types independently while ensuring that they don’t accidentally end up using the same type.
The maximum length of the subtype component is 250 characters (not including the NULL terminator). However, shorter type names are RECOMMENDED due to the short-message nature of typical proximity technologies.
Build date: 11/16/2013