I figured out that this might be useful for certain developers out there...that intends invoking their apps, by simply reading the NFC tag....and voila!!! Magic....awesome one from the BlackBerry 10....finding it so easy to develop my NFC enabled apps nowadays!!! Thank you to the people inside this forum too for your contribution!!!
<invoke-target id="com.example.bb10app.nfc ">
<require-source-permissions>invoke_across_perimete
<invoke-target-type>application</invoke-target-typ
<!-- The action(s) we support-->
<action>bb.action.OPEN</action>
<!-- The mime type(s) we support, application/vnd.rim.nfc.ndef is for all
NDEF types (i.e. text, media, smart poster, uri-->
<mime-type>application/vnd.rim.nfc.ndef</mime-type
<!-- ndef:// means that we want to register for ALL NDEF messages,
in most cases we want to be more specific; we can filter these
messages further with the following format ndef://TNF/RECORD_TYPE
(e.g. ndef://1/Sp for tnf: Well Known, record type: smart posters).
for URI record types the record type needs to be URL encoded
(e.g. ndef://3/http%3A%2F%2F for tnf: Uri, record type: http://).
for external record types the colon (
needs to be replaced with a
(e.g. ndef://4/rim.com/bbm for tnf: External, record type: rim.com:bbm).
<property var="uris" value="ndef://"/>
invoke_across_perimeters application bb.action.OPEN ...
*****NOTE: Note the TNF Value, 0,1,2,3,4
