shins****@users*****
shins****@users*****
2006年 2月 7日 (火) 21:54:09 JST
Update of /cvsroot/jetspeed-japan/jetspeed-2-trans/ja/xdocs/guides In directory sf-cvs:/tmp/cvs-serv9842/ja/xdocs/guides Modified Files: guide-portal-design.xml Log Message: submitted by KATOH Yasufumi jetspeed-2-trans/ja/xdocs/guides/guide-portal-design.xml 1.1.1.1 -> 1.2 (modified) http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/jetspeed-japan/jetspeed-2-trans/ja/xdocs/guides/guide-portal-design.xml.diff?r1=1.1.1.1&r2=1.2 =================================================================== RCS file: jetspeed-2-trans/ja/xdocs/guides/guide-portal-design.xml,v retrieving revision 1.1.1.1 retrieving revision 1.2 diff -u -r1.1.1.1 -r1.2 --- guide-portal-design.xml 2005/12/16 03:43:36 1.1.1.1 +++ guide-portal-design.xml 2006/02/07 12:54:09 1.2 @@ -1,176 +1,290 @@ -<?xml version="1.0"?> -<!-- -Copyright 2004 The Apache Software Foundation - -Licensed under the Apache License, Version 2.0 (the "License"); -you may not use this file except in compliance with the License. -You may obtain a copy of the License at - - http://www.apache.org/licenses/LICENSE-2.0 - -Unless required by applicable law or agreed to in writing, software -distributed under the License is distributed on an "AS IS" BASIS, -WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. -See the License for the specific language governing permissions and -limitations under the License. ---> -<document> - <properties> - <title>Guide to Portal Design</title> - <subtitle>Documentation for Designers working with Jetspeed Portal Design</subtitle> - <authors> - <person name="David Sean Taylor" email="taylo****@apach*****"/> - </authors> - </properties> - <body> -<section name="Portal Design Introduction"> -<p> -The Java Portlet API (JSR-168) defines the Java standard interface for programming portlets. -The Java Portlet API specification enables interoperability between Portlets and Portals. -It is the standard specification for developing Java portlets. However the Java Portlet API -does not define standards for laying out and aggregating portlets and markup on a page. -The documentation here under "Portal Design" covers: -<ul> - <li><a href='psml.html'>Page Aggregation - see the section on PSML</a></li> - <li><a href='decorators.html'>Page and Portlet Decorators</a></li> - <li><a href='layouts.html'>Page Layouts</a></li> - <li><a href='jpt.html'>The Jetspeed Power Tool</a></li> - <li><a href='site.html'>The Site Content Model</a></li> - <li><a href='#Template Locators'>Template Locators</a></li> - <li><a href='#Terminology'>Terminology</a></li> -</ul> -</p> -</section> -<section name='Templates'> -<p> -Rendering one or more portlets into a portlet page is largely made up of the process of aggregating -portlets as dynamic content with templates. Jetspeed-2 makes use of Velocity templates in -creating a page layout. Although the Jetspeed-2 architecture fully supports the use of JSP templates for -decorators and layouts, the developers thus far have chosen Velocity as the tool of choice for writing -templates. There are two types of templates in Jetspeed: layouts and decorators. -The process of rendering a page is the combined aggregation of a layout template, -a page decorator template, a PSML definition, and one or more portlet decorator templates. -As of release 2.0, templates can be stored on the file system. In future releases, templates -will also be stored in a CMS backend for versioning. -</p> -<subsection name='Layout Templates'> -<p> -Layout templates are packaged in special Jetspeed-specific and deployable portlet applications. -Layout templates control the overall aggregation of a portal page. Layout templates are -combined with portlets, providing a component model for aggregation. Jetspeed-2 comes out -of the box with several layout components including one, two and three column layouts. -See the <a href='layouts.html'>Layout Documentation</a> for all available Layouts in the -default Jetspeed-2 system. Of course you can define and derive your own layouts. -</p> -</subsection> -<subsection name='Decorators'> - <p> -Decorator templates are packaged in special Jetspeed-specific and deployable archives. -Layout templates control the overall aggregation of a portal page. Layout templates are -combined with portlets, providing a component model for aggregation. Jetspeed-2 comes out -of the box with several layout components including one, two and three column layouts. -See the <a href='guide-decorators.html'>Decorator Documentation</a> for all available Layouts in the -default Jetspeed-2 system. Of course you can define and derive your own layouts. -</p> -</subsection> -</section> -<section name='Template Locators'> -<p> -Templates are located by the Jetspeed Template (and Decorator) Locator Component. These components -locates templates using a normalized name/value pair URL scheme. -using this scheme in what is called a 'normalized' URL to either a decorator or layout. -However, templating engines such as Velocity need to work with templates using paths to templates that are -relative of a document root. The <a href='guide-jpt.html'>Jetspeed Power Tool</a> facilitates conversion between normalized -and relative paths. Typically in the Spring configuration, the template root of all decorators is defined as: -<source test=""><![CDATA[ -${applicationRoot}/WEB-INF/decorations -]]></source> -and the root of all layouts (per portlet application) is defined as: -<source test=""><![CDATA[ -${applicationRoot}/WEB-INF/templates -]]></source> -The Normalized Path is defined with named pair values. Examples: -<source test=""><![CDATA[ -type/layout/media-type/html/name/tigris/decorator.vm -type/decorator/media-type/html/language/en/country/US/name/metal/decorator.vm -]]></source> -<table> - <tr> - <th>Name</th> - <th>Value</th> - <th>Description</th> - </tr> - <tr> - <td>type</td> - <td>layout | portlet | generic</td> - <td>The type of template locator. Expected to be either one of the following values - <b>layout</b>, <b>portlet</b> (decorator) or <b>generic</b> (decorator). Layouts can be for either page layouts - or decorators. Generic type decorators can be used - for either portlets or page decorations.</td> - </tr> - <tr> - <td>media-type</td> - <td>html | wml | dhtml | ...</td> - <td>The markup media type to be located. Should be a valid media type (html, dhtml, wml...)</td> - </tr> - <tr> - <td>name</td> - <td>A valid decorator or layout name</td> - <td>The name of the decorator or layout. Usually corresponds to a - sub-directory holding the decorator or layout templates, images and stylesheets.</td> - </tr> - <tr> - <td>language</td> - <td>A valid ISO-639 standard two-character language abbreviation</td> - <td>ISO-639 (http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt) defines a standard for language abbreviations. - Typical abbreviations are en for english, fr for french, de for German, ...</td> - </tr> - <tr> - <td>country</td> - <td>A valid ISO-3166 standard two-character country code abbreviation</td> - <td>ISO-3166 (http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html) defines a standard for country code abbreviations. - Typical abbreviations are US for United States, FR for France, ...</td> - </tr> - -</table> - -</p> -</section> - -<section name='Terminology'> -<table> - <tr> - <th> - Term - </th> - <th> - Definition - </th> - </tr> - <tr> - <td> - Layout - </td> - <td> -Defines the fashion in which grouping of Fragments -will organized relative to the final, aggregated -content of a request to the portal. Layouts are defined by -a portlet which applies an algorithm to a template to -generate the aggregated content of a page. Typical -algorithms are two column, three column, nested. - </td> - </tr> - <tr> - <td> - TODO: left off here: - </td> - <td> - fragment, decoration, page, page decorator, portlet decorator, - application relative, normalized template path, absolute URL - </td> - </tr> -</table> -</section> -</body> -</document> - +<?xml version="1.0"?> +<!-- +Copyright 2004 The Apache Software Foundation + +Licensed under the Apache License, Version 2.0 (the "License"); +you may not use this file except in compliance with the License. +You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, software +distributed under the License is distributed on an "AS IS" BASIS, +WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +See the License for the specific language governing permissions and +limitations under the License. +--> +<document> + <properties> + <title>Guide to Portal Design</title> + <subtitle>Documentation for Designers working with Jetspeed Portal Design</subtitle> + <authors> + <person name="David Sean Taylor" email="taylo****@apach*****"/> + </authors> + <translators> + <person name="$B2CF#BYJ8(B" email="karma****@prog*****" /> + </translators> + </properties> + <body> +<section name="[Portal Design Introduction] $B%]!<%?%k%G%6%$%s$N<j0z$-(B"> +<div class="original"> +<p> +The Java Portlet API (JSR-168) defines the Java standard interface for programming portlets. +The Java Portlet API specification enables interoperability between Portlets and Portals. +It is the standard specification for developing Java portlets. However the Java Portlet API +does not define standards for laying out and aggregating portlets and markup on a page. +The documentation here under "Portal Design" covers: +<ul> + <li><a href='psml.html'>Page Aggregation - see the section on PSML</a></li> + <li><a href='decorators.html'>Page and Portlet Decorators</a></li> + <li><a href='layouts.html'>Page Layouts</a></li> + <li><a href='jpt.html'>The Jetspeed Power Tool</a></li> + <li><a href='site.html'>The Site Content Model</a></li> + <li><a href='#Template Locators'>Template Locators</a></li> + <li><a href='#Terminology'>Terminology</a></li> +</ul> +</p> +</div> +<p> +Java $B%]!<%H%l%C%H(B API (JSR-168) $B$O!"%]!<%H%l%C%H%W%m%0%i%_%s%0$N(B Java $BI8=`%$%s%?!<%U%'!<%9$rDj5A$7$F$$$^$9!#(BJava $B%]!<%H%l%C%H(B API $B;EMM$K$h$j!"%]!<%H%l%C%H$H%]!<%?%k$N4V$NAj8_$N@\B3$,2DG=$K$J$j$^$9!#$3$l$O(B Java $B%]!<%H%l%C%H$r3+H/$9$k$?$a$NI8=`;EMM$G$9!#$7$+$7!"(BJava $B%]!<%H%l%C%H(B API $B$O!"%l%$%"%&%H$d!"%]!<%H%l%C%H$N=8Ls$d!"%Z!<%8$N%^!<%/%"%C%W$K$D$$$F$NI8=`$ODj5A$7$F$$$^$;$s!#$3$N%I%-%e%a%s%H$N(B "Portal Design" $B0J2<$NItJ,$O0J2<$r%+%P!<$7$^$9!#(B +<ul> + <li><a href='psml.html'>$B%Z!<%8$N=8Ls(B - PSML $B$N%;%/%7%g%s$r8+$F$/$@$5$$!#(B</a></li> + <li><a href='decorators.html'>$B%Z!<%8$H%]!<%H%l%C%H%G%3%l!<%?(B</a></li> + <li><a href='layouts.html'>$B%Z!<%8%l%$%"%&%H(B</a></li> + <li><a href='jpt.html'>Jetspeed $B%Q%o!<%D!<%k(B</a></li> + <li><a href='site.html'>$B%5%$%H%3%s%F%s%D%b%G%k(B</a></li> + <li><a href='#Template Locators'>$B%F%s%W%l!<%H%m%1!<%?(B</a></li> + <li><a href='#Terminology'>$B ＠ lLgMQ8l(B</a></li> +</ul> +</p> +</section> +<section name='[Templates] $B%F%s%W%l!<%H(B'> +<div class="original"> +<p> +Rendering one or more portlets into a portlet page is largely made up of the process of aggregating +portlets as dynamic content with templates. Jetspeed-2 makes use of Velocity templates in +creating a page layout. Although the Jetspeed-2 architecture fully supports the use of JSP templates for +decorators and layouts, the developers thus far have chosen Velocity as the tool of choice for writing +templates. There are two types of templates in Jetspeed: layouts and decorators. +The process of rendering a page is the combined aggregation of a layout template, +a page decorator template, a PSML definition, and one or more portlet decorator templates. +As of release 2.0, templates can be stored on the file system. In future releases, templates +will also be stored in a CMS backend for versioning. +</p> +</div> +<p> +$B%]!<%H%l%C%H%Z!<%8Fb$N0l$D0J>e$N%]!<%H%l%C%H$r%l%s%@%j%s%0$9$k$H$$$&$3$H$O!"<g$K%F%s%W%l!<%H$r;H$C$FF0E*$J%3%s%F%s%D$H$7$F%]!<%H%l%C%H$r=8Ls$9$k=hM}$r9T$&$H$$$&$3$H$G$9!#(BJetspeed 2 $B$O!"%Z!<%8%l%$%"%&%H$r(B Velocity $B%F%s%W%l!<%H$r;H$C$F:n$j$^$9!#(BJetspeed 2 $B$N9=B$$O!"%G%3%l!<%?$d%l%$%"%&%H$N$?$a$K(B JSP $B%F%s%W%l!<%H$r;H$&$3$H$,2DG=$J9=B$$r$7$F$$$^$9$,!"$3$l$^$G3+H/<T$O!"%F%s%W%l!<%H$r=q$/$?$a$N%D!<%k$H$7$F(B Velocity $B$rA*Br$7$F$$$^$9!#(BJetspeed $B$K$O!"Fs<oN`$N%F%s%W%l!<%H$,B8:_$7$F$$$^$9!#$=$l$O%l%$%"%&%H%F%s%W%l!<%H$H%G%3%l!<%?%F%s%W%l!<%H$G$9!#%Z!<%8$r%l%s%@%j%s%0$9$k=hM}$O!"%l%$%"%&%H%F%s%W%l!<%H$H!"%Z!<%8%G%3%l!<%?%F%s%W%l!<%H$H!"(BPSML $B$NDj5A$H!"0l$D0J>e$N%]!<%H%l%C%H%G%3%l!<%?$N%F%s%W%l!<%H$r=8Ls$7$F7k9g$7$^$9!#%j%j!<%9(B 2.0 $B$G$O!"%F%s%W%l!<%H$O%U%!%$%k%7%9%F%`$KJ]B8$9$k$3$H$,2DG=$G$9!#>-Mh$N%j%j!<%9$G$O!"%F%s%W%l!<%H$O%P!<%8%g%s4IM}$N$?$a$K(B CMS $B%P%C%/%(%s%I$KJ]B8$5$l$k$G$7$g$&!#(B +</p> +<subsection name='[Layout Templates] $B%l%$%"%&%H%F%s%W%l!<%H(B'> +<div class="original"> +<p> +Layout templates are packaged in special Jetspeed-specific and deployable portlet applications. +Layout templates control the overall aggregation of a portal page. Layout templates are +combined with portlets, providing a component model for aggregation. Jetspeed-2 comes out +of the box with several layout components including one, two and three column layouts. +See the <a href='layouts.html'>Layout Documentation</a> for all available Layouts in the +default Jetspeed-2 system. Of course you can define and derive your own layouts. +</p> +</div> +<p> +$B%l%$%"%&%H%F%s%W%l!<%H$O!"(BJetspeed $B$KFC2=$7$?G[Hw2DG=$J%]!<%H%l%C%H%"%W%j%1!<%7%g%s$H$7$F$^$H$a$i$l$F$$$^$9!#%l%$%"%&%H%F%s%W%l!<%H$O!"%]!<%?%k%Z!<%8$NA4BNE*$J=8Ls$r%3%s%H%m!<%k$7$^$9!#%l%$%"%&%H%F%s%W%l!<%H$O!"=8Ls$N$?$a$N%3%s%]!<%M%s%H%b%G%k$rDs6!$7!"%]!<%H%l%C%H$rAH$_9g$o$;$^$9!#(BJetspeed 2 $B$O0l9T!"$^$?$OFs9T!"$^$?$O;09T$N%l%$%"%&%H$r4^$`$$$/$D$+$N%l%$%"%&%H%3%s%]!<%M%s%H$r;}$DH"$+$iI=<($5$l$^$9!#%G%U%)%k%H$N(B Jetspeed 2 $B%7%9%F%`$G2DG=$JA4$F$N%l%$%"%&%H$K$D$$$F$O(B <a href='layouts.html'>$B%l%$%"%&%H$N%,%$%I(B</a> $B$r;2>H$7$F$/$@$5$$!#$b$A$m$s!"<+?H$G%l%$%"%&%H$rDj5A$9$k$3$H$b2DG=$G$9!#(B +</p> +</subsection> +<subsection name='[Decorators] $B%G%3%l!<%?(B'> +<div class="original"> + <p> +Decorator templates are packaged in special Jetspeed-specific and deployable archives. +Layout templates control the overall aggregation of a portal page. Layout templates are +combined with portlets, providing a component model for aggregation. Jetspeed-2 comes out +of the box with several layout components including one, two and three column layouts. +See the <a href='guide-decorators.html'>Decorator Documentation</a> for all available Layouts in the +default Jetspeed-2 system. Of course you can define and derive your own layouts. +</p> +</div> +<p> +$B%G%3%l!<%?%F%s%W%l!<%H$O!"(BJetspeed $B$KFC2=$7$?G[Hw2DG=$J%"!<%+%$%V$H$7$F$^$H$a$i$l$F$$$^$9!#%l%$%"%&%H%F%s%W%l!<%H$O!"%]!<%?%k%Z!<%8$NA4BNE*$J=8Ls$r%3%s%H%m!<%k$7$^$9!#%l%$%"%&%H%F%s%W%l!<%H$O!"=8Ls$N$?$a$N%3%s%]!<%M%s%H%b%G%k$rDs6!$7!"%]!<%H%l%C%H$rAH$_9g$o$;$^$9!#(BJetspeed 2 $B$O0l9T!"$^$?$OFs9T!"$^$?$O;09T$N%l%$%"%&%H$r4^$`$$$/$D$+$N%l%$%"%&%H%3%s%]!<%M%s%H$r;}$DH"$+$iI=<($5$l$^$9!#%G%U%)%k%H$N(B Jetspeed 2 $B%7%9%F%`$G2DG=$JA4$F$N%l%$%"%&%H$K$D$$$F$O(B <a href='guide-decorators.html'>$B%G%3%l!<%?$N%,%$%I(B</a> $B$r;2>H$7$F$/$@$5$$!#$b$A$m$s!"<+?H$G%l%$%"%&%H$rDj5A$9$k$3$H$b2DG=$G$9!#(B +</p> +</subsection> +</section> +<section name='[Template Locators] $B%F%s%W%l!<%H%m%1!<%?(B'> +<div class="original"> +<p> +Templates are located by the Jetspeed Template (and Decorator) Locator Component. These components +locates templates using a normalized name/value pair URL scheme. +using this scheme in what is called a 'normalized' URL to either a decorator or layout. +However, templating engines such as Velocity need to work with templates using paths to templates that are +relative of a document root. The <a href='guide-jpt.html'>Jetspeed Power Tool</a> facilitates conversion between normalized +and relative paths. Typically in the Spring configuration, the template root of all decorators is defined as: +<source test=""><![CDATA[ +${applicationRoot}/WEB-INF/decorations +]]></source> +and the root of all layouts (per portlet application) is defined as: +<source test=""><![CDATA[ +${applicationRoot}/WEB-INF/templates +]]></source> +The Normalized Path is defined with named pair values. Examples: +<source test=""><![CDATA[ +type/layout/media-type/html/name/tigris/decorator.vm +type/decorator/media-type/html/language/en/country/US/name/metal/decorator.vm +]]></source> +<table> + <tr> + <th>Name</th> + <th>Value</th> + <th>Description</th> + </tr> + <tr> + <td>type</td> + <td>layout | portlet | generic</td> + <td>The type of template locator. Expected to be either one of the following values + <b>layout</b>, <b>portlet</b> (decorator) or <b>generic</b> (decorator). Layouts can be for either page layouts + or decorators. Generic type decorators can be used + for either portlets or page decorations.</td> + </tr> + <tr> + <td>media-type</td> + <td>html | wml | dhtml | ...</td> + <td>The markup media type to be located. Should be a valid media type (html, dhtml, wml...)</td> + </tr> + <tr> + <td>name</td> + <td>A valid decorator or layout name</td> + <td>The name of the decorator or layout. Usually corresponds to a + sub-directory holding the decorator or layout templates, images and stylesheets.</td> + </tr> + <tr> + <td>language</td> + <td>A valid ISO-639 standard two-character language abbreviation</td> + <td>ISO-639 (http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt) defines a standard for language abbreviations. + Typical abbreviations are en for english, fr for french, de for German, ...</td> + </tr> + <tr> + <td>country</td> + <td>A valid ISO-3166 standard two-character country code abbreviation</td> + <td>ISO-3166 (http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html) defines a standard for country code abbreviations. + Typical abbreviations are US for United States, FR for France, ...</td> + </tr> + +</table> + +</p> +</div> +<p> +$B%F%s%W%l!<%H$O!"(BJetspeed $B%F%s%W%l!<%H(B ($B$H(B Jetspeed $B%G%3%l!<%?(B) $B$N%m%1!<%?%3%s%]!<%M%s%H$K$h$j8!:w$5$l$^$9!#$3$l$i$N%3%s%]!<%M%s%H$O!"@55,2=$5$l$?L>A0$HCM$N%Z%"$K$h$k(B URL $B%9%-!<%`$r;H$C$F%F%s%W%l!<%H$r8!:w$7$^$9!#(Busing this scheme in what is called a 'normalized' URL to either a decorator or layout. $B$7$+$7!"(BVelocity $B$N$h$&$J%F%s%W%l!<%H%(%s%8%s$O!"%I%-%e%a%s%H%k!<%H$+$i$NAjBP%Q%9$GI=8=$5$l$k%F%s%W%l!<%H$X$N%Q%9$r;H$C$FF0:n$9$kI,MW$,$"$j$^$9!#(B<a href='guide-jpt.html'>Jetspeed $B%Q%o!<%D!<%k(B</a> $B$O!"@55,2=$5$l$?%Q%9$HAjBP%Q%9$N4V$NJQ49$rMF0W$K$7$F$/$l$^$9!#(BSpring $B$N ＠ _Dj$G$OE57?E*$KA4$F$N%G%3%l!<%?$N%F%s%W%l!<%H%k!<%H$O<!$N$h$&$KDj5A$5$l$^$9!#(B +<source test=""><![CDATA[ +${applicationRoot}/WEB-INF/decorations +]]></source> +$B$=$7$F!"A4$F$N(B ($B%]!<%H%l%C%H%"%W%j%1!<%7%g%sKh$N(B) $B%l%$%"%&%H$N%k!<%H$O<!$N$h$&$KDj5A$5$l$^$9!#(B +<source test=""><![CDATA[ +${applicationRoot}/WEB-INF/templates +]]></source> +$B ＠ 55,2=$5$l$?%Q%9$OL>A0$HCM$N%Z%"$H$7$FDj5A$5$l$^$9!#Nc$($P(B +<source test=""><![CDATA[ +type/layout/media-type/html/name/tigris/decorator.vm +type/decorator/media-type/html/language/en/country/US/name/metal/decorator.vm +]]></source> +$B$N$h$&$K$G$9!#(B +<table> + <tr> + <th>åå‰</th> + <th>$BCM(B</th> + <th>$B ＠ bL@(B</th> + </tr> + <tr> + <td>type</td> + <td>layout | portlet | generic</td> + <td>$B%F%s%W%l!<%H%m%1!<%?$N%?%$%W!#(B<b>layout</b>, <b>portlet</b> (decorator) or <b>generic</b> (decorator) $B$N$$$:$l$+$NCM$N$&$A$N$I$l$+$G$9!#%l%$%"%&%H$O%Z!<%8%l%$%"%&%H$+%G%3%l!<%?$N$$$:$l$+$N$?$a$N$b$N$K$J$j$($^$9!#(B</td> + </tr> + <tr> + <td>media-type</td> + <td>html | wml | dhtml | ...</td> + <td>$B8!:w$5$l$k%^!<%/%"%C%W%a%G%#%"%?%$%W!#M-8z$J%a%G%#%"%?%$%W(B (html, dhtml, wml...) $B$G$"$kI,MW$,$"$j$^$9!#(B</td> + </tr> + <tr> + <td>name</td> + <td>$BM-8z$J%G%3%l!<%?$b$7$/$O%l%$%"%&%H$NL>A0(B</td> + <td>$B%G%3%l!<%?$b$7$/$O%l%$%"%&%H$NL>A0!#IaDL$O%G%3%l!<%?$b$7$/$O%l%$%"%&%H$N%F%s%W%l!<%H$d2hA|$d%9%?%$%k%7!<%H$,J]B8$5$l$F$$$k%5%V%G%#%l%/%H%j$H0lCW$7$^$9!#(B</td> + </tr> + <tr> + <td>language</td> + <td>ISO-639 $BI8=`$H$7$FM-8z$JFsJ8;z$N8 ＠ 8l$N>JN,7A(B</td> + <td>ISO-639 (http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt) $B$O8 ＠ 8l$N>JN,7A$NI8=`$rDj5A$7$^$9!#(B + $BBeI=E*$J>JN,7A$H$7$F1Q8l$K$?$$$9$k(B en$B!"%U%i%s%98l$KBP$9$k(B fr$B!"%I%$%D8l$KBP$9$k(B de $BEy$,$"$j$^$9!#(B</td> + </tr> + <tr> + <td>country</td> + <td>ISO-3166 $BI8=`$H$7$FM-8z$JFsJ8;z$N9qL>$N>JN,7A(B</td> + <td>ISO-3166 (http://userpage.chemie.fu-berlin.de/diverse/doc/ISO_3166.html) $B$O9q%3!<%I$N>JN,7A$NI8=`$rDj5A$7$^$9!#(B + $BBeI=E*$J>JN,7A$H$7$F%"%a%j%+9g=09q$KBP$9$k(B US $B$d%U%i%s%9$KBP$9$k(B FR $BEy$,$"$j$^$9!#(B</td> + </tr> + +</table> +</p> +</section> + +<section name='[Terminology] $B ＠ lLgMQ8l(B'> +<div class="original"> +<table> + <tr> + <th> + Term + </th> + <th> + Definition + </th> + </tr> + <tr> + <td> + Layout + </td> + <td> +Defines the fashion in which grouping of Fragments +will organized relative to the final, aggregated +content of a request to the portal. Layouts are defined by +a portlet which applies an algorithm to a template to +generate the aggregated content of a page. Typical +algorithms are two column, three column, nested. + </td> + </tr> + <tr> + <td> + TODO: left off here: + </td> + <td> + fragment, decoration, page, page decorator, portlet decorator, + application relative, normalized template path, absolute URL + </td> + </tr> +</table> +</div> +<table> + <tr> + <th> + $BMQ8l(B + </th> + <th> + $BDj5A(B + </th> + </tr> + <tr> + <td> + $B%l%$%"%&%H(B(Layout) + </td> + <td> +$B%U%i%0%a%s%H$N%0%k!<%W$,4X78$9$k$b$N$G$^$H$a$i$l$F!":G=*E*$K%]!<%?%k$X$N%j%/%(%9%H$KBP$9$k=8Ls$5$l$?%3%s%F%s%D$K$^$H$a$i$l$k:]$N7A>u$rDj5A$7$^$9!#%l%$%"%&%H$O%Z!<%8$N=8Ls$5$l$?%3%s%F%s%D$r ＠ 8@.$9$k%F%s%W%l!<%H$K%"%k%4%j%:%`$rE,MQ$9$k$?$a$N%]!<%H%l%C%H$K$h$j7h$a$i$l$^$9!#E57?E*$J%"%k%4%j%:%`$K$OFs9T!";09T!"F~$l;R9=B$$,$"$j$^$9!#(B + </td> + </tr> + <tr> + <td> + TODO: left off here: + </td> + <td> + fragment, decoration, page, page decorator, portlet decorator, + application relative, normalized template path, absolute URL + </td> + </tr> +</table> +</section> +</body> +</document> +
