text:
2010 Olympics: Figure Skating
Artistry takes center stage
by John Gettings and Christine Frantz
Related LinksMemorable Moments |
Once a vital means of transportation throughout northern Europe, ice skating evolved into a sport during the 18th century.
The man credited with giving birth to the type of figure skating we see today is Jackson Haines, an American from New York.
In the early 1860s, Haines's new combination of music, ballet, ice skating, and dancing wasn't well received in this country. So he took his revolutionary ideas to Vienna, Austria, where they flourished.
Figure skating debuted at the 1908 Olympic Summer Games in London. The singles and pairs competitions have been a part of every Winter Games since 1924. The ice dancing competition was introduced in 1976.
The men's and women's singles competitions and the pairs competition each consist of two parts: a short program, in which skaters must complete required elements; and a free skate, which is a longer program that has few restrictions and emphasizes skaters' artistry.
The ice dancing competition has three parts: a compulsory dance, an original dance, and a free skate.
Figure skating was in the spotlight in the 2002 Olympics when it was discovered that vote-swapping had pushed the Russian pair into first place above the near-flawless Canadian performance. The French judge was sent packing and in an Olympic first, the gold was awarded to both the Canadians and the Russians. In response to the events at the 2002 Olympics, figure skating judging and scoring have been overhauled. The old six-point system is gone, replaced by one in which the performance is awarded points for a technical score as well as five other elements: skating skills, transitions, performance/execution, choreography, and interpretation. Also, no more booing of any particular judge—it's now anonymous, so the whole lot of them will have to get the raspberry.
p>At the 2010 Vancouver Games, the figure skating events will be held Feb. 18–25, with the exhibition gala taking place on Feb. 27. All skating will take place at the Pacific Coliseum; ice time will be shared with short track speed skating.The men's singles will be held Feb. 16 and 18, while the women's singles will be held Feb. 23 and 25.
Figure skating is notorious for injury. Many top competitors are choosing not to participate in events leading up to the Olympics in order to be in top form for Vancouver. As of Nov. 2009, the International Skating Union's world standings (based on points accumulated in international competition)show the following women in the top four spots: current World Champion Kim Yu-Na of Korea, Italy's Carolina Kostner, Mao Asada of Japan, and five-time Canadian national champion Joannie Rochette. For the men, Czech Tomas Verner, USA's Evan Lysacek and Jeremy Abbott, and Brian Joubert of France fill the top spots.
China has two pairs in the top four, with Germany and Russian also making their presence known.
It is in the ice dancing event that things are expected to heat up in Vancouver. For the first time, the United States looks to have two ice dancing teams vying for gold. The team of Davis and White is currently ranked first, but the U.S. also has time-tested favorites in Belbin and Agosto. The Russian team of Domnina and Shabalin, and Canadians Virtue and Moir are also top contenders-fully able to work ice dancing alchemy, combining athleticism and artistry to win Olympic gold.


