| :resourcename | | :resourcename |
| | | |
| A resource name must be a valid Python identifier | | A resource name must be a valid Python identifier |
| (possibly including dots). For example: `resname` | | (possibly including dots). For example: `resname` |
| or `modname.resname`. | | or `modname.resname`. |
| | | |
| The resource name is followed by the resource's me | | The resource name is followed by the resource's me |
| tadata; zero or more lines defining key-value pair | | tadata; zero or more lines defining key-value pair |
| s. These have the same format as in the [Metadata] | | s. These have the same format as in the [Metadata] |
| file. | | file. |
| t | | t |
|
| | | ## Resource metadata
|
| | |
|
| | | Dublin Core metadata terms may be used to describe |
| | | the title of a resource, its author, and so on. S |
| | | ee the [Metadata] page for details.
|
| | |
|
| | | Besides those, Boodler pays special attention to t |
| | | he following terms:
|
| | |
|
| | | * `boodler.filename` : The filename, for a file re |
| | | source. This must be in universal format: relative |
| | | to the module root, and written with forward slas |
| | | hes, not backslashes.
|