<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Tech Articles</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/" />
    <link rel="self" type="application/atom+xml" href="http://webdesign.ghhutch.com/tech_articles/atom.xml" />
   <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2</id>
    <link rel="service.post" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2" title="Tech Articles" />
    <updated>2007-08-29T02:39:49Z</updated>
    
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.35</generator>
 
<entry>
    <title>Typography Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/typography_definition.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=31" title="Typography Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.31</id>
    
    <published>2007-08-29T02:27:36Z</published>
    <updated>2007-08-29T02:39:49Z</updated>
    
    <summary>The art and technique of arranging and formatting text.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="CSS" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[
<p>
The art and technique of arranging and formatting text.
</p>

<p>
Typography is the art and techniques of type design, modifying type glyphs, and arranging type. Type glyphs (characters) are created and modified using a variety of illustration techniques. The arrangement of type is the selection of typefaces, point size, line length, leading (line spacing) and letter spacing.
</p>

<p>
Typography is performed by typesetters, compositors, typographers, graphic artists, art directors, and clerical workers. Until the Digital Age, typography was a specialized occupation. Digitization opened up typography to new generations of visual designers and lay users.
</p>

<h2>Text Typeography</h2>
<p>
In traditional typography, text is composed to create a readable, coherent, and visually satisfying whole that works invisibly, without the awareness of the reader. Even distribution with a minimum of distractions and anomalies are aimed at producing clarity and transparency.
</p>
<p>
Choice of font(s) is perhaps the primary aspect of text typography—prose fiction, non-fiction, editorial, educational, religious, scientific, spiritual and commercial writing all have differing characteristics and requirements. For historic material, established text typefaces are frequently chosen according to a scheme of historical genre acquired by a long process of accretion, with considerable overlap between historical periods.
</p>
<p>
Contemporary books are more likely to be set with state-of-the-art seriffed "text romans" or "book romans" with design values echoing present-day design arts, which are closely based on traditional models such as those of Nicolas Jenson, Francesco Griffo (a punchcutter who created the model for Aldine typefaces), and Claude Garamond. With their more specialized requirements, newspapers and magazines rely on compact, tightly-fitted text romans specially designed for the task, which offer maximum flexibility, readability and efficient use of page space. Sans serif text fonts are often used for introductory paragraphs, incidental text and whole short articles. A current fashion is to pair sans serif type for headings with a high-performance seriffed font of matching style for the text of an article.
</p>
<p>
The text layout, tone or color of set matter, and the interplay of text with white space of the page and other graphic elements combine to impart a "feel" or "resonance" to the subject matter. With printed media typographers are also concerned with binding margins, paper selection and printing methods.
</p>
<p>
Typography is modulated by Orthography and linguistics, word structures, word frequencies, morphology, phonetic constructs and linguistic syntax. Typography also is subject to specific cultural conventions. For example, in French it is customary to insert a non-breaking space before a colon (:) or semicolon (;) in a sentence, while in English it is not.
</p>

<h2>Readability and legibility</h2>
<p>
Readability and legibility are often confused. Readability is most often and more properly used to describe the ease with which written language is read and understood – it concerns the difficulty of the language itself, not its appearance. Factors that affect readability include sentence and word length, and the frequency of uncommon words.
</p>
<p>
In contrast, legibility describes how easily or comfortably a typeset text can be read. It is not connected with content or language, but rather with the size and appearance of the printed or displayed text.
</p>
<p>
Studies of legibility have examined a wide range of factors including type size, type design (for example, comparing serif vs sans serif type, italic type vs roman type), line length, line spacing, colour contrast, the design of right-hand edge (for example, justification (straight right hand edge) vs ranged left, and whether hyphenated). Legibility research was published from the late nineteenth century on, but the overall finding has been that the reading process is remarkably robust, and that significant differences are hard to find. So comparative studies of seriffed vs sans serif type, or justified vs unjustified type, have failed to settle the argument over which is best. (Serifs are the small cross-strokes at the end of letters in fonts such as Times; sans serif fonts, such as Arial, lack these cross strokes). Unfortunately, the fashion for legibility research was over by the time that revolutionary changes in printing and display technology (ie, laser printing and PC display screens) made it actually of potential interest.
</p>
<p>
Legibility is usually measured through speed of reading, with comprehension scores used to check for effectiveness (ie, not a rushed or careless read). For example, Miles Tinker, who published numerous studies from the 1930s to the 1960s, used a speed of reading test that required participants to spot incongruous words as an effectiveness filter.
</p>
<p>
These days, legibility research tends to be limited to critical issues, or the testing of specific design solutions (for example, when new typefaces are developed). Examples of critical issues include typefaces (also called fonts) for people with visual impairment, and typefaces for highway signs, or for other conditions where legibility may make a key difference.
</p>
<p>
Much of the legibility research literature is somewhat atheoretical - various factors were tested individually or in combination (inevitably so, as the different factors are interdependent), but many tests were carried out in the absence of a model of reading or visual perception. Some typographers believe that the overall word shape is very important in readability, and that letter by letter recognition (sometimes known as parallel letterwise recognition) is either wrong, less important, or not the entire picture. Studies that distinguish between the two models have favored parallel letterwise recognition, and the latter is widely accepted by cognitive psychologists (citation?).
</p>
<p>
Some commonly agreed findings of legibility research include: text set in lower case is more legible than text set all in upper case (capitals), presumably because lower case letter structures and word shapes are more distinctive, having greater saliency with the presence of extenders (ascenders, descenders and other projecting parts); regular upright type (roman) is found to be more legible that italics, contrast, without dazzling brightness, has also been found to be important, with black on yellow/cream being most effective; positive images (eg, black on white) are easier to read than negative or reversed (eg, white on black); the upper portions of letters play a stonger part than the lower portions in the recognition process; legibility is compromised by letterspacing, word spacing and leading that are too tight or too loose. Generous vertical space separates lines of text, making it easier for the eye to distinguish one line from the next, or previous line. Poorly designed fonts and those that are too tightly or loosely fitted can also result in poor legibility.
</p>
]]>
    </content>
</entry>
<entry>
    <title>Baking vs Frying Templates</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/baking_vs_frying_templates.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=13" title="Baking vs Frying Templates" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.13</id>
    
    <published>2007-08-27T21:30:42Z</published>
    <updated>2007-08-28T02:10:25Z</updated>
    
    <summary>The argument of baking and frying is determining where and when to apply presentation to data. In this article I will describe some of the pros, cons and selection criteria of baking vs frying templates</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Templating" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<h3>Baking vs Frying at a High Level</h3>
<p>
The argument of baking and frying is determining where and when to apply presentation to your information.
</p>

<p>The baking vs frying argument has been around for some time now.  When I was first introduced to content management I was taught that the baking approach was the best although I have come to the conclusion that the best approach to templating is dependant on your requirements.  In this article I will describe some of the pros, cons and selection criteria of baking vs frying templates.</p>

<h3>Baking</h3>
<h4>Overview</h4>
<p>
The baking approach is common in systems that consists of static non-dynamic data.  The baking approach generally consists of a presentation template, data files, a merge process (baking) and output files.  The merge process pulls the data and presentation together to generate output files that are a combination of both information and formatting.  The output files are generally ready to be consumed by users as is.  The baking process usually takes place before a user consumes data in an external system.
</p>
<h4>Pros</h4>
<ul>
<li>Less processing needed to consume a page</li>
<li>Performance</li>
<li>Simplified delivery of information</li>
<li>Control of display on the CMS (<a href="http://webdesign.ghhutch.com/tech_articles/2006/08/what_is_content_management.php">Content Management System</a>) or  merge side.  This approach does not require a redeployment of a web application such as an EAR (Enterprise Archive) or WAR (Web Archive).</li>
<li>Low impact on users</li>
</ul>
<h4>Cons</h4>
<ul>
<li>Baking aka merging large volumes of information is time consuming</li>
<li>Merging may be complicated</li>
<li>Baking may cause some presentation logic to be embeded into the merging system</li>
<li>More effort required by content contributor</li>
<li>Requires a robust publishing system</li>
</ul>

<h3>Frying</h3>
<h4>Overview</h4>
<p>
The frying approach is common in systems that consists of dynamic non-static data.   The frying approach generally consists of a presentation template, data files, and a merge process (frying).  The merge process pulls the data and presentation together and stores the output in memory or cache at the time of the request.  The frying process usually takes place when a user requests a the information. 
</p>
<h4>Pros</h4>
<ul>
<li>Provides control of display on the consumption/delivery side</li>
<li>Simple publish of presentation/layout. "Publish Once"</li>
<li>Control of display is on the consumption side.</li>
<li>Generally better for personalization. (This approach is often used in Portal technology)</li>
</ul>
<h4>Cons</h4>
<ul>
<li>Presentation templates can be very complex and contain proprietary markup.</li>
<li>Impacts performance..</li>
<li>My require a deployment of ear/war to make changes to the presentation.  (This is only true if the layouts being used are part of the web application.</li>
<li>More effort is required by a template designer</li>
</ul>
<h3>Selection Criteria</h3>
<p>This section of the article will hopefully help you choose between a frying or baking system.  This criteria is dependant on many factors but here are a few to get you started thinking about which approach is best for you.
</p>
<p>
Answer yes or no to the following questions?
</p>
<ol>
<li>Does your system provide a robust publishing mechanism?</li>
<li>Does your system require personalization?</li>
<li>Does your system require large amounts of dynamic information?</li>
<li>Does your system contain large amounts of static information?</li>
<li>Will the presentation of your system change frequently?</li>
<li>Is performance a high priority requirement for your system?</li>
</ol>
<p>
If you answered yes to number 1, 4, and 6 I would reccomend selecting a baking templating approach.  If you answered yes to 2 ,3 , and 5 I would reccomend selecting a frying templating approach.  The selection criteria is only a simple set of questions that at a high level may point you in the right direction.
</p>
<p>
On several projects I have found myself somewhere in between the lines of baking vs frying.  There is no rule that limits you to only selecting one.  The best solution for you may be a blend of the two approaches.  For example imagine part of your system is an archive of static information and baking is the best approach but the other part of your system is a highly personalized dynamic application.  In this case I would reccomend blending.  At the end of the day you must carefully analyze the requirements for your system and prioritize them.  Take the highest priority requirements and see if they fall within a baking or frying approach.
</p>
<h3>Conclusion</h3>
<p>
Hopefully this article was informational and helped you better understand the difference between a baking and frying approach.  This is a subject that will be visted and revisted when dealing with presenting information.  Always remember that systems evolve and so do the people consuming it.  There are often waves of popularity between the two approaches based on the hot technolgy that is out there.  In my opinion it is important to remain objective and develop a solid approach that works and keeps your users and customers happy.
</p>]]>
    </content>
</entry>
<entry>
    <title>PHP Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/php_definition.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=29" title="PHP Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.29</id>
    
    <published>2007-08-20T03:06:58Z</published>
    <updated>2007-08-27T02:10:14Z</updated>
    
    <summary>PHP is a reflective programming language originally designed for producing dynamic web pages. PHP is used mainly in server-side scripting, but can be used from a command line interface or in standalone graphical applications. Textual User Interfaces can also be created using ncurses. PHP is a recursive acronym for PHP: Hypertext Preprocessor.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="PHP" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>PHP is a reflective programming language originally designed for producing dynamic web pages. PHP is used mainly in server-side scripting, but can be used from a command line interface or in standalone graphical applications. Textual User Interfaces can also be created using ncurses. PHP is a recursive acronym for "PHP: Hypertext Preprocessor".</p>

