| K. Fujimura and Y. Nakajima. General-Purpose Digital Ticket Framework. In Proc. of the 3rd USENIX Workshop on Electronic Commerce, September 1998. |
....tickets, digital tickets can not be developed by every ticket merchant. We need a common framework for all the digital tickets that we use. Lets briefly review some of the representations proposed for tickets. An interesting scheme based in RDF (Resource Description Framework) is presented in [5]. The authors classify tickets in three levels: common features (for all tickets) industry features (common to plane tickets, restaurant reservations, etc. and company or individual features. Important drawbacks of this scheme are the size of the tickets and their design that is specific to ....
Fujimura, K; Nakajima Y.: General-purpose Digital Ticket Framework. Proceedings of the 3rd USENIX Workshop on Electronic Commerce. pp 177-186.1998. Available at http://www.usenix.org/publications/library/proceedings/ec98/fujimura.html
....ticket is not copied, since the transaction ticket exists for each resource and nobody can purchase the goods or services without getting the ticket. To prevent the copying of transaction tickets, we propose to implement these transaction tickets as a digital right [4] or digital ticket [5,6]) which can be circulated securely using a digital right trading system. This approach also enables delegation of the right to purchase to the check out agent securely by transferring the transaction ticket to the check out agent. Although this scheme assumes that the digital right trading ....
....a digital right circulation model, all of which are needed to understand this paper. The copy prevention method, which can be used in implementing a DRTS and other implementation issues are beyond the scope of this paper. The model and framework of DRTS are discussed in the area of digitalticket [5,6] and digital bearer instrument [7,8] and their implementation issues are discussed in [12,14,17] 2.1. Objectives The goals of DRTS are to provide an infrastructure that prevents duplicate redemption and enables the trading of various rights via the Internet. In other words, it is to provide a ....
K. Fujimura and Y. Nakajima, "General-purpose Digital Ticket Framework", 3rd USENIX Workshop on Electronic Commerce, pp. 177-186, 1998.
.... using a common ticket processing system, we proposed a general purpose digital ticket framework, in which a ticket is circulated by interpreting the ticket properties of anonymity, transferability, and divisibility, specified in the ticket itself using the Generalized Ticket Definition Language [9]. No circulation control scheme or trust management scheme for digital tickets have, however, been presented up to now. These issues are especially important since the requirements depend on the ticket s business scheme, and this makes generalization difficult. This paper focuses on these issues ....
....manage only one type definition for each type of ticket, even if complicated issuer conditions are set. 5. Overview of Implementation 5. 1 Generalized ticket definition language We proposed to implement the Generalized Ticket Definition Language on top of RDF [18] which, in our previous paper [9], is layered on XML [17] Our current implementation, however, uses XML directly [12] The reason for this is because RDF is too rich and redundant to describe circulation conditions or other properties for controlling ticket circulation, which are common to all tickets, and the semantics are not ....
K. Fujimura and Y. Nakajima, "General-purpose Digital Ticket Framework", 3rd USENIX Workshop on Electronic Commerce, August 1998, pp. 177-186.
No context found.
K. Fujimura and Y. Nakajima. General-Purpose Digital Ticket Framework. In Proc. of the 3rd USENIX Workshop on Electronic Commerce, September 1998.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC