| Bytecode for <wap-provisioningdoc version="1.1"> |  Search
|
|
NowSMS Support Forums ⬆ WAP Technical Discussions (unsupported) ⬆ Archive through March 07, 2006 ⬆ |
◄ ► |
| Author | Message | |||
| Anonymous |
Hello, I know that OMA specification explain that for <wap-provisioningdoc version="1.0"> we need C54601 for <wap-provisioningdoc> we need 45 but what about for the version 1.1 ?? I often found this version number for several XML files (pre-IMS SIP etc etc) but I don't found even in OMA documentation (OMA-WAP-ProvCont-v1_1-20021112-C and even in the 2005 release) the explanation about the encoding rule of the "7.2.1. Wap-provisioningdoc Attribute Start Tokens" chapter). Thanks for any Idea!! Regards. | |||
| Anonymous |
Hello, This is the response I have from OMA support team. Regards. --------------------- Since there is no token defined for the attribute value "1.1", it must be encoded as an inline string. The reason for not specifying the token for version number anymore was that properly done 1.0 clients would have been totally baffled by an unknown token (e.g. encoded "1.1" or "3.0" or something else), whereas now the clients are supposed to be able to decode the string value and realise that "1.1" is backwards compatible with "1.0". This means that "1.0" clients can safely use the "1.1" content as long as they ignore the content they don't understand. | |||