text:
I moderate comments so it may take a while for yours to show up.
Tuesday, April 19
Eating Well Every Day - and Celebrating Earth Week in a BIG Organic Way
I moderate comments so it may take a while for yours to show up.
151 comments:
a) I liked EARTH DINNER
b way you go organic--GROWN MY OWN
c) Your e-mail address (so I can contact you if you win).
a) I "liked" Farmgirl Fare
b) A favorite way you go organic. Buy local organics when I can
c) Your e-mail address (so I can contact you if you win).
What a great day to find your blog!!- Wendy Johnston4/19/2011 1:46 PM
Hi there I wanted to let you know that I Liked the Earth Day page. I live on a 100+ acre farm in southern West Virginia where we raise beef cattle, Katahdin Hair Sheep, and a large vegetable garden with my parents. We are operating a CSA for vegetables and recently got our distributors license for selling meat directly from our farm. email@example.com
ReplyDelete - Janet S4/19/2011 1:51 PM
I 'liked' Farmgirl Fare.
Ever since I tried organic sour cream, I've been hooked. And I only buy organic milk now.
firstname.lastname@example.com Three ways we go organic are 1)in all our dairy products (which is why this win would be great!), 2)we try to keep our meat local and if not "certified" organic at least know what the farm practices, and 3)we consider it a matter of "voting with your money" in everthing else that we try to buy organic. To us its more than just about the health of the earth, its about social justice to laborers as well.
email@example.com'm 'going organic' by gardening. I manage to grow & preserve most of the produce we eat throughout the year.
We don't have enough land for animals, so we buy pastured organic beef from friends.
I use natural products elsewhere in our home- to clean the house, and even to brush my teeth!
joshandjoanna at gmail- Anonymous4/19/2011 2:10 PM
Loved the earth dinner ideas, but I always check all your listings. All the new babies have been wonderful. I was thinking it is a good thing Mother Nature has most of that work preprogrammed into the moms.
Sincere thanks for all you do and post.
The world is a better place because of your energies.
Alida - Kathy4/19/2011 2:35 PM
I have "liked" Earth Dinner on Facebook and was already a fan of yours. I enjoy your posts...
We should all compost for several reasons: Landfills aren't utilized, it is really easy, the end result of the compost is wonderful for organic gardening. And it teaches our children good gardening habits!
I have purchased heirloom seeds for the past 3 years and have experienced bumper crops. The heirloom seeds haven't been altered and are much more heathly. These can also be passed on to the next generations!
I always try to buy locally and support my neighbors and farmers when the opportunity comes along.
Keep up your great blog!!
keden22 (@) gmail (.com) I liked Earth Dinner on FB as I am already your fan! We go organic by growing gorgeous organic heirloom food for ourselves and our friends and by shopping locally at Farmer's Markets with organic farmers. This year for the first time we bought organic pork from our wonderful neighbor farm, gorgeous meat! We also raise our own organic free range chickens and just sold our first dozen to our friend across the street who loves organic eggs.
carylanneb at gmail dot com- Anonymous4/19/2011 3:01 PM
Three ways we go organic
1. We have a rental garden and grow our own produce without pesticides and using only organic fertilizers
2. We buy organic milk
3. We buy organic free-range eggs. In the summer we buy them at the local farmer's market.
Lisaabucci (at) yahoo (dot) com - Anonymous4/19/2011 3:16 PM
a) I liked EARTH DINNER
b way you go organic- buy local, at farmers markets
c) Your e-mail address (so I can contact you if you win).
a) I "liked" Farmgirl Fare
b) A favorite way you go organic. Composting
c) Your e-mail address (so I can contact you if you win).
email@example.com What a wonderful blog you share with us! Love all the babies and their guard-doggies! We compost our kitchen waste. We garden organically. We support the local farmers and meat producers at our farmers markets. We buy organic dairy and local artisan cheeses as well as locally raised eggs. We grow our own shiitake mushrooms. We also support our chefs who are using as much locally raised food stuffs as possible. Once again thanks for the great blog! firstname.lastname@example.com
ReplyDelete- Anonymous4/19/2011 3:33 PM
Three ways I go organic:
a) Raise my own free-range chickens, pigs, and ducks.
b) Forage for as many local wild edibles as possible (especially blueberries!)
c) Buy local produce from the farmer's market in town when I can.
firstname.lastname@example.com Fun giveaway! 3 ways I go organic:
1. We have a year-round CSA membership with a local organic farm.
2. I avoid most heavily processed packaged foods and buy bulk organic whole foods whenever possible (other than the cheez-its I'm currently eating -- oops :-)
3. We compost all of our organic trash (woohoo for municipal composting -- awesome for those of us who don't have a garden of our own!)
bookgeekgirl at gmail dot comI am lucky here to have a local lamb farmer who raises his lambs au-natural (and is affordable too). I also have a year-round farmers' market that I get food from every week to supplement my own garden.
Living in a warm climate means that it is easier to go organic and close-by all year long.
(hmattax at gmail dot com)I liked Farmgirl Fare and Earth Dinner on facebook. Three ways I go organic are as follows: I recently bought Earth friendly laundry detergent. I work at a self serve frozen yogurt shop that promotes buying local. A percentage of the toppings are locally supplied. We eat at Trolley Stop Market, a restaurant/market, opened by local farmers that serves organic food.
ReplyDelete- firstname.lastname@example.com/19/2011 6:00 PM
For the last 3 years my husband and I have been removing decorative plants and shrubs from our small yard(1/3 acre lot) and replacing them with fruiting trees and berry shrubs. We've also built 3 gardens where we grow many vegetables and herbs organically. So we go organic by:
1. Growing as many fruits and vegetables as space allows in our garden.
2.Composting kitchen scraps and yard clippings.
3. Buying organic milk/dairy products and hormone/antibiotic free meat at the grocery.
I also think it's important to share with family and friends so that they can see what's possible in your backyard. I know this won't give me a better chance of winning, but I have to say that I love your blog! And my 4-year-old loves looking at the cute lambs, too. :)
1. I get a twice monthly organic fruit delivery, which I like because it supports organic food and a small business owner.
2. I subscribe to an organic CSA, and buy meat from a local "beyond organic" farmer.
3. I use (and LOVE) all of my reusable bags for grocery or any type of shopping. They're technically not organic, but I know they keep a lot of plastic out of my home!
doniamae AT gmail DOT com- Anonymous4/19/2011 8:39 PM
I liked earth dinner on Facebook.
I do organic by buying as many organic products as possible.
My email: kdznme2atgmaildotcom - Anonymous4/19/2011 9:07 PM
I buy organic meat for my boyfriend, fruit that I eat the skin of, and organic turkey on the holidays (Easter's a-comin'!). Rest of the time I schlepp it out with conventional stuff. Wish I could eat organic all the time! amianerd at yahoo dot com
ReplyDelete - Anonymous4/19/2011 10:05 PM
I liked Earth Dinner!
I go Organic as often as possible by buying organic, eating organic, and living organic!
Here's my email… sdealaman at gmail dot com
Thanks! We buy organic products whenever I can as a single mom - Stoneyfield Organic Yogurt for one and usually I can get organic carrots and onions for not too much more than the pesticide ones! My daughters and I have been using more natural and organic body products like soaps and shampoos and clean with natural cleaners, buy organic lip balms and lotions. Fortunately it is getting easier and less expensive to buy the products than it used to be - I hope somday they become mainstream! janschop at aol dot com
ReplyDelete- Anonymous4/20/2011 9:31 AM
1) I buy organic when possible.
2) Grow all organic vegies in the garden and put up the extras for winter
3) Use organic cleaners and beauty products
pkktbeyer AT gmail DOT com Oh, let's see . . .
1) Our garden is mostly organic. I only say mostly because the seeds aren't necessarily, but the practices are. "Practices" meaning the back-breaking labor of hand pulling weeds in favor of blasting them with Round-up.
2) Our sheep are raised on organic pastures. We don't have the money or equipment to be spraying fertilizers or whatever on the grass anyway. But we DO have the equipment to spread soiled hay to fertilize all over the acre of grass in the paddock. And by "equipment" I mean a pitchfork, a rake, a wheelbarrow, and two very tired people.
3) We don't buy much produce, and it's not always organic when I do buy it, but carrots are organic when I buy them. Cubby likes to chew on a whole carrot (helps with teething), so organic seemed prudent in that case especially.
countrykrisATgmailDOTcomI compost everything and use the resulting mixture in my gardens, which are all organic as well. I make my own household cleaners rather than using the chemical-based ones. We recycle nearly everything - I make over outgrown garments, reuse jars, and just generally try to be as organic as possible as well as reduce our waste. Karin - khsds2 at yahoo dot com.
ReplyDeleteI tried to "like" Earth Dinner but saw no button on their page? I posted on their wall and will keep checking back to "like"! The book looks awesome. I just started liking you about 2 weeks ago. Your site is great and I love it.
I belong to a full-diet, year-round CSA in the cold hinterlands of upstate NY. Mark and Kristin Kimball are the bomb! My favorite way to go organic is to spend my late summer like a busy bee-- canning, freezing and putting up so I can enjoy treats like blueberries, pickles, green beans, broccoli and melon in LOCAL way ALL WINTER LONG!
aquinn1970 AT yahoo DOT com- Anonymous4/20/2011 12:47 PM
I liked farmgirl fare on facebook.
buying as much as possible at the farmer's market
krystaldwilson AT gmail.com - Anonymous4/20/2011 6:40 PM
We go organic by
1) buying organic tomato and herb seedlings
2) no chemical pesticides or weed killers allowed
3) composting all our yard clippings for use in the garden
mamatrahan (at) msn (dot) com I just "liked the Farmgirl Fare FB page". As a stay at home mom of 3 kids aged 3 and twin 18-month olds, it's hard financially to go organic all the time. However, we do our best by buying organic milk when we are out of milk WIC checks for the month, and shopping organically based on the "dirty dozen."
email : firstname.lastname@example.com liked the "Earth Dinner" page, looking forward to reading more! I also like to go organic by really focusing on the things that we eat the most of, even if they're not in the "dirty dozen." If it's going in our bodies a lot, it's gotta be as natural as possible!
email: firstname.lastname@example.com- Anonymous4/21/2011 11:34 AM
I just liked Farmgirl fare on FB.
We have gone organic a few years ago by expanding our garden and canning as much as we can. Love home grown veggies in the winter months.
My email address is missysids (at) yahoo dot com - Anonymous4/21/2011 3:05 PM
A few ways I've gone organic: 1) I quit eating most meat, as it's hard to find local organic meat in my area. 2) I've moved to companion planting in my vegetable garden to eliminate the need for pesticides. 3) I've started doing the bulk of my shopping at farmers markets.
My email: firstname.lastname@example.com Great giveaway in celebration of Earth Day! Thanks. We go organic by growing our own veggies, having our own chickens for organic eggs and by choosing to by organic clothing for our little one that's on the way. I believe that even with clothing, buying organic cotton is key to help reducing pesticide waste in water sources and damaging soils. Love your blogs! email@example.com
ReplyDelete- Anonymous4/21/2011 3:25 PM
HI!! I "Liked" Earth Dinner on Facebook because I already "Like" you!
We grow our own blueberries and peppers,melons etc. We have just started(Last year) growing..and selling Goji plants which we are very excited about!!!! I traveled to China last year and brought lots of dried berries back.
WE are now also starting to raise our own StCroix sheep and should have our first Lambing season! end of July...so exciting!
email@example.com - Anonymous4/21/2011 3:37 PM
I liked it on FB! =D My favorite way to go organic is to grow my own as much as possible using healthy soil and organic seeds! Just found your blog and love it! firstname.lastname@example.com
ReplyDelete - Anonymous4/21/2011 4:58 PM
I liked you on Facebook. my favorite organic thing is to help at an organic CSA veggie farm, my 2 boys love to play in the dirt! My email is higentry at yahoo dot com. Thanks Heidi
ReplyDelete I liked this on facebook! and I like it everywhere else too! My favorite way to go organic this week is to color my Easter eggs with onion skins. I boiled the skins with the left over egg-boiling water and let it cool. Added some vinegar and soaked the eggs overnight. Lovely!
genahohman AT gmail DOT com- Anonymous4/21/2011 7:23 PM
1) I liked Earth Dinner
2) Grow my own!!! I recently started companion gardening to combat the local bugs.
3) email@example.com - Anonymous4/21/2011 8:04 PM
Since I had previously "liked" you on Facebook, my second entry is:
3 ways we go organic (already mentioned growing our own:)
1) I buy my eggs from a friend, who only feeds her chickens organic mash
2) I make my family's yogurt from organic milk
3) We use holistic remedies whenever possible, including raw local wildflower honey.
email: americanvalkyrie at hotmail dot com
Thanks! I liked Earth Dinner TWICE on FB - once from my personal account, and once from my page, Decadent Philistines Save the World. :)
We have a CSA only about 10 miles away from our house here in the Phoenix area. We purchase all of our vegetables from the farm, so it's not only organic but local. And let's not forget DELICIOUS.
My email address is allison DOT lee DOT powell AT gmail DOT comThis really is a fun contest! :)
Three of the ways that I am trying to go organic are the following:
1) We have been buying our eggs from a colleague of my husband's; we recycle the egg cartons, too (and collect them from friends to take to her). Not only are the eggs organic, but they are generally 4 days old at the most. We also usually get a duck egg or two - all for $2 a dozen!!!!!
2) Next month, I'll be headed out to a local peach orchard and picking as many peaches, apricots, and plums as I can possibly fit into my truck and then canning them, drying them, making them into jam, etc. The farm is organic (although not certified so) and focuses on supporting the community.
3) I'm purposely seeking out local restaurants that use local and sustainable farms (such as the peach farm I noted above) for their ingredients. What a huge difference in the quality of the meal!
My email address is allison DOT lee DOT powell AT gmail DOT com3 Ways I go Organic -
1 Try to grow some veggies and herbs in my yard every summer.
2. Buying organic milk, yogurt, cereals and snacks - and certain produce.
3. Shopping at our Local Farmers' Markets (found a couple new ones that are nearby through localharvest.org) and especially going to pick our own strawberries, apples and peaches at nearby farms (one is certified organic).
cdreyes AT yahoo DOT comI liked you on facebook
I liked earth dinner on face book
And I go organic by:
Giving yummy earth organic lollipops to my nieces and nephews
Buying organic starter plants and seeds (most things I start from seed but not tomatoes since I can't get them to grow) (ps I buy my seeds from seed savers exchange - lurve them)
I feed my husband only certified organic grass fed beef (I'm vegan so I don't eat it but I changed him from a mcdonald's man to someone who eats stuff that is better)
My email
Joy . Clark (at) gmail . COMWe go organic by: growing our own garden without the use of pesticides or chemical fertilizers, we consistently buy the dirty dozen foods organic and other organic foods as our budget allows, We're getting our own chickens to provide us with eggs and we'll feed them food remains that are health for them and then use their poop in our garden as fertilizer!
Jlfmcnichols at gmail dot comI liked Earth Dinner on FBook too!
I work with an organic farm here on the Central Coast of California. All last year I wrote the newsletters, did research on vegetables and fruit and learned a lot to apply to my own baby attempts at gardening. The farm offers a CSA program and I am just building the website (you can see it - still a work in progress: www.cvorganicfarm.com). I eat and cook and share as much organic food as possible!Three more ways that we go organic:
1. Back in the 90's we had an organic market garden. We don't sell anymore, but we inspired a few others to grow their own organic gardens.
2. We start most of our own seedlings using organic methods.
3. We buy organic coffee beans from Equal Exchange....the best!
cgulvin AT hotmail DOT com- Anonymous4/22/2011 4:47 AM
I "liked" Farmgirl on Facebook.
My favorite way to go organic is to grow my own veggies & herbs!
slswayze AT gmail DOT com - Alicia4/22/2011 6:38 AM
Hello! 3 ways I go organic... can I say garden, garden, garden? Hahaha... Here we go:
1. I compost and use that in my garden
2. I visit the farmers market
3. I try to shop from the organic section when possible.
aleash25 at yahoo dot com - lhouchin34/22/2011 7:28 AM
I "like" Farmgirl Fare on Facebook!! My favorite way to go organic is growing my own vegetables and herbs in my garden and shopping at my local co op. I also make my own laundry detergent and cleaners LHouchin3 AT ivytech DOT edu Thank you love your blog especially the gardening posts!!
ReplyDelete - lhouchin34/22/2011 7:30 AM
I "liked" Earth Dinner. Another favorite way I go organic is buying organic produce at my local farmers market on Fridays. It's a great way to get good food while staying local and I know it's fresh and affordable! LHouchin3 AT ivytech DOT edu
ReplyDelete - Elizabeth H4/22/2011 7:49 AM
3. Leave a comment here on this post telling me:
a) Three ways you go organic. Raise my own chickens for eggs, raise my own cattle for beef, forage in the forest for berries and mushrooms.
b) Your e-mail address (so I can contact you if you win). lizage1 at yahoo dot com - Elizabeth H4/22/2011 7:51 AM
2. "Like" Farmgirl Fare on Facebook (this option for new fans only), then leave a comment here on this post telling me:
a) That you "liked" it. DONE!
b) A favorite way you go organic. grow all my own veggies for year round consumption
c) Your e-mail address (so I can contact you if you win). lizage1 at yahoo dot com I liked you on facebook. We get better at local and organic every year (its hard sometimes). I've found a source of local and naturally grown chickens. We buy meat from a locally owned butcher who gets his meat from a naturally grown farmer. I am very active and buy from our farmers market and other local food organizations. I can and freeze. I'm getting better at growing more food. I compost. Is that enough?
ReplyDelete- Anonymous4/22/2011 8:38 AM
I liked Earth Dinner on Facebook, since I have already followed your amazing posts for a while now. I go organic by GROWING MY OWN veggies and fruit and supplementing from our awesome farmers' market. Meat and dairy are always organic, free-range, and local if I can find it. It's a dream of mine to live your life, sheep and all.
jshankar913ATyahooDOTcom - Anonymous4/22/2011 8:49 AM
Like Earth Dinner on FB - Kitty Mayne
1. We go organic by growing our own berries and veggies and canning/freezing/drying them for winter. 2. We also have half share in a CSA. 3. We buy chicken and beef from local organic farmers.
maynekitty[at]live[dot]com - Chris4/22/2011 8:54 AM
Love this giveaway!
I do what I can...where I can. I frequent the closest Farmers' Market. 'Have started gardening myself in the last two years. I buy organic when/where possible. I also think practically when choosing flowers for my yard...going with native plants as much as possible to conserve water. And I plant specifically for birds, too!
My favorite place is the organic blueberry ranch! (I went picking SIX times last summer!) Gotta love that freezer stash!
I LOVE this "place" and come to "see" you almost every day!
silvernsassy AT yahoo DOT com I've been slowly going more and more organic like this:
1) I've started growing my own food at the side of my house (hard because no one spot in my yard is "full sun" - but doable if you do a little research about what will grow in part-shade conditions)
2) I participate in a local (WI) summer CSA
3) I compost & use that where I can
laima UNDERSCORE r AT yahoo DOT comI like Earth Dinner on facebook :)
My favorite way to go organic is to simply look for MORE ways to be able to slowly incorporate more pieces fo organic in to my life (slowly, so my pocketbook doesn't freak out) ... most recently, this meant joining a local *meat* CSA. Every other week for three months I picked up assorted cured meats made locally and from locally grown, organic meat.- Erin S4/22/2011 9:03 AM
3 ways I go organic:
1. grow most of our own fruits/veggies organically
2. raise chickens on organic feed for eggs
3. shop at the local farmer's market
tightwaderin AT cox DOT net I've gone organic by:
1) ripping out my front lawn to grow more of my own fruits and vegetables, no pesticides allowed!
2) Started a second garden next to the vegetable garden that's solely for attracting beneficial insects (bee's, ladybugs, butterflies, etc)
3)Joined a local organic CSA to supplement items that I currently dont grow in my own yard.
My email is betweenthelimes AT gmail DOT comOrganic is the only way to go!
1. Every little sunny patch in our yard is growing our own organic food, herbs and fruits.
2. We fill in our groceries with a local CSA year-round. They rock, and they can give us a few more items that I can't grow myself.
3. We regularly shop the farmer's markets here (and there are a ton of them) to pick up bigger bunches of organic stuff too - like boxes of berries and mounds of cucumbers to can and preserve for the rest of the year.
happyflapjack AT gmail DOT comI already "like" you on Facebook, so I added Earth Dinner as well to my likes.
I shop only the certified organic vendors at our three local farmer's markets. I try to buy only the organic products at Trader Joe's (one of my jobs is working there)
My yard and garden is organic, I have lots of herbs and several fruit trees and a few container veggies as well.I'm entering by placing my comment here on the blog.
We practice oranic living in an urban environment in these ways:
1. We grow our own!! (square foot gardening)
2. We compost.
3. We support local growers by patronizing the downtown farmer's market at Pepper Place in Bham Alabama.
4. We support local growers/producers by buying their locally produced food and art items at AlabamaGoods.
elsnow AT homewood dot k12 dot al dot usI could almost smell the oregano! Great photos! The Earth Dinner book has great ideas.Thanks!
Here's my usual organic efforts:
I like to grow my own fruits and veggies.
I compost as much as I can from the kitchen and garden.
I LOVE to shop the farmers' markets
fogardengirl AT comcast Dot net- Abiga/Karen4/22/2011 11:02 AM
I "liked" Earth Dinner. I go organic by buying local eggs from pastured chickens. Soon I will help slaughter some broilers too. email@example.com
ReplyDelete - Anonymous4/22/2011 11:21 AM
1. Liked Earth Dinner on Facebook.
2. A favorite way to go organic is growing our own herbs and vegetables. We hope to add chickens to the equation soon as well.
3. email@example.com - Anonymous4/22/2011 1:28 PM
liked Earth Dinner on facebook
Recycle all paper, bottles
Buy organic from our Farmers Mkt here in the Valley
Love the pictures and farm views - Anonymous4/22/2011 3:09 PM
We go organic by growing our own produce as space allows on our condo patio
We buy locally produced eggs and dairy products
We purchase grass fed beef and chicken as availabe
megden2007ATgmailDOTcom - Anonymous4/22/2011 5:39 PM
We go organic three ways by joining a CSA, buying our meats from local farmers, and getting eggs from friends who raise chickens!
jessicadotpritchardatgmaildotcom Love all your stuff...we are hunting for property looking to go rural and you are an inspiration!
We go organic by 1) 100% organically growing (and sharing) much of our own veggies, fruit, and herbs and buying the bulk of what we don't grow from our local organic veggie farm, and our local organic beef and raw milk producers, 2) foraging - much of it the weeds in our own yard! and 3) producing homemade cleaning and personal products from our harvest. I am at quozzle at hotmail dot com.- Mary from Madison4/22/2011 6:35 PM
I so enjoy your posts! Liked Earth Dinner on Facebook as LaFarge is not far from me and we love organic.
1. We participate in a CSA and I work with an organic farmer at the one and only DANE COUNTY FARMERS' MARKET!
2. We grow vegetables and small fruits in our backyard organically.
3. We buy local.
buchhma AT live dot com
Happy Easter! Hope the lambs have a great time gamboling! I Like what Ohio Farm Girl said! And I agree!
Pick me!!
Three ways that we go organic:
1) I have a pea patch in our backyard complete with Hoop house that grows a good deal of our veggies every year. I get my seeds from organic, non-GMO producers (like Baker Creek - they are rad.)
2) I make our own organic compost using Vermicomposting and pile compost methods and use this in our garden. (No chemicals for us!)
3) When I shop, I buy organic ingredients and make all my daughter's baby food from scratch with these ingredients. The more we buy, the more they will offer!!
l.w.nickell AT gmail DOT come- Sally M.4/22/2011 7:03 PM
#1 - Growing as much of my own food as possible on my shady city lot and rental garden.
#2- Purchasing organic foods as much as possible, especially organic milk to make yogurt and bulk grains and seeds from the co-op.
#3 - I know this is not really organic, but I buy most of my clothes in the Thrift stores, which reduces the amount of cotton that is needed, most of which is heavily saturated with pesticides. I must say that this does not feel like a hardship to me, as the quality of clothing at the Thrift shops is so obscenely good and I save so much money by doing this, that I can't really claim any credit for this.
Thank you for the site, especially for the bran muffin recipes and variations.
New comments are not allowed.

