text:
Rose-breasted grosbeak
August 2011
Respites for migratory birds
Saving Great Lakes stopover sites.
Kim Grveles and Sumner Matteson
How different it is to observe a silent wood thrush in fall at Manitowoc County's Point Beach State Forest! During spring, one cannot help but be transfixed by the wood thrush's flute-like, ethereal ee-oh-lay, ee-oh-lay – a triumphant melody from a songbird newly returned from wintering in the Neotropics. Now, thanks to the technological advances in tracking small animals, we can follow the migratory routes of this forest denizen as it migrates to and from the shores of Lake Michigan.
Researchers use a small, 1.5-gram device called a light level geolocator that captures and measures the intensity of visible light every minute and allows them to determine latitude and longitude coordinates. They now not only know how far a wood thrush migrates (233-271 kilometers per day in spring), but also the number and approximate duration of visits to, and relative locations of, "stopover sites," where the bird briefly stops to refuel before continuing its migration.
Every spring and fall, tens of mil millions of migrating birds sweep through the Great Lakes region and stop at a variety of sites on their way to breeding grounds as far north as Greenland and the Arctic Ocean and wintering grounds as far south as Argentina's Tierra del Fuego. These stopover sites provide birds with critical food and shelter en route. Loss of stopover habitats poses an ongoing threat to the health and stability of migratory bird populations in the Great Lakes region.
Wisconsin Stopover Initiative takes wing
For decades, reported declines in migratory bird populations have resulted in studies focused primarily on breeding and, to a lesser extent, wintering bird populations. Little serious attention had been given to identifying, prioritizing and protecting migratory bird stopover sites.
Many ornithologists believe that migration may be a part of the life cycle in which birds are most vulnerable. During migration, birds are under physiological stress and mortality may be quite high. For one group of migrants, the wood warblers, mortality rates during migration may be 15 times higher than in breeding and wintering periods, with adult rates as high as 85 percent for migrating black-throated blue warblers. Similar rates might also be true for the wood thrush and other forest-dependent migratory songbirds.
The Wisconsin Stopover Initiative (WISI), launched in 2005, aims to place protection of migratory stopover sites, particularly along the Great Lakes, in the forefront of conservation. Founded by the Department of Natural Resources (DNR) and The Nature Conservancy (TNC) with funding from the Natural Resources Foundation of Wisconsin and State Wildlife Grants, WISI's goals are to protect 30,000 acres (about 25 percent of total coastal zone acreage) of critical stopover habitat in the Lake Michigan basin and 6,000 acres (about 5 percent of total coastal zone acreage) in the Lake Superior basin over the next decade.
To meet this challenge, the Department of Natural Resources depends upon a myriad of partners – including federal, state and local agencies as well as landowners, conservation organizations, private organizations and businesses – to accomplish the following four key steps:
One size doesn't fit all
Migratory birds require an array of sites between wintering and breeding areas to survive, including sites not often thought of as having conservation value. Ornithologists recognize these different types of sites and creatively categorize them as Fire Escapes, Convenience Stores and Full-service Hotels.
Fire Escapes are sites such as a city park or a fragmented forest on an island in Lake Michigan that may receive less use because they are resource-poor, yet they are vital during times of stress as places for migrants to seek shelter from predators or storms.
Convenience Stores are areas with intermediate amounts of resources, typically larger in size than a Fire Escape, such as a county park. These sites are used occasionally or regularly and allow migrants to replenish enough energy stores to continue on to their next stop.
Full-service Hotels are extensive, intact areas that are rich in resources and contain a diversity of habitat types that provide abundant food, water and shelter to large numbers of birds on a consistent basis. Examples of Full-service Hotels include a state or national park, national wildlife refuge or state wildlife area. All three types of stopover sites must be protected if we are to establish a network of sites that spans the Great Lakes region and beyond.
Recognizing the urgency of establishing a network of protected sites, the Department of Natural Resources invited local wildlife professionals, birders and other experts to attend workshops in 2006 to identify migratory stopover sites, which they knew well. These experts drew site boundaries on quadrangle maps and provided details about the habitats, surrounding land uses and migratory bird uses at 223 migratory bird sites. The data, combined with the literature and expert opinion, were used to construct spatial Geographic Information System (GIS) stopover habitat models that predict where migratory birds are likely to concentrate in each basin, thus helping to fill in gaps in our collective knowledge of Wisconsin's stopover sites.
We produced GIS habitat models for three bird groups – landbirds (songbirds and other perching birds), waterfowl/ waterbirds and shorebirds – in each Great Lakes basin in Wisconsin. One important finding was that the Lake Michigan basin has more sites and a larger area where action is needed to preserve stopover habitats than the Lake Superior basin.
Partners are key to success
As urban development expands in coastal areas, public land becomes increasingly important for providing migrating birds places to stop, rest and refuel. Although some publicly owned lands in the Great Lakes basins support high concentrations of migratory birds during spring and fall, these properties may be degraded by invasive species that displace native plants migratory birds depend on for food and cover. Stopover habitat quality may also decline due to habitat fragmentation, a lack of vertical or horizontal vegetation structure affecting food and cover availability, and an inadequate surface water depth and/or quality.
For WISI to effectively protect, manage and maintain quality stopover habitats, partnerships are key, including TNC – the DNR's first stopover partner – and our primary funding source, the Natural Resources Foundation of Wisconsin. The stopover project represents the collaborative efforts of seven TNC state chapters, Audubon chapters, the Wildlife Habitat Council, Canadian partner organizations and many other organizations. Since 2003, TNC has taken the lead in identifying, protecting and restoring stopover sites in fast-developing areas of the Great Lakes region, beginning with sites on Lake Erie. The Nature Conservancy's Dr. David Ewert helped frame the stopover issue for the Department of Natural Resources and encouraged us to develop the models that we now use to assist land trusts, agency personnel and others.
Since 2006, WISI has formed partnerships with local land trusts, watershed groups, citizens and property managers to implement a strategic stopover plan. We are beginning to see the protection of migratory bird stopover sites become a conservation priority on the Great Lakes and are well on our way to achieving our protection goals by working with many agencies and organizations. Protection includes land acquisitions/easements; stewardship activities such as habitat restoration on public and private lands; recommendations on wind energy and communication tower sitings; application of bird diversion techniques on tall structures; and community planning and zoning.
Land trusts recognize the importance of conserving critical stopover habitats along the Great Lakes shores because of increasing recreational and development pressures affecting landscapes that interest them. For example, in 2007 the Ozaukee Washington Land Trust (OWLT) expressed an interest in restoring a golf course to provide stopover habitat for shorebirds (see sidebar).
Now called the Forest Beach Migratory Preserve, this innovative stopover site provides valuable habitat on an important migratory bird corridor known as the Lake Michigan Flyway, a link between Canada and the Northwest Territories and Central and South America for many shorebirds, flycatchers, vireos, swallows, thrushes, warblers, sparrows and other birds. Rapidly declining species, many with globally important breeding populations in Wisconsin, such as the golden-winged warbler, will likely benefit from this restoration.
There also is a growing interest among governmental and non-governmental organizations in establishing stopover sites. The Forest Beach Migratory Preserve has generated interest among counties along Lake Michigan, not only because of the intrinsic conservation values but because there are potential economic rewards from birders willing to seek out and explore a Great Lakes bird preserve.
The Stopover Initiative in action
Mark Martin of the DNR's State Natural Areas program has embraced the Stopover Initiative and is involved with two major efforts to protect and restore stopover habitat along Lake Michigan. Using our stopover habitat models and known priority site data, Martin is currently working with the Door County Land Trust, The Ridges Sanctuary, and TNC to protect more than 1,500 acres of stopover habitat along Door County's coast through land acquisition using U.S. Fish and Wildlife Coastal Wetland and Knowles-Nelson Stewardship funds.
"The importance of these properties," Martin commented, "is they include critical habitats, such as mixed hardwood forests, lowland forest, and coastal wetlands, for tens of thousands of migratory birds every spring and fall." Martin also asserts that land protection efforts will provide habitat for nesting birds including 17 species of wood warblers as well as for rare species such as the dwarf lake iris and Hine's emerald dragonfly. "These sites will protect natural communities, will help maintain water quality, and will provide land for education and research, and for the public to enjoy," Martin said.
Martin is also involved with a DNR restoration project that is working with many partners to remove nonnative phragmites (giant reed grass) along 118 miles of Lake Michigan shoreline and 3,600 acres of coastal wetlands in six counties. Nonnative phragmites replaces native vegetation and provides little or no food or shelter for most wetland- dependent wildlife, including migratory birds.
In Manitowoc County, at Martin's request, WISI drafted management recommendations for master planning of the Two Creeks Buried Forest State Natural Area. The master plan of this Lake Michigan property will provide a 22-acre stopover site in an otherwise open agricultural landscape that has little woody cover available for wood thrushes and other species.
In Door County, TNC is completing the protection of 88 acres at their Mink River preserve through the use of Great Lakes Restoration Initiative and Knowles-Nelson Stewardship funds. These acres were targeted because they hold high value habitat for migratory land and wetland associated birds. As with the lands being protected with the U.S. Fish and Wildlife Coastal Wetland funds, these lands will also protect habitat for a variety of other species.
Wisconsin DNR's Environmental Review Program (ER) champions stopover habitat protection and worked with WISI to develop guidelines for locating communication towers and wind turbines in order to reduce bird collisions.
Most fatalities of migrants at communication towers occur because migratory birds become disoriented by certain lighting conditions on tall (taller than 200 meters) towers while migrating at night. Once confused by the light, they fly into guy wires that support the tower rather than colliding with the tower.
Recent studies reveal that mortality can be significantly reduced if towers are less than 200meters in height, do not have guy wires, and are unlit, or, if taller than 200 meters, are marked with strobe rather than solid lighting. Environmental Review Program guidance incorporates results from these studies as well as federal guidelines to promote responsible placement of communication towers and wind turbines in Wisconsin.
Private lands are a very important part of a network of stopover sites, especially along Lake Michigan, where much of the coast is owned and managed by private individuals and businesses. Many of these properties contain stopover attributes (e.g. forest cover, emergent marsh, lowland shrubs, etc.) determined to be of high or very high priority for migratory birds during either spring, fall, or both. For those properties adjacent to or near managed properties where birds already concentrate, improved backyard habitat will increase the amount of shoreline habitat available. When backyard management occurs in isolated situations, even a small amount of habitat may serve as a Fire Escape, providing vital respite for migratory birds that need to rest before making the next leg of their journey.
Through a variety of promotional events, WISI is encouraging and equipping private landowners with tools and knowledge to enhance their properties for the benefit of migratory birds. For example, WISI, the Western Great Lakes Bird and Bat Observatory (WGLBBO), and many other partners host an annual spring celebration of International Migratory Bird Day at the Forest Beach Migratory Preserve. WISI and the WGLBBO will be hosting a workshop for private landowners on October 8 called, "Grosbeaks Galore: Birds on Your Landscape." Learn landscaping techniques to attract migratory birds to appropriate habitat, food and water on your property. To register for the workshop contact the author, Kim Grveles.
Looking toward the future, it is only by working collaboratively and energetically, with the vision of an interconnected network of Great Lakes stopover sites uppermost in our minds, that we will save for posterity the landscapes needed by long-distance migratory birds such as the wood thrush and scores of other bird species. Together, we can secure the resting places they need on their often perilous migrations, and ensure our own enjoyment in their return.
Kim Grveles and Sumner Matteson are DNR avian ecologists.