<p>The main implementation is produced by The PHP Group and released under the PHP License. It is considered to be free software by the Free Software Foundation. This implementation serves to define a de facto standard for PHP, as there is no formal specification.</p>

<p>Currently, two major versions of PHP are being actively developed: 5.x and 4.4.x; on July 13, 2007, the PHP group announced that active development on PHP4 will cease by December 31, 2007, however, critical security updates will be provided until August 8, 2008.</p>]]>
    </content>
</entry>
<entry>
    <title>Javascript Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/javascript_definition.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=28" title="Javascript Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.28</id>
    
    <published>2007-08-20T03:00:10Z</published>
    <updated>2007-08-20T03:01:51Z</updated>
    
    <summary>JavaScript is a scripting language most often used for client-side web development.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Javascript" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>JavaScript is a scripting language most often used for client-side web development. Its standardized name is ECMAScript, though "JavaScript" is much more commonly used. "JavaScript" is actually Netscape Communications Corporation's (and now the Mozilla Foundation's) implementation of the ECMAScript standard.</p>

<p>JavaScript is a dynamic, weakly typed, prototype-based language with first-class functions. JavaScript was influenced by many languages and was designed to have a similar look to Java, but be easier for non-programmers to work with. The language is best known for its use in websites (as client-side JavaScript), but is also used to enable scripting access to objects embedded in other applications.</p>

<p>Despite the name, JavaScript is unrelated to the Java programming language; though both have a common debt to C syntax. The language was renamed from LiveScript in a co-marketing deal between Netscape and Sun in exchange for Netscape bundling Sun's Java runtime with their browser, which was dominant at the time. JavaScript semantics is much more similar to the Self programming language.</p>

<p>"JavaScript" is a registered trademark of Sun Microsystems, Inc. It was used under license for technology invented and implemented by Netscape Communications and current entities such as the Mozilla Foundation.<br />
</p>]]>
    </content>
</entry>
<entry>
    <title>CSS Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/css_definition.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=27" title="CSS Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.27</id>
    
    <published>2007-08-20T02:47:01Z</published>
    <updated>2007-08-20T03:03:57Z</updated>
    
    <summary>A Cascading Style Sheet (CSS) provides the ability to separate the layout and styles of a web page from the data or information.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="CSS" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>A Cascading Style Sheet (CSS) provides the ability to separate the layout and styles of a web page from the data or information. Styles such as fonts, font sizes, margins, can be specified in one place, then the Web pages feed off this one master list, with the styles cascading throughout the page or an entire site.</p>

<h3>CSS 1</h3>

<p>The CSS 1 specicifcation for level 1 of the Cascading Style Sheet mechanism can be found here(<a href="http://www.w3.org/TR/REC-CSS1">CSS1</a>). CSS1 is a simple style sheet mechanism that allows authors and readers to attach style (e.g. fonts, colors and spacing) to HTML documents. The CSS1 language is human readable and writable, and expresses style in common desktop publishing terminology. </p>

<p>One of the fundamental features of CSS is that style sheets cascade; authors can attach a preferred style sheet, while the reader may have a personal style sheet to adjust for human or technological handicaps. The rules for resolving conflicts between different style sheets are defined in this specification. </p>

<h3>CSS 2</h3>

<p>The CSS 2 specification defines Cascading Style Sheets, level 2 can be found here (<a href="http://www.w3.org/TR/REC-CSS2/">CSS2</a>). CSS2 is a style sheet language that allows authors and users to attach style (e.g., fonts, spacing, and aural cues) to structured documents (e.g., HTML documents and XML applications). By separating the presentation style of documents from the content of documents, CSS2 simplifies Web authoring and site maintenance. </p>

<p>CSS2 builds on CSS1 (see [CSS1]) and, with very few exceptions, all valid CSS1 style sheets are valid CSS2 style sheets. CSS2 supports media-specific style sheets so that authors may tailor the presentation of their documents to visual browsers, aural devices, printers, braille devices, handheld devices, etc. This specification also supports content positioning, downloadable fonts, table layout, features for internationalization, automatic counters and numbering, and some properties related to user interface. </p>