subset: commoncrawl


text:
Ofloxacin Tablets
Price And Quantity
- Box/Boxes
- 50
- Box/Boxes
Product Specifications
- Generic Drugs
- Tablets
- as directed by physician
- cool and dry place
Product Description
What is Ofloxacin for
This medication is a antibiotic, prescribed for certain types of bacterial infections such as chronic bronchitis, pneumonia, skin and skin structure infections, and others. It fights bacteria in the body.
How does Ofloxacin work:
Ofloxacin works to harm the bacteria and fight the infection.
How should Ofloxacin be used:
It comes as a tablet to take by mouth, with or without food. It also comes as eye drops to instill into the affected eyes as directed by your physician. Adult- PO- The recommended dose range is 200 to 800 mg per day in divided doses. Eye drops- Instill 1-2 drops into affected eye(s) every 4 hours.
Common side effects of Ofloxacin :
Headache. Belly pain. Upset stomach or throwing up. Many small meals, good mouth care, sucking hard, sugar-free candy, or chewing sugar-free gum may help. Loose stools (diarrhea). Yogurt or probiotics may help. You may get these products at health food stores or in some pharmacies. Tendons may rarely get irritated and tear. Unsafe allergic effects may rarely happen.
What do I do if I miss a dose
Take a missed dose as soon as you think about it. If it is close to the time for your next dose, skip the missed dose and go back to your normal time. Do not take 2 doses at the same time or extra doses. Do not change the dose or stop this drug. Talk with the doctor.
What precautions should I take when taking Ofloxacin :
Do not give oral product to a child younger than 18 years of age. If you have an allergy to ofloxacin or any other part of this drug. If you have had tendons get irritated or torn when taking this drug or an alike drug in the past. Tell your doctor if you are allergic to any drugs. Make sure to tell about the allergy and what signs you had. This includes telling about rash; hives; itching; shortness of breath; wheezing; cough; swelling of face, lips, tongue, or throat; or any other signs. If you have myasthenia gravis. If you are breast-feeding.
When do I need to seek medical help
If you think there was an overdose, call your local poison control center or ER right away. Signs of a very bad reaction to the drug. These include wheezing; chest tightness; fever; itching; bad cough; blue or gray skin color seizures or swelling of face, lips, tongue, or throat. A fast heartbeat. Very bad dizziness. Very upset stomach or throwing up. Very loose stools (diarrhea), even after drug is stopped. Pain in back of the ankle. Joint pain or swelling. Very bad muscle pain or weakness. Numbness or tingling in your hands or feet. Any rash. Side effect or health problem is not better or you are feeling worse.
Can I take Ofloxacin with other medicines:
Sometimes drugs are not safe when you take them with certain other drugs and food. - Taking them together can cause bad side effects. - Be sure to talk to your doctor about all the drugs you take.
Are there any food restrictions
Avoid Alcohol
How do I store Ofloxacin :
Store in a cool, dry place away from the reach of children. - Medicines must not be used past the expiry date.
Pregnancy Category
Category C : Animal reproduction studies have shown an adverse effect on the fetus and there are no adequate and well-controlled studies in humans, but potential benefits may warrant use of the drug in pregnant women despite potential risks.
Therapeutic Classification
Eye Anti-Infectives & Antiseptics, Ear Anti-Infectives & Antiseptics
Trade Information
- 1000 Per Day
- 1-2 Days
- All India
Related Products
Contact Us


text:
What is a gravity assist or a swingby for a spacecraft? I've heard about spacecraft gaining velocity from passing close to planets and being 'sling shot'-ed into a higher orbit. Where does this energy come from?
Gravity assist is a technique used to speed up, slow down or change the direction of a spacecraft as it approaches a planet within our solar system. This technique saves fuel that would otherwise have to be used to make these adjustments.
The basic principles behind gravity assist have to do with the relative velocities of the spacecraft and of the planets involved and the conservation of angular momentum. The spacecraft approaches the planet. Because the planet is moving too (while orbiting the Sun), it actually transfers some of its angular momentum to the spacecraft. What the craft gains in velocity, the planet loses. The mass of the planet is huge compared to that of the spacecraft so the loss is imperceptible. For example, Galileo increased its speed at Earth by 11,620 mph in 1990 and 8,280 mph in 1992. The Earth slowed down in its orbit by a speed of about 5 billionths of an inch per year from the two events.
The technique of gravity assist or swingby approach for a spacecraft was used as early as the Mariner 10 mission in 1973-1974 and has been used recently to create unique orbits such as with the Ulysses spacecraft.
Submitted by Mark (Maryland, USA)
Submitted by Jean-Marc (Oullins, France)
(September 3, 1998)


text:
Net::LDAP::RFC - List of related RFC's |
Net::LDAP::RFC - List of related RFC's
The LDAP protocol is defined in the following RFC's
The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. This document provides a road map of the LDAP Technical Specification.
This document describes the protocol elements, along with their semantics and encodings, of the Lightweight Directory Access Protocol (LDAP). LDAP provides access to distributed directory services that act in accordance with X.500 data and service models. These protocol elements are based on those described in the X.500 Directory Access Protocol (DAP).
The Lightweight Directory Access Protocol (LDAP) is an Internet protocol for accessing distributed directory services that act in accordance with X.500 data and service models. This document describes the X.500 Directory Information Models, as used in LDAP.
This document describes authentication methods and security mechanisms of the Lightweight Directory Access Protocol (LDAP). This document details establishment of Transport Layer Security (TLS) using the StartTLS operation.
This document details the simple Bind authentication method including anonymous, unauthenticated, and name/password mechanisms and the Simple Authentication and Security Layer (SASL) Bind authentication method including the EXTERNAL mechanism.
This document discusses various authentication and authorization states through which a session to an LDAP server may pass and the actions that trigger these state changes.
The X.500 Directory uses distinguished names (DNs) as primary keys to entries in the directory. This document defines the string representation used in the Lightweight Directory Access Protocol (LDAP) to transfer distinguished names. The string representation is designed to give a clean representation of commonly used distinguished names, while being able to represent any distinguished name.
Lightweight Directory Access Protocol (LDAP) search filters are transmitted in the LDAP protocol using a binary representation that is appropriate for use on the network. This document defines a human-readable string representation of LDAP search filters that is appropriate for use in LDAP URLs (RFC 4516) and in other applications.
This document describes a format for a Lightweight Directory Access Protocol (LDAP) Uniform Resource Locator (URL). An LDAP URL describes an LDAP search operation that is used to retrieve information from an LDAP directory, or, in the context of an LDAP referral or reference, an LDAP URL describes a service where an LDAP operation may be progressed.
Each attribute stored in a Lightweight Directory Access Protocol (LDAP) directory, whose values may be transferred in the LDAP protocol, has a defined syntax that constrains the structure and format of its values. The comparison semantics for values of a syntax are not part of the syntax definition but are instead provided through separately defined matching rules. Matching rules specify an argument, an assertion value, which also has a defined syntax. This document defines a base set of syntaxes and matching rules for use in defining attributes for LDAP directories.
The previous Lightweight Directory Access Protocol (LDAP) technical specifications did not precisely define how character string matching is to be performed. This led to a number of usability and interoperability problems. This document defines string preparation algorithms for character-based matching rules defined for use in LDAP.
This document is an integral part of the Lightweight Directory Access Protocol (LDAP) technical specification. It provides a technical specification of attribute types and object classes intended for use by LDAP directory clients for many directory services, such as White Pages. These objects are widely used as a basis for the schema in many LDAP directories. This document does not cover attributes used for the administration of directory servers, nor does it include directory objects defined for specific uses in other documents.
This specification provides a mechanism for Lightweight Directory Access Protocol (LDAP) clients to obtain the authorization identity the server has associated with the user or application entity. This mechanism is specified as an LDAP extended operation called the LDAP ``Who am I?'' operation.
This document describes the LDAP/X.500 'entryUUID' operational attribute and associated matching rules and syntax. The attribute holds a server-assigned Universally Unique Identifier (UUID) for the object. Directory clients may use this attribute to distinguish objects identified by a distinguished name or to locate an object after renaming.
This document defines the Lightweight Directory Access Protocol (LDAP) Assertion Control, which allows a client to specify that a directory operation should only be processed if an assertion applied to the target entry of the operation is true. It can be used to construct ``test and set'', ``test and clear'', and other conditional operations.
This document specifies an extension to the Lightweight Directory Access Protocol (LDAP) to allow the client to read the target entry of an update operation. The client may request to read the entry before and/or after the modifications are applied. These reads are done as an atomic part of the update operation.
This document extends the Lightweight Directory Access Protocol (LDAP) to support absolute True and False filters based upon similar capabilities found in X.500 directory systems. The document also extends the String Representation of LDAP Search Filters to support these filters.
This document provides a collection of schema elements for use with the Lightweight Directory Access Protocol (LDAP) from the COSINE and Internet X.500 pilot projects.
This document describes schema for representing X.509 certificates, X.521 security information, and related elements in directories accessible using the Lightweight Directory Access Protocol (LDAP). The LDAP definitions for these X.509 and X.521 schema elements replace those provided in RFCs 2252 and 2256.
Each attribute stored in a Lightweight Directory Access Protocol (LDAP) directory has a defined syntax (i.e., data type). A syntax definition specifies how attribute values conforming to the syntax are normally represented when transferred in LDAP operations. This representation is referred to as the LDAP-specific encoding to distinguish it from other methods of encoding attribute values. This document defines an attribute option, the binary option, that can be used to specify that the associated attribute values are instead encoded according to the Basic Encoding Rules (BER) used by X.500 directories.
This document defines the Lightweight Directory Access Protocol (LDAP) Proxy Authorization Control. The Proxy Authorization Control allows a client to request that an operation be processed under a provided authorization identity instead of under the current authorization identity associated with the connection.
This document defines the Lightweight Directory Access Protocol (LDAP) Client Update Protocol (LCUP). The protocol is intended to allow an LDAP client to synchronize with the content of a directory information tree (DIT) stored by an LDAP server and to be notified about the changes to that content.
This specification describes a Lightweight Directory Access Protocol (LDAP) extended operation to cancel (or abandon) an outstanding operation. Unlike the LDAP Abandon operation, but like the X.511 Directory Access Protocol (DAP) Abandon operation, this operation has a response which provides an indication of its outcome.
This document describes a control for the Lightweight Directory Access Protocol version 3 that is used to return a subset of attribute values from an entry. Specifically, only those values that match a ``values return'' filter. Without support for this control, a client must retrieve all of an attribute's values and search for specific values locally.
It is often desirable to be able to indicate the natural language associated with values held in a directory and to be able to query the directory for values which fulfill the user's language needs. This document details the use of Language Tags and Ranges in the Lightweight Directory Access Protocol (LDAP).
This document updates the specification of the component matching rules for Lightweight Directory Access Protocol (LDAP) and X.500 directories (RFC3687) by collecting the Abstract Syntax Notation One (ASN.1) definitions of the component matching rules into an appropriately identified ASN.1 module so that other specifications may reference the component matching rule definitions from within their own ASN.1 modules.
This document defines a mapping of the Policy Core Information Model to a form that can be implemented in a directory that uses Lightweight Directory Access Protocol (LDAP) as its access protocol. This model defines two hierarchies of object classes: structural classes representing information for representing and controlling policy data as specified in RFC 3060, and relationship classes that indicate how instances of the structural classes are related to each other. Classes are also added to the LDAP schema to improve the performance of a client's interactions with an LDAP server when the client is retrieving large amounts of policy-related information. These classes exist only to optimize LDAP retrievals: there are no classes in the information model that correspond to them.
This document provides a collection of matching rules for use with the Lightweight Directory Access Protocol (LDAP). As these matching rules are simple adaptations of matching rules specified for use with the X.500 Directory, most are already in wide use.
The syntaxes of attributes in a Lightweight Directory Access Protocol (LDAP) or X.500 directory range from simple data types, such as text string, integer, or boolean, to complex structured data types, such as the syntaxes of the directory schema operational attributes. Matching rules defined for the complex syntaxes usually only provide the most immediately useful matching capability. This document defines generic matching rules that can match any user selected component parts in an attribute value of any arbitrarily complex attribute syntax.
In X.500 directories, subentries are special entries used to hold information associated with a subtree or subtree refinement. This document adapts X.500 subentries mechanisms for use with the Lightweight Directory Access Protocol (LDAP).
X.500 collective attributes allow common characteristics to be shared between collections of entries. This document summarizes the X.500 information model for collective attributes and describes use of collective attributes in LDAP (Lightweight Directory Access Protocol). This document provides schema definitions for collective attributes for use in LDAP.
This document details schema and protocol elements for representing and managing named subordinate references in Lightweight Directory Access Protocol (LDAP) Directories.
The integration of the Lightweight Directory Access Protocol (LDAP) and external authentication services has introduced non-DN authentication identities and allowed for non-directory storage of passwords. As such, mechanisms which update the directory (e.g., Modify) cannot be used to change a user's password. This document describes an LDAP extended operation to allow modification of user passwords which is not dependent upon the form of the authentication identity nor the password storage mechanism used.
This document describes two LDAPv3 control extensions for server side sorting of search results. These controls allows a client to specify the attribute types and matching rules a server should use when returning the results to an LDAP search request. The controls may be useful when the LDAP client has limited functionality or for some other reason cannot sort the results but still needs them sorted. Other permissible controls on search operations are not defined in this extension.
This document describes a file format suitable for describing directory information or modifications made to directory information. The file format, known as LDIF, for LDAP Data Interchange Format, is typically used to import and export directory information between LDAP-based directory servers, or to describe a set of changes which are to be applied to a directory.
This specification defines how HTTP Digest Authentication can be used as a SASL [RFC 2222] mechanism for any protocol that has a SASL profile. It is intended both as an improvement over CRAM-MD5 [RFC 2195] and as a convenient way to support a single authentication mechanism for web, mail, LDAP, and other protocols.
When scheduling a calendar entity, such as an event, it is a prerequisite that an organizer has the calendar address of each attendee that will be invited to the event. Additionally, access to an attendee's current ``busy time'' provides an a priori indication of whether the attendee will be free to participate in the event. In order to meet these challenges, a calendar user agent (CUA) needs a mechanism to locate individual user's calendar and free/busy time. This memo defines three mechanisms for obtaining a URI to a user's calendar and free/busy time. These include:
LDAP supports lightweight access to static directory services, allowing relatively fast search and update access. Static directory services store information about people that persists in its accuracy and value over a long period of time. Dynamic directory services are different in that they store information about people that only persists in its accuracy and value while people are online. Though the protocol operations and attributes used by dynamic directory services are similar to the ones used for static directory services, clients that are bound to a dynamic directory service need to periodically refresh their presence at the server to keep directory entries from getting stale in the presence of client application crashes. A flow control mechanism from the server is also described that allows a server to inform clients how often they should refresh their presence.
The protocol described in this document is designed to satisfy some of the operational requirements within the Internet X.509 PKI. Specifically, this document addresses requirements to provide access to PKI repositories for the purposes of retrieving PKI information and managing that same information. The mechanism described in this document is based on the LDAPv2, defined in RFC 1777, defining a profile of that protocol for use within the PKIX and updates encodings for certificates and revocation lists from RFC 1778. Additional mechanisms addressing PKIX operational requirements are specified in separate documents.
LDAP uses X.500-compatible distinguished names for providing unique identification of entries. This document defines an algorithm by which a name registered with the Internet Domain Name Service can be represented as an LDAP distinguished name.
This document describes a method for adding authentication support to connection-based protocols. To use this specification, a protocol includes a command for identifying and authenticating a user to a server and for optionally negotiating protection of subsequent protocol interactions. If its use is negotiated, a security layer is inserted between the protocol and the connection. This document describes how a protocol specifies such a command, defines several mechanisms for use by the command, and defines the protocol used for carrying a negotiated security layer over the connection.
This IETF Integrated Directory Services(IDS)
Working Group
proposes a standard specification for a simple Internet White
Pages service by defining a common schema for use by the
various White Pages servers. This schema is independent of
specific implementations of the White Pages service. This
document specifies the minimum set of core attributes of a
White Pages entry for an individual and describes how new
objects with those attributes can be defined and published. It
does not describe how to represent other objects in the White
Pages service. Further, it does not address the search sort
expectations within a particular service.
MIXER (RFC 2156) defines an algorithm for use of a set of global mapping between X.400 and RFC 822 addresses. This specification defines how to represent and maintain these mappings (MIXER Conformant Global Address Mappings of MCGAMs) in an X.500 or LDAP directory. Mechanisms for representing OR Address and Domain hierarchies within the DIT. These techniques are used to define two independent subtrees in the DIT, which contain the mapping information.
URLs are being widely used to specify the location of Internet resources. There is an urgent need to be able to include URLs in directories that conform to the LDAP and X.500 information models, and a desire to include other types of URIs as they are defined. A number of independent groups are already experimenting with the inclusion of URLs in LDAP and X.500 directories. This document builds on the experimentation to date and defines a new attribute type and an auxiliary object class to allow URIs, including URLs, to be stored in directory entries in a standard way.
The Lightweight Directory Access Protocol (LDAP) is extensible. It provides mechanisms for adding new operations, extending existing operations, and expanding user and system schemas. This document discusses considerations for designers of LDAP extensions.
This document provides procedures for registering extensible elements of the Lightweight Directory Access Protocol (LDAP). The document also provides guidelines to the Internet Assigned Numbers Authority (IANA) describing conditions under which new values can be assigned.
The Internet is used for information exchange and communication between its users. It can only be effective as such if users are able to find each other's addresses. Therefore the Internet benefits from an adequate White Pages Service, i.e., a directory service offering (Internet) address information related to people and organizations.
This document describes the way in which the Internet White Pages Service (from now on abbreviated as IWPS) is best exploited using today's experience, today's protocols, today's products and today's procedures.
This document describes an extension to the Lightweight Directory Access Protocol (LDAP) Modify operation to support an increment capability. This extension is useful in provisioning applications, especially when combined with the assertion control and/or the pre- read or post-read control extension.
This document defines the Lightweight Directory Access Protocol (LDAPv3) schema for representing Universal Description, Discovery, and Integration (UDDI) data types in an LDAP directory. It defines the LDAP object class and attribute definitions and containment rules to model UDDI entities, defined in the UDDI version 3 information model, in an LDAPv3-compliant directory.
The Lightweight Directory Access Protocol (LDAP) Bulk Update/Replication Protocol (LBURP) allows an LDAP client to perform a bulk update to an LDAP server. The protocol frames a sequenced set of update operations within a pair of LDAP extended operations to notify the server that the update operations in the framed set are related in such a way that the ordering of all operations can be preserved during processing even when they are sent asynchronously by the client. Update operations can be grouped within a single protocol message to maximize the efficiency of client-server communication.
The protocol is suitable for efficiently making a substantial set of updates to the entries in an LDAP server.
The International Telecommunications Union Standardization Sector (ITU-T) has created the H.350 series of Recommendations that specify directory services architectures in support of multimedia conferencing protocols. The goal of the architecture is to 'directory enable' multimedia conferencing so that these services can leverage existing identity management and enterprise directories. A particular goal is to enable an enterprise or service provider to maintain a canonical source of users and their multimedia conferencing systems, so that multiple call servers from multiple vendors, supporting multiple protocols, can all access the same data store.
Because SIP is an IETF standard, the contents of H.350 and H.350.4 are made available via this document to the IETF community. This document contains the entire normative text of ITU-T Recommendations H.350 and H.350.4 in sections 4 and 5, respectively. The remaining sections are included only in this document, not in the ITU-T version.
This document extends the Lightweight Directory Access Protocol (LDAP) bind operation with a mechanism for requesting and returning the authorization identity it establishes. Specifically, this document defines the Authorization Identity Request and Response controls for use with the Bind operation.
This document defines a schema, object classes and attributes, for printers and printer services, for use with directories that support Lightweight Directory Access Protocol v3 (LDAP-TS). This document is based on the printer attributes listed in Appendix E of Internet Printing Protocol/1.1 (IPP) (RFC 2911). A few additional printer attributes are based on definitions in the Printer MIB (RFC 1759).
This document recommends the retirement of version 2 of the Lightweight Directory Access Protocol (LDAPv2) and other dependent specifications, and discusses the reasons for doing so. This document recommends RFC 1777, 1778, 1779, 1781, and 2559 (as well as documents they superseded) be moved to Historic status.
This document discusses the fundamental requirements for replication of data accessible via the Lightweight Directory Access Protocol (version 3) (LDAPv3). It is intended to be a gathering place for general replication requirements needed to provide interoperability between informational directories.
This document describes schema in support of user/password
authentication in a LDAP (Lightweight Directory Access Protocol)
directory including the authPassword attribute type. This attribute
type holds values derived from the user's password(s)
(commonly using
cryptographic strength one-way hash). authPassword is intended to
used instead of userPassword.
This document specifies two Lightweight Directory Access Protocol (LDAP) attributes, vendorName and vendorVersion that MAY be included in the root DSA-specific Entry (DSE) to advertise vendor-specific information. These two attributes supplement the attributes defined in section 3.4 of RFC 2251.
This memo provides a selection of object classes and attribute types for use in conjunction with public-key cryptography and Lightweight Directory Access Protocol (LDAP) accessible directories. It also includes ASN.1 syntax for all constructs.
The strength of the TISDAG (Technical Infrastructure for Swedish Directory Access Gateways) project's DAG proposal is that it defines the necessary technical infrastructure to provide a single-access- point service for information on Swedish Internet users. The resulting service will provide uniform access for all information -- the same level of access to information (7x24 service), and the same information made available, irrespective of the service provider responsible for maintaining that information, their directory service protocols, or the end-user's client access protocol.
This document defines a multipurpose internet mail extensions (MIME) directory profile for holding a lightweight directory access protocol (LDAP) schema. It is intended for communication with the Internet schema listing service.
This document describes a procedure for mapping between Service Location Protocol (SLP) service advertisements and lightweight directory access protocol (LDAP) descriptions of services. The document covers two aspects of the mapping. One aspect is mapping between SLP service type templates and LDAP directory schema. Because the SLP service type template grammar is relatively simple, mapping from service type templates to LDAP types is straightforward. Mapping in the other direction is straightforward if the attributes are restricted to use just a few of the syntaxes defined in RFC 2252. If arbitrary ASN.1 types occur in the schema, then the mapping is more complex and may even be impossible. The second aspect is representation of service information in an LDAP directory. The recommended representation simplifies interoperability with SLP by allowing SLP directory agents to backend into LDAP directory servers. The resulting system allows service advertisements to propagate easily between SLP and LDAP.
This document describes the fundamental requirements of an access control list (ACL) model for the LDAP directory service. It is intended to be a gathering place for access control requirements needed to provide authorized access to and interoperability between directories.
While the X.500 standards define many useful attribute types [X520] and object classes [X521], they do not define a person object class that meets the requirements found in today's Internet and Intranet directory service deployments. We define a new object class called inetOrgPerson for use in LDAP and X.500 directory services that extends the X.521 standard organizationalPerson class to meet these needs.
CORBA is the Common Object Request Broker Architecture defined by the Object Management Group. This document defines the schema for representing CORBA object references in an LDAP directory.
This document defines the schema for representing Java objects in an LDAP directory. It defines schema elements to represent a Java serialized object, a Java marshalled object, a Java remote object, and a JNDI reference.
This document describes an LDAPv3 control extension for simple paging of search results. This control extension allows a client to control the rate at which an LDAP server returns the results of an LDAP search operation. This control may be useful when the LDAP client has limited resources and may not be able to process the entire result set from a given LDAP query, or when the LDAP client is connected over a low-bandwidth connection. Other operations on the result set are not defined in this extension. This extension is not designed to provide more sophisticated result set management.
This document defines a C language application program interface to LDAP, which is designed to be powerful, yet simple to use. It defines compatible synchronous and asynchronous interfaces to LDAP to suit a wide variety of applications. This document gives a brief overview of the LDAP model, then an overview of how the API is used by an application program to obtain LDAP information. The API calls are described in detail, followed by an appendix that provides some example code demonstrating the use of the API.
This specification describes the Lightweight Directory Access Protocol (LDAP) Content Synchronization Operation. The operation allows a client to maintain a copy of a fragment of the Directory Information Tree (DIT). It supports both polling for changes and listening for changes. The operation is defined as an extension of the LDAP Search Operation.
This specification describes a Lightweight Directory Access Protocol (LDAP) extended operation to reverse (or ``turn'') the roles of client and server for subsequent protocol exchanges in the session, or to enable each peer to act as both client and server with respect to the other.
Domain registration data has typically been exposed to the general public via Nicname/Whois for administrative purposes. This document describes the Referral Lightweight Directory Access Protocol (LDAP) Service, an experimental service using LDAP and well-known LDAP types to make domain administrative data available.
The OpenLDAP Project is operating an experimental LDAP (Lightweight Directory Access Protocol) referral service known as the ``OpenLDAP Root Service''. The automated system generates referrals based upon service location information published in DNS SRV RRs (Domain Name System location of services resource records). This document describes this service.
LDAPv2 clients as implemented according to RFC 1777 have no notion of referral. The integration between such a client and an Index Mesh, as defined by the Common Indexing Protocol, heavily depends on referrals and therefore needs to be handled in a special way. This document defines one possible way of doing this.
This document defines an LDAPv3 based mechanism for signing directory operations in order to create a secure journal of changes that have been made to each directory entry. Both client and server based signatures are supported. An object class for subsequent retrieval are 'journal entries' is also defined. This document specifies LDAPv3 controls that enable this functionality. It also defines an LDAPv3 schema that allows for subsequent browsing of the journal information.
This document describes an experimental mechanism for mapping entities related to TCP/IP and the UNIX system into X.500 entries so that they may be resolved with the LDAP. A set of attribute types and object classes are proposed, along with specific guidelines for interpreting them. The intention is to assist the deployment of LDAP as an organizational nameservice. No proposed solutions are intended as standards for the Internet. Rather, it is hoped that a general consensus will emerge as to the appropriate solution to such problems, leading eventually to the adoption of standards. The proposed mechanism has already been implemented with some success.
Organizations running multiple directory servers need an ability for administrators to determine who is responsible for a particular server. This is conceptually similar to the 'sysContact' object of SNMP. The administratorsAddress attribute allows a server administrator to provide the contact information of the responsible party for an LDAP server. This can be used by management clients which are, for example, checking the state of a replication or referral topology, to provide a way for the user of the management client to send email to manager of a particular server.
Lightweight Directory Access Protocol (LDAP) update operations, such as Add, Delete, and Modify operations, have atomic, consistency, isolation, durability (ACID) properties. Each of these update operations act upon an entry. However, It is often desirable to update two or more entries in a single unit of interaction, a transaction. Transactions are necessary to support a number of applications including resource provisioning. This document defines an LDAP extension to support transactions.
This document consists of two primary components, a schema for agents that make use of the Lightweight Directory Access protocol (LDAP) and a proposed use case of that schema, for distributed configuration of similar directory user agents. A set of attribute types and an objectclass are proposed. In the proposed use case, directory user agents (DUAs) can use this schema to determine directory data location and access parameters for specific services they support. In addition, in the proposed use case, attribute and objectclass mapping allows DUAs to re-configure their expected (default) schema to match that of the end user's environment. This document is intended to be a skeleton for future documents that describe configuration of specific DUA services.
This document defines the Lightweight Directory Access Protocol (LDAP) No-Op control which can be used to disable the normal effect of an operation. The control can be used to discover how a server might react to a particular update request without updating the directory.
Each attribute stored in a Lightweight Directory Access Protocol (LDAP) directory has a defined syntax (i.e., data type). A syntax definition specifies how attribute values conforming to the syntax are normally represented when transferred in LDAP operations. This representation is referred to as the LDAP-specific encoding to distinguish it from other methods of encoding attribute values. This document introduces a new category of attribute options, called transfer encoding options, that can be used to specify that the associated attribute values are encoded according to one of these other methods.
This document defines an 'namedObject' structural object class for the Lightweight Directory Access Protocol (LDAP) and X.500. This is useful for entries with no natural choice of structural object class, e.g. if an entry must exist even though its contents are uninteresting.
This document defines the Lightweight Directory Access Protocol (LDAP) Don't Use Copy control extension which allows a client to specify that copied information should not be used in providing service. This control is based upon the X.511 dontUseCopy service control option.
This document defines attributes that can be retrieved via Lightweight Directory Access Protocol version 3 (LDAP) requests, which contain URIs pointing to the privacy policy documents. These documents describe the privacy policy concerning access to a directory server, and the privacy policies that apply to the contents of the directory (a subtree of entries).
Abstract Syntax Notation One (ASN.1) defines a general framework for annotating types in an ASN.1 specification with encoding instructions that alter how values of those types are encoded according to ASN.1 encoding rules. This document defines the supporting notation for encoding instructions that apply to the Generic String Encoding Rules (GSER), and in particular defines an encoding instruction to provide a machine-processable representation for the declaration of a GSER ChoiceOfStrings type.
As LDAP is used more extensively for managing various kinds of data, one often encounters a need to preserve both the ordering and the content of data, despite the inherently unordered structure of entries and attribute values in the directory. This document describes a scheme to attach ordering information to attributes in a directory so that the ordering may be preserved and propagated to other LDAP applications.
In order to facilitate remote administration and auditing of LDAP server operation, it is desirable to provide the server's operational logs themselves as a searchable LDAP directory. These logs may also be used as a persistent change log to support various replication mechanisms. This document defines a schema that may be used to represent all of the requests that have been processed by an LDAP server. It may be used by various applications for auditing, flight recorder, replication, and other purposes.
This document describes the LDAP/X.500 'entryDN' operational attribute. The attribute provides a copy of the entry's distinguished name for use in attribute value assertions.
This document defines the Lightweight Directory Access Protocol (LDAP) Relax Rules Control which allows a directory user agent (a client) to request the directory service temporarily relax enforcement of various data and service model rules.
This document defines a new DHCP option for delivering configuration information for LDAP services. Through this option, the client receives an LDAP URL [8] of the closest available LDAP server/replica that can be used to authenticate users or look up any useful data.
This document describes Attribute Types and an Object Class for use in representing XRI (eXtensible Resource Identifier) values in LDAP (Lightweight Directory Access Protocol) and X.500 directory services.
Many network devices, application servers, and middleware components of a enterprise software infrastructure generate some form of session tracking identifiers, which are useful when analyzing activity and accounting logs to group activity relating to a particular session. This document discusses how Lightweight Directory Access Protocol version 3 (LDAP) clients can include session tracking identifiers with their LDAP requests. This information is provided through controls in the requests the clients send to LDAP servers. The LDAP server receiving these controls can include the session tracking identifiers the the log messages it writes, enabling LDAP requests in the LDAP server's logs to be correlated with activity in logs of other components in the infrastructure. The control also enables session tracking information to be generated by LDAP servers and returned to clients and other servers. Three formats of session tracking identifiers are defined in this document.
This document defines an attribute that enables administrative clients using the Lightweight Directory Access Protocol (LDAP) to determine the source of directory entries.
This document defines two controls that extend the LDAPv3 search operation to provide a simple mechanism by which an LDAP client can receive notification of changes that occur in an LDAP server. The mechanism is designed to be very flexible yet easy for clients and servers to implement.
This document describes a Virtual List View control extension for the LDAP Search operation. This control is designed to allow the ``virtual list box'' feature, common in existing commercial e-mail address book applications, to be supported efficiently by LDAP servers. LDAP servers' inability to support this client feature is a significant impediment to LDAP replacing proprietary protocols in commercial e-mail systems.
The control allows a client to specify that the server return, for a given LDAP search with associated sort keys, a contiguous subset of the search result set. This subset is specified in terms of offsets into the ordered list, or in terms of a greater than or equal comparison value.
Net::LDAP::RFC - List of related RFC's |


text:
Greg Silvermaster
Nathan Gregory Silvermaster (27 November 1898 – 1964) was born in Russia, attended school in China, received a B.A. from the University of Washington in Seattle and a Ph.D. from the University of California. He became a naturalized American citizen in 1927.
KGB in the USG
Silvermaster headed up a very large KGB operation inside the United States Government (USG) during World War II. Elizabeth Bentley idenitifed Silvermaster as a long-time courier for Soviet intelligence. While nominally remaining on the employment rolls of the Farm Security Administration, Silvermaster arranged in 1942 to be detailed to the Board of Economic Warfare. The transfer, however, triggered objections from military counter-intelligence who suspected he was a hidden Communist and regarded him as a security risk. On 16 July, the U.S. Civil Service Commission recommended "Cancel eligibilities...and bar him for the duration of the National Emergencey."
Silvermaster denied any Communist links and appealed to Under Secretary of War Robert Patterson to overrule the security officials. Harry Dexter White contacted Patterson and told him that suspicions about Silvermaster were baseless. Lauchlin Currie, a presidential aide personally phoned Patterson and urged a reconsideration of Silvermaster's case. Silvermaster subsequently received two promotions and pay raises.
At the War Production Board Silvermaster was able to provide the Soviet Union with a large amount of data on arms, aircraft, and shipping production. In June 1943, Silvermaster sent a War Production Board report on arms production in the United States, including bombers, pursuit planes, tanks, propelled guns, howitzers, radar and submarines, sub chasers, and the like, to Soviet intelligence. Then in December 1944, the New York KGB office cabled another Silvermaster report stating: "(Silvermaster) has sent us a 50-page Top Secret War Production Board report . . . on arms production in the U.S."
Silvermaster is also associated with Harry Dexter White at the Bretton Woods conference, and his testimony before the US Senate Internal Security Subcommittee covers "175 pages of interrogation and exhibits" regarding his espionage activities in the US. His code name in Soviet intelligence and in the Venona files is "Pal", "Pel" and "Pol" (i.e. Paul).
- August 1935 to November 1938 Farm Security Administration
- November 1938 to July 1940 Maritime Labor Board
- July 1940 to December 1944 U.S. Department of Agriculture
- 1942 to 1945 U.S. Department of Treasury
- mid 1945 Reconstruction Finance Corporation (became the War Assets Corporation)
- March 1946 resigned from government
Silvermaster group
The Silvermaster ring operated primarily in the Department of the Treasury but also had contacts in the Army Air Force and in the White House. Sixty-one of the Venona cables concern the activities of the Silvermaster spy ring.
- Nathan Gregory Silvermaster, Chief Planning Technician, Procurement Division, United States Department of the Treasury; Chief Economist, War Assets Administration; Director of the Labor Division, Farm Security Administration; Board of Economic Warfare; Reconstruction Finance Corporation Department of Commerce
- Helen Silvermaster (wife)
- Schlomer Adler, United States Department of the Treasury
- Norman Chandler Bursler, United States Department of Justice Anti-Trust Division
- Frank Coe, Assistant Director, Division of Monetary Research, Treasury Department; Special Assistant to the United States Ambassador in London; Assistant to the Executive Director, Board of Economic Warfare; Assistant Administrator, Foreign Economic Administration
- Lauchlin Currie, Administrative Assistant to President Roosevelt; Deputy Administrator of Foreign Economic Administration; Special Representative to China
- Bela Gold, Assistant Head of Program Surveys, Bureau of Agricultural Economics, United States Department of Agriculture; Senate Subcommittee on War Mobilization; Office of Economic Programs in Foreign Economic Administration
- Sonia Steinman Gold, Division of Monetary Research U.S. Treasury Department; U.S. House of Representatives Select Committee on Interstate Migration; U.S. Bureau of Employment Security
- Irving Kaplan, Foreign Funds Control and Division of Monetary Research, United States Department of the Treasury Foreign Economic Administration; chief advisor to the Military Government of Germany
- George Silverman, civilian Chief Production Specialist, Material Division, Army Air Force Air Staff, War Department, Pentagon
- William Henry Taylor, Assistant Director of the Middle East Division of Monetary Research, United States Department of Treasury
- William Ullman, delegate to United Nations Charter meeting and Bretton Woods conference; Division of Monetary Research, Department of Treasury; Material and Services Division, Air Corps Headquarters, Pentagon
- Anatole Volkov
- Harry Dexter White, Assistant Secretary of the Treasury; Head of the International Monetary Fund
- Christopher M. Andrew and Vasili Mitrokhin, The Sword and the Shield: The Mitrokhin Archive and the Secret History of the KGB (New York: Basic Books, 1999).
- 746, 747, 748 Venona New York KGB to Moscow 25 May 1942 Data on construction and distribution of U.S. military aircraft.
- 1061, 0162, 1063 Venona New York KGB to Moscow 3 July 1943 p.1 p.2 Numerical strength of the United States Army Air Forces.
External links
- Silvermaster Group FBI FOIA
- Silvermaster file Summaries from the Education and Research Institute
- FBI Master Chart of the Silvermaster network
- FBI Silvermaster file, Morgan to Clegg, Janaury 14, 1947
- FBI Silvermaster file, Brent to Hennrich, October 30, 1950


