Skip to content

Commit

Permalink
Merge pull request #3 from WyattMufson/nft
Browse files Browse the repository at this point in the history
Remove tokenURI
  • Loading branch information
hal0x2328 authored Jul 29, 2019
2 parents 9b838e4 + 208d630 commit f1ff9f5
Showing 1 changed file with 1 addition and 26 deletions.
27 changes: 1 addition & 26 deletions nep-11.mediawiki
Original file line number Diff line number Diff line change
Expand Up @@ -171,7 +171,6 @@ The returned tokens should be in the following format:
<pre>
{
"id": <ID>,
"uri": tokenURI(<ID>),
"properties": properties(<ID>),
...
}
Expand All @@ -180,32 +179,13 @@ The returned tokens should be in the following format:
It must have the fields <code>id</code>, <code>uri</code> and <code>properties</code>.
It can contain other dApp-specific fields.

====tokenURI====

<pre>
public static string tokenURI(byte[] tokenid)
</pre>

Returns a distinct Uniform Resource Identifier (URI) for a given asset.
URIs are defined in [https://tools.ietf.org/html/rfc3986 RFC 3986].
This URI contains optionally mutable properties for the given NFT.

The parameter <code>tokenid</code> SHOULD be a valid NFT.
If not, this method SHOULD <code>throw</code> an exception.

The URI MUST point to a JSON file that conforms to the "NEO NFT Metadata JSON Schema":

The supported scheme of the returned URI MUST be one of the following: <code>http</code>, <code>https</code>, <code>data</code>.

The "data" URI scheme is defined in [https://tools.ietf.org/html/rfc2397 RFC 2397].

====properties====

<pre>
public static string properties(byte[] tokenid)
</pre>

Returns a serialized NVM object containing immutable on-chain properties for the given NFT.
Returns a serialized NVM object containing the properties for the given NFT.
The NVM object must conform to the "NEO NFT Metadata JSON Schema".

The parameter <code>tokenid</code> SHOULD be a valid NFT.
Expand Down Expand Up @@ -234,11 +214,6 @@ If not, this method SHOULD <code>throw</code> an exception.
}
</pre>

The schema must contain a <code>title</code>, <code>type</code> and <code>properties</code>.

Any custom fields can be included in the JSON file.
Each field contains a <code>type</code> and <code>description</code>.

===Events===

====Transfer====
Expand Down

0 comments on commit f1ff9f5

Please sign in to comment.