text:
Introduction of Single Scissors Electric Platform Cart
Single Scissors Electric Platform Cart , as a plane lifting machine, is mainly used for lifting heavy objects. It has wide applications in many fields, such as lifting platform for loading and unloading freight yard, operation platform for various engineering operators, etc.Single Scissors Electric Platform Cart is a widely used lifting platform with simple structure, large lifting force, stable lifting, low noise, easy operation, simple maintenance, and can stay in the lifting area. It is widely used in all walks of life. It is an ideal and reasonable lifting platform in the field of cargo handling and circulation. The hydraulic system is the drive and control part of the scissors hydraulic lifting platform. The hydraulic cylinder drives the shear fork to change the amplitude, and completes the lifting task. Through the control function of the balancing valve, the speed regulating valve and the relief valve, it completes the functions of speed regulation, pressure keeping, braking and balancing.
Elephant Group
Add:InTime Center,No.1600, Kejiguan Road,Binjiang District,Hangzhou, Zhejiang province, China.

subset: commoncrawl


text:
Da Bomb Ghost Pepper Nuts are spicy peanuts seasoned with Naga Jolokia (Ghost) Pepper, dehydrated Habanero Pepper, Paprika, and select spices. These very hot peanuts are brought to you by Original Juan, who also product the Pain is Good Hot Nuts. Note: Da'Bomb Ghost Pepper Nuts are hotter than the Pain is Good Hot Nuts!
Heat Rating: Very Hot
Estimated Scoville Unit Rating: ?
Ingredients: Peanuts, Seasoning (Salt, Spices, Ghost Chili Pepper, Dehydrated Habanero Pepper, Maltodextrin, Onion Powder, Garlic Powder, Citric Acid, Malic Acid, Extractives of Paprika, Natural Smoke Flavor, Peanut Oil.


text: Fredrik Lundh wrote: > john walshaw (JIC) wrote: > > > > because that's where the libjpeg.a and jpeglib.h files are, > > did you build these yourself ? > > one brute-force workaround worth trying is to remove all > libjpeg files > except the static library (libjpeg.a) from /usr/local/lib and > rebuild, > to force the linker to do a static build. > thanks for the suggestion. I've tried it out, and the short story is that again the compilation completes, but I'm now getting a different runtime problem when I import the _imaging library - I get this: >>> import sys >>> sys.path.insert(1,"PIL") >>> import _imaging Traceback (most recent call last): File "<stdin>", line 1, in ? ImportError: dlopen: Cannot map library PIL/_imaging.so The long story is - first to answer your question, I hadn't built libjpeg myself, so one thing I tried was getting the most recent source and building this again, and using that for the compilation, ensuring that the older one doesn't get used. I have the same error when trying to import the _imaging built with the new one. As far as forcing a static build using libjpeg.a goes - I did try the brute force method, producing the _libjpeg.so which gives the above error. However I also tried a cleaner way of doing this with running the linker with -non_shared, and -ljpeg, and forcing (with -L ) the linker to never look anywhere except the dirs specified with the other -L qualifiers. This produced the same error unfortunately. I also tried doing both the non-static and static builds using the native cc instead of gcc which setup.py uses by default, but in each case the cc build gives the same respective run-time error as with gcc. (I have another beginner's question here - how do I cleanly tell setup.py which compiler and directives to use?). Finally, I decided to do a fresh install of Python itself, so I installed Python 2.5 in a separate location, and used the 2.5 executable to do the PIL build and then attempt the import of _imaging - but I got the same error message as before. Any ideas, or if anyone on this list has PIL on Tru64, I'd be grateful to hear from them. best wishes John


text:
WebCajun.com great sites to visit
Growing a Vegetable Garden
Located on the banks of Bayou Des Glaise in South Louisiana. A 2 acre vegetable garden with lots of pictures, gardening videos with plenty help and how to. Features a calendar, planting guide for the Spring, Summer, Fall and Winter gardens. The Bayou Gardener grows just about any vegetable you could imagine. Growing a vegetable garden
Redfish Lures, Speckled Trout Lures, Bass Lures
Bayou Buck's Redfish lures - Speckled Trout lures - Snook lures - and Bass fishing lures. When conditions are tough for Redfish, Speckled Trout and Snook you need a lure that could change a bad day on the water into a successful fishing trip. Bayou Buck's saltwater fishing lures gives you the edge to help you do just that. Our fishing lures are a product of years of testing and refinement by saltwater anglers. It is for this reason our terminal tackle and saltwater fishing lures are quickly becoming a dominant part of many a coastal fisherman's " fishing arsenal."
Bass anglers from around the country are discovering Bayou Buck's Bass Lures. Constructed of the highest quality materials for those really rough conditions. Available in all colors and styles. Bayou Buck's fishing lures and terminal tackle can be purchased online or at your local tackle shop.
While visiting Bayou Buck Lures don't forget to check out the fishing tips from the Pros and Guides who use his lures every day.
Houma Louisiana Saltwater Fishing
Bayou Guide Service - Capt Bill Lake
Redfish charters - Speckled Trout charters Capt. Bill Lake, a native of Houma, Louisiana grew up fishing the fresh and saltwater marshes of Terrebonne Parish. After 30 years of successful fishing, he has learned to narrow his focus to trophy speckled trout and redfish. Most of his effort & expertise is expended in the inland/coastal waters of Bayou Dularge and Cocodrie. The Sister Lake-Lake Mechant area out of Bayou Dularge offer great springtime, fall and winter fishing for specks and reds. So why not include a saltwater fishing charter in your next family vacation.
Sewing Patterns and Seminars
Sewing with Cynthia Guffey
Cynthia Guffey has been designing women's clothing and teaching sewing and fitting techniques for seventeen years. She owns an up-scale fabric store and custom dressmaking business in Baton Rouge, Louisiana and her designs have been worn everywhere from the opening of the Met to Acapulco. Cynthia has developed effective, practical, and simple fitting and construction techniques that she teaches throughout the United States. Her sold-out sewing seminars are filled with information that result in beautifully fitted, custom-look clothing. Her sewing seminars receive rave reviews because, as one of America's best sewers, she shows you how to save time by getting it right the first time. By using her creativity and talents in designing, sewing and writing, Cynthia continues to inspire sewing enthusiasts around the world.
Gyroplane, Gyrocopter, Autogyro, Gyro
The Gyroplane ... With the recent Sports Pilot's License in the US and a growing number of people interested in the hobby the Gyrocopter is gaining in popularity all over the country. The advantages of the Autogyro is its ability for short takeoffs and even shorter landings. Unlike a helicopter the Gyro cannot hover but it can fly very slowly giving the pilot more time to take in the landscape below.
To contact us
Free web templates


text:
Modern Family Toddler Cursing
Did You Find Modern Family's "Little Bo Bleep" Controversial?
Oh you silly Lily! Last night's episode of Modern Family had First Amendment advocates cheering, the No Cussing Club fuming, and parents everywhere nodding their heads through the shared experience as 2½-year-old Lily seemingly dropped the F-bomb throughout the episode (it was bleeped out and pixelated so viewers never heard or saw it).
Hearing a toddler say a cuss word isn't anything new for experienced parents (though this may be the first time it was done on TV), and I, for one, found dads Cam and Mitchell's reactions quite real — in our home, we often find ourselves hiding our laughter as we utter the necessary admonishments for bad behavior.
Take a look at the clip and tell me what you thought of the episode.


text:
This is Moses, an excellent farmer and nurturer of honey bees. While he has great skill and ability in these areas, like many in Kenya, he didn't have the cash needed to buy a bee keeper outfit and he and his community group struggled with just a few hives. Thanks to the kindness of so many at St E's, Moses and his group purchased the bee keeper protective clothing, and expanded their hives to 25. They now harvest 50 gallons per season of some of the finest honey ever to pass a human lip! The monies earned are used to help the group members, and the many widows and orphans in the village, with some always set aside to grow into new areas, like cattle raising.
This is Boniface, the trusty school bus and clergy driver who's up at 4 am every day bringing children from remote areas to school, then driving volunteers to the various villages where micro enterprises are happening. He's displaying one of the beautiful handmade bags created by the Empower Women's group.