text:
Want to make one too? It's so easy.
I was looking through one of my sewing drawers and came across this thimble that I've had forever. We all have them, but I don't use the metal kind. I use a leather thimble when hand sewing my hexagons. What to do with this little thimble...let's make a necklace!!
All you need is a thimble, a jump ring and a necklace. I used a silver chain that I had, but you could use a ribbon or cording.
Jump rings come in packages at the craft store in the jewelry section.
For the pincushion, you'll need a small scrap of fabric, stuffing, a needle and thread.
an awl and a hammer.
If you are using the drill, start out slow and drill just below the lip of the thimble. Don't forget to drill on an old piece of wood, because you will be drilling right through.
I used the awl and hammer technique. Make sure you are on a sturdy surface and hammer on an old piece of wood, because the awl will be poking through.
Take a small tap to start the hole. Once there is a dink...hammer until it pokes through.
Here is the hole.
There will be rough metal shavings on the other side. You can clip those with wire cutters and/or file with sand paper.
Now loop the jump ring through the hole.
Squeeze the ring closed with pliers.
You could be finished here, because this is perfect as a necklace.
However, if you want to sew with your thimble necklace...let's add a pincushion!!
I used a spool of thread to trace the circle.
With needle and thread, sew a running stitch around the edge of the circle.
Doesn't have to be perfect, because we are just gathering it up.
Gather up the circle to look like a little bowl.
Fill with a little craft stuffing. Pull thread to gather tightly and knot off to secure.
I used a little hot glue to attach the pincushion inside the thimble.
Glob of hot glue on the bottom of the gathered pincushion...
Insert into thimble.
All Done!!
Oh, wait...she needs pins!!
Just hang around your neck and you'll never lose your pins and needles again.
Ok, I have to say...this is the cutest little thing ever. I'm not patting myself on the back, I just think anything in miniature is adorable!!
Happy Tuesday,


