search

latch101 / seek-for-android

Automatically exported from code.google.com/p/seek-for-android
0 stars 0 forks source link

SEEK 3.1 is not fully compliant with OpenMobile 2.04 specification, by missing SEService.getVersion() #79

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
the public document for SEEK 3.1 seems to indicate its compliancy with 
OpenMobile 2.04 at 
http://seek-for-android.googlecode.com/svn/trunk/doc/index.html
with the following wording:

public class SEService extends Object

The SEService realises the communication to available Secure Elements on the 
device. This is the entry point of this API. It is used to connect to the 
infrastructure and get access to a list of Secure Element Readers. 

See Also:SIMalliance Open Mobile API v2.04

However, it is missing the getVersion API support mentioned in OM 2.04 at the 
following section:

6.4.5
Method: String getVersion()
Returns the version of the Open Mobile API specification this implementation is 
based
on.
Return value:
String containing the Open Mobile API version (e.g. "2.04").

SEEK should consider implementing this function as a "static" method.
The reason this should be a static method instead of a member method is because 
this is an information-al only API that should not require access/specific 
instance of any class of OpenMobile.

Original issue reported on code.google.com by tommypo...@gmail.com on 30 Jan 2014 at 10:33