text:
Make Your 2011 Best of the Mid-Valley Nominations By March 14!
It's that time of year again! It is time to again nominate your favorite businesses in the Statesman Journal Best of the Mid-Valley 2011 Poll! Last year, Bentley's Grill was honored to be named the Gold Medal Winner in 3 Categories: Best Creative Cocktails; Best Business Lunch and Best Happy Hour. We also made it onto the Top 3 list for Best Appetizers in the Mid Valley!
We are asking for your help again! If you are a fan, please support us and nominate Bentley's Grill in the appropriate categories before the nomination period ends at noon on Monday, March 14, 2011. You may nominate us at StatesmanJournal.com/bestof.
StatesmanJournal.com's Best of the Mid-Valley invites readers to nominate and vote for their favorite people, businesses and things to do in Marion and Polk counties. Readers nominate their favorites by selecting one of seven topic areas (Food & Drink, Entertainment, Recreation & Fitness, Personal Services, Professional Services, Shopping, or Local Schools) and then completing the survey in each area. Nominating is as simple as entering a name in a text entry field. Only organizations and activities that are currently in business in Marion and Polk counties will be eligible for nomination.
Nominations will be accepted until 12pm Monday March 14 and the regular voting period begins 8 a.m. Sunday, March 20 and ends 5 p.m. Sunday, April 10, 2011. For fans of Statesman Journal's Facebook page, the voting period begins 8 a.m. Thursday, March 17 and ends 5 p.m. Sunday, April 10, 2011.
The names of the winners and runners-up will be posted at StatesmanJournal.com on Sunday, May 1, 2010. All also will be honored in our Best of the Mid-Valley special section publishing in the Statesman Journal on Sunday, May 1. In the event of a tie in any category, more than one winner or runner-up may be awarded.
The Statesman Journal serves the Mid-Willamette Valley. Salem news, community, entertainment, yellow pages and classifieds.


text:
And...then a friend sent me this photo stating that Lucy has a very steampunky look!
Oh my!
This one is called The Observer by Winardi and it's at a blog called Steampunk Tendencies...it's a Victorian Steampunk Kitty!
Normal Saturday routine today...leave raking and lawn mowing! Absolutely nothing for dinner and no plan...at all! Winging it...
Reading this...it's by the same author who wrote The Summer Of Dead Toys...it's really good!
Happy Saturday!
I made the mistake of sitting down for a moment and now my lap is filled with kitties...so I have a break before vacuuming! Hurray!


text:
LINZ, Austria, Oct. 9 (UPI) -- Qualifier Bethanie Mattek-Sands earned a second-round berth at the Generali Ladies Linz tennis tournament in Austria with an upset win Tuesday.
Mattek-Sands eliminated seventh-seeded Tamira Paszek 6-2, 6-4. Mattek-Sands landed just 38 percent of her first serves but still took two-thirds of the points while serving.
She had her serve broken once but countered that with a pair of breaks in each set.
No. 5-seeded Julia Goerges also advanced, beating Daniela Hantuchova 6-5, 7-6 (7-5). Goerges only saw one break point in the match.
Qualifiers Mallory Burdette and Kirsten Flipkens joined Mattek-Sands in the second round. Burdette piled up six breaks in beating Ksenia Pervak 6-3, 6-4 while Flipkens was a 6-4, 6-3 winner over Alize Cornet.
Romina Oprandi had the easiest match on Tuesday's schedule, racing past Alexandra Cadantu 6-2, 6-1 in 55 minutes. Oprandi lost only 14 points over eight service games and saved all three break points Cadantu managed.
Also Tuesday, Irina-Camelia Begu topped Catalina Castano 6-0, 6-4; Carla Suarez Navarro defeated Magdalena Rybarikova 6-3, 6-4; Andrea Petkovic got by Barbora Zahlavova Strycova 7-6 (7-3), 6-2; and Simona Halep was up 3-0 when Lesia Tsurenko retired with a right shoulder injury.


text:
Returning to the Basics to Grow
By Elijah Shaw
Several months ago I was burning the midnight oil having just returned from an overseas trip with a High Net-Worth corporate client who was doing something in relation to an international charity. As I set on my couch semi exhausted and working on some paperwork, I received a phone call from an individual that I've known for years with some pretty extensive ties to the entertainment industry. He asked if I was in town of which I replied yes, then without any warning, said he wanted me to speak to someone and passed the phone. The gentleman on the other line introduced himself to me as the manager of a hip-hop artist who I was familiar with by reputation only. This artist was new to the music scene, but extremely popular do to the massive response of the initial release of his songs.
The manager stated that he was in town with the artists for a performance, and was looking for security. Apparently, the artist main bodyguard had problems with his flight and would not be making the trip. After looking at my watch and the late hour I said I'd be happy to try and get him sorted, and told them I'd reach out to someone in my network and get back to him. His immediate response was, "I was actually hoping for you". Looking at the mountain of paperwork that will spread out across my desk and knowing that this artist was a rapper with a VERY "urban" audience, my first inclination was to say no. While I have no problems with the music business, I don't usually work with rappers that I don't have long standing relationships with these days, simply because I like to choose my battles. (Translation: I want to be the only one with a firearm in the entourage!) There was an obvious pause on the phone as I thought about it, and then my response was, "sure give me the details".
Fast forward to a night that included a crowded nightclub, a large entourage, fights in the audience, "groupies" backstage, and overzealous house security and you get an idea of how the night was. –-Crazy.
With that said, the crowds response was massive, and if you've been in the business for as long as I have, you start to recognize the next big star in the making. The Principal himself was low key and respectful. The manager was easy to work with and gave me the responsibility I needed to get the job done. After the performance we went directly from the stage to the waiting SUV parked right outside the back door, did a few loops to loose any tails and took the Principal up to his room for the night. (This was now 2:00 am with a 4:30 am lobby call so that the travel party could leave to make their plane).
Throughout the night, the manager asked several questions about my background and after getting the Principal to the airport thanked me for the last minute service and said he would keep my contact information handy. Later the next day I got a call from the client's rep asking if they could schedule a call to discuss an upcoming overseas tour as the Principal himself had noticed a difference in the service provided that night from what I assume he normally received and asked him to call. I said I'd be open to "discussion" and that's where we left it. He also mentioned the portfolio of other artist he represents, several of who were in different musical genres and wanted to discuss services for each.
A funny postscript of this story is the initial contact I mentioned at the beginning of the tale was part of the group that called me in for music megastar over 10 years ago. In fact the performance was in the same venue. At the time this individual was also a new artist with a "hardcore" fan base, and from working with him on a one off assignment, the call back from that turned into a long and fruitful relationship, in which he traveled the world and subsequently sold 14 million copies of his first album. My handling of the security was both financially rewarding and opened the doors to other relationships that led to other business.
The point I'd like to get across is that at any time the phone rings, it's a potential opportunity calling. While it's certainly ok (and necessary) to say no at times, remember that every opportunity can be a doorway to another opportunity. The Close Protection industry is a business, and the only way a business thrives is by having the lights on and the sign reading "OPEN". Who knows, that next call you receive might be the one that takes your business to the next level.
Originally written for my ongoing column entitled, "Keeping Your Edge" for The Circuit ~ The Magazine for the Executive Protection Professional. Find this article and more by clicking HERE.


text:
It seems a fictional story, typical of an Italian comedy, but it happened in real life last Sunday ...
The Sassuolo-Milan was played and an amateur team Berlusconi got tired of seeing losing theirs and 77 minutes, just when Berardi scored the third goal for the home, left the bar where he was witnessing and went home .
Big mistake, would have saved disgust. And, when it came to his home to find his wife in bed with another.
Obviously, it was not taken well. So much so that he became violent and hit both lovers. Alerted by neighbors, the carabinieri had to intervene to anger neither resulted in tragedy.
It is not an unprecedented case nearby. In May 2013, another 'tifoso' Vicenza had a similar experience. Pissed off by the ridicule of his team against Empoli, he took off the stage and caught red-handed to his wife with another man.


text:
by Jason Sizemore on Feb 7, 2017 in Nonfiction | 0 comments
Welcome to issue 93!
The writing profession is filled with rumors, half-truths, and whispers. People that make up speculative fiction all day enjoy speculating about matters. Imagine that!
One of the most common misconceptions spread by writers is the concept of black lists. In publishing, a black list is a collection of people an editor will not work with. You'll hear rumormongers saying "You better not do this or do that or an editor will place you on his/her list!"
Some of these theoretical acts include:
The truth about black lists from my perspective is that they are mostly imagined. As a whole, most professional editors care little about the person behind the story (except in extreme examples). They're only interested in the story. But like most things, there are facets to personal black lists that make things not so cut and dry.
Do I have people I absolutely would not publish? You bet. I am not going to publish someone that I am aware actively harbors and promotes hateful ideas. Do I keep a list of people who might have slighted me in the past? Yes, I scratch their names on a wall every night before I sleep—I WILL NOT FORGET. But will that keep the person from appearing in the magazine or books I edit? The answer is a 99% "nah." The remaining 1% are the extremes … those who have threatened physical violence to my family, those who have falsely accused me of bad behavior, those who I know have denigrated the Apex brand, etc.
The reality about black lists? If you're an extreme asshole, you might be closing some doors on yourself. Otherwise, you have no reason to fear any editor putting you in "do-not-publish" jail.
I want to bid our amazing poetry editor Bianca Spriggs a fond farewell. She's a wonderful person, a force of nature. We wanted her to join our fiction editing team, but alas, she elected to move on. I have no doubt you'll be hearing more from Bianca in the future.
This month we will run our last poem selection for the foreseeable future. We love the form, but we want to narrow our focus in the coming months.
Congratulations to our Apex Magazine Story of the Year winner Alexandria Baisden. Her heartbreaking short "The Old Man and the Phoenix" is our readers' choice! Read it here.
Also, congratulations to Marcela Bolivar, our Apex Magazine Cover of the Year winner. Her piece from issue 87 is readers' choice! Click here to see a full-sized image of the cover.
This past November we asked you to send us your best flash fiction stories about love/Valentine's Day … with an Apex twist of course. And you definitely answered the call!
We received around 500 submissions! Stories about love, obsession, Cupid, and hearts!
After reading through all the wonderful submissions, we have selected the top three which will be published in this issue of Apex Magazine—just in time for Valentine's Day!
The winning entries are "As Long as You Can Stand It" by Joanna Truman, "Butterfly Man" by Tonya Walter, and "St. Theophilus the Penitent" by Rich Larson. You can read all three winning entries in this issue!
Congratulations to our winners and thank you so much to everyone who entered!
We welcome a whole bunch of nice writers to issue 93. Nisi Shawl is known as one of the nicest people in scifi, and we have her! She contributes her original story "Queen of Dirt." Also new this month is "The Bells" by Lyndsie Manusos. The ubiquitous Rich Larson gets edgy with "You Too Shall Be Psyche." One of our readers' favorite authors returns as we reprint Samuel Marzioli's "Servant of the Aswang."
In nonfiction we have two interviews and an article. Russell Dickerson interviews our cover artist Adrian Borda. Andrea Johnson talks to Nisi Shawl about "Queen of Dirt." I had the wonderful opportunity to speak with Mac Rogers, the writer of the popular podcasts LifeAfter and The Message. Finally, poet Simona Sušec gives us "Fury."


