Merge pull request #573 from lijiachuan1982/release-2.0

Release 2.0 - Getting Start

docs/source/developapps/analysis.md

@@ -1,21 +1,12 @@
-# Analysis
+# 分析
 
-**Audience**: Architects, Application and smart contract developers, Business
-professionals
+**受众**: 架构师，应用和合约开发者，业务专家
 
-Let's analyze commercial paper in a little more detail. PaperNet participants
-such as MagnetoCorp and DigiBank use commercial paper transactions to achieve
-their business objectives -- let's examine the structure of a commercial paper
-and the transactions that affect it over time. We will also consider which
-organizations in PaperNet need to sign off on a transaction based on the trust
-relationships among the organizations in the network. Later we'll focus on how
-money flows between buyers and sellers; for now, let's focus on the first paper
-issued by MagnetoCorp.
+让我们更详细的分析商业票据。MagnetoCorp 和 DigiBank 等 PaperNet 参与者使用商业票据交易来实现其业务目标 -- 让我们检查商业票据的结构以及随着时间推移影响票据结构的交易。我们还将根据网络中组织之间的信任关系，考虑 PaperNet 中的哪些组织需要签署交易。稍后我们将关注买家和卖家之间的资金流动情况; 现在，让我们关注 MagnetoCorp 发行的第一个票据。
 
-## Commercial paper lifecycle
+## 商务票据生命周期
 
-A paper 00001 is issued by MagnetoCorp on May 31. Spend a few moments looking at
-the first **state** of this paper, with its different properties and values:
+票据 00001 是 5 月 31 号由 MagnetoCorp 发行的。花点时间来看看该票据的第一个 **状态**，它具有不同的属性和值：
 
 ```
 Issuer = MagnetoCorp
@@ -27,17 +18,9 @@ Face value = 5M USD
 Current state = issued
 ```
 
-This paper state is a result of the **issue** transaction and it brings
-MagnetoCorp's first commercial paper into existence! Notice how this paper has a
-5M USD face value for redemption later in the year. See how the `Issuer` and
-`Owner` are the same when paper 00001 is issued. Notice that this paper could be
-uniquely identified as `MagnetoCorp00001` -- a composition of the `Issuer` and
-`Paper` properties. Finally, see how the property `Current state = issued`
-quickly identifies the stage of MagnetoCorp paper 00001 in its lifecycle.
+该票据的状态是 **issue** 交易的结果，它使得 MagnetoCorp 公司的第一张商业票据面世！注意该票据在今年晚些时候如何兑换面值 500 万美元。当票据 00001 发行后 `Issuer` 和 `Owner` 具有相同的值。该票据有唯一标识 `MagnetoCorp00001` -- 它是 `Issuer` 属性和 `Paper` 属性的组合。最后，属性 `Current state = issued` 快速识别了 MagnetoCorp 票据 00001 在它生命周期中的阶段。
 
-Shortly after issuance, the paper is bought by DigiBank. Spend a few moments
-looking at how the same commercial paper has changed as a result of this **buy**
-transaction:
+发行后不久，该票据被 DigiBank 购买。花点时间来看看由于 **购买** 交易，同一个商业票据如何发生变化：
 
 ```
 Issuer = MagnetoCorp
@@ -49,14 +32,9 @@ Face value = 5M USD
 Current state = trading
 ```
 
-The most significant change is that of `Owner` -- see how the paper initially
-owned by `MagnetoCorp` is now owned by `DigiBank`.  We could imagine how the
-paper might be subsequently sold to BrokerHouse or HedgeMatic, and the
-corresponding change to `Owner`. Note how `Current state` allow us to easily
-identify that the paper is now `trading`.
+最重要的变化是 `Owner` 的改变 -- 票据初始拥有者是 `MagnetoCorp` 而现在是 `DigiBank`。我们可以想象该票据后来如何被出售给 BrokerHouse 或 HedgeMatic，以及相应的变更为相应的 `Owner`。注意 `Current state` 允许我们轻松的识别该票据目前状态是 `trading`。
 
