RSS
 

8 Natural Ways to Prevent a Sunburn (And Sunscreen’s Not One of Them)

19 Jul

beachAs summer descends upon the world, a young Primal eater’s fancy turns to playful frolicking in the sunshine. And when you’re frolicking, the last thing you want to do is slather a bunch of horrible-smelling, greasy, overpriced sunblock all over your body. It makes you slippery and imbues your countenance with a deathly pallor that is very unbecoming. If you could, you’d love to avoid the nasty practice altogether. You’d love to use more alternative methods. Methods that may not have the support of the medical community, but for which supportive research does exist. Seeing as how a common refrain throughout the newly Primal is that sunburns seem fewer and further between than ever before, I’m guessing that there’s something to it. Dietary? Supplementary?

I’ve noticed the same thing in myself and my family, so I got to wondering: what about going Primal, exactly, might be having this effect? And if something is protecting us from the sun, and it’s not just in everyone’s heads, what else can we do to bolster our natural sunblock? What can we recommend to friends and family who aren’t quite on board with the whole deal but still want protection from the sun? Let’s take a look at some potential supplements and dietary strategies. I’ll reference research as often as possible, but I’ll also draw on anecdotal experience, both personal and from the community at large.

Eat Some Lycopene

Lycopene, that famous carotenoid found in tomatoes, has been shown in a recent in vivo RCT to protect humans against sun damage. Healthy women, aged 21-47, who ate 55 g of tomato paste containing 16 mg of lycopene every day for 12 weeks experienced significant protection against acute – and potentially long term – sun damage. Remember that cooked tomatoes, and tomato products like paste and sauce, offer far more bioavailable lycopene than raw tomatoes. If you’re counting, 55 grams of tomato paste is a hair over 3 tablespoons worth.

Get Some Astaxanthin

The super-antioxidant astaxanthin is found in algae, the organisms that eat it, and the organisms that eat those organisms (like salmon, shrimp, and pink flamingo – the pink/red color gives it away). It has been getting some attention as an “internal sunscreen.” Does it stack up? Well, here’s a study on isolated human skin cells, in which astaxanthin definitely protects against UVA damage. And here’s another study on isolated skin cells showing its protective effects. But those are limited. Does the effect persist in real life settings? In other words, does ingesting astaxanthin supplements or food that contains astaxanthin offer protection from UVA? This hairless mouse study suggests that it might; astaxanthin was more effective than even retinol. I’d say it looks promising, and I’m always interested in an excuse to dine on pink flamingo thigh.

Get Some Vitamin D

A common anecdotal report is that supplementing vitamin D increases sun tolerance and protection against sun damage, and a recent study seems to confirm this. Various forms of the vitamin D prohormone offered various protections against UV damage in a mouse model: reduced sunburn, lowered incidence of tumor development. Huh, imagine that! Getting sun gives you vitamin D, which in turn protects you from too much sun. It’s funny how these things work out. Nature can be very elegant.

Get Your Long-Chain Omega-3s and Ditch the Omega-6s

A recent study out of Australia found that adults with the highest serum concentrations of DHA and EPA had the least “cutaneous p53 expression.” What’s the significance of cutaneous p53 expression? When your skin is in danger of damage from the sun, p53 expression is upregulated to protect it, and high p53 immunoreactivity can lead to melanoma. The fact that high DHA/EPA meant low p53 immunoreactivity suggests that the omega-3s were protecting the skin. And although the study’s authors noted that high serum omega-6 content didn’t seem to correlate with high p53 activity, I think a likelier explanation is this: omega-6 is so prevalent in the modern Australian diet, that even “low” levels are still above the threshold for increased susceptibility to sunburn. Going higher than that threshold won’t make things any worse, and it won’t show up in the statistics. Drop that omega-6 intake to 2% of calories, though, while getting an equal amount of omega-3s? I bet you’d see some incredible UV-resistance.

Eat Plenty of Saturated Fat

This is slightly redundant in light of the last suggestion – after all, if you’re limiting PUFAs, you gotta eat some saturated fat – but I think it’s worth mentioning. I hear about people bumping up their saturated fat intake and improving their UV-resistance all over the place, and I’ve experienced the same thing myself, but I’d never seen it mentioned in the literature. Well, here’s a cool rodent study in which mice were either given a saturated fat-enriched diet or a PUFA-enriched diet. No word on the exact composition of the two diets. When both groups of mice were injected with melanoma cells, “the initiation time required for visible tumor growth in mice receiving the polyunsaturated fat diet was significantly less than that in mice receiving the saturated fat diet.” A higher-saturated fat diet was protective, while a higher-PUFA diet was not. If you’re gonna be out in the sun, better eat your butter, palm oil, and coconut oil, eh?

Drink Tea

Tea, especially green tea, offers a complex arsenal of antioxidant compounds. How it works and what’s doing it isn’t fully understood, but it’s generally accepted that drinking green tea is a smart move and a mainstay of many healthy traditional cultures. Unsurprisingly, there’s also evidence that dietary green tea, specifically its polyphenols, inhibit the development of skin tumors by controlling inflammation and preventing DNA damage. Topical green tea extracts applied directly to the skin also offer photoprotection.

Get Some Proanthocyanidins

Proanthocyanidins, which can be found in wine and grape seeds, berries like blueberries and chokeberries, nuts like hazelnuts and pistachios, and certain niche grains like sorghum and barley, have been efficacious in preventing UV damage in hairless rodents. Whether it works for hairless apes remains to be seen, but drinking wine and eating berries sound like fine ideas regardless of their photoprotective efficacy. Actually, score one for the hairless apes who quaff wine: a recent study found that people who supplemented with grape seed extract (high in anthocyanidins) had a significantly lower risk of skin cancer. It sounds promising.

