Size of an SE API standard

Dear All,

If you settle for the current "input document" all with be quick and easy since it essentially about a setting up dumb pipes for transmitting *vendor-specific* SE-commands.

If you OTOH rather buy into the idea of creating an *interoperable SE concept* that is used by everybody on the planet for everything from login to Facebook or the e-government, paying with virtual credit-cards, locally or on the Internet, etc. you should be prepared for a *very* big standard in terms of documents, possibly only eclipsed by HTML5.  Harnessing such a monster as a *second-priority sub-task* in a WG having several other tasks to cater for is simply put a pretty bad idea.

In fact, I don't consider this a suitable item for standardization at all since achieving consensus would take forever and then the so called "standard" would already be obsoleted by more agile efforts...

FYI: This is what the SKS/KeyGen2 "not-a-standard" currently consists of:

SKS API (72 pages):
https://openkeystore.googlecode.com/svn/resources/trunk/docs/sks-api-arch.pdf

KeyGen2 Schema (23 pages):
https://openkeystore.googlecode.com/svn-history/r1002/resources/trunk/docs/keygen2schema.pdf

SKS Reference Implementation (4000 lines including support classes):
https://code.google.com/p/openkeystore/source/browse/library/trunk/src/org/webpki/sks/test/SKSReferenceImplementation.java

JUnit tests (3400 + 2000 lines)
https://code.google.com/p/openkeystore/source/browse/library/trunk/src/org/webpki/sks/test/SKSTest.java
https://code.google.com/p/openkeystore/source/browse/library/trunk/src/org/webpki/keygen2/test/KeyGen2Test.java

Public interoperability test server:
10000+ lines of Java code

Numerous of other documents and executive level descriptions; probably in excess of 40 pages

Estimated work to date: 5000 hours including an Android PoC ("WebPKI Suite" on PlayStore).

thanx,
Anders

Received on Saturday, 27 July 2013 20:11:51 UTC