-After 6 months, if DigiBank still holds the commercial paper, it can redeem
-it with MagnetoCorp:
+6 个月后，如果 DigiBank 仍然持有商业票据，它就可以从 MagnetoCorp 那里兑换：
 
 ```
 Issuer = MagnetoCorp
@@ -68,29 +46,21 @@ Face value = 5M USD
 Current state = redeemed
 ```
 
-This final **redeem** transaction has ended the commercial paper's lifecycle --
-it can be considered closed. It is often mandatory to keep a record of redeemed
-commercial papers, and the `redeemed` state allows us to quickly identify these.
-The value of `Owner` of a paper can be used to perform access control on the
-**redeem** transaction, by comparing the `Owner` against the identity of the
-transaction creator. Fabric supports this through the
-[`getCreator()` chaincode API](https://github.com/hyperledger/fabric-chaincode-node/blob/master/fabric-shim/lib/stub.js#L293).
-If golang is used as a chaincode language, the [client identity chaincode library](https://github.com/hyperledger/fabric-chaincode-go/blob/master/pkg/cid/README.md)
-can be used to retrieve additional attributes of the transaction creator.
+最终的 **redeem** 交易结束了这个商业票据的生命周期 -- 它可以被认为票据已经终止。通常必须保留已兑换的商业票据的记录，并且 `redeemed` 状态允许我们快速识别这些。
 
-## Transactions
+通过将 `Owner` 跟交易创建者的身份进行比较，一个票据的 `Owner` 值可以被用来在 **redeem** 交易上进行访问控制。Fabric 通过 [`getCreator()` chaincode API](https://github.com/hyperledger/fabric-chaincode-node/blob/master/fabric-shim/lib/stub.js#L293). 来对此提供支持。
 
-We've seen that paper 00001's lifecycle is relatively straightforward -- it
-moves between `issued`, `trading` and `redeemed` as a result of an **issue**,
-**buy**, or **redeem** transaction.
+如果 golang 作为一个链码的语言，[client identity chaincode library](https://github.com/hyperledger/fabric-chaincode-go/blob/master/pkg/cid/README.md) 可以被用来取回交易创建者的额外的属性。
 
-These three transactions are initiated by MagnetoCorp and DigiBank (twice), and
-drive the state changes of paper 00001. Let's have a look at the transactions
-that affect this paper in a little more detail:
+## 交易
 
-### Issue
+我们已经看到票据 00001 的生命周期相对简单 -- 由于 **issue**, **buy**, 和 **redeem** 交易，它在 `issued`, `trading` 和 `redeemed` 状态之间转移。
 
-Examine the first transaction initiated by MagnetoCorp:
+这三笔交易由 MagnetoCorp 和 DigiBank（两次）发起，并推动了 00001 票据的状态变化。让我们更详细地看一下影响票据的交易：
+
+### 发行
+
+检查 MagnetoCorp 发起的第一笔交易：
 
 ```
 Txn = issue
@@ -101,22 +71,13 @@ Maturity date = 30 November 2020
 Face value = 5M USD
 ```
 
-See how the **issue** transaction has a structure with properties and values.
-This transaction structure is different to, but closely matches, the structure
-of paper 00001. That's because they are different things -- paper 00001 reflects
-a state of PaperNet that is a result of the **issue** transaction. It's the
-logic behind the **issue** transaction (which we cannot see) that takes these
-properties and creates this paper. Because the transaction **creates** the
-paper, it means there's a very close relationship between these structures.
+观察 **发行** 交易是如何具有属性和值的结构的。这个交易的结构跟票据 00001 的结构是不同的但是非常匹配的。那是因为他们是不同的事情 -- 票据 00001 反应了 PaperNet state，是作为 **issue** 交易的结果。这是在 **发行** 交易背后的逻辑（我们是看不到的），它带着这些属性并且创建了票据。因为交易 **创建** 了票据，着意味着在这些结构之间具有着飞铲更密切的关系。
 
-The only organization that is involved in the **issue** transaction is MagnetoCorp.
-Naturally, MagnetoCorp needs to sign off on the transaction. In general, the issuer
-of a paper is required to sign off on a transaction that issues a new paper.
+在这个 **发行** 的交易中唯一被引入的组织是 MagnetoCorp。很自然的，MagnetoCorp 需要对交易进行签名。通常，一个票据的发行者会被要求在发行一个新的票据的交易上提供批准。
 
-### Buy
+### 购买
 
-Next, examine the **buy** transaction which transfers ownership of paper 00001
-from MagnetoCorp to DigiBank:
+接下来，检查 **buy** 交易，将票据 00001 的所有权从 MagnetoCorp 转移到 DigiBank：
 
 ```
 Txn = buy
@@ -128,27 +89,13 @@ Purchase time = 31 May 2020 10:00:00 EST
 Price = 4.94M USD
 ```
 
-See how the **buy** transaction has fewer properties that end up in this paper.
-That's because this transaction only **modifies** this paper. It's only `New
-owner = DigiBank` that changes as a result of this transaction; everything else
-is the same. That's OK -- the most important thing about the **buy** transaction
-is the change of ownership, and indeed in this transaction, there's an
-acknowledgement of the current owner of the paper, MagnetoCorp.
+了解 **buy** 交易如何减少票据中最终的属性。因为交易只能**修改**该票据。只有 `New owner = DigiBank` 改变了；其他所有的都是相同的。这没关系 -- 关于 **buy** 交易最重要的是所有权的变更，事实上，在这次交易中，有一份对该票据当前所有者 MagnetoCorp 的认可。
 
-You might ask why the `Purchase time` and `Price` properties are not captured in
-paper 00001? This comes back to the difference between the transaction and the
-paper. The 4.94 M USD price tag is actually a property of the transaction,
-rather than a property of this paper. Spend a little time thinking about
-this difference; it is not as obvious as it seems. We're going to see later
-that the ledger will record both pieces of information -- the history of all
-transactions that affect this paper, as well its latest state. Being clear on
-this separation of information is really important.
+你可能会奇怪为什么 `Purchase time` 和 `Price` 属性没有在票据 00001 中体现？ 这要回到交易和票据之间的差异。494 万美元的价格标签实际上是交易的属性，而不是票据的属性。花点时间来思考一下这两者的不同；它并不像它看上去的那么明显。稍后我们会看到账本会记录这些信息片段 -- 影响票据的所有交易历史，和它最新的状态。清楚这些信息分离非常重要。
 
-It's also worth remembering that paper 00001 may be bought and sold many times.
-Although we're skipping ahead a little in our scenario, let's examine what
-transactions we **might** see if paper 00001 changes ownership.
+同样值得注意的是票据 00001 可能会被买卖多次。尽管在我们的场景中略微跳过了一点，我们来检查一下如果票据 00001 变更了所有者我们**可能**会看到什么。
 
-If we have a purchase by BigFund:
+如果 BigFund 购买：
 
 ```
 Txn = buy
@@ -159,7 +106,9 @@ New owner = BigFund
 Purchase time = 2 June 2020 12:20:00 EST
 Price = 4.93M USD
 ```
-Followed by a subsequent purchase by HedgeMatic:
+
+接着由 HedgeMatic 购买：
+
 ```
 Txn = buy
 Issuer = MagnetoCorp
@@ -170,19 +119,17 @@ Purchase time = 3 June 2020 15:59:00 EST
 Price = 4.90M USD
 ```
 
-See how the paper owners changes, and how in our example, the price changes. Can
-you think of a reason why the price of MagnetoCorp commercial paper might be
-falling?
+看看票据所有者如何变化，以及在我们的例子中，价格如何变化。你能想到 MagnetoCorp 商业票据价格会降低的原因吗？
 
 Intuitively, a **buy** transaction demands that both the selling as well as the
 buying organization need to sign off on such a transaction such that there is
 proof of the mutual agreement among the two parties that are part of the deal.
 
-### Redeem
+很直观地，一个 **购买** 交易要求售卖组织和购买组织都要对该交易进行批准，一次作为该笔交易的两方参与者之间的一个共同的协议的证据。
+
+### 赎回
 
-The **redeem** transaction for paper 00001 represents the end of its lifecycle.
-In our relatively simple example, HedgeMatic initiates the transaction which
-transfers the commercial paper back to MagnetoCorp:
+票据 00001 **赎回**  交易代表了它生命周期的结束。在我们相对简单的例子中，HedgeMatic 启动将商业票据转回 MagnetoCorp 的交易：
 
 ```
 Txn = redeem
@@ -192,35 +139,21 @@ Current owner = HedgeMatic
 Redeem time = 30 Nov 2020 12:00:00 EST
 ```
 
-Again, notice how the **redeem** transaction has very few properties; all of the
-changes to paper 00001 can be calculated data by the redeem transaction logic:
-the `Issuer` will become the new owner, and the `Current state` will change to
-`redeemed`. The `Current owner` property is specified in our example, so that it
-can be checked against the current holder of the paper.
+再次注意 **赎回** 交易有更少的属性；票据 00001 所有更改都可以通过兑换交易逻辑计算数据：`Issuer` 将成为新的所有者，`Current state` 将变成 `redeemed`。在我们的例子中指定了 `Current owner` 属性，以便可以针对当前的票据持有者进行检查。
 
 From a trust perspective, the same reasoning of the **buy** transaction also
 applies to the **redeem** instruction: both organizations involved in the
 transaction are required to sign off on it.
 
-## The Ledger
-
-In this topic, we've seen how transactions and the resultant paper states are
-the two most important concepts in PaperNet. Indeed, we'll see these two
-fundamental elements in any Hyperledger Fabric distributed
-[ledger](../ledger/ledger.html) -- a world state, that contains the current
-value of all objects, and a blockchain that records the history of all
-transactions that resulted in the current world state.
-
-The required sign-offs on transactions are enforced through rules, which
-are evaluated before appending a transaction to the ledger. Only if the
-required signatures are present, Fabric will accept a transaction as valid.
-
-You're now in a great place translate these ideas into a smart contract. Don't
-worry if your programming is a little rusty, we'll provide tips and pointers to
-understand the program code. Mastering the commercial paper smart contract is
-the first big step towards designing your own application. Or, if you're a
-business analyst who's comfortable with a little programming, don't be afraid to
-keep dig a little deeper!
+从信任的角度来说，跟 **购买** 交易具有相同的原因，也可以应用到 **赎回** 的说明：在交易中引入的双方组织都需要对它提供批准。
+
+## 账本
+
+在本主题中，我们已经看到交易和产生的票据状态是 PaperNet 中两个重要的概念。的确，我们将会在任何一个 Hyperledger Fabric 分布式[账本](../ledger/ledger.html)中看到这些基本元素 -- 包含了当前所有对象最新状态的世界状态和记录了所有交易历史并能归集出最新世界状态的区块链。
+
+在交易上必须的批准通过规则被强制执行，这个在一个交易被附加到账本之前被评估。只有当需要的签名被展示的时候，Fabric 才会接受一个交易作为有效的交易。
+
+你现在处在一个很棒的地方，将这些想法转化为智能合约。如果您的编程有点生疏，请不要担心，我们将提供了解程序代码的提示和指示。掌握商业票据智能合约是设计自己的应用程序的第一个重要步骤。或者，你是一个有一点编程经验的业务分析师，不要害怕继续深入挖掘！
 
 <!--- Licensed under Creative Commons Attribution 4.0 International License
 https://creativecommons.org/licenses/by/4.0/ -->