Consider Resveratrol

Resveratrol gets a lot of publicity for its possible anti-cancer, cardioprotective, and lifespan enhancing qualities, but it’s also gaining steam as a potential photoprotective agent. This study found that once incorporated into skin cells, resveratrol protected them from UV damage. Topical resveratrol seems viable, too, but I can imagine rubbing resveratrol into your sun-exposed skin would get expensive rather quickly.

Well, that’s what I came up with. I think the first four appear to be the most effective, but if you have a real problem with burning, it might be worth checking out all the strategies I mentioned. I’m also interested in what’s worked for you. Have you tried the above methods? Did they work? Fill us in and thanks for reading!

Grab The Primal Blueprint Cookbook Today and Receive Free S&H and a Free Primal Blueprint Poster

Related posts:

  1. 6 Sneaky Ways to Work Offal Into Your Diet

 
 

Enable Comments in the Margins of Your Website with Highlighter (& 1 Line of JavaScript)

19 Jul

comments_screenshot.jpg

One of the longstanding laments about our move to digital literature is how difficult and cumbersome this makes marginalia, those notes and annotations we make in the margins of printed text. A story in The New York Times earlier this year went so far as to call the future of marginalia "dim," not only due to our inability to write comments in the margins but because there's not been any good system by which to track and preserve our notes.