<h3>CSS 3</h3>

<p>The CSS 3 specification is still being developed at this point.  <a href="http://www.w3.org/Style/CSS/current-work.html#CSS3">Learn more about CSS3.</a></p>]]>
    </content>
</entry>
<entry>
    <title>Javascript Email Validation</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/javascript_email_validation.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=26" title="Javascript Email Validation" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.26</id>
    
    <published>2007-08-19T23:31:40Z</published>
    <updated>2007-08-19T23:46:33Z</updated>
    
    <summary>This is a simple e-mail address validation script. While it is not too sophisticated, it does provide the basic validation function. This function will return false if an email address is not valid.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Javascript" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>
This is a simple e-mail address validation script. While it is not too sophisticated, it does provide the basic validation function. This function will return false if an email address is not valid.
</p>

<b>

<textarea rows="18" style="width:90%;">
/**
 * Validates Email Address
 * 
 *  @value	email address entered into form
 */
function isEmail(value)
{
                var regEx = /^([a-zA-Z0-9_\.\-])+\@(([a-zA-Z0-9\-])+\.)+([a-zA-Z0-9]{2,4})+$/;
	if (regEx.test(value)){
		return true;
	}else{
		return false;
	}
}
</textarea>
</pre>
</iframe>
</b>
]]>
    </content>
</entry>
<entry>
    <title>Templating Definitions</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/templating_definitions.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=25" title="Templating Definitions" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.25</id>
    
    <published>2007-08-19T18:09:15Z</published>
    <updated>2007-08-19T18:12:06Z</updated>
    
    <summary>Page template, a pre-developed page layout used to create new pages (paper or electronic) from the same design, pattern, or style. </summary>
    <author>
        <name></name>
        
    </author>
            <category term="Templating" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<ul>
<li>
Page template, a pre-developed page layout used to create new pages (paper or electronic) from the same design, pattern, or style. </li>
<li>
Mail-merge template, a specific kind of word processing document used to generate mailing lists.</li>
<li> 
Master page, a page template in a multiple page desktop publishing software data file that duplicates and globally edits graphic elements across multiple pages.
</li>
<li>
Template (file format), any of various standardized file types used by computer software as a pre-formatted example on which to base other documents or files. 
</li>
<li>
Template (word processing), a "document template" for use in configuring word processing software.
</li>
<li> 
Style sheet, a template for globally editing the format of graphic elements and text on a page. 
</li>
<li>
Web template, used in web application development in conjunction with a web template system.
</li>
</ul> ]]>
    </content>
</entry>
<entry>
    <title>Javascript Show-Hide Element</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/javascript_showhide_element.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=24" title="Javascript Show-Hide Element" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.24</id>
    
    <published>2007-08-19T16:40:31Z</published>
    <updated>2007-08-28T03:06:50Z</updated>
    
    <summary>The following Javascript code will show or hide an html element.  This can be used for a variety of tasks but is useful in forms when displaying or hiding fields.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Javascript" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>The following Javascript code will show or hide an html element.  This can be used for a variety of tasks but is useful in forms when displaying or hiding fields.</p>
<h3>
Show Element
</h3>
<textarea cols="" rows="15">
/**
 * Show an HTML element 
 * 
 *  @elemID     The ID of the html element that will be displayed
 */
function showElement(elemID)
{
	if(document.getElementById(elemID))
	{
	document.getElementById(elemID).style.display="block";
	}
}
</textarea>
<br/>
<h3>
Hide Element
</h3>
<textarea cols="" rows="15">
/**
 * Hide an HTML element 
 * 
 *  @elemID     The ID of the html element that will be hidden
 */
function hideElement(elemID)
{
	if(document.getElementById(elemID))
	{
	document.getElementById(elemID).style.display="none";
	}    
}
</textarea>]]>
    </content>
