@funzel: Probably we can introduce something like
Contexts? (some examples stolen from
comment-Zohar's Open Issues With SnipSnap-11)
Context is important in a Meta-Language that is used to define Meta-Models, because it defines the circumstances in which information within the system is viewed, analyzed, impacted, etc.
google glossaryA path is something like dir1/dir2/.../dirn.
I don't know if the Context should be the first (dir1/../dir(n-1)) or the last entries (dir2/../dirn) in a path.
Some examples:
Database/Java would give JDBC. Probably Java/Database would give the same.
The implementation could straight-forward from the definition. This means a "ferrer" instead of "referrer" have to be introduced to see if many users visit one snip from another one. To determine which snip can work as a context you could use a artificial measure - i think there should be a view count e.g. more than 1000 hits or something like this could work. Probably it could be done via
Labels?
Some predefined Contexts should be:
- comments
- sub-postings (via titles in the weblog or headings in a normal snips) start/2003-01-14/MySubject would select 2003-01-14 from start
- via labels (types and so on)
Important notices
- The snip remains his unique name to identify himself.
- The purpose of the path is only to find topics faster and to structure the content in a "dynamic" way.
- The path can be used to run some investigations to find out, how people tend to search and learn (how can we structure talks, which prerequisites should we use?)