Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
| filereference:fileformat [2021/10/18 19:11] – [General File items] enviadmin | filereference:fileformat [2021/10/18 19:12] – [Special EML items] enviadmin |
|---|
| </code> | </code> |
| |
| ''Collections'' are Multi-Item tags stored as normal item tags. In the example above, the item ''<soilprofil>'' holds a series of 19 individual values (sub-items) which are stored in a comma-sepearated list. | ''Collections'' are Multi-Item tags stored as normal item tags. In the example above, the item ''<soilprofil>'' holds a series of 19 individual values (sub-items) which are stored in a comma-sepearated list (to keep it readable we used only 2 instead of 6 chars for the IDs). |
| |
| These kind of tags only work with items that have explicit defined number of subitems to follow. They will only be interpeted correctly with programs understanding the meaning of such a comma-seperated list. In standard XML, this //collection// would have been splitted into 19 sub-items, one for each soil layer. Each of these sub-items would have its own opening and closing tag. For ENVI-met this was considered as an overkill. Therefor the Multi-Item tags have been introduced. | These kind of tags only work with items that have explicit defined number of subitems to follow. They will only be interpeted correctly with programs understanding the meaning of such a comma-seperated list. In standard XML, this //collection// would have been splitted into 19 sub-items, one for each soil layer. Each of these sub-items would have its own opening and closing tag. For ENVI-met this was considered as an overkill. Therefor the Multi-Item tags have been introduced. |
