# Working draft Structure

### Structure of the new standard (EIP):

* Metadata
* Simple summary (optional) - what
* Abstract
* Motivation - why
* Specification
* Rationale
* Backward compatibility
* Test cases
* Implementation
* Security considerations
* Copyright

### Common mistakes:

* not reading EIP1
* spelling & grammatical errors
* avoiding community feedback
* mixing too much motivation into the abstract
* too focused on a single-use case
* abandoning work

Source: <https://www.youtube.com/watch?v=Vnu4m4bBqCs>

### Further reading

* A comprehensive guide on writing and submitting an EIP <https://medium.com/ethereum-magicians/comprehensive-guide-on-writing-and-submitting-an-eip-9474163771f0>
* Guidelines on How to write EIP <https://anettrolikova.medium.com/guide-on-how-to-write-perfect-eip-70488ad70bec>
* What is EIP, and how can I create one? Ethereum Standards EIP ERC FAQs <https://medium.com/coinmonks/what-the-heck-is-eip-and-how-can-i-create-one-ethereum-standards-eip-erc-faqs-2fd1194eebe0>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nft-standards.gitbook.io/nft-standards-wiki/working-group/working-draft-structure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.