MicroContent domain

I had a talk with Seb Pacquet about all the aspects that are relevant to MicroContent if you want to cover everything. I realised that I might also use the tags on this blog to describe that domain. I notice that I am building up a tree with multiple branches.

• information branch - the first branch describes the information contained in MicroContent Items. This branch defines the various MicroContent types and the meaning of the types. This implies thus also the meaning of each field of a MicroContent type. And I guess that the definition of MicroContent itself also falls in this branch. Related tags are: definition, type, review, blog, etc;
• invocation branch - this branch deals with the users of MicroContent. It describes the necessary processes, protocols and tools. Related tags are: services, clients, netnewswire, etc.
• provisioning branch - this branch is about the creation and publishing process of MicroContent Items. It is about how the how author creates Items, how and where the Items get published. Related tags are: blogsystems, formats, structuredblogging, rss, xhtml, clients, ecto, etc.
• development branch - this branch is about developing new MicroContent types, Related tags are xsd, etc.

I have to go through my tag-cloud in order to see whether I can map all my tags to this domain tree. Probably one can set-up other trees at well, but I have the idea that this tree is able to cover everything. The last three branches have sub-branches whose order is determined by the life-cycles of those branches.

Categories/tags: definition
PermaLink • Comments • TrackBacks