On 2/8/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > El mié, 08-02-2006 a las 03:06 -0500, [EMAIL PROTECTED] escribió: > > 2. General Usage defines "Document" as "a single unit of textual > > information". > ...and that is exactly my problem of this word in lenya. It is not > (better does not have to be) a *single* unit of textual information! > Further it is *not* limited to *textual information*.
Please give examples. Or maybe it is because (in my mind) a "Document" is a single piece of textual information, and a "Page" is the single unit displayed to a visitor. If you use "Document" for both definitions, things get very confused. Lenya adds navigation and presentation to Documents to create a Page. > > A Related Technology (XML) defines "Document" as "a > > single unit of textual information conforming to the XML > > specification". A Previous Version (Lenya 1.2) defines "Document" as > > "a single unit of textual information conforming to the XML > > specification with specified security and workflow". No other > > definition is allowed. > > This implies that a document *cannot* contain other then "textual > information" which is not reflecting the reality of the usage in lenya > nor on this list! See above. > > 6. No software uses the term "Nugget". > That is why it is perfect. ;-) > > The phrase "I created a > > Nugget" currently has no meaning. > Well put it like "I created a(n) (information/content) nugget". Then it > has perfect meaning. Now you are using two words where previously one was sufficient. > > "I created a Document" can be > > understood by people who are barely computer literate. > For "people who are barely computer literate" that may mean something > else then we have here. I was demonstrating the ubiquitousness of the term and its definition. > More, a document is a unit, like you pointed out > above, of textual information, coming back to a svg drawing that would > not fit this "document" definition, but still I consider it as an > information unit/nugget. SVG is XML. A unit of SVG data is a Document. The resulting image could be saved as an Asset (losing its dynamic abilities) or saved in a cache by the "svg2image" Module. > > While none of the old definitions of "Resource" are > > needed, the word is already used by Lenya, and should be used before > > adding a new word. > Well http://en.wikipedia.org/wiki/Resource > "Resource (economics), commodities and human resources used in the > production of goods and services. > Resource (computer science), valuable information" > > Resources has for me the same sweeping meaning like the word "thing". It > is everything and nothing. What is the difference for you between > document and resources? Why should we keep on using a definition that > only confuses? According to your source, "Resource" is "valuable information". All the units under Content are "valuable information". Yes, it is more generic than "Document" and "Asset", which is why "Resource" is a good term as the generic for both. > I do not follow and see the logic of the statement "the word is already > used by Lenya, and should be used before adding a new word". For Lenya people, there is already a an entry in the brain for "Resource". The definition is rather blurry, but the entry exists. Reusing that entry requires changing the definition. Adding a new term requires creating a new entry, which increases the memory requirements. > > General Usage defines "Publication" as "A > > specific issue of a public work including textual information". The > > output of a Lenya 1.2 Publication is close enough to the General Usage > > definition that very few people have been confused by the term. If it > > works, do not break it. > Well, it depends where you turn to look up "general usage". ;-) > http://en.wikipedia.org/wiki/Publication > "The word publication means the act of publishing, and it also means any > writing of which copies are published, and any website. Among > publications are books, and periodicals, the latter including magazines, > scholarly journals, and newspapers." Yes, I skipped the alternate definitions of "something that regularly publishes {definition #1}", and "the act of publishing {definition #1}". A Lenya Publication fits those definitions too, which is why "Publication" is so easily understood. > > 8. "Resource" is better than "ContentItem" because it contains fewer words. > ...but does not say anything about the function. IMO it should be > (content)nugget. See every post I have made about that subject. Both terms meet the functional requirements. "Resource" is shorter, and was previously used in Lenya. See above. > > === > > 1. "TableOfContent" is three words where we have been using one > > ("Sitetree"). It also implies a single structure. > No, that depends on the abstraction level. You are correct that a text > book has *one* toc but as well some has a glossary, ... That are other > ways to represent the structure on the book. There is also the "Index" and the "Index of Illustrations". :) > > 2. "TOC" is not immediately recognizable by people outside the printed > > paper industry. > Well, it is a common acronym > http://www.acronymfinder.com/af-query.asp?String=exact&Acronym=TOC&Find=Find I did not write "TOC" is not recognizable, just that it required thought for most people. Requiring people to think is a lost cause. If we used "TOC" as a term, how often would we see user-ML posts asking, "What is a TOC?" solprovider --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