</entry>
<entry>
    <title>Versioning Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/versioning_definition.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=23" title="Versioning Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.23</id>
    
    <published>2007-08-19T16:30:57Z</published>
    <updated>2007-08-19T16:34:10Z</updated>
    
    <summary>A versioning file system is a file system which provides for the concurrent existence of several versions of a file; a form of revision control. In their most common form, they keep a configurable number of older copies of a file around, creating a new copy of the file at every change.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Versioning" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>A versioning file system is a file system which provides for the concurrent existence of several versions of a file; a form of revision control. In their most common form, they keep a configurable number of older copies of a file around, creating a new copy of the file at every change. Some limit the number of changes per minute or per hour to avoid storing large numbers of trivial changes. A different approach is taking periodic snapshots and making their contents accessible with similar semantics to normal file access.</p>

<p>A versioning file system is similar to a periodic backup, with several key differences. First, backups normally go to separate media; versioning file systems write to the same hard drive (and normally the same folder, directory, or local partition). Second, backups are normally triggered on a timed basis; versioning occurs when the file changes. Third, backups are usually system-wide or partition-wide; versioning occurs independently on a file-by-file basis.</p>

<p>Versioning file systems provide some of the features of revision control systems. However, unlike most revision control systems, they are transparent.</p>]]>
    </content>
</entry>
<entry>
    <title>Compliance Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/compliance_definition.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=22" title="Compliance Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.22</id>
    
    <published>2007-08-19T16:26:15Z</published>
    <updated>2007-08-19T16:27:18Z</updated>
    
    <summary>Compliance is either a state of being in accordance with established guidelines, specifications, or legislation or the process of becoming so.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Compliance" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>Compliance is either a state of being in accordance with established guidelines, specifications, or legislation or the process of becoming so. Software, for example, may be developed in compliance with specifications created by some standards body, such as the Institute of Electrical and Electronics Engineers (IEEE), and may be distributed in compliance with the vendor's licensing agreement. In the legal system, compliance usually refers to behavior in accordance with legislation, such as the United States' Can Spam Act of 2003, the Sarbanes-Oxley Act (SOX) of 2002, or HIPAA (United States Health Insurance Portability and Accountability Act of 1996).</p>

<p>Compliance in a regulatory context is a prevalent business concern, perhaps because of an ever-increasing number of regulations and a fairly widespread lack of understanding about what is required for a company to be in compliance with new legislation. In the financial sector, SOX was enacted in response to the high-profile Enron and WorldCom financial scandals to protect shareholders and the general public from accounting errors and fraudulent practices in the enterprise. In the healthcare sector, HIPAA Title II includes an administrative simplification section which mandates standardization of healthcare-related information systems.</p>

<p>As compliance has increasingly become a concern of corporate management, corporations are turning to specialized software, consultancies, and even a new job title, the Chief Compliance Officer (CCO). </p>]]>
    </content>
</entry>
<entry>
    <title>Business Process Management Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/business_process_management_de.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=21" title="Business Process Management Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.21</id>
    
    <published>2007-08-19T16:19:14Z</published>
    <updated>2007-08-19T16:21:01Z</updated>
    
    <summary>Business process management (BPM) is a field of knowledge at the intersection between management and information technology, encompassing methods, techniques and tools to design, enact, control, and analyze operational business processes involving humans, organizations, applications, documents and other sources of information.[</summary>
    <author>
        <name></name>
        
    </author>
            <category term="BPM" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>Business process management (BPM) is a field of knowledge at the intersection between management and information technology, encompassing methods, techniques and tools to design, enact, control, and analyze operational business processes involving humans, organizations, applications, documents and other sources of information.[1] The term 'operational business processes' refers to repetitive business processes performed by organizations in the context of their day-to-day operations, as opposed to strategic decision-making processes which are performed by the top-level management of an organization. BPM differs from business process reengineering, a management approach popular in the 1990s, in that it does not aim at one-off revolutionary changes to business processes, but at their continuous evolution. In addition, BPM usually combines management methods with information technology.</p>
<p>
BPM covers activities performed by organizations to manage and, if necessary, to improve their business processes. While such a goal is hardly new, software tools called business process management systems (BPM systems) have made such activities faster and cheaper. BPM systems monitor the execution of the business processes so that managers can analyze and change processes in response to data, rather than just a hunch.</p>
]]>
    </content>
