umarks > container
| Required/Optional | Optional |
|---|---|
| Format | Contains sub elements only |
| Restrictions | N/A |
| Parent Element | <umarks> |
| Child Elements | <title> <updated> <parent> <order> |
| Default Value | N/A |
| Number Allowed | Unlimited (0 - ∞) |
Description
The <container> tag is used to denote entities that can contain other elements in a bookmark hierarchy, such as links, separators and other containers. They are analogous to folders found on operating systems. They contain no content, only other tags.
A UMarks file can contain from zero to an unlimited number of containers i.e. you can add as many as you like.
The containers are grouped together and cannot be mixed with other elements.
Location
Nested inside the root element <umarks>. Placed after the global timestamp (<file-updated>) and before separators and links.
<umarks>
<!-- Global Timestamp -->
<container> … </container>
<container> … </container>
<!-- Separators -->
<!-- Links -->
</umarks>
Recommendations
| Reading from UMarks file | - |
|---|---|
| Writing to UMarks file | Any <container> tag used must include a <title> and <updated> tag, the others are optional. Sub elements shouldn’t be empty; tags with NULL values should be deleted. Sub elements have to follow a strict running order. NB: UMarks quietly enforces the use of unique container or folder names. That is, you cannot have two containers in the same place with the same name. |
See also
- umarks > container > title
- umarks > container > updated
- umarks > container > parent
- umarks > container > order
- Download sample files
- Overview of UMarks Tags
Feedback and criticism
We welcome feedback and criticism on any any aspect of UMarks, especially the tags, elements and general format of UMarks itself. So please don't hesitate to get in touch if you have anything to add. We read everything we get, and we never spam or retain your details in any way.