text:
The pregnant ichthyosaur female from Holzmaden (Germany) that perished 182 million years ago puzzled researchers for quite some time: The skeleton of the extinct marine reptile is almost immaculately preserved and the fossilized bones of the mother animal lie largely in their anatomical position.
This is an ichthyosaur female with scattered embryos outside of the body of the mother [Credit: UZH] |
The bones of the ichthyosaur embryos, however, are a different story: For the most part, they lie scattered outside the body of the mother. Such peculiar bone arrangements are repeatedly found in ichthyosaur skeletons.
According to the broadly accepted scientific doctrine, this is the result of exploding carcasses: Putrefaction gases produced during the decomposition process cause the carcass to swell and burst. Through such explosions, even the bones of embryos can supposedly be ejected out of the body.
Based on an elaborate series of measurements and an analysis of the physical-biological parameters, however, a research team of sedimentologists, paleontologists and forensic scientists has now managed to dispel the myth of exploding dinosaur carcasses.
Putrefaction gas pressure not high enough
In order to gauge the pressure of the particular gases that can actually develop inside a putrefying ichthyosaur, the researchers sought comparative models and found one in human corpses: Humans and many ichthyosaur species have a similar size range.
Consequently, the formation of similar amounts of putrefaction gas can be expected during decomposition. At the Institute of Forensic Medicine in Frankfurt, Germany, a manometer was inserted into the abdominal cavity through the umbilicus in one hundred corpses.
The putrefaction gas pressures measured were only 0.035 bar. In the case of the ichthyosaur carcasses that came to rest below 50 to 150 meters of water, however, putrefaction gas pressures of over five to 15 bar would have been necessary to cause an explosion.
According to Zurich paleontologist Christian Klug, gas pressures of this dimension and therefore actual explosions are impossible: "Large vertebrates that decompose cannot act as natural explosive charges." And he is convinced: "Our results can be extended to lung-breathing vertebrates in general."
What actually happened 182 million years ago
According to the researchers, the fate of ichthyosaur carcasses can be reconstructed as follows: Normally, the bodies sank to the seabed immediately post mortem.
In very deep, hospitable waters, they were broken down completely through putrefaction,scavengers, bone-destroying organisms and dissolving processes.
In shallower water (up to 50 meters) and a temperature of over four degrees Celsius, however, the corpses often rose back to the surface on account of the putrefaction gases accumulating inside the body.
At the surface, exposed to the waves and scavengers, they decomposed within anything from a few days to weeks and the bones were scattered over a wide area on the seabed as they sank.
Ichthyosaur skeletons only remained preserved more or less in their anatomical position under very special circumstances: A lack of oxygen, medium water depths and insignificant bottom water currents. Because only then were the putrefaction gases compressed strongly enough through the high water pressure and dissolved in the bodily fluids, and the carcasses not completely broken down due to a lack of scavengers.
The carcass of the ichthyosaur female from Holzmaden thus sank to the bottom of the sea, which was up to 150 meters deep, where it decomposed. In doing so, the decomposed embryo skeletons were transported out of the body of the mother by minor currents at the seabed.
Source: University of Zurich [March 27, 2012]


text:
9 May 2013 - UNODC Executive Director Yury Fedotov has launched the new UNODC Liaison and Partnership Office in Brazil together with the Secretary of National Drug Policy of the Ministry of Justice, Vitore Maximiano. Mr. Fedotov traveled to the country this week to formalize this new partnership with the Brazilian government: "The opening of a Liaison and Partnership Office in Brazil is a very important moment in the development of UNODC's integrated response to illicit drugs and transnational organized crime".
UNODC has been operating in Brazil for over 20 years, and has been a Regional Office since 2001 covering Brazil, Argentina, Chile, Paraguay and Uruguay. The newly established Liaison and Partnership Office in Brasilia will operate in a new format focused on regional and inter-regional cooperation - including South-to-South initiatives - with an added emphasis on promoting collaboration and dialogue with other countries.
"UNODC's added value is its ability to work with Member States to build sustainable responses to the issues of illicit drugs, corruption and crime. The new Liaison and Partnership Office is a vital part of that strategy", said Mr. Fedotov. He expects that this format of a Liaison and Partnership Office will serve as a model for similar initiatives in other countries.
During the event, Maximiano declared: "This is a strategic partnership for Brazil and neighboring countries to act on decreasing supply and reducing demand for drugs."
The mid-term strategy of the UNODC Liaison and Partnership Office in Brazil will focus on: transnational organized crime; illicit trafficking, including drugs; corruption; terrorism prevention; justice; drug use prevention and treatment; trend analysis; and support for research and policy development.