TechStars alum Highlighter believe it has cracked this nut, with one line of JavaScript (inserted into site's footer) that lets publishers enable marginalia on their websites and in turn allows visitors to highlight, annotate, save, and share passages and comments.

Sponsor

Of course, the ability to comment, per se, on websites isn't new. But blog comments and the like always come at the end of a post, and likely means that readers would leave different sorts of notes and have different sorts of discussions with one another than if they could mark up a particular passage and make in-line comments there.

Annotations & Academics

That exercise in annotation is something most scholars and students are very familiar with, and no surprise Highlighter says it plans to market to this group specifically. By installing Highlighter on a class blog, for example, teachers will be able to enable commenting and highlighting by individual students and will also have a means to track students' level of engagement with the text. Part of what publishers (and let's use that word loosely here, after all, with blogs and Tumblr and the like, we're almost all publishers now) get with Highlighter is analytics - the ability to see who's reading, who's highlighting and who's sharing.

analytics_screenshot.jpg

Visitors needn't sign up for a Highlighter account in order to write marginalia and share highlights and comments. They do, however, need an account if they want to track and store their own annotations. With an account you can also choose to make your highlights and comments public, semi-public or private, meaning that you can share your notes openly or just with those in a particular group, or keep everything to yourself.

This sharing of notes and annotations is important, but it isn't something that's widely available or supported. Take Amazon Kindle highlights. There's no way to share your notes with others. There's no way to follow other readers (or authors) and see what interests them, what they've highlighted, and what notes they've jotted down. Highlighter solves that problem

Encouraging Engaged Readers --Something Teachers, Authors, and Publishers Alike Want

This social component is important in classroom reading, but it's also great in general for building an engaged audience. Highlighter co-founder Josh Mullineaux says that authors, many of whom are increasingly turning to self-publishing efforts, will be able to take advantage of turning over sample chapters and the like to their fans, not just their editors, eliciting feedback not just on a whole piece, but on a word, a phrase, a paragraph.

Much like blog comments, publishers will be able to monitor comments and have a number of administrative controls so that comments and highlights must be pre-approved, for example, or that commenters are forced to give their name and email address before leaving or sharing notes.

Highlighter's official launch today will bring it into competition with a number of other startups that are trying to tackle the problem of digital marginalia, including OpenMargin and Readum.

Discuss

 
 

Bad News For Lamb Fans

19 Jul

I’ve long felt that the American consumer’s aversion to lamb was slightly odd. It’s got a more delicious flavor than beef, in my opinion, and sheep are generally raised in more humane conditions than other mass market animals. Unfortunately, lamb turns out to be an ecological catastrophe:

That meat in general is bad news, climate-wise, is familiar. But it’s interesting what a big gap there is. The carbon gap between lamb & beef on the one hand and pork & chicken on the other is larger than the gap between between pork & chicken and vegetarianism.

 
 

Little Picture: America Has Changed in 45 Years

18 Jul
The Republican "cut, cap and balance" plan caps federal spending at 18 percent of the previous year's gross domestic product. Federal spending has not been at that level since 1966. This chart, courtesy of the Center for American Progress, explains how the world has changed since then.

cap and cut graphic.jpg

 
 

Neighbors Are Mad At Guy Who Got $300K House For $16

18 Jul

That unappealing smell could be the stench of jealousy, after a man uses the law to his advantage and snags a $300,000 house in Texas for a mere $16. Now his high-falutin' neighbors are all cranky that he might get away with such a steal.

KHOU.com out of Texas brings us the story of the man who moved into a foreclosed home and filed some paperwork, along with a $16 fee, in the town of Flower Mound, and could end up with his McMansion if he lives in it for three years.

Kenneth Robinson's new neighbors say he's a squatter, but he says he is just using the law to his advantage. After the previous owners walked away from the house when it was in foreclosure, the mortgage company went out of business. So Robinson moved in after researching "adverse possession," a little-known Texas law.

He printed out an online form and filed it at Denton County courthouse for $16 and was granted rights to the house. The home has no electricity or running water, but Robinson just set up camp anyway. The law says he gets exclusive negotiating rights with the original owner. If they want him out, they have to pay off the mortgage debt and the bank would have to file a lawsuit.

Robinson doesn't think that's likely, and after three years, he can ask the court for the title to the home. In the meantime, he posted "No Trespassing" signs after his neighbors tried to get him arrested for squatting. Cops can't remove him because home ownership is a civil, not criminal matter.

"If he wants the house, buy the house like everyone else had to," says one neighbor. "Get the money, buy the house."

Or, just pay $16 and still get the house.

Stranger moves into foreclosed home, citing little-known Texas law [KHOU.com]

 
 

Liberté, égalité, fraternité, surveillance

17 Jul

From this isn’t happiness | tomorrow started, via Paul Graham Raven

 
 

The Internet of Things [Infographic]

17 Jul

In 2008, the number of devices that connected to the Internet exceeded the number of people. That number continues to rise, thanks to a growing number of connected devices and gizmos, ranging from televisions to soda machines. Folks at Cisco have put together this infographic to showcase the growth of the Internet of things.

.

Infographic courtesy of Cisco.

Related research and analysis from GigaOM Pro:
Subscriber content. Sign up for a free trial.


 
 

All the IBM WCM 7 Tags

16 Jul

Page edited by Ben Shoemate

You use IBM® Web Content Manager tags to reference elements (such as title, id, date, and custom elements you added to authoring templates when you created them) within presentation templates and element designs (menu components, personalization components, etc). IBM Documentation here: http://www-10.lotus.com/ldd/portalwiki.nsf/dx/Creating_web_content_tags_wcm7 and consolidated below.

Alternate design tags 

You use an alternate design tag to display a different component based on whether the item being returned by a menu or navigator is on the current path or not.

[alternatedesign highlight=" " normal=" " type=" " start=" " end=" " ]

Table 1. Additional tag parameters

Tag parameters Details
normal=" " To use the library specified in the URL of the current page, use normal="./name"

Note: If you specify normal="./name", the library name does not appear in your presentation template or element design. The actual path is not resolved until the item is rendered.
highlight=" " To use the library specified in the URL of the current page, use highlight="./name"

Note: If you specify highlight="./name", the library name does not appear in your presentation template or element design. The actual path is not resolved until the item is rendered.
start=" "

end=" "
The Start and End attributes are used to wrap the data returned by a tag within other tags, such as HTML. These attributes are not mandatory.
Back to Top

Attribute resource tags

You use the attribute resource tag to define the information returned by a search query.

[attributeResource attributeName="parameter" separator=" " format=" "]

Table 1. Additional tag parameters

Tag parameters Details
attributeName=authoringtemplate The name of the authoring template, if available, that was used to create the content item.
attributeName=author The name or names of the authors of the content item, if any are defined. If there is more than one author, then they are rendered with the string specified in the optional separator attribute between each value.
attributeName=category The categories of the content item if any are defined. If there is more than one category, then they are rendered with the string specified in the optional separator attribute between each value.
attributeName=contentid The id of the content item.
attributeName=contentpath The path excluding the server address, port, or servlet context (/wps/wcm) for this search result.
attributeName=date The value of the date field from the SIAPI result. The format of the date can be specified by using the optional format attribute. See the Javadoc HTML documentation for SimpleDateFormat in the Java SDK for details.
attributeName=description The description of the content item.
attributeName=effectivedate The effective date of the content item. The format of the date can be specified by using the optional format attribute. See the Javadoc HTML documentation for SimpleDateFormat in the Java SDK for details.
attributeName=expirationdate The expiration date of the content item. The format of the date can be specified by using the optional format attribute. See the Javadoc HTML documentation for SimpleDateFormat in the Java SDK for details.
attributeName=keywords The keywords of the content item if any are defined. If there is more than one keyword, then they are rendered with the string specified in the optional separator attribute between each value.
attributeName=lastmodifieddate The last modified date of the content item. The format of the date can be specified by using the optional format attribute. See the Javadoc HTML documentation for SimpleDateFormat in the Java SDK for details.
attributeName=modifier The name of the last person to modify the content item.
attributeName=name The name of the content item.
attributeName=namelink This assembles a complete link based on the name of the item being returned.
attributeName=owner The name or names of the owners of the content item, if any are defined. If there is more than one author, then they are rendered with the string specified in the optional separator attribute between each value.
attributeName=parentcontentpath This is used to return the content path excluding the server address, port, or Servlet context for the parent content item of this search result. For example: /wps/wcm

This parameter is valid when the search results include a link to a file resource element in the parent content item and is used to give context to the attached file. When the search result is not for an attached file in a file resource element, this value is an empty string.
attributeName=relevance The relevance “score” for this search result from the search engine.
attributeName=summary The summary of the content item as generated by Portal Search.
attributeName=title This is the title of a content item.
attributeName=titlelink This assembles a complete link based on the title of the item being returned.
attributeName=url Displays the URL of a content item.
format=" " This parameter is optional and can only be used with some parameter types:
When referencing number or date elements:
  •  Options:
    • format="DATE_SHORT"
    • format="DATE_MEDIUM"
    • format="DATE_LONG"
    • format="DATE_FULL"
    • format="DATE_TIME_SHORT"
    • format="DATE_TIME_MEDIUM"
    • format="DATE_TIME_LONG"
    • format="DATE_TIME_FULL"
    • format="TIME_SHORT"
    • format="TIME_MEDIUM"
    • format="TIME_LONG"
    • format="TIME_FULL"
    • format="relative" (The relative date is displayed as either "today", "yesterday" or the number of days ago.)** Setting parameters to format dates
    • Note on formatting numbers
separator=" " Enter text or code to be used to separate multiple search results. For example: separator=" - "
Back to Top

Component tags

The Component tag is used to reference the content of a component within a presentation template or element design.

[Component name=" " context="autofill" format=" " separator=" " compute=" "
  htmlencode=" " awareness=" " start=" " end=" " ]

Table 1. Additional tag parameters

Tag parameters Details
name=" " To use the library specified in the URL of the current page, use name="./item".

Note: If you specify name="./item", the library name does not appear in your presentation template or element design. The actual path is not resolved until the item is rendered.
context="autofill" This parameter is only used when referencing a Component tag within a Personalization element design to display the results of a Personalization rule that searches for components.
start=" "

end=" "
The start and end attributes are used to wrap the data returned by a tag within other tags, such as HTML. These attributes are not mandatory.
format=" " This parameter is optional and can only be used with some component types:
When referencing an image component:
format="url"
format="tag"
When referencing a file resource component
  • word-processing documents (*.doc, *.odt)
  • spreadsheets (*.xls) *
  • HTML files (*.htm, *.html)
    Text files (.txt)*Maximum Cache Size:

    resourceserver.maxCacheObjectSizeWCM WCMConfigServiceresourceserver.maxCacheObjectSizeformat="HTML"
    When referencing file resource and image components:
  •  
  • Use format="mimetype" to render the mime type of a file or image. If no valid mime type can be determined then "www/unknown" is rendered.
  • Use format="filename" to render the name of a file or image.
  • Use format="size" to render the size of a file or image using the most appropriate unit. If the resource is smaller than 1K then the size in bytes is rendered. If the size of the resource is less than 1MB then the size in kilobytes are rendered. If the size is greater than or equal to 1MB then the size is rendered in megabytes.
  • Use format="size_bytes" to render the size of a file or image in bytes. Only the numeric value is displayed.
  • Use format="size_KB" to render the size of a file or image in kilobytes. Only the numeric value is displayed.
  • Use format="size_MB" to render the size of a file or image in megabytes. Only the numeric value is displayed.

    When referencing a link component:
  • /wps/wcm/myconnect/Library/SiteArea/Content
    /Library/SiteArea/Content
    **  
    •  
    • format="noprefixurl"
    • format="noprefixpath"
    • format="noprefixtag"
  • <a href="/wps/wcm/myconnect/Library/SiteArea/Content"></a>

    Note: format="url"format="path"format="tag"
    When referencing number or date elements:   * format="DATE_SHORT"
  • format="DATE_MEDIUM"
  • format="DATE_LONG"
  • format="DATE_FULL"
  • format="DATE_TIME_SHORT"
  • format="DATE_TIME_MEDIUM"
  • format="DATE_TIME_LONG"
  • format="DATE_TIME_FULL"
  • format="TIME_SHORT"
  • format="TIME_MEDIUM"
  • format="TIME_LONG"
  • format="TIME_FULL"
  • format="relative" (The relative date is displayed as either "today", "yesterday" or the number of days ago.)** Setting parameters to format dates
  • Note on formatting numbers

    When referencing user details:*  format="cn" is used to display the common name.
  • format="dn" is used to display the distinguished name.
    Maximum character length:
  •  format="length:number_of_characters"** format="length:10" |
compute=" " This is only applicable to menu, navigator, and taxonomy components. You specify compute="always" when you reference some JSP code within a component design, and you want that code to be run separately on each result returned by a menu, navigator and taxonomy component.

For example, if a menu referenced JSP code that used the public DocumentId getCurrentResultId(); method, you would use compute="always" to make the JSP code run separately in every result returned by the menu.

If not specified, then compute="once" is used which is the default method for delivering the results of menu, navigator, and taxonomy components.
htmlencode=" " If htmlencode="true" the reserved HTML characters in text and short text components are converted into character entities. For example, '<' is converted to '<'. This is useful if you would like to prevent users adding malicious code, or if you want to prevent users changing the look and feel of their text using HTML.

If not specified, the default setting specified by the cmpnt.htmlEncodeDefault property in the WCM WCMConfigService service is used. By default, this property is set to true.
awareness=" " If awareness="true" then user names are displayed using the people awareness features. This feature displays user names as hyperlinks that allow users to contact people with whom they might want to work. Wherever person links appear, users can click the link to display a menu of actions for collaborating (contacting and working) with the person named by the link. If you, as administrator, have also configured an IBM® Lotus® Sametime® server to work with WebSphere® Portal, person links indicate whether a person is active, away, offline, or in a Do Not Disturb state.

People awareness only works in content rendered using either a local or remote rendering portlet.

If not specified, then awareness="false" and people awareness is not used.
separator=" " This only used when referencing a user selection component. It is used to define what text or code is rendered between each selection. For example, to add a line break between each selection, you would use separator="<br>" . If not defined, a comma is placed between each selection when rendered.
Back to Top

Element tags

The Element tag is used to reference an element within a presentation template or element design.

[Element type=" " context=" " name=" " key=" " format=" " link=" " separator=" "

htmlencode=" " awareness=" " start=" " end=" " ]

Table 1. Additional tag parameters

Tag parameters Details
name=" " If you specify name="./itemName", the actual path is not resolved until the item is rendered. This takes slightly longer to resolve than specifying the path to the item.
format=" " This parameter is optional and can only be used with some element types:
When referencing an image element:
format="url"
format="tag"
When referencing a link element:
  •  
    /wps/wcm/myconnect/Library/SiteArea/Content
    /Library/SiteArea/Content
    **  
      • format="noprefixurl"
      • format="noprefixpath"
      • format="noprefixtag"

        <a href="/wps/wcm/myconnect/Library/SiteArea/Content"></a>

        Note: format="url"format="path"format="tag"
        When referencing a file resource element:
  •  
    •  
      • word-processing documents (*.doc, *.odt)
      • spreadsheets (*.xls) *
      • HTML files (*.htm, *.html)
      • Text files (.txt)*Maximum Cache Size:

        resourceserver.maxCacheObjectSizeWCM WCMConfigServiceresourceserver.maxCacheObjectSizeformat="HTML"
        When referencing file resource and image elements:
  • Use format="mimetype" to render the mime type of a file or image. If no valid mime type can be determined then "www/unknown" is rendered.
  • Use format="filename" to render the name of a file or image.
  • Use format="size" to render the size of a file or image using the most appropriate unit. If the resource is smaller than 1K, then the size in bytes is rendered. If the size of the resource is less than 1MB, then the size in kilobytes is rendered. If the size is greater than or equal to 1MB, then the size is rendered in megabytes.
  • Use format="size_bytes" to render the size of a file or image in bytes. Only the numeric value is displayed.
  • Use format="size_KB" to render the size of a file or image in kilobytes. Only the numeric value is displayed.
  • Use format="size_MB" to render the size of a file or image in megabytes. Only the numeric value is displayed.

    When referencing number or date elements:
  •  
    • format="DATE_SHORT"
    • format="DATE_MEDIUM"
    • format="DATE_LONG"
    • format="DATE_FULL"
    • format="DATE_TIME_SHORT"
    • format="DATE_TIME_MEDIUM"
    • format="DATE_TIME_LONG"
    • format="DATE_TIME_FULL"
    • format="TIME_SHORT"
    • format="TIME_MEDIUM"
    • format="TIME_LONG"
    • format="TIME_FULL"
    • format="relative" (The relative date is displayed as either "today", "yesterday" or the number of days ago.)** Setting parameters to format dates
    • Note on formatting numbers

      When referencing user details:
  •  
    • format="cn" is used to display the common name.
    • format="dn" is used to display the distinguished name.

      Maximum character length:
  •  
    • format="length:number_of_characters"** format="length:10"

link=" " The link parameter is used to define the type of link created by the element tag:
  • link="default" 
  • link="path"
  • link="contextual"
    Contextual linking: 
    Contextual linking is used so that when content is linked from another site, the link is rendered relative to the current site if possible. It can only be used if context=current orcontext=autofill. 
separator=" " This is used when referencing an option selection or user selection element. It is used to define what text or code is rendered between each selection displayed in an option selection or user selection element. For example, to add a line break between each selection, you would use separator="<br>". If not defined, a comma is placed between each selection when rendered.
htmlencode=" " If htmlencode="true" the reserved HTML characters in text, short text and option selection elements are converted into character entities. For example, '<' is converted to '<'. This is useful if you would like to prevent users adding malicious code, or if you want to prevent users changing the look and feel of their text using HTML.

If not specified, the default setting specified by the cmpnt.htmlEncodeDefault property in the WCM WCMConfigService service is used. By default, this property is set to true.
awareness=" " If awareness="true" then user names are displayed using the people awareness features. These features display user names as hyperlinks that allow users to contact people with whom they might want to work. Wherever person links appear, users can click the link to display a menu of actions for collaborating (contacting and working) with the person named by the link. If you, as administrator, have also configured an IBM® Lotus® Sametime® server to work with WebSphere® Portal, person links indicate whether a person is active, away, offline, or in a Do Not Disturb state.

People awareness only works in content rendered using either a local or remote rendering portlet.

If not specified, then awareness="false" and people awareness is not used.
start=" "

end=" "
The start and end attributes are used to wrap the data returned by a tag within other tags, such as HTML. These attributes are not mandatory.
Back to Top

Information tags 

You use the page information tag to display page navigation details in the design of a page navigation element.

[PageInfo value=" " knowntext=" " unknowntext=" " start=" " end=" " ]

Table 1. Additional tag parameters

Tag parameters Details
knowntext=" "

unknowntext=" "
These parameters are used when value="unknownPages". For example:

[PageInfo value="unknownPages"
knowntext="of" unknowntext="of at least" ]

This could be used with other PageInfo tags to render the following:
  • When the total number of pages are known: "Page 2 of 5."
  • When the total number of pages are unknown: "Page 2 of at least 5."

start=" "

end=" "
The start and end attributes are used to wrap the data returned by a tag within other tags, such as HTML. These attributes are not mandatory.
Back to Top

Path component tags

The path component tag is used to represent certain parts of the URL such as the servlet path, the base path, or the context path of the current page. This tag can be added to presentation templates, element designs, and component designs.

[pathcmpnt type=" " start=" " end=" " ]

Table 1. Additional tag parameters

Tag parameters Details
start=" "

end=" "
The start and end attributes are used to wrap the data returned by a tag within other tags, such as HTML. These attributes are not mandatory.

Back to Top



placeholder tags 

You use a placeholder tag to display metadata within an element or component design.

[placeholder tag=" " htmlencode=" " start=" " end=" " ]
  • Name - This is used to display the name of the site area or content being retrieved in a menu or navigator. This can also be used when you create a user name component, where you can add a placeholder tag in the design and specify tag="name" to render the name of the user.
  • Title - This is used to display the title of the site area or content being retrieved in a menu or navigator.
  • dn - This is for when you create a user name component. You can add a placeholder tag in the design and specify tag="dn" to render the distinguished name of the user.
  • HREF - This inserts a link to the page of the site area or content being retrieved in a menu or navigator.  
  • noprefixhref - The URLs generated by "HREF" parameter is fully qualified when viewed through a portal. To generate URLs with no prefix, use the "noprefixhref" parameter instead of the "HREF" parameter.
  • NameLink - This is a combination of the name and HREF tags. It assembles a complete link based on the name of the item being returned.
  • noprefixnameLink - The URLs generated by "nameLink" parameter is fully qualified when viewed through a portal. To generate URLs with no prefix, use the "noprefixnameLink" parameter instead of the "nameLink" parameter.
  • TitleLink - This is a combination of the title and HREF tags. It assembles a complete link based on the title of the item being returned.
  • noprefixtitleLink - The URLs generated by "titleLink" parameter is fully qualified when viewed through a portal. To generate URLs with no prefix, use the "noprefixtitleLink" parameter instead of the "titleLink" parameter.
  • sitepath - This is similar to the HREF placeholder except that it only display the site path of an item's URL.
    • For example, an HREF placeholder tag displaying a content item may give you: /ILWWCM/connect/metaorg/intranet/press+releases
    • Whereas the site path will give you: /metaorg/intranet/press+releases
    • For example, an HREF placeholder tag displaying a site area may give you:  /ILWWCM/connect/metaorg/intranet/
    • Whereas the site path will give you: /metaorg/intranet
      Note that the final / slash is not included when the site path is displayed for site areas.
  • Idnum - This returns the hexadecimal ID value of an item. This can be used when creating static URLs in menus and navigators. You could hard-code the site area path in a menu or navigator element design and use the Idnum for each content item being displayed. This would allow you to display content with a different presentation template (for example, a printer friendly presentation template) or use different security settings.
  • Listnum - Displays a single column list of numbered links:
    1. First
    2. Second
    3. Third
  • Treenum - Displays a hierarchical numbered list:
    1.0
    1.1
    1.2
    2.0
    2.1
    2.2
  • Paddedtreenum - Similar to Treenum, but the numbers are padded:
    0001
    00010001
    00010002
    000100020001
    000100020002
  • Depth - Displays the depth of the currently processed node (in a navigator or menu) as a number. A top-level node has a depth of 1.
Back to Top

Plug-in tags

Rendering plug-ins are referenced using the plug-in tag.

[plugin:pluginname paramKey="paramVal" ]
  Tag Body Content
[/plugin:pluginname]

You can have multiple paramKeys:

[plugin:pluginname paramKey1="paramVal" paramKey2="paramVal" paramKey2="paramVal2" ]

No parameters or body:

[plugin:pluginname ]

Content tags within the plugin tag

[plugin:pluginname paramKey1=" [IDCmpnt context='current' type='sitearea' field='id' ]" ]

Note: You must use single quotes within the web content tag being used as a parameter value.

Plug-in tag with body content

To reference a plug-in with parameters and content including a reference to a component:

[plugin:pluginname paramKey1="paramVal" paramKey2="paramVal" paramKey2="paramVal2" ]
    This is the tag body content.
    <br>
     [component name="test"]
    <br>
    More content.
[/plugin:pluginname ]

Remote action plugin tag example

You can reference remote actions using plugin tags using the following format:

[plugin:RemoteAction action=" " docid=" "
    useCurrentSelection=" " dialog=" " useCurrentContext=" "]
  • action= This is the remote action to perform.
  • docid= This is the document ID of the item to run the remote action against.
  • useCurrentContext= If set to true, then the document ID is obtained form the rendering context instead of the docid attribute.
  • dialog= If set to true, when rendered within a JSR 286 web content viewer portlet the remote action is rendered as a URL that redirects the user to a hidden portal page that is used by the JSR 286 web content viewer for inline editing.

This is an example of a "new" action to create a content item:

[plugin:RemoteAction action="new" type="com.ibm.workplace.wcm.api.WCM_Content"
 pid="com.ibm.workplace.wcm.api.WCM_SiteArea/ID2" atid="com.aptrix.pluto.presentation.template/ID1"
 wcmfield.content.name="newcontent" wcmfield.autosave="true" wcmfield.saveValidate="true" ]

JSP plugin tag:

Rendering plug-ins can be referenced within JSP code using the following format:

<wcm:plugin name=" " param1="value" param2="value2" >
// Your text.
</wcm:plugin>
Back to Top

Property tag

A property tag is used to display various fields and metadata from content items and site areas.

[Property field=" " context=" " type=" " name=" " key=" " format=" " link=" " separator=" "
htmlencode=" " awareness=" " ifEmpty=" " include=" " restrict=" " resolve=" "
start=" " end=" " ]

field=" " parameter:*

  • Name - Displays the text entered in the name field of an item.
  • Title - Displays the text entered in the title field of an item.
  • Description - Displays the text entered in the description field of an item.
  • Authors - Displays the users and groups selected in the authors field of an item.
  • Owners - Displays the users and groups selected in the owners field of an item.
  • ID - Displays the GUID of an item.

Authoring template properties:

  • authtemplateid - Displays the GUID of the authoring template used by the current content item.
  • authtemplatename - Displays the name of the authoring template used by the current content item.
  • authtemplatetitle - Displays the display title of the authoring template used by the current content item.

History properties:

  • lastmodified - Displays the last modified date and the last change message.
  • lastmodifieddate - Displays the last modified date. 
  • creation - Displays the creation date. 
  • lastmodifier - Displays the name of the user who last modified the item. 
  • creator - Displays the name of the user who created the item.

Profiling properties:

  • Categories - Displays a list of categories that an item has been profiled with. 
  • Keywords - Displays a list of Keywords that an item has been profiled with.

Access level properties:

  • *User - *Displays a list of users and groups assigned user access to an item. 
  • Contributor - Displays a list of users and groups assigned contributor access to an item.
  • Editor - Displays a list of users and groups assigned editor access to an item. 
  • Manager - Displays a list of users and groups assigned manager access to an item.

Workflow Properties:

  • Status - Displays the workflow status of an item. 
  • Workflow - Displays the selected workflow of an item. 
  • Current Stage - Displays the workflow stage that the item is currently in. 
  • Publish Date - Displays the date and time selected in the publish date field of an item. 
  • Expiry Date - Displays the date and time selected in the expiry date field of an item. 
  • General Date One - Displays the date and time selected in the general date one field of an item. 
  • General Date Two - Displays the date and time selected in the general date two field of an item. 
  • Additional Viewers - Displays the names of any additional viewers selected for an item. 

    type=" " parameter

  • Content - Use this option to display a property from the current content item.
  • Parent - Use this option to display a property from the parent site area of the current content item
  • Top - Use this option to display a property from the top site area in the current path of the current content item.

context=" " parameter:

  • Selected - Use this option to select a specific site area or content item. You must then add the name of the item being referenced using the name=" " parameter. You can select an item by clicking Select.
  • Current - Use this option to display a property from the current site area or content item
  • AutoFill - Use this option when the item is determined by the search parameters of a menu, navigator, or taxonomy component. If the tag is not used within a menu, navigator, or taxonomy component, the context will revert to the current item

If you select Selected, click the Select button to select a specific site area or content item.


Table 1. Additional tag parameters

Tag parameters Details
name=" " You must specify the name of the item being referenced if the context="selected". If you specify name="./itemName", the actual path is not resolved until the item is rendered. This takes slightly longer to resolve than specifying the path to the item.
format=" " This parameter is optional and can only be used with some element types:
When field="ID":
  • format="id" displays the plain ID. If not specified, this format is used by default.
  • format="uri" outputs a wcm:oid:<id> style URI.
    When referencing user details:
  • format="cn" is used to display the common name.
  • format="dn" is used to display the distinguished name.
    When field="categories":
  • format="title" displays a list of category titles.
  • format="uri" displays a wcm:oid:<id> style URI for each listed category.
    Maximum character length:
  •  format="length:number_of_characters"** format="length:10"
    When referencing number or date elements:
  •  
  • format="DATE_SHORT"
  • format="DATE_MEDIUM"
  • format="DATE_LONG"
  • format="DATE_FULL"
  • format="DATE_TIME_SHORT"
  • format="DATE_TIME_MEDIUM"
  • format="DATE_TIME_LONG"
  • format="DATE_TIME_FULL"
  • format="TIME_SHORT"
  • format="TIME_MEDIUM"
  • format="TIME_LONG"
  • format="TIME_FULL"
  • format="relative" (The relative date is displayed as either "today", "yesterday" or the number of days ago.)** Setting parameters to format dates
  • Note on formatting numbers
separator=" " This is used when referencing a property that returns multiple results. For example, to add a line break between each result, you would use separator="<br>" . If not defined, a comma is placed between each result when rendered.
htmlencode="" If htmlencode="true" any reserved HTML characters is converted into character entities. For example, '<' is converted to '<'. This is useful if you would like to prevent users adding malicious code, or if you want to prevent users changing the look and feel of their text using HTML.

If not specified, the default setting specified by the cmpnt.htmlEncodeDefault property in the WCM WCMConfigService service is used. By default, this property is set to true.
awareness="" If awareness="true" then user names are displayed using the people awareness features. This feature displays user names as hyperlinks that allow users to contact people with whom they might want to work. Wherever person links appear, users can click the link to display a menu of actions for collaborating (contacting and working) with the person named by the link. If you, as administrator, have also configured an IBM® Lotus® Sametime® server to work with WebSphere® Portal, person links indicate whether a person is active, away, offline, or in a Do Not Disturb state.

People awareness only works in content rendered using either a local or remote rendering portlet.

If not specified, then awareness="false" and people awareness is not used.
ifEmpty=" " Enter some text to display if no result is returned by the tag. If not specified, nothing is displayed if no result is returned by the tag.
include=" " Used only with field=categories. Determines which level of a taxonomy to display:
  • exact
  • ancestors
  • descendants
  • all
    For example, if an item is profiled with a category of Sport, and include=descendants, then all the descendants of "sport" would also be displayed.
restrict=" " Used only with field=library/categories. Enter a list of categories separated by commas to only return results for the categories specified in the list. For example, restrict="library/red, library/green" only displays profile details of items profiled with the categories of red or green. If no library is specified, the default library is used.
resolve=" " This determines which type of access to resolve to when rendering access level properties:
none

virtual

inherited

inheritedonly

effective

all |

start=" "

end=" "
The start and end attributes are used to wrap the data returned by a tag within other tags, such as HTML. These attributes are not mandatory.

Back to Top



style element tag

- The style element tag is used to reference a style sheet component selected as the default style sheet in an authoring template, or a style sheet component referenced within a site area or content item using a component reference.

Note: To directly reference a specific style sheet component, use a component tag.

This is the format of a style element tag:

[StyleElement source=" " name=" " start=" " end=" "]

source=" " parameter:

  • *Template - *This option uses the style sheet specified in the authoring template of the current content item. You do not specify a name when using template as the source. To use this option, you must have selected a default style sheet in the related authoring template.
  • *Path - *This option uses the first style sheet element matching the name, specified in the name parameter, from either the current site area or content item in that order. To add a style sheet to a site area or content item, you need to use a component reference element and select a style sheet component as the component reference.

If a source type of "path" is selected, you must also select a content item and then select the component reference element that is used to reference the stylesheet.

Back to Top

URL tags

- The URLCmpnt tag is used to generate a URL to a site area or content item.

[URLCmpnt mode=" " context=" " type=" " name=" " pageDesign=" " portalTarget" " usedIn=" " start=" " end=" " htmlencode=" "]

mode=" " parameter:

  • *portal - *This generates a URL to a portal page. This is used when displaying web content within a web content viewer portlet
  • *standAlone - *This generates a URL to a web page. This is used when displaying web content using the Web Content Manager servlet.
  • *current - *This generates a URL based on the format of the current request. For example, if the current request is a WebSphere® Portal request, then mode="portal" is used.
    ----type=" " parameter*:** *Content - *Use this option to display the URL of the current content item.
  • *Parent - *Use this option to display the URL of the parent site area of the current content item
  • Top - Use this option to display the URL of the top site area in the current path of the current content item.
    ----context=" " parameter*:*
  • Selected - *Use this option to select a specific site area or content item. You must then add the name of the item being referenced using the name=" " parameter. You can select an item by clicking *Select.
  • *Current - *Use this option to retrieve the URL from the current site area or content item.
  • *AutoFill - *Use this option when the URL being retrieved is determined by the search parameters of a menu, navigator, or taxonomy component. If the tag is not used within a menu, navigator, or taxonomy component, the context will revert to the current item.

If you select Selected, click the Select button to select a specific site area or content item.
If you select Current or Autofill, click Select authoring template to select an appropriate authoring template.

If you want to render the content using an alternative presentation templates, click presentation template. This is added to the tag as the pageDesign=" " parameter.
Select Portal Page Target if you want to render the content on a specific Portal page. You can enter the compound name of the URL mapping or friendly URL of the target portal page in the tag after you add the tag to your design. This can only be used if mode="current" or mode="portal". This is added to the tag as the portalTarget=" " parameter.

Table 1. Additional tag parameters

Tag parameters Details
  name="./itemName"
   
   
   
Back to Top

Indenting element designs

- You use an indent tag to format element designs that require results to be indented.

[indentcmpnt repeat=" " offset=" " start=" " end=" " ]

Table 1. indent tag parameters

Tag parameter Description
repeat=" " Enter the text to repeat at the beginning of the indent.
start=" "

end=" "
The start and end attributes are used to wrap the data returned by a tag within other tags, such as HTML. These attributes are not mandatory.

Example:

[indentcmpnt offset="0" repeat="&amp;nbsp;&amp;nbsp;"]
Back to Top

 
 

Ultrasonic French Fries

16 Jul

It’s one of the most commonly consumed snacks in the Western world and has been made in one form or another for at least three centuries, so you might think nothing new could come of the humble french fry. But British chef Heston Blumenthal put paid to that notion years ago. He and his research chef Chris Young came up with a triple-cooked “chip” with a taste and texture that blow away anything you will find at a burger joint. Other chefs have raised the bar further. Nils Norén and Dave Arnold of the French Culinary Institute in New York City, building on work by a Polish researcher, figured out how to improve the texture inside fries by treating the potatoes with an enzyme. The chemical helps break apart the pectin in the fries, yielding a smoother mouthfeel.

Inspired by these heroic efforts, Maxime Bilet, Johnny Zhu and the other research chefs (including Young) at our culinary lab in Belle­vue, Wash., explored a variety of techniques for doing better still. The winning combination is simple in its ingredients but quite fancy in its execution. The potato batons are vacuum-sealed with 2 percent salt brine in bags to keep them intact during boiling. They are then bombarded with intense sound waves from the same device that dentists and jewelers use. A lengthy ultrasound treatment at 40 kilohertz causes the surface of each fry to crack and blister with myriad tiny bubbles and fissures.

[More]
 
 

E-Prime: The Invented Language That Has No Verb To Be

15 Jul

To be or not to be ... is not a question in the invented language of E-Prime. TopTenz explains:

Another language constructed to make a philosophical point, E-Prime is simply a version of English that forbids all forms of the verb ‘to be’ (is, was, were, etc).

According to Alfred Korzybski, who promoted the language in his 1933 book Science and Sanity, E-Prime can be used to sharpen critical thinking and make ideas clearer. For example, in E-prime a person can’t say ‘This is an awful movie’: it must be rephrased as ‘I dislike this movie.’ ‘You’re wrong’ is also impossible: instead he must say ‘I disagree with you.’ Because of this, it’s easier for speakers and listeners distinguish fact from opinion.

On the other hand, following E-Prime to the letter becomes burdensome: ‘This is a flower’ must become something like ‘English speakers call this a flower.’ Today, E-Prime remains popular, but mostly just as an interesting thought exercise to improve clarity.

Read more about the Top 10 Invented Languages: Link