A MicroContent Item needs a container in order to be exchanged and re-used. One can think of a file as a container. In order to encode the MicroContent Item into the file, one needs a [[format]]. \n\nOne can have two possibilities ([[2416|http://www.sivas.com/microcontent/musings/blog/comments/2416/]]):\n1-1: Then a single MicroContent Item is encoded in a single file. The metadata of the file contains ifor instance information on the creation date/time and the author of the file. Enclosures in RSS-feeds are examples of such single Items [[(2228|http://www.sivas.com/microcontent/musings/blog/longhorn_rss/]]).\n1-n: It is also possible to encode multiple MicroContent Items in a single file. This is then a MacroContent Container([[2179|http://www.sivas.com/microcontent/musings/blog/micro_versus_macro/]]). Each of these Items might be of a different MicroContent Type, i.e. Compound ([[2184|http://www.sivas.com/microcontent/musings/blog/compound_blogs/]]). \n\nAn publisher might create many MicroContent Items. He could either create many containers, each for each item, or a single Container with all Items in a single file. There exists however a third possibility: the sliding view. A sliding view Containers has only a limited number of Items. Which Items are present in this sliding view Container, changes with time: new ones are added, old ones are removed.\n\nThe encoding method is based on a format, such as a [[MicroFormat|http://www.microformats.org]] ([[2207|http://www.sivas.com/microcontent/musings/blog/site_microformatsorg/]]) or [[Structured Blogging|http://www.structuredblogging.org/]]. I will not discuss these formats (any many) others here. A problem is that for the same MicroContent