El mié, 08-02-2006 a las 03:06 -0500, [EMAIL PROTECTED] escribió: > Rules for Determining Terminology >
... > 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*. > 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! ... > > 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. > "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. 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. > "I created an > Asset" (meaning uploaded a file) is understood by users of Lenya 1.2. > "I created a Resource" would be understood by most people. Lenya 1.2 > used "Resources" for a variety of additions: static graphics, storage > of "Assets", presentation configuration (CSS and i18n), and software > plug-ins (such as editors). That was confusing to developers, and > created a messy datastore. Lenya 1.4 has not defined "Resource" yet, > but should relate to one or more of Lenya 1.2's definitions. Software > plug-ins are being defined as "Modules". All graphics should be > "Assets" (Why allow static graphics? Let everything be editable, and > improve security so the security granted by requiring file system > access is unnecessary.) Presentation configuration will be moved > inside Modules. 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? 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". > 7. Lenya 1.2 defines "Publication" as "Content and related processing > instructions" where "Content" is defined as "(XML) Documents and > related Assets" where "Assets" is defined as "uploaded files". > People keep suggesting using "Site", "Website", "Book", and other > terms for this concept. 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." > 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. > === > On 2/7/06, Thorsten Scherler <[EMAIL PROTECTED]> wrote: > > What both models of http://wiki.apache.org/lenya/GlossaryStructure have > > in common is that "content" is stored in a Publication. Now Andreas is > > using frequently the word "structure" in referring to the sitetree or > > like solprovider is calling it index of a publication. Seeing it from a > > different angle a sitetree or index or structure is nothing else then > > the typical table of content (toc) of a (text) book. > > 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 write 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. > 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 salu2 -- Thorsten Scherler COO Spain Wyona Inc. - Open Source Content Management - Apache Lenya http://www.wyona.com http://lenya.apache.org [EMAIL PROTECTED] [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