</entry>
<entry>
    <title>Lifecycle Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/lifecycle_definition.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=20" title="Lifecycle Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.20</id>
    
    <published>2007-08-19T16:15:39Z</published>
    <updated>2007-08-19T16:16:38Z</updated>
    
    <summary>The various phases that content moves through, such as authoring, review, management, delivery, and archiving. </summary>
    <author>
        <name></name>
        
    </author>
            <category term="Lifecycle" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>The various phases that content moves through, such as authoring, review, management, delivery, and archiving.</p>]]>
    </content>
</entry>
<entry>
    <title>Document Management Defintion</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/document_management_defintion.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=19" title="Document Management Defintion" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.19</id>
    
    <published>2007-08-19T16:13:43Z</published>
    <updated>2007-08-19T16:14:46Z</updated>
    
    <summary>DM is highly similarly and overlaps with Content Management. Document management applies specifically to the management of discreet documents and images throughout their lifecycle. </summary>
    <author>
        <name></name>
        
    </author>
            <category term="Content Management" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>DM is highly similarly and overlaps with Content Management. Document management applies specifically to the management of discreet documents and images throughout their lifecycle. Typical functionality includes acquisition, organization, versioning, access control, and archiving. </p>]]>
    </content>
</entry>
<entry>
    <title>Enterprise Content Management Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/enterprise_content_management.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=18" title="Enterprise Content Management Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.18</id>
    
    <published>2007-08-19T16:12:10Z</published>
    <updated>2007-08-27T02:33:53Z</updated>
    
    <summary>ECM is a broad term that means many different things to many different people. Typically EMC implies the acquisition and management of both structured and unstructured content that is dispersed across a number of different repositories, often described as information silos.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="Content Management" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>ECM is a broad term that means many different things to many different people. Typically EMC implies the acquisition and management of both structured and unstructured content that is dispersed across a number of different repositories, often described as "information silos". ECM technologies typically are capable of managing structured content, unstructured content, email, images, raw print data, and other digital assets. Increasingly ECM implies the ability to manage legal compliance with regards to privacy, content metadata, and records management. </p>]]>
    </content>
</entry>
<entry>
    <title>Web Content Management Definition</title>
    <link rel="alternate" type="text/html" href="http://webdesign.ghhutch.com/tech_articles/2007/08/web_content_management_definit.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.grahamhutchinson.com/mt/mt-atom.cgi/weblog/blog_id=2/entry_id=17" title="Web Content Management Definition" />
    <id>tag:webdesign.ghhutch.com,2007:/tech_articles//2.17</id>
    
    <published>2007-08-19T16:07:26Z</published>
    <updated>2007-08-19T16:09:47Z</updated>
    
    <summary>WCM is the management of both structure and unstructured content that is delivered over the Internet, typically via a web site.</summary>
    <author>
        <name></name>
        
    </author>
            <category term="WCM" />
    
    <content type="html" xml:lang="en" xml:base="http://webdesign.ghhutch.com/tech_articles/">
        
        <![CDATA[<p>WCM is the management of both structure and unstructured content that is delivered over the Internet, typically via a web site. Web Content Management includes content creation, site management, workflow, access control, and delivery. Many Enterprise Content Management (ECM) systems include WCM capabilities. Many Web Content Management systems aspire to ECM capabilities, but typically lack the ability to integrate with multiple repositories, acquire data directly, and/or ensure any sort of legal compliance.</p>
]]>
    </content>
</entry>

</feed> 