text:
Audi Q4 e-tron on sale now from £40,750
Audi has confirmed its all-new, all-electric Q4 e-tron will start at £40,750, with the Q4 Sportback e-tron priced from £42,250. Deliveries of the Q4 e-tron have already started, while the first Sportback customers are due to take delivery in October. Both are capable of around 320-miles on a full charge
From launch, both models are available in three variants; the 35, 40 and 50 Quattro. Not surprisingly, the 50 Quattro gets Audi's iconic all-wheel drive as standard, while both the 35 and 40 have power sent solely to the rear wheels.
Hide AdAdvertisement
Hide AdAll models are also available with Audi's Sport, S Line, Edition 1 and Vorsprung trim levels, each adding their own heightened level of standard equipment.
In simple terms, details and pricing of the Audi Q4 e-tron are:• 35: 168bhp, 229lb ft, 9.0sec 0-62mph, 52kWh battery, 211/216-mile range, from £40,750 (Sportback £42,250)• 40: 201bhp, 229lb ft, 8.5sec 0-62mph, 77kWh battery, 323/328-mile range, from £44,990 (Sportback £46,960)• 50 Quattro: 295bhp, 339lb ft, 6.2sec 0-62mph, 77kWh battery, 303/309-mile range, from £51,370 (Sportback £52,870)
When it comes to charging, the Q4 e-Tron can support 11kW AC charging and up to 125kW DC charging. As a result, Audi claims around 80 miles can be fed into its new EV in just 10 minutes using the fastest of chargers.Audi has also rather sensibly offered an 'e-Tron Charging Service'. Cleverly it means owners receive an RFID card, and then sign up to a tariff that gives them streamlined access to chargers from different networks. The primary result? It saves you the annoyance of having to sign up to a host of individual networks.
One of the strengths which promises to set the Q4 e-tron part from its competitors is the quality of finish in the cabin; Audi says it's similar to that of a Q7. That, allied to the fact that though the SUV's external dimensions are similar to this of an Audi Q3, the interior space is more akin to that of a Q5. And in the non-Sportback version, the Q4 e-tron is fitted with a sliding rear bench which can increase bootspace to 520 litres.
Hide AdAdvertisement
Hide AdInside the cabin the fascia is dominated by a the central MMI touchscreen, which is 10.1-inch as standard, but increases to 11.6-inch as an option. There's also only one touchscreen, and thankfully, positioned below it is the manually-controlled air-con switchgear. The Q4 also introduces a steering wheel with a flat top and bottom on S-line spec models, and includes haptic touch panel buttons.


text:
The issue of Mac malware is one that is often understood poorly. Malware for the Mac does exist, but it is rare and generally only affects Macs for brief periods until it is discovered and blocked by Apple. Learning about the threats, and how to protect yourself against future malware, is the only way to stay safe online.
I strongly advise reading this guide in order, rather than jumping straight to the topic that interests you most. It will be a bit of a long read, but each chapter is written on the assumption that you will already be familiar with the material from previous chapters, so that I don't have to constantly repeat myself. Of course, if you are already familiar with the topic of Mac malware and are just looking for clarification on a particular topic, feel free to skip ahead.
Table of Contents
- What are the threats?
- How does Mac OS X protect me?
- Do I need anti-virus software?
- How can I protect myself?
- Am I infected?
- Malware Dictionary
If you are serious about security, I also highly recommend reading one of Apple's Mac OS X Security Configuration Guides. If you have further questions, you are welcome to contact me, or to seek advice on the Malwarebytes Malware Removal Help for Mac forum.


text: Carole Walker is also performing at The Cincy Folk Festival, taking place June 27, 2015 at The Southgate House Revival. Proceeds from this event will benefit local NPR radio station WNKU. Lineup includes AJ Ghent Band, Chicago Farmer, Kim Taylor, David Gans, Hickory Robot, Young Heirlooms, Honey and Houston , Mamadrones, Ma Crow & The Lady Slippers, Tracy Walker, Carole Walker, My Brother The Bear, Wilder, The Gabbard Brothers, SOUSE, Bulletville, Daniel Wayne and The Silver Lines. $20, 18+ http://www.ticketfly.com/event/828823


text:
2005 Alaska Cell FOP - Neotectonics of the Central Alaska Range
Group photo in front of Beaver Pond Trench Site. Healy, Alaska
Silly group photo in front of the Beaver Pond Trench Site. Healy, Alaska
September 3-5, 2005 (Labor Day weekend)
The guidebook is now available as a PDF. Please let me know if there are any major problems and a revised copy can be posted by the end of the week. We will have a few emergencies copies on hand, but please try to print your own.
We will begin the trip Saturday morning at 8 am in the parking lot behind the Natural Sciences Building on the campus of the University of Alaska, Fairbanks. If you won't be in Fairbanks, then meet us at the mouth of Suntrana Creek (6.7 miles east of Healy on Healy Road - see guidebook) at 11 am.
Looking forward to seeing everyone!
Evan Thoms
U.S. Geological Survey, Alaska Science Center
4210 University Drive, Anchorage, AK 99508
voice: 907-786-7409
fax: 907-786-7401
Oblique west-directed view of the Nenana River valley and Central Alaska Range foothills


text:
US Centers for Disease Control, Swine flu Director's Update Brief, Day of Planning for an H1N1 Vaccination Campaign, 18 May 2009
From WikiLeaks
Unless otherwise specified, the document described here:
- Was first publicly revealed by WikiLeaks working with our source.
- Was classified, confidential, censored or otherwise withheld from the public before release.
- Is of political, diplomatic, ethical or historical significance.
Any questions about this document's veracity are noted.
The summary is approved by the editorial board.
See here for a detailed explanation of the information on this page.
If you have similar or updated material, see our submission instructions.
- Release date
- May 19, 2009
The US Centers for Disease Control (CDC) is the peak body for the controling the spread of "swine" flu.
See also US Centers for Disease Control: Swine flu Directors Briefing, 14 May 2009.
Further information
File size in bytes


text:
After School Safety and Enrichment for Teens Program (ASSETs Program)
The Kern High School District (KHSD) is providing this notice of intent to apply for the After School Safety and Enrichment for Teens Program. The application is due on or before November 15, 2018. This notice outlines KHSD's plan for submitting the application through the California Department of Education. This notice identifies KHSD as the Local Education Agency responsible for submitting the application for funding. The application and any waiver request will be available for public review after submission of the application.
KHSD currently operates one expanded learning program at Arvin High School. The program provides students with academic support, enrichment opportunities, and a nutritious snack and dinner at no cost to students or families.
KHSD is applying for the After School Safety and Enrichment for Teens Program grant in order to fund expanded learning programs to seven additional sites in KHSD for the 2019-2020 school year: East, Foothill, Golden Valley, Mira Monte, North, Shafter or South. The successful Arvin High expanded learning program is currently in high demand and meeting student and family needs in that community. KHSD intends to apply for funding in order to serve the maximum number of students possible at sites where there is most need for free, daily expanded learning programs.
We also take this opportunity to inform private schools, faith-based organizations, and community-based organizations serving young people and families in our area of our intent to provide safe, accessible academic support, enrichment opportunities, and family literacy programs in the aforementioned schools. Parties interested in participating in our proposal are asked to contact Felisa Patiño-Longoria at 661-827-3285 or send Felisa an email.


text:
This article is more than 1 year old
Google readies 'late fall' Chrome OS release
Just how late is late?
Google is planning to spin out its browser-based Chrome OS "operating system" in the "late fall" of 2010, according to a Mountain View wonk.
Sundar Pichai, who was speaking at the Computex show yesterday, said the company's Windows rival would arrive later this year. However, Google's product management veep didn't nail a specific date.
That's pretty much sticking to what Google has already confirmed about when Chrome OS will be released.
As we reported last month, the ad broker unleashed a preliminary software development kit for Native Client, its native-code browser plug-in.
Google has said that Native Client will be an "important part" of its Chrome OS, which is set to debut on x86 and ARM netbooks by the end of the year.
The original research version of native Client ran on x86-32, and recently Google introduced versions that runs on x86-64 and ARM. The firm said Native Client executables run at about 97 per cent of the speed of unmodified native code.
The company announced it was releasing an operating system initially for netbooks in July 2009. Google said at the time that Chrome OS would land in the second half of this year. ®


text:
Fuel prices fall as big four supermarkets make 3p cuts
These cuts were swiftly followed by its 'big four' rivals - Tesco cutting petrol and diesel prices by up to 3p per litre on Monday afternoon, and Morrisons and Sainsbury's making similar announcements.
The cost of fuel had already fallen slightly last week, bringing to a halt the recent steep rises.
Before the supermarket announcements, Office of National Statistics (ONS) figures showed that unleaded petrol stood at 116.5 pence per litre - 0.1 pence per litre more than the previous week - with the cost of diesel similarly having dropped - by 0.1 pence per litre to 118.9 pence per litre.


text:
Kanye West is being forced to bid adieu to yet another one of his divorce attorneys amid proceedings with Kim Kardashian.
Ahead of Friday (August 5)'s trial-setting conference between Kim and Ye, Samantha Spector asked a judge to relieve her as counsel, according to TMZ. She was originally set to withdraw next week, but the judge allowed her to head out early on Friday. Spector said her relationship with Kanye was "irretrievably broken," but didn't disclose why.
Spector is the fifth divorce attorney to call it quits and now Kanye is lawyer-less.
Kim was declared legally single back in March, but these proceedings are regarding custody and property, TMZ reported.
As far as their relationship goes, they're "getting along" now and have been spotted supporting their children together at sporting events and family gatherings.