Rtiv,
Right, we are early on this, but the DTD or a more extensive schema
(coming soon) defines the parent-child relationships of the tags, and
you are right, the tags can be nested as deeply as needed - that is XML.
Basically there are block and inline components or information items.
The document tree can be any depth, you define it to be. Each path
terminates in content and/or an empty tag. An html example might be:
<body>
<div>
<p>content<img.../>
</p>
</div>
</body>
In the example I used DKRid as the name of a tag because that is
probably what we will need to do in order to set the DKR contents in a
particular namespace. In fact, each DKR will probably have its own
personel namespace and its own set of custom tags essentially defined by
the user(s).
In the example DKR config I have been discussing, a top level item might
have the tage:
<DRKid category'='knowledge'...>content</DKRid>
where content may be a complete html document.
Best Regards,
Joe
------------------------------------------------------------------------
Double your manufacturer's warranty on all computers,
home appliances, and electronics AND win up to $500
towards your purchase!
http://click.egroups.com/1/3749/3/_/444287/_/956801230/
------------------------------------------------------------------------
Community email addresses:
Post message: unrev-II@onelist.com
Subscribe: unrev-II-subscribe@onelist.com
Unsubscribe: unrev-II-unsubscribe@onelist.com
List owner: unrev-II-owner@onelist.com
Shortcut URL to this page:
http://www.onelist.com/community/unrev-II
This archive was generated by hypermail 2b29 : Wed Apr 26 2000 - 19:14:48 PDT