From 47f09c0e672649c7f7dea6aed4d285c8b1c09c03 Mon Sep 17 00:00:00 2001
From: Scott Sadler <scott@alphanode.co>
Date: Mon, 16 Jan 2017 15:24:51 +0100
Subject: [PATCH] documentation changes for duplicate asset id
---
docs/server/source/data-models/asset-model.md | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/docs/server/source/data-models/asset-model.md b/docs/server/source/data-models/asset-model.md
index 312c6765..16188400 100644
--- a/docs/server/source/data-models/asset-model.md
+++ b/docs/server/source/data-models/asset-model.md
@@ -1,10 +1,11 @@
# The Digital Asset Model
-To avoid redundant data in transactions, the digital asset model is different for `CREATE` and `TRANSFER` transactions.
+The asset ID is the same as the ID of the CREATE transaction that defined the asset.
-A digital asset's properties are defined in a `CREATE` transaction with the following model:
+In the case of a CREATE transaction, the transaction ID is duplicated into the asset object for clarity and consistency in the database. The CREATE transaction also contains a user definable payload to describe the asset:
```json
{
+ "id": "<same as transaction ID (sha3-256 hash)>",
"data": "<json document>"
}
```