Re: I-D ACTION:draft-ietf-trade-voucher-vtsapi-02.txt

[Ko Fujimura <fujimura@isl.ntt.co.jp>]

Hello All,

We updated the VTS-API draft as you noticed by the IETF Announce.
The major changes we made from the previous version are following points:

(1) Modified the last paragraph of section 5.1 VTSManager as follows
    to clarify the meaning (editorial).

      A class that implements the VTSManager interface must have a public
      default constructor (a constructor without any parameters).  The VTS
      provides a name for such constructor so that the implementation class
      can bootstrap the interface.

(2) Introduced a new exception FeatureNotAvailableException and 
    Added the following paragraph to the end of section 5.4 VTSAgent:

      Some VTSAgents may not have all of the trading methods; a voucher
      collecting system doesn't require its VTSAgent to provide method for
      issuing or creating vouchers.  A VTSAgent returns
      FeatureNotAvailableException when an unsupported method is invoked.

    Added this exception to section 5.4.3 prepare, 5.4.4 issue, 5.4.5 transfer
    5.4.6 consume, 5.4.7 present, 5.4.10 create, and 5.10 Exceptions

# Profile specification for issuing, wallet, and collecting system might 
# be needed but we decided not to include it since this approach introduces 
# complexity without benefit, i.e., it is evident for a collecting system doesn't
# require the issuing method, although a system (e.g., a POS device) can be both 
# collecting and issuing system.

(3) Added the following paragraph to the end of section 5.7.1 register
    to clarify the case in which the voucher component has already been 
    registered.

      The method returns the registered voucher component if the specified
      DOM object has been already registered.  (No new voucher component is
      created in this case).

(4) Added the following paragraph to the end of section 5.8 getDocument
    to clarify the lifetime of voucher component stored in the repository.

      The VTS must guarantee that the getDocument method will eventually
      return the DOM object provided that the voucher associated with the
      corresponding voucher component exists in the VVS.

(5) Added Acknowledgments section.

Thank you.

Ko
--------------------------------------------------------------
Dr. Ko Fujimura, NTT Information Sharing Platform Laboratories
1-1 Hikari-no-oka, Yokosuka-shi, Kanagawa 239-0847, JAPAN
Tel: +81-(0)468-59-3814, Fax: +81-(0)468-59-8329
Email: fujimura@isl.ntt.co.jp