text:
Country Life Fair 2019
Posted by Pomeroy Farm
on April 05, 2019
The annual Country Life Fair is approaching and we have a weekend filled with family fun! Mark your calendars from April 27th from 10am-4pm and April 28th from 11am-4pm to join our live demonstrations, hay rides, herb and plant sale and much more!
Follow Pomeroy Farm on Facebook for updates and a sneak peek of vendors joining and farm life demonstrators.read more


text:
That's what Saoirse said to me this morning, running up to me with little plastic sunglasses on her face, upside down. That's the first time I've heard her say that sentence, but not the last, I feel certain.
I asked Rowan to pause in their game to let me take this picture of her:
Saoirse ran over, said "Sha-Sha turn!" This is how she wanted her picture taken:
We got to spend some time on the playground again today, before the thunderstorm hit.
"Looky me!!"
Posted by Gwen Papp Saturday, April 25, 2009 at 5:59 PM
That's what Saoirse said to me this morning, running up to me with little plastic sunglasses on her face, upside down. That's the first time I've heard her say that sentence, but not the last, I feel certain.
The Arb
Posted by Gwen Papp Friday, April 24, 2009 at 8:10 PM
So today was the first really hot day of spring '09. It was above 80 degrees and sunny. Chris has been studying full-time lately, anticipating starting work on May
4th. But who could sit in a library all afternoon on a day like today? So he left early and we did our best to wear the kids out. (I mean, we spent an afternoon sharing quality time...)
We went to the park across the street for a while. But we do that every single day that the weather allows, we wanted to get out of our neighborhood. Saoirse wasn't as thrilled with that, because she was really enjoying pushing the whole family on the merry-go-round. If Chris tried to put his foot down to help, she'd run over and shove it up, saying, "NO! On there!" She liked showing us how "stong" she is.
When we convinced her, we headed to the Arb. Of course, Piggy had to go too.
We headed down by the river, and the girls even got to wade a little.
The girls also spent some time picking up pinecones (or "combs" as they call them) and stuffing them through the slats of a bench.
Next time we go to the Arb, I hope the trees have gotten leaves, because it was HOT today and Mommy could have used some shade.
Even hotter tomorrow, we hear. :)
Big outing
Posted by Gwen Papp at 8:03 PM
I've been looking forward to Reema and I getting our kids together for years. Although the logistics of getting two sets of twins out of the house for a morning concert at the library can be daunting, today we did it!! It was the first time that Reem brought them out alone to something like this, and she was (of course) a rock star. There were no meltdowns, no screaming, no disasters. The kids all seemed to enjoy themselves, Saoirse and Rowan were fascinated by Sahil and Sareena. Rowan gave each of them kisses, even. So much fun!
Really really belated Easter Egg hunt..
Posted by Gwen Papp Wednesday, April 22, 2009 at 4:05 PM
After the party I tried to change Rowan, and she insisted on adding pants but not taking off her dress. Here she is chilling a little with Daddy before dinner.
Big sister
Posted by Gwen Papp at 4:03 PM
Last weekend when it was warm, we had ice cream on State St. Saoirse didn't really want any of the ice cream, but she was very vigilant about making sure Rowan got cleaned up when she spilled.
a hotel trip...
Posted by Gwen Papp Thursday, April 16, 2009 at 3:50 PM
A couple weeks ago, when the April snow hit here in Ann Arbor (and what the hell is up with that, by the way?), we lost power. It was out for more than 24 hours, and since it was snowing it got really cold pretty quickly in the house. So we went and spent the night in a hotel. One on hand, not living close enough to family to just go to someone else's house when our power is out is a pain. (mostly financially) The good thing is that we get a little mini-vacation, which we all enjoy.
We spent some quality time in the pool while we were there. The girls are getting braver all the time about the water. Rowan wanted me to hold her hands on the side of the pool and let her "jump" in, dipping her about chest deep. Then she'd say "Out!" and I'd lift her back up. We did this for about a half hour, until my poor back protested too much, and we had to quit. Then she went to Chris in the water.
The last picture is the next day, when we were back in our house. I just thought Rowan looked too cute in her pigtails. :)
Cookie Mouse at story time
Posted by Gwen Papp Friday, April 3, 2009 at 8:28 PM
There's a whole series of books that the girls love. If you give a mouse a cookie. If you give a pig a pancake. Etc..I bought a collection of them while we were in California last fall, and Rowan claimed that book as her own. She cries if Saoirse touches it. She calls the book "mouse cookie." Last weekend they read it at story time at the Barnes and Noble by us, and Cookie Mouse came to the story-time and brought the kids a cookie. I figured we had to be there. It was like if the cast of Lost showed up at the movie store down the street, Chris and I would need to be there, you know? So we went. The girls loved it. Rowan wanted to touch the mouse a million times, she didn't really care for the story part, she just wanted to get to the mouse. They loved the drawing and the cookie, too.
Look at Saoirse sit so quietly and follow along in her book. :)
Here they are both listening. Don't they look teeny? Notice the other set of twins to their right. Isn't this generation strange? Is being a twin even going to seem unusual to them?
Jack hasn't gone to the farm yet
Posted by Gwen Papp at 8:12 PM
So the pre-Easter bunny is still hanging on. Saoirse is getting braver every day, both girls "home-um" whenever they can. (That's "hold him" in Rowan-speak) It looks like this bunny may actually make it to Easter in our house.
The last photo is Saoirse playing in Jack's cage while I clean the bottom part. She climbed in the door, lay down to "sleep" and is asking us to close the door. She loves this and runs for it as soon as we take the cage apart.
I forgot how to do this...
Posted by Gwen Papp Thursday, April 2, 2009 at 10:08 PM
Today Chris left the house early in the morning and only came back for dinner. Now that most of the job hunting stuff is wrapping up, he's spending the days studying for oral boards. So today I was totally alone with the girls for a whole day, without him in the house at all. That hasn't happened much in the last few months. I forgot how long the last few hours are. I forgot how much energy it takes to entertain toddlers without a break, completely alone for so long.
We did, though, have a good day. It was really warm, so we got outside for a run/walk. (I walked, they slept in the stroller) We ran some errands and had lunch together on campus.
Here's the saving grace of staying home with almost two year olds compared to last spring. I was folding some laundry and the girls were in the other room. I went to look for them, and here's what I found:


text:
See also: IRC log
<trackbot> Date: 09 June 2009
<asir> Scribe: Asir S Vedamuthu
<asir> ScribeNick: Asir
3-day meeting
Bob: calling for 6 volunteers for 6
different slots
... there are 6 premium slots, calling for tenders
... the first one is already gone
Prasad: prefers Wed PM
Tom: prefers Tue PM
Ashok: Wed AM
Jeff: met for 6 months, discussed the same issue several times, prefers voting
Bob: formed taskforces, F2F is the best time to discuss hard issues
Asir: agree with Bob, we should try
and build consensus to the best extent possible, we should build
industry consensus not just within this group
... it is important that carry the WG to see adoption
... it is important taht we carry industry consensus to see adoption
... would prefer that we don't get into any premature voting doldrums
Bob: points out the dependencies in
the charter
... featured issue of the day is 'mode'
... featured issue for tomorrow is 6413
Asir: will we discuss FO?
Bob: will discuss on day 3
Jeff: WG does not discuss FO, sent to the Director
<jeffm> please add to the log mr. scribe: jeff asked how many many more weeks and months do we have to talk and "try to build consensus" before it is time to actually take a decsion and vote
Yves: WG should try and dispose formal objections
Asir: I would like to echo what Yves mentioned. We should try and avoid formal objections
Bob: keep the discussion on tech merits and professsional
<jeffm> so don't file them when u lose on an issue,
We should work towards avoiding any such formal objections ...
RESOLUTION: 2009-06-02 minutes approved
Gil is ready to discuss 6401
Bob: ready to discuss mode proposals
Bob: ready to discuss T and Frags issue
See http://www.w3.org/Bugs/Public/show_bug.cgi?id=6956
<scribe> postponed
Gil walks through his high-level proposal
Gil: wants to clarify invalid rep fault
Geoff: there are 3 cases in which Put
should be disallowed
... 1. Should PUT be disallowed entirely in this case
... 2. Should the client be able to send a PUT that contains only the elements that can be updated (partial)?
... 3. Should the client send the whole resource, with the read-only values same?
Yves: define a fault
Doug: define a fault and not specify
the cases when it should be used
... something wrong with the data
Yves: in the case of partial PUT, use
a PATCH like operation
... perhaps, IFMATCH and ETAG style mechanism, similar to HTTP
... this will clearly dilineate fragment style PUT operation
Doug: want to see a PATCH proposal
<scribe> ACTION: Yves to open an issue to solve versioning and partial PUT in Transfer AND provide a proposal [recorded in http://www.w3.org/2009/06/09-ws-ra-minutes.html#action01]
<trackbot> Created ACTION-67 - Open an issue to solve versioning and partial PUT in Transfer AND provide a proposal [on Yves Lafon - due 2009-06-16].
Asir: when you mentioned PATCH, are you thinking of a new operation for fragment PUT
Yves: yes
Doug: sounds like a fragment-like feature, nice to have feature for tomorrow's discussion
Yves: will prepare some material for tomorrow's discussion
pop the stack
Geoff walk through the proposal
<gpilz> http://www.w3.org/Bugs/Public/show_bug.cgi?id=6956
Doug: SHOULD should be a MUST
... in section 3.2
... applies to both request and response
... MUST fail and MUST generate
Geoff: not sure yet
... you have to look at the proposal in context, let's look at the spec
Ashok: have two options: send another end of sequence or send an invalid context. Why don't we say that?
Geoff: if it is going to gen then the system should gen an invalid context, sometimes the system may generate a perfectly valid message, end of seq
Doug: hurts, hurts
... perhaps, we need to introduce more changes to cover what Geoff is asking for
Geoff: will re-work the proposal to include enum context as well
<scribe> ACTION: Geoff to re-work the proposal for issue 6956, due tomorrow! [recorded in http://www.w3.org/2009/06/09-ws-ra-minutes.html#action02]
<trackbot> Could not create new action - please contact sysreq with the details of what happened.
<trackbot> Could not create new action - please contact sysreq with the details of what happened.
Bob: temporarily disposed 6924 and 6956
Gil: not hard to do!
... means XML as is
Bob: related to 6712
... would a def for lit rep move forward 6712?
Geoff: IFF 6712 outcome is no
dialect, then high-level def is sufficient
... IFF 6712 outcome is - use dialect, then lit rep should be clearly defined
Bob: should we record a dependency?
<jeffm> http://news.bbc.co.uk/2/hi/business/7490346.stm
<jeffm> http://www.guardian.co.uk/commentisfree/2009/may/22/pringles-potato-crisp
<scribe> ACTION: Gil to provide a draft definition for lit rep, issue 6975 [recorded in http://www.w3.org/2009/06/09-ws-ra-minutes.html#action03]
<trackbot> Sorry, couldn't find user - Gil
Doug: sent out a revised proposal
Geoff: two kinds of areas that are
... 1. concept of DB example, service acting like a DB, taking a stream, creating something in a DB
<gpilz> ?
Geoff: transfer spec does not,
transfer talks about a resource, it is upto a resource to decide
what to do
... DB service, will deal with things as it always it used to
... will take string, xml, instruction
... it is upto the DB to figure out how to handle classes of things
... it is upto the DB to figure out different classes of things
... as they say in Aus, Bob is your uncle!
... it is upto the service to decide what to do
... walks through an example, say an issue client
... 2. it is not easy to define what is a literal rep
... have not seen any answers to questions that I posted to the WG
... walks through a priority rep example
... so, no need to intro any new attributes
... we could follow Bob's suggestion of using the term 'payload'
Dug: will go with the assumption:
authors had some smarts and introduced instruction
... moving to payload = removing functionality
... service can figure out by letting client to indicate
... but this is one-off and not interoperable
... transfer does not have any mechanism to tell the client what is the shape of the resource
... very simple to clear this ambiguity
... not comfortable to remove the functionality
Bob: why did the authors not provide a mechanism to indicate
Doug: guessing
Gil: authors were on a schedule and
did not have sufficient time to think thru
... is it instruction or is it literal
... does the service need to be aware
... supports doug's proposal
Asir wants to point of that Transfer Member Submission says
"Implementations should provide metadata which describes the use of the representation and how it relates to the resource which is created, but such mechanisms are beyond the scope of this specification."
It is upto the service to tell the world what is the shape of a resource
Geoff: what is the actual interop scenario?
<gpilz> how come nothing I said got in the minutes?
Please add it Gil
<gpilz> the crux of this issue is dualities
<gpilz> sometimes you want the service to interpret the contents, sometimes you don't
<gpilz> neither the client nor the service is "the absolute master"
<gpilz> they need to interact
<gpilz> "isResource" is a means for the client to hint to the service what is intended
<gpilz> obviously the service may or may not honor that hint
<gpilz> finally, denigrating other peoples use cases is non-productive (unless a use case is non-implementable, etc.)
Doug: service can tell the client to
include a header
... wants a transfer-level mechanism for a client to tell the diff
Geoff: for the issue processing example, would you, as a client, have said the attribute is a resource or instruction?
Doug: in the example, you are storing
an example
... it may not matter
... there is no ambiguity
... my proposal will not impact existing impl
... this is a fringe usecase
... default is the status quo
Ashok: you actually started with an
attribute as an URI
... URI gives you a bigger scope, different values (rather than binary
... what did you change from URI to boolean?
Doug: wants to know if this is raw data or instruction
Asir: transfer does not spell out any
mechanism to tell the client what is the shape of a resource
... [quoted material from the transfer spec]
<dug> HTTP+HEAD IMO gives the metadata the client needs
Asir: And the create operation says
that the contents of the create operation are service specific
... it could be many things
... the spec talks about a few possibilities
... why is an instruction treated specially?
... all you need is an URI and service-specific contents
... this is similar to HTTP specification
Yves: in HTTP, it is upto the server
(implementation of a resource) to figure out what to do with the
... and the implementation of a resource can vary in nano seconds
Bob: I received a request from Hemal
Shah to present his views on some of WS-RA issues
... he is a member of the DMTF/WS-Man WG
<gpilz> as are Bob, Doug, Tom, Jeff, and myself
<gpilz> (members of the WS-MAN WG)
Bob: walks through the principle of
... if you are making a statement about modeling after something, we should be cognizant of how much of those underlying stuff are used
... summarizing ...
... we have this thing called transfer
... we are talking about creation
... want something to be created
... it could be a lit rep, instruction or something else
... authors didn't define any further
... this means
... disambiguation is totally out of the hands of the Transfer spec
... it is upto some other specs to define what the rep or something else
... if we go along the lines of let's annotate using a boolean to disambiguate
... I am worried that we are narrowing our use to a smaller scope
... just lit rep and instruction
... or here is another language that i dev to provide instructions
... if we were to get on the route then I am worried
Doug: now prefers a URI
Bob: we are talking about a vague
thing, contraining to any small set is premature
... that leaves us with three alternatives
... a) if you want to tag a content, we will give you one that is optional
... b) nothing is necessary, these are service-specific, defer to services
... c) Recommend other mechanisms to get metadata or providing a place holder for client-server negotiation
... practically boils down to a and b
Ram: noticed that there is a struggle
between what belongs to the protocol versus app layer
... what is sent by the client could be data, instruction or both
... how am I going to negotiate with the service?
Ashok: perhaps, a negotiation mechanism
Bob: may be some rough analogy to media type
Wu: there are umpteen possibilities, there is no reason for us to define these possibilities, I am more inclined to leave this to service-specific
<dug> Wu - this isn't a new feature - the transfer spec already talks about doing this - we're just clearing up an ambiguity
Gil: we have an open thing here to define a policy for transfer, we don't need to know that now to decide on this issue
Ram: both parties seem to make good
points, you don't know what the payload is going to be, range of
values - data, instruction, both or something else
... a proposal to indicate using a mechanism
... why not specify in the spec that payload could be anything, state that anyone could define the payload, use extensions for servers to figure out the nature of the payload
Geoff: use some wording to articulate clearly in the spec would help
Doug: opinion, you are removing a feature
Ashok: adding only a attribute, you
do not have to use it
... optional attribute
... HTTP is not a good example
... people are constantly inventing new protocols rather than using HTTP
Gil: Ram said that app can extend, Doug mentioned that is an interop issue, Geoff said that we could clarify
Geoff: you may say that the attribute
is optional ... but it is not
... not actually optional
... if the client gets confused then this will confuse the client
... what if I use it and what if I don't use it
... this is the point that Wu mentioned
... this is shifting the ball from service-specific to client-specific
Bob wants to hear from Tom
Bob: can you argue for both sides?
Tom: prefers strong typing, so
prefers an extra flag
... how can I defend for the other side
... it is upto the app side to figure out
Bob: there are two options
... a) add an optional xs:anyURI
... b) close with no action
... c) provide guidance to implementers on how to extend the protocol for indicating content
Ram: c) is all about setting expectations and providing guidance
Asir: points out how to build consensus
<gpilz> Asir moves to delay with additional, undefined proposals
<gpilz> as far as consensus goes, I have not interest in an attribute that is "optional to understand"
Bob: what does a) mean? If I am the creator of the message, it would pass schema validation. If I were a receiver of it I could not understand, I could not support that URI
<gpilz> it totally undoes the intent of the original proposal
Bob: it is
Bob's option a) is a hint that is ignorable
Bob is looking at one of Doug's proposal
<gpilz> doug refers to the issue description for his original proposal
Folks on the phone - whiteboard discussion in-progress
Transcribing white board
a) OPTIONAL Hint that describes the content, CONTENT DESCRIPTION
b) Close with no action
Adding more stuff to option a)
a) OPTIONAL Hint that describes the content, CONTENT DESCRIPTION. If the service cares then faults if the URI is not known. If the service does not need the hint, then ignrores
restating option a)
a) OPTIONAL Hint that describes the content, CONTENT DESCRIPTION. If the service needs a hint and the CONTENT DESCRIPTION is not known, then service MUST generate fault. If the service does not require a hint then may ignore the CONTENT DESCRIPTION. Type(CONTENT DESCRIPTION) = xs:anyURI
b) Close with no action
<dug> a) includes defining a fault
OPTIONAL Hint that describes the content, CONTENT DESCRIPTION. If the service needs a hint and the CONTENT DESCRIPTION is not known, then service MUST generate fault. If the service does not need a hint then may ignore the CONTENT DESCRIPTION and will NOT generate a fault. Type(CONTENT DESCRIPTION) = xs:anyURI
a) OPTIONAL Hint that describes the content, CONTENT DESCRIPTION. If the service needs a hint and the CONTENT DESCRIPTION is not known, then service MUST generate a fault (to be defined). If the service does not need a hint then may ignore the CONTENT DESCRIPTION and MAY NOT generate a fault. Type(CONTENT DESCRIPTION) = xs:anyURI
b) Close with no action
Bob: a) is only a direction not a concrete proposal, editors will need to prep a concrete proposal
RESOLUTION: consensus on a) as the directional proposal
Issue is still open
<scribe> ACTION: Doug to prep a concrete proposal based on directional proposal a) for issue 6712 [recorded in http://www.w3.org/2009/06/09-ws-ra-minutes.html#action04]
<trackbot> Created ACTION-68 - Prep a concrete proposal based on directional proposal a) for issue 6712 [on Doug Davis - due 2009-06-16].
<gpilz> http://www.w3.org/2002/ws/ra/edcopies/wst.html isn't working
<gpilz> scribin - ur doin it wrong
<Bob> scribe: Tom Rutt
<Bob> scribenick: TomRutt
<Bob> http://www.w3.org/2002/ws/ra/wiki/
Gil: I suggest that we are familiar with all the proposals, and suggest we move this to CHAD. Is there anyone whose opinion will change with further review of the proposals?
No support for Proposal A indicated
Some support for Proposal B
Some support for Proposal C
Some support for Proposal D
Bob: lets do a single vote per company STV.
Proposal B. remove wse:Delivery element and all it's sub-elements Proposal C. close with no action Proposal D. Add new mode
Bob: B handles policy centric world well, C does not service it, D provides a way to indicate use of policy. In terms of charter, C and D are stronger
Geoff: Can we separate the proposals, remove delivery element, ws only remove mode attribute of delivery element?
<dug> Delivery element's purpose can be achieved using the EPR element instead.
Geoff: there has not been a lot of discussion on delivery item itself
<Wu> There are things in Delivery that are not good for EPR, see examples
<Wu> in Li's cases
<dug> those are properties of the subscription and would go outside of the Delivery element.
Geoff: delivery element allows for containment of life cycle
<dug> And Li's example is a perfect example of the problem with Mode. How do you compose those two new modes with your Proxy example? Who will define those new modes?
Asir: It seems premature to stop working for consensus. Implementers have spoken, we need to consider their views for adoption purposes
Bob: can someone speak why D is not appropriate?
Dug: Proposal D does not do anything for interop or composability. Keeping Mode in any shape or fashion encourages bad behaviour.
Asir: I do not agree Mode is being used as a replacment for RM or Security.
Bob: Push with Ack in ws-man is not an adequate replacement for ws-rm, it is mainly a flow control mechanism.
Gil: while mode push with ack is not an adequate replacment for WS-RM there is a lot of functional overlap
Bob: I am concerned that Mode
conflates characteristics of format, protocol behaviour, network
characteristics and jumbles them into a single URI value
... Dug's argument is that the Mode mechanism is not consistent with other extension mechanisms commonly used in ws-* specs
... I am not hearing new concerns on the use of Mode.
... my device implementers could accept an alternative which is a qname check, however if a policy intersection engine like thing is required, they would balk.
... is eventing a device spec, a large system spec (possibliy uncomfortable for devices) or for both?
Asir: I believe it has to work for
both types of system
... I suggest we have a set of guidelines for the proper use of the Mode mechanism. We can have an example of one or two modes, to set the precident for the rest of the world to use.
Bob: I am not sure the big system guys would be happy unless there as a policy friendly approach to use
<asir> I also added that we should do it in a way that big system vendors adopts them too
Wu: option C does not disallow use of policy, however it maintains mode for small devices
<asir> Actually, option C composes with the use of WS-Policy
<dug> http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Apr/0016.html
<asir> if there is a perceived composition issue that should be addressed
<asir> no doubts
Dug: mode is a fundamentally broken feature, it not only does not compose with ws-* world, it also does not even work with its own suggested uses. Some of the examples (e.g., mode with proxy) do not work
<Wu> There is clear value for a light solution in mode. And delivery element is critical seamtics in WS-E (See section 2.2)
Dug: what is missing is a way for event source to tell synch what it supports. A middle ground proposal is to give equivalent to mode, with a single uri check, but use a policy reference.
bob: the smallest device implementers will only support "push" mode.
Dug: we can define a mechanism to
advertise which policy URIs are supported. This allows the best of
both worlds.
... a source can provide metadata to describe which policy can be placed within the subscribe.
Asir: it is qname not uri.
Dug: You could use a policy ref
... mode is not extendable. You cannot add tweaks to an existing mode without creating a new mode URI.
Geoff: I recommend that we live with mode, and decide the best way to organize to move forward to give both sides what they need (not fracture market)
Bob: At smallest end they do not
think of protocol layers, they implement a state machine which
minimally ensures the protocol will work within their particular
constraints. They want a simple qname, or URI attribute which they
can do a comparison to.
... On the other side, the system guys state mode is unacceptable. All behaviour is in extension specs, such as ws-man. You are not implementing eventing, but ws-man eventing.
... this makes it difficult to extend in an incremental manner.
... the small device guys want to know where to look for the value which they can do a quick check on.
Yves: with regard to proposal D being "ugly". We have two user views, use policy, use a single value. Proposal D was not meant to be beautiful, but was meant to allow both user views. What is blocking factor in the use of proposal D? We have a wider community than WS-Man on both sides of these views
Dug: D promotes an extensibility point which is not useful in anything other than the simplest cases. I see it as fundamentally broken. Alllowing use of full blown policy or use of policy refs allows a solution which can work for the small and large systmes.
Bob: does example 1 of proposal b
provide a mechanism for small system side? 1. This first one uses a
PolicyReference to refer to a predefined policy assertion
... is a policy ref uri a functional replacement for Mode?
<asir> Policy Reference URI does not carry any semantics
<asir> it is just a reference
Wu: I do not think so, since mode has defined fault messages.
bob: the fault is optional.
Gil: the fault as policy negotiaion at run time is way too late for me. There is a need to know ahead of time what is supported.
Wu: the policy reference does not satisfy the negotiation allowd by the mode with its faulting behaviour.
Dug: we could define a fault to use with the policy reference approach.
<asir> We are not convinced that policy reference URI is a functional replacement for mode
Dug: we can define a fault which is just as informative if the value of the policy reference URI is not acceptable, including the policy refs which are supported in the fault information
Bob: this approach is reducable to
the minimal case for mode behaviour, but is extensible to more full
use of policy.
... we could state "resource constained systems should only use policy reference URI".
Geoff: By doing this we are missing the distinction of two life cycles by deleting delivery element. Â You cannot stick everything you want into NotifyTo, you have lost differentiation.
Bob: back to the original question, can the policy ref (where it is placed can be discussed further) value serve as a functional equivalent to mode?
Geoff: this would require further discussion before answering.
Asir: while I agree a uri value can be used, it is a different question as to whether that uri can be a policy reference. The policy ref is defined elsewhere.
Ashok: would you be happier with a policy expression being used rather than a policy ref?
Asir: that has concerns for the small device implementers. Also who would define the policy assertion for "push"
Ashok: this spec could define such a policy assertion type.
Asir: that would require a complete
proposal to evaluate.
... using full policy expression would not help the small device implementers.
Ashok: the use of policy is not a problem, it seems to be the full policy intersection which is troublesome for implementers of small systems.
Li: how about an option E: there are several modes listed in the Wiki. There is a hierarchy of things, push vs pull, then other features (ack or not), interval or not, and the combination may not be suitable for one uri. A compromise is to keep mode as element, and separate out the push vs pull indication. This would allow multiple refinements to do combinations. For those which do not support refinements, we still have push vs pull
bob: mode element with multiple possible children as refinement elements. One might be push, another ack. then push with acks would be adding both children.
Li: no I would prefere a mode element with name "push" allowing refinements such as "acks" or "intervals"
Bob: I see this as having some of the characteristics of ws-policy.
Gil: the ws world has ws-policy,
which is a general purpose framework for dealing with such issues.
Why do we need to have a concept of mode?
... do not see need for additiona wrapper element, such as delivery, to deal with extensions. WS-man mode has functions which are outside of semantics of delivery element. The semantics of extension tell you what they are for, and can be kept as extension to subscribe element.
Bob: I hear Li's proposal as a way to
express the semantics of current uses of mode, using a mechanism
which is similar to the policy expression.
... are you suggesting to put this new mode element within the deliver element, as an alternative to a mode attribute?
Li: yes that is my proposal.
<dug> Gil: given a nested structure, such as
<dug> Subscribe
<dug> Delivery
<dug> Mode
<dug> PolicyURI
<dug> NotifyTo
<dug> EndTo
<dug> Would a policy on notifyTo and EndTo require its own child policy like element.
<Bob> scribenick: Tom_Rutt
Bob: the fundamental issue on mode as
a single URI , regarding the combinatorial effect is helped by the
list of behaviour elements, which makes it look more like the use
of ws-policy
... if we did have such a new "mode" element allowing a list of behaviour subElements, where would it be placed
... I would like to understand why the delivery element would place this new mode element
Geoff: Mode as originally defined was to define lifecycle of notifications. If one was to replace mode with something like policy, this is a general concept which is broader than delivery aspects.
Gil: extension is extension, with its own semantics. All we need is an any extension, which if not understood is ignored. You can also add a header element to indicate its use is required or in use.
<gpilz> wsman:ContentEncoding, wsman:SendBookmarks both exist outside of wse:Delivery, yet apply to the lifecycle of the notifications
Dug: lifecycle of notification seems
no different than lifecycle of any message. We already have an
extension inside of EPR. both Notify To and End To have different
semantics, but both could have a new feature which needs to be
turned on. I see no need for having a new "endTo:@Mode" when epr
extension could be used.
... I see three extensions for:
Properties of notifications (notifyTo epr)
Properties of end to message (endTo epr)
Properties of subscription itself (xs any of subscribe)
dug: what do you need to do for a
notification delivery that you do not have to do for end to and
notify to
... would it not be better to use a solution mechanism which can be used in other places for ws-*
Geoff: All the things which have been done with mode so far are eventing specific. I would have to think about (given eventing is one-way construct) mechanisms which are more general
Dug: the push vs pull example is concrete and might be a reason to keep mode. However we have ways to solve this without mode (e.g. make connection). RM has an acksTo epr which can work in push and pull environment without using something like the eventing delivery mode attribute
Geoff: it is not clear to me that make connection is a complete solution for pull mode of eventing. It is the limitations of eventing that has me saying that the concept of doing eventing is different than just passing around messages
Dug: to keep mode there needs to be concrete examples as to why eventing is different. I need to understand why an EPR is not good enough to satisfy those needs. Most examples I have heard could be handled using an EPR. It seems to keep coming back to "that is the way we implemented it already"
Wu: having a delivery mode attribute gives a single place to add delivery extensions. I do not see a problem of keeping mode, and also allowing more general policy mechanisms
Gil: experience shows that people to not stay within the model of having delivery extension only be in the mode attribute. The idea that wse:delivery is a magical envelope to constrain all extensions does not work. For example, WS-Man has extensions that are not handled by delivery mode
Wu: I see value in delivery element, it is there and should not be removed
Dug: delivery does harm, since we
have to explain how to use it and when to use it. We have to define
what goes into subsribe, the delivery element, and the eprs. I see
two extensibility points, say the subsribe and the notifyTo epr.
Why is sending out notifications different than sending any other
message. There are two lifecles, one for the subscription, the
other for the message...
... (notification). I do not see how we have an additional lifecycle between those two.
... given structure
scribe: ...
I see no need for anything between these two. NotifyTo gives all that is required for delivery.
Asir: if you take away push and pull this could be true
<asir> I am afraid that Doug wasn't around when Eventing was designed
<asir> Interesting rationale
Dug: eventing did not do a mode for endTo.
<li> where is time machine?
Wu: that is because endTo has only push way.
<asir> i wish we had one .. so we could put doug in and roll him back
dug: why is push the only way to deliver endTo?
Li: Dug says epr alone can indicate
if I can do push or pull. What about anonymous address, this does
not give enough information for push and pull.
... ws addressing has "anonymous" and "none" as address.
bob: Li is saying: with epr I can do push and pull mode with epr. How do I tell to do pull mode with EPR. I cannot send message to anonymous or none? How do I send pull message.
dug: you can pass in a makeConnection uri instead of an anonymous URI, that states the make connection is used to pull the message
<asir> Li drives home the point that an EPR is not enough
Li: if you have to extend EPR why is it not acceptable to just use Mode, rather than define a new extension for epr?
<Bob> Li now understands that the epr could be a container for more information
Geoff: If we put everything in an extension to notifyTo epr, I do not see how this could handle things such as queuing
Dug: priority mechanisms could apply to both push and pull. Those types of things would be properties of subscription, and thus would be outside notifyTo EPR.
Geoff: epr is to decide mechanism to send the information. However eventing has subscription mechanism to define how to send the information, not associated with mechanism used to send notification
Dug: we cannot remove extensibility inside the eprs, we need extensibility inside subscribe, I see not need for also having extensibility inside delivery element
Bob: regarding push and pull, we need
a queuing mechanism for pull. If we need different qos for separate
queues, this is not part of delivery but is part of the
subscription. We could define a queuing behind a push (higher
priority send first). It might be better to define in a general
subscription bucket a way for defining extensions pertaining to the
subscription. Some specs have put...
... such extensions into the delivery mode, but they are not really associated with delivery endpoints
... having a flexible way to place extensibility points in different buckets seems good. Slicing the current aspects associate with current uses of mode into their more appropriate locations would be good. The concern seems to remain about evolution from current implementations.
Gil: putting policy in subscribe message itself is not how I see it. If I want to request that this subscription is pausable, I would put in an extension element for pause. Where policy comes in is for the event source to state whether it supports such an extension
Bob: If we use policy as general mechanism to govern operation of eventing for large systems, and retain the mode stuff for small systems, the large systems would not use such a mode extension unless they were implementing the specific spec which uses mode (e.g. ws-man)
Li: the mode could have an attribute at a high level (e.g, pull or push) Then its children could have more specific behaviour identifiers within the context of the higher level mode
Why is this not good enough for such an extension
<dug> <subscribe>
<dug> <notifyTo> ... </notifyTo>
<dug> <pull/>
<dug> <queue foo=true|false/>
<dug> </subscribe>
<li> should <queue> be inside <pull>?
<dug> it can be - gil just moved it there :-)
gill: or could do:
<Queue />
<li> ok, something like that
If queue is defined as part of pull extension
<li> or the root could be <mode name="push|pull" >
Geoff: Gil's proposal has always been: 1) use basic extensions to add new features, 2) use new headers to indicate feature must be understood, 3) use policy to advertise what is supported
Dug: another example:
<notifyTo> </notifyTo>
Dug: this is just as easy to check. The qname can be seached for in the subscribe message
Geoff: this approach allows many things to be added. How do you find the extensions
Dug: same problem exists for a mode element with multiple children
Gil: there is nothing that can be done with a uri that cannot be done with a qName extension
as particpant rather than scribe: Any way to get around the combinatorial limitations of the mode attribute (such as Li's proposal to allow a smaller number of high level mode names, e.g., push or pull, with a nested list of further detail elements, e.g, use ack) will require current ws eventing extensions to change theirimplementations to evolve. I am now even more of the opinion that using the...
scribe: extensions with qNames will not be more difficult to implement than these other proposed hacks to retain the mode attribute
<notifyTo> </notifyTo> (changed from <Delivery/>
<endTo> </endTo>?
why is this more difficult?
<notifyTo> </notifyTo> (changed from <Delivery/>
<endTo> </endTo>?
<mode uri= />
Bob: we could define a predefined
extension called mode with the proposal above
... as an alternative could put the mode extension into the notifyTo EPR, or any other EPR you need to extend
... currently there is no way to describe mode for endTo
<li> it didn't die but was murdered
<gpilz> it couldn't live with its own lameness
<Bob> recessed until tomorrow
<Bob> ashok tomorrow am, Prasad tomorrow pm


text:
Simply select "Pick up in store (FREE)" as your shipping method and leave the rest to us! Happy shopping!
24 May 2013
NEW! Shop TT online, pick up in store!
Simply select "Pick up in store (FREE)" as your shipping method and leave the rest to us! Happy shopping!
9 comments:
- AnonymousMay 25, 2013 at 12:37 AM
І may gеt around to doing а similar thіngReplyDelete
myself sometime, if I can fіnd the funding.
Here is my blog: fast cash till payday
- AnonymousMay 25, 2013 at 11:15 AM
What kind of scanning technology does The Bod Pod use to figure out bodyReplyDelete
Feel free to visit my weblog before and after weight loss success stories
- AnonymousMay 25, 2013 at 12:11 PM
The datа is nigh-on ωorthless, whiсh meansReplyDelete
the rеsults don't make sense either.
my blog ... payday loans fast
- AnonymousMay 26, 2013 at 8:19 AM
Hi terrific blog! Does running a blog like this takeReplyDelete
a large amount of work? I've virtually no understanding of coding however I had been hoping to start my own blog soon. Anyway, if you have any recommendations or tips for new blog owners please share. I understand this is off topic but I just had to ask. Thanks a lot!
Here is my page - vigrx plus verdad o mentira
- AnonymousJune 14, 2013 at 1:41 PM
Journaling allows people reconnect with their Inner Wizard to clarify theirReplyDelete
thoughts and feelings, and gain self-awareness. ' A list will appear, and then double click the library you want to access, and then double-click the file or folder you want to access. com to learn all you need to know about the 'Wizard of
Oz' hanging.
Review my website - wizard101 Cheats
- AnonymousJune 14, 2013 at 10:02 PM
- After cleaning their neighborhood's pipe from shell creepers, the Mario Bros. It is said that one nasty green creature is responsible for their existence. He said he has no other building plans for the island, which is valued at $2.ReplyDelete
Also visit my homepage ... clash of clans hack download no survey :: evival.net ::
- AnonymousJune 17, 2013 at 9:09 AM
Consult with your Database Administrator for more assistance.ReplyDelete
It was an original invention of the early American colonists, a new
form of paper currency backed by the "full faith and credit" of the people.
com, they believe Dorothy represents Theodore Roosevelt because
Dor-o-thy are the reverse of the syllables The-o-dore.
Have a look at my blog ... wizard101 cheats (http://focusbromley.co.uk/members/rogelio78/activity/518/)
- AnonymousJune 17, 2013 at 12:05 PM
To change the brown background, right-click it andReplyDelete
select Format Shape. On that page, you can select
the border you want to download and download it
to your computer. small businesses, there is no government
help for you and if you find some'consider it a gift.
Have a look at my blog post; candy crush hack (greatgiftcircle.com)
Hi, I was simply checking out this blog and I really admire the premise of the article this is regarding Online shopping store and this is really informative. I will for sure refer my friends the same. ThanksReplyDelete


text:
Fall is a bit late this year. The DC farm markets are still selling beautiful peaches and even a few nectarines. There's nary a head of broccoli or Brussels sprout in sight. With the pressure of weekly recipe development, that calls for another Hail Mary pass. That, of course, is the origin of chicken pear piccata.
The immediate concern is whether sweet pears will pair well with a sauce of lemon, parsley and butter, all of which sound rather springy, like something you'd drizzle over young roasted chicken served with new potatoes and fresh asparagus. And what of the capers, whose combination of salt and bitterness seems distinctly un-pearlike?
The result? Either I have a really perverse sense of humor, or it was really good and the tart, sweet sauce was beautifully complex, richly textured, and even played well with capers. (Or I just have a really perverse sense of humor.) After all, I feel a little off with fall being so late.
Chicken Pear Piccata
Serves 4
This is the time to reach for those super-tender pears that have a couple of bruises on them. They'll make the smoothest sauce.
For chicken:
- 4 boneless, skinless chicken breasts
- 1 cup flour
- 2 tbs olive oil
For sauce:
- 1/2 cup dry white wine
- 1/2 cup chicken stock
- 2 Bartlett pears, grated, about 1 cup pulp
- 1/2 lemon, juiced
- 2 tbs cold butter
- Nutmeg
- White pepper
- 1/4 cup minced parsley
- 1 tbs capers, minced
- Place chicken breasts under plastic wrap and pound flat to 1/2" thick.
- Season flour with salt and pepper and place in a large freezer bag. Add chicken breasts to bag, one at a time, and shake to coat.
- Heat 1 tbs oil in a 12" skillet over medium high heat. Add two breasts and brown on both sides, cooking through. Reserve, add remaining oil and cook remaining breasts. Reserve, tented with foil.
- Return pan to med-high heat and add wine. Reduce by half, scraping brown bits from pan. Add stock, grated pear and lemon juice. Reduce heat to med and simmer for 10 min.
- Work sauce through a fine mesh strainer, leaving any solids behind. Return pan with any juices from the chicken. Cook 2 min longer over medium heat. Remove from heat, whisk in cold butter and season to taste with nutmeg, white pepper and a pinch of salt.
- Serve chicken with sauce, parsley and capers.


text: Artifact Details Title Apple I motherboard Catalog Number 102626976 Type Still Image Identifying Numbers Other number 297 Verso pencil Dimensions overall: 8 in x 10 in Description Black and white image of the Apple I motherboard. To right of motherboard is a small board with several chips. On verso white paper label with "CM" and a green paper label with " Byte 13-0470 60'/(10)" Category Photograph Credit Courtesy of Gwen Bell Lot Number X7413.2015


text:
Sundial Brands (SheaMoisture and Nubian Heritage) partners with Bain Capital
A little under a week ago, September 2nd to be exact, Sundial Brands announced a partnership with Bain Capital. Sundial owns such popular natural hair brands as SheaMoisture and Nubian Heritage.
Here, Sundial describes its partnership with Bain Capital:
"Today, Sundial Brands, announced an historic and exciting partnership with Bain Capital to bring the firm on as a minority, non-control investor in our company. As we approach our 25th year in business, this begins another transformative chapter in our story – a story that our community of employees, consumers, retail partners and many more are writing along with us. So, we wanted all of you to hear straight from us why we made the decision. Quite simply, we want to be better so that we can serve our communities better. Period. But we thought you might want a few more details as well, so here are some of the key reasons why this is such an incredible opportunity for us – and you!"
The website goes on to provide 10 reasons SundialBrands chose a new partner. Feedback on social media seems largely positive. For some, the partnership with Bain will allow SunDial to reach more consumers, broaden the brand's reach, and, hopefully, generate additional revenue. However, some bristle because Bain Capital was founded by Mitt Romney. In essence, some may perceive Bain Capital as a Republican haven and think that the firm cannot properly handle a natural hair brand. Articles in the Wall Street Journal and the Boston Globe provide additional context on the partnership and Bain Capital.
What are your thoughts? Is it it a good move for Sundial Brands to partner with Bain Capital? Why or why not?


text:
I can safely say, I'm getting into Beaded Colorways first because I love color. I can also say it was a cruel thing to order four books at one time. What was I thinking? Not regretting ordering so many beads though. Can never have too many beads!
January 24, 2012
A lovely bunch of new beads AND new books
January 20, 2012
Lots of Catching Up to Do
Where did the last year go? Had all the best intentions to get a website created......done - an Etsy site up and running....done - get a facebook page.......done - get a blog and keep it up......Not! I love reading others blogs but I must admit that to write something for myself is not an easy thing to do. My excuses to myself are that I'm too busy creating and keeping up but no, let's be honest my website is not up to date either. I love designing and creating jewelry but to keep all the internet media going is a struggle for me at the moment.
I believe that 2012 will be a much more productive year. These are some of my latest works.
I have some new designs in the works, and new beads ordered so maybe that will be my inspiration to get moving. Keep checking back just in case I'm right!
Subscribe to: Posts (Atom)


text:
Although it's a bad practice, Oracle allows the columns to be named arbitrarily using the double-quote syntax. With this, the names can include keywords, lowercase or unicode characters.
A similar problem occurs when replicating to non-Oracle targets - some of the valid names in Oracle are keywords in other database systems and thus can cause issues for the APPLY process.
- For lowercase names: as the SQL is case insensitive and APPLY does not use double quotes, just create the column name in uppercase on the target
- For unicode: not supported
- For spaces in names: not supported (although spaces at the beginning or end of column names are ignored)
- For keywords: a global rename function is implemented. This APPLY_COLUMN_NAMES_MAP variable specifies a global rule renaming all columns in all replicated tables with a specified name to a different name.
set *.APPLY_COLUMN_NAMES_MAP coumn1=newcolumn1[,column2=newcolumn2[,...]]
set *.APPLY_COLUMN_NAMES_MAP COMMENT=COMMENT_COLUMN
APPLY process requires a restart to implement this mapping.
After restart, APPLY process log will show column mapping details as follow.
2016/06/06 05:34:37 INFO> Column translate: [COMMENT]=>[COMMENT_COLUMN]


text:
SOLANA BEACH — A special one-night reading of "The Rape of the Chambermaid" by author Judge H. Lee Sarokin will be presented at 7:30 p.m. April 15 at the North Coast Repertory Theatre, 987 Lomas Santa Fe Drive, Suite D.According to Rancho Santa Fe resident Sarokin, "The play was inspired by the rape charges against Dominique Strauss-Kahn. It covers a number of themes that have always concerned me. I wrote an article for the Huffington Post entitled: 'What If He Is Innocent?' First, I am constantly troubled about the role pre-trial publicity plays. Strauss-Kahn was forced to resign his position as head of the International Monetary Fund and give up his quest to be president of France solely based upon charges against him.
"Second, I find it fascinating that the name of a rape victim is voluntarily withheld by the media (a practice which I do not oppose), but not the name of the alleged rapist. What's worse being known as a rape victim or a rapist? Third, the play also depicts my concern about the role of money in the justice system, the abuse of rape victims during trials (virtually a second rape) and the fallibility of eye-witness identification. Finally, I hope it also raises profound ethics questions faced by lawyers representing clients accused of crimes."
A $5 donation at the door is suggested. For information, call (858) 481-1055 or northcoastrep.org.
Sarokin attended Dartmouth College and Harvard Law School. He was a distinguished trial lawyer in New Jersey for 25 years before being nominated to the United States District Court for the District of N.J. by President Jimmy Carter. He was elevated to the United States Court of Appeals by President Bill Clinton. He served 17 years on the federal bench and retired in 1996. He was appointed Distinguished Jurist in Residence at the University of San Diego School of Law and served in that capacity for five years. His first play is about a fictional trial in which a man wrongly accused of aiding terrorists is imprisoned and tortured and sues the President of the United States. He is married to Marjorie Lang and resides in Rancho Santa Fe.


text:
Elvis Tribute.... The Ultimate
Music and Video
Music Demo's
Suspicious Minds
An American Trilogy
Don't Be Cruel
How Great Thou Art
Singing Live at Capitol Square , Witham to a
sell out crowd ! To view simply click on the youtube links below.
Thats Alright Mama, CC Rider and Viva Las Vegas
One Night with You and Burning Love.
Can't Help Falling in love and Suspicious Minds.
This is the very Gretsch guitar that
Elvis played on the 68 Comeback Special. Unfortunately not owned by Danny; it was bought for £40,000 at auction and he was
asked by the buyer to have photo's taken with it
for the press. What an honour and privilage just to hold it even for a short while !!
Why not book Danny to supply for your evenings entertainment, his amazing Laser Disco !!! Click the
link below to see it in action......
Starry Night Laser Disco


text:
The early decades of science fiction film and music included non-talking versions of 20,000 Leagues Under The Sea and The Lost World. But they were expensive and difficult to make, special effects were creative but the visions were too epic for the technology. And music was what we'd call needle drop today: fitting existing music to the picture. Pop songs and light classical. People loved them, but the films had a short life.
We jump forward in time from 1902 to 1927 to get the next big breakthrough: Metropolis. Fritz Lang created an amazing team to make this film, that still looks visionary today. Including a score for large orchestra by Gottfried Huppertz. The music was played live at each screening, and fit the film perfectly. Just the first minute shows you how far the art has advanced in emotion, storytelling, and spectacular sound and picture.
The version to get is the newly restored one from 2010, that includes scenes lost for 83 years, and a great live performance that hits over a thousand cues. The film was far ahead of its time.
The music is operatic, in the tradition of Strauss. Could also work in a fantasy drama. It's great film music, but is there anything that says science fiction?


text:
This title may not be available to watch from your location. Go to www.amazon.com to see the video catalog in United States.
Tom Hanks "gives one of the towering screen performances of all time" (New York Post) as Chuck Noland, a Fed Ex® systems engineer whose existence abruptly ends when a harrowing plane crash leaves him isolated on a remote island.


text:
Alienation in "Black Boy"
Eng. 111
Prof. Weitz
Causes of Alienation in Black Boy
Black Boy demonstrates how the protagonist, Richard Wright, alienated himself from his community because he did not share the same religious and societal beliefs practiced by his community and felt that the questions he had about everyday life would not be answered if he conformed to his degraded position in society. Richard alienated himself from his community because he wanted to find answers to his questions about racism that were not being answered. His desire and capacity for knowledge is discouraged and underestimated by whites and blacks due to living in the Jim Crow South. Religion is also a cause of alienation because Richard does not share the same enthusiasm for religion as the community does. These are all causes of alienation for Richard.
The first signs of alienation come as a result of Richard's curiosity with the world around him. An insatiable sense of curiosity grew in him after learning to read, write, and count to one hundred that he soon became, "a nuisance by asking far too many questions of everybody." This led him to learn about the relations between whites and blacks. After finding out about the white man beating the black boy he began to ask questions regarding race and why there is a puzzling coexistence between whites and blacks. He asked his mother why that happened and she simply responded by saying, "You're too young young to understand." She did this to dodge this controversial topic. He had so many questions regarding this topic and no one in his community was willing to give him a straight, if any, answer. On another occasion, Richard asked his mother if they could look in the white side of the train and noticed his mother becoming irritated. "I had begun to notice that my mother became irritated when I questioned her about whites and blacks, and I could not...
Please join StudyMode to read the full document


text:
Canare's XLR Lo-Z microphone cable benefits from the quality of their own L-4E6S+ which features the "Star-Quad" configuration and high-shield densit...Click To Read More About This Product
Microphone cable that protects your sound thanks to ingenious design.
Canare's XLR Lo-Z microphone cable benefits from the quality of their own L-4E6S+ which features the "Star-Quad" configuration and high-shield density to reduce hum and noise to less than 1/10 that of conventional 2-conductor mic cables.
The Star Quad configuration is 4 inner conductors that provide a substantial improvement in rejection of EMI. Each inner conductor has 40 strands of small diameter (.000315") copper wire that provide maximum flexibility and avoid breakage. Its polyethylene insulation is a better dielectric than rubber insulation, thereby reducing capacitive coupling for improved high-frequency response. Cotton filler acts as strain relief and also reduces handling noise by preventing changes in stray capacitance. The high density, braided shield blocks most static and other noise.
Its tough, yet flexible jacket uses a specially formulated PVC compound which makes a tough and cold-resistant outer jacket that can be unpacked in extreme cold and used immediately. It is also durable enough to bend or twist while remaining safely flexible.
This cable handles the rigors of the road and maintains the quality of your sound. Order today!
Our product catalog varies by country due to manufacturer restrictions. If you change the Ship-To country, some or all of the items in your cart may not ship to the new destination.


text:
As she drifted into a light sleep, bloody images of Virginia lying dead on the bathroom floor snaked their way into her mind and waves of sorrow replaced her earlier feelings of contentment.
Thirty years ago, a young girl took her own life, leaving behind only her paintings to remember her. When Lorelei purchases one of these paintings, she doesn't expect it to stir up unfinished business from the past that will put her life in jeopardy.
From day one, disturbing things start to happen and they only get worse. Working alongside her best friend, Cherry, Lorelei is thrown into a world of the supernatural. When paranormal investigators dig up even more chaos, she seeks out the only person who might be able to help: a shamanic practitioner, who will reveal a truth so unexpected, it will change her forever.