On 2/3/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > On 2/3/06, Andreas Hartmann <[EMAIL PROTECTED]> wrote:
> >> That's not a vote, but it would be appreciated if you could state
> >> your opinion. I'd like to emphasize that this discussion is not
> >> about the API itself, but only about the terms we use. So please
> >> don't go and complain about the concept of areas or language versions.
> >> These issues can be discussed later on.
> >
> > Well, that eliminates some of my ideas. The problem is the technology
> > follows the terminology.
>
> It's the chicken+egg problem. This thread is just to create a
> basis for discussion. Class names etc. can be decided later.
> But I see the problem, deciding on the terms can depend on how
> it's implemented.
>
> Thanks a lot for your comments, here's how I'd summarize
> your statements (comments below):
>
>
> > ----
> >
> > A website in Lenya is called a
> >
> > - publication [+andreas] [+solprovider]
> > - site
> > - ...
> >
> > ----
> >
> > The resources of a website can exist at the same time in several
> >
> > - areas [+andreas]
> > - ...
> > - drop the concept [+solprovider]
> >
> > ----
> >
> > The entirety of plain information (without structuring) is called
> >
> > - content [+andreas]
> > - resources [+solprovider]
> > - ...
> >
> > ----
> >
> > The set of language versions of a piece of information is called
> >
> > - content node
> > - content item [+andreas]
> > - document
> > - resource [+solprovider]
> > - ...
> >
> > ----
> >
> > A specific language version is called
> >
> > - content item
> > - language version [+andreas] [+solprovider]
> > - document
> > - ...
> >
> > ----
> >
> > A version in the history of a language version is called
> >
> > - (history) version [+andreas] [+solprovider]
> > - ...
> >
> > ----
> >
> > The structuring information (there may be several of them) are
> >
> > - sites
> > - structures [+andreas]
> > - navigations
> > - indizes [+solprovider]
> >
> > (maybe we have to make a distinction between "structure" and "navigation")
> >
> > ----
> >
> > A node in the structure is called
> >
> > - (structure/index) node [+andreas] [+solprovider]
> > - site node
> > - navigation item
> > - ...
> >
> >
>
>
>
> >> ----
> >> A website in Lenya is called a
> >> - publication [+1]
> >> - site
> >
> > Publication: Collection of data and special processing instructions.
> >
> > Website: A collection of Publications and other material accessed
> > through a single Internet domain.
> >
> >> ----
> >> The resources of a website can exist at the same time in several
> >> - areas [+1]
> > Cannot comment since this terminology hurts the technology.
> >
> >> ----
> >> The entirety of plain information (without structuring) is called
> >> - content [+1]
> >> - resources
> >
> > Decision time. Will "Assets" (images and other files) be stored with
> > the documents?
>
> IMO yes, all of them should be treated in the same way.
>
>
> > Historically, "Content" refers only to a collection of "Documents",
> > and "Resources" referred a collection of "Assets". If "Assets" are
> > not included, we should keep the term "Content". Either term
> > ("Content" or "Resources") is good for the collection of Documents and
> > Assets, but changing it to "Resources" may reduce confusion with the
> > historical definition of "Content".
> >
> >
> >> ----
> >> The set of language versions of a piece of information is called
> >> - content node
> >> - content item [+1]
> >> - document
> >> - resource
> >
> > I prefer "Document" for an XML Document, because that is what XML and
> > Lenya1.2 call it.
>
> OK, but that would be a specialization of "content item" / "resource".
>
>
> > To refer to something that could be either a Document or an Asset, I
> > prefer "Resource". "Content Node" uses two words for the same
> > concept.
>
> That would mean
>
> Resource
> - Document extends Resource (XML)
> - Asset extends Resource (binary, text, ...)
>
> [...]
>
> > For me, the following text sounds quite good:
> > In Lenya, a Website consists of one or more Publications. A
> > Publication is a collection of Resources (Documents and Assets), and
> > any special functionality. Documents (and soon Assets) are
> > maintained by Language, and each edit creates a new Version for
> > historical documentation and the ability to rollback to an older
> > Version. Indexes provide selection of Documents for use by various
> > functionality, including Navigation Elements which provide easy access
> > to the Documents through the web interface.
>
> That sounds good to me as well. "Resource" and "content item" are
> both fine with me. The structure vs. index question needs IMO
> some more discussion. "Structure" sounds more like a static way to
> organize things, "index" rather like a dynamic way. But maybe that's
> only my personal perception.
>
> -- Andreas
I would advise against the continued use of the word "resource". It
has almost no definite meaning in English, but if anything it means a
thing that supports something else, which is closer to what an asset
is than the union of assets and documents. "Content Item" is far
better, IMHO, and in my experience is closer to an industry standard
term.
I prefer "site" over "publication".
I prefer "navigation tree" over "structure" or "index".
I wonder if we shouldn't compile a table of terms that other CMS's
(both OS & commercial) use, and try to use the terms that most have in
common for the same concepts. I suppose between us all we have had
exposure to a large number of other CMS's.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
