At Thu, 09 Dec 1999 13:39:33 -0600, "Todd Daniel Woodward"
<[EMAIL PROTECTED]>
wrote:
>
>>I wonder if symbolic links are the right conceptual model
>here.
>>Really what you have in the articles is two types of
>information:
>>'content,' with components that are closely bound and are
>>relatively isolated from anything external; and then apart
>from
>>content some kind of 'package', consisting of components
>that
>>are configured to arrange and express the article content
>in
>>the environment in which it's referenced.
>>
>>This suggests that article_content might be disconnected
>from
>>topics altogether, and then joined with (at least one)
>>article_package, of which there may be many versions
>>registered under different topics, but all referencing the
>>same article_content.
>>
>>Maybe looking at it this way gets us out of having to think
>>about the problems of which is the 'master' article, and
>where
>>should it be located.
>>
>>Make any sense, or does this just muddy the waters?
Hmmm.. having read this suggested something to me:
What about a meta-data arrangement? Let me explain...
Instead of a straight topic-article arrangement, we could go with an arrangement
where we had two, independent sets of data. One would be an "article-topic"
arrangement, similar to the current one. The other(s) would be "sitemaps"
- they would reference the articles in the other set, adding relevant, site
specific data, and be accesed directly by the sites.
To restate:
Two sets of data:
o Meta Data - one
- contains an "article/topic" hierarchy
- consists of solely "content" data - ie, the author, abstract,
content
fields, as well as some "meta-data" - internal comments, flags, etc. not
relating to display...
o Site Map(s) - more than one, such as when you have more than one site.
- contains an "article/topic" hierarchy
- articles...
- reference an article from the MetaData tree.
- contain display data (format, location in site, related
articles on
site, etc.)
- topics....
- may either be created from scratch or reference a topic from
the MetaData
tree
- contain display data, descriptions, etc.
- optional "override" ability - ie, to override an abstract
which doesn't
quite fit, or trim titles, or the like. (may just be option to load alternate
abstract from the MetaData tree.)
How's this sound?
Ben Garney
LHS Webmaster
www.lincolnhs.pps.k12.or.us
IMPORTANT NOTICE: If you are not using HushMail, this message could have been
read easily by the many people who have access to your open personal email messages.
Get your FREE, totally secure email address at http://www.hushmail.com.
--
This is The Midgard Project's mailing list. For more information,
please visit the project's web site at http://www.midgard-project.org
To unsubscribe the list, send an empty email message to address
[EMAIL PROTECTED]
