{"action":"opened","issue":{"url":"https://api.github.com/repos/hyperledger/fabric/issues/2274","repository_url":"https://api.github.com/repos/hyperledger/fabric","labels_url":"https://api.github.com/repos/hyperledger/fabric/issues/2274/labels{/name}","comments_url":"https://api.github.com/repos/hyperledger/fabric/issues/2274/comments","events_url":"https://api.github.com/repos/hyperledger/fabric/issues/2274/events","html_url":"https://github.com/hyperledger/fabric/issues/2274","id":166841750,"number":2274,"title":"Editorials for application-ACL.md","user":{"login":"joshhus","id":16542757,"avatar_url":"https://avatars.githubusercontent.com/u/16542757?v=3","gravatar_id":"","url":"https://api.github.com/users/joshhus","html_url":"https://github.com/joshhus","followers_url":"https://api.github.com/users/joshhus/followers","following_url":"https://api.github.com/users/joshhus/following{/other_user}","gists_url":"https://api.github.com/users/joshhus/gists{/gist_id}","starred_url":"https://api.github.com/users/joshhus/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/joshhus/subscriptions","organizations_url":"https://api.github.com/users/joshhus/orgs","repos_url":"https://api.github.com/users/joshhus/repos","events_url":"https://api.github.com/users/joshhus/events{/privacy}","received_events_url":"https://api.github.com/users/joshhus/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-07-21T15:02:17Z","updated_at":"2016-07-21T15:02:17Z","closed_at":null,"body":"## Description\r\nSuggested language tweaks to /fabric/docs/tech/application-ACL.md\r\n\r\n## Describe How to Reproduce\r\nCompare to existing text below.\r\n\r\nFabric Support:\r\nTo allow Alice to specify her own access control lists and Bob to gain access, the fabric layer gives access to following capabilities: >> \r\nTo allow Alice to specify her own access control lists and Bob to gain access, the fabric layer provides the following capabilities:\r\n\r\n1. Alice and Bob can sign and verify any message with specific transaction certificates or enrollment certificate they own; >>\r\n1. Alice and Bob can sign and verify any message with specific transaction certificates or the enrollment certificate that they own;\r\n\r\n2. The fabric allows to name each transaction by means of a unique binding to be used to bind application data to the underlying transaction transporting it; >>\r\n2. The fabric allows Alice and Bob to name each transaction by means of a unique binding to be used to bind application data to the underlying transaction transporting it;\r\n\r\n3. Extended transaction format. >>\r\n3. Alice and Bob can optionally ? choose the extended transaction format to ... ? (describe what it is/does?) \r\n\r\nCertificate Handler:\r\n\r\nThe following interface allows to sign and verify any message using signing key-pair underlying the associated certificate. The certificate can be a TCert or an ECert: >>\r\nThe following interface allows Alice and Bob to sign and verify any message by using the key-pair which underlies the associated certificate. The certificate can be a tCert or eCert. (We started with lc t and e for eCert and tCert, unless we've switched to UC TCert and ECert.)\r\n\r\nTransaction Handler:\r\nThe following interface allows to create transactions and give access to the underlying binding that can be leveraged to link application data to the underlying transaction. >>\r\nThe following interface allows Alice and Bob to create transactions and give access to the underlying binding that can be leveraged to link application data to the underlying transaction.\r\n\r\nClient\r\nThe following interface offers a mean to get instances of the previous interfaces. >>\r\nThe following interface offers a means to get instances of the previous interfaces.\r\n\r\nTransaction Format\r\nThe content of this field is decided by the application. >>\r\nThe content of this field is determined by the application. \r\n\r\nAnother way to achieve this is to have the payload contain the metadata itself. >>\r\nAnother way to achieve this is to have the payload itself contain the metadata.\r\n\r\nValidators >>\r\nare these \"Validating nodes\"? \r\nValidating nodes\r\n\r\nTo assist chaincode execution, the validators provide the chaincode additional information, such as the metadata and the binding. >>\r\nTo assist chaincode execution, the validating nodes provide the chaincode with additional information, such as the metadata and the binding.\r\n\r\nExecute Transaction\r\n5. ... Now, signature can be included in the transaction as one of the argument to be passed to the function or as transaction metadata.\r\n5 ... Now, signature can be included in the transaction as one of the arguments to be passed to the function, or as transaction metadata.\r\n\r\nChaincode Execution\r\nThe validators, who receive the execute transaction issued by Bob, will provide to hello the following information: >>\r\nThe validating nodes, which receive the execute transaction issued by Bob, will provide hello with the following information:"}}
{"actor":{"display_login":"joshhus"}}