text:
INDIANAPOLIS -- Injured Indiana Pacers forward Paul George said Friday he is not done playing for the USA Basketball Men's National Team.
Appearing publicly for the first time since breaking his right leg in the USA Basketball Showcase on Aug. 1 in Las Vegas, George said he still wants to play in the Rio de Janeiro 2016 Olympic Games.
"Absolutely. It's in Brazil," George said. "I look forward to a comeback. I look forward to have an opportunity again to participate in Team USA in 2016. This injury has nothing to do with my take on playing for my country at all."
George, who is on crutches and may begin light rehabilitation as early as next week, is expected to miss all of the 2014-15 NBA season. If his healing process goes quicker than expected, he might still play for the defending Central Division champion Pacers by the end of the season.
"I would love to come back and play this year. I'm a competitor," George said. "I understand there's a possibility I won't be back this year. I'm very aware of that. But if I have the opportunity to make a comeback, I'm looking forward to it."
A national debate surfaced after his injury as to whether NBA players should participate with USA Basketball because of the safety risk. George called the criticism of the national team "unfair."
"It was a freak accident. It was just a freak accident," George said. "No one's really been injured the whole time … since USA Basketball has been here. They've never seen someone take a huge injury. I think it just happened. Freak accidents happen.
"They don't deserve any criticism for this. I would love to be a part of USA Basketball in 2016."
Players on Team USA will wear a patch on their practice shooting jerseys in honor of George. They are not permitted to wear a patch on their game uniforms during the upcoming FIBA World Cup, per FIBA regulations.
The United States will play Brazil in an exhibition game Saturday night at the United Center in Chicago. George said he will stay home in Indianapolis and watch the game on TV.


text: Trovit uses our own and third party cookies to enhance your user experience, improve our services, and to analyze your browsing habits in order to show you advertisements related to your preferences. By continuing browsing please note you are accepting this policy. You can change the settings or get more information here >>

subset: commoncrawl


text:
Since its announcement last fall, EA's Dead Space has made some big waves. We'll dispense with the background and niceties about the plot and get down to the nitty gritty. In the future, Earth's resources are scarce, and humanity survives by sending mining ships around the galaxy to strip the elements from other planets. As space miner Isaac Clarke, you're aboard the Nishimura, a massive mining ship that's gone AWOL and offline. Naturally, after you board the ship with fellow employees, things go decidedly pear-shaped.
We've discussed the numerous gameplay quirks, such as zero-gravity combat and "strategic dismemberment," EA's coined term to describe gunplay. But we haven't been able to sit down and spend more than a matter of minutes with it until now. We're less than a month off from Dead Space's release, so nearly everything we've played should be indicative of what you'll experience in mid-October. We'll spare you spoilers and plot details, but as of now, we're playing the fifth of 12 chapters, and will probably keep playing until the build stops us.
It might not seem apparent from the offset, but the first few chapters of the game indicate that it breaks down its twelve chapters into tasks (get the dead ship's tram running, fix the fuel boosters to prevent it from hitting an asteroid cluster, etc.). This seems appropriate, considering the way that EA's pushing Isaac as a working-class guy, or at least as working-class as you can get in outer space. EA Redwood Shores has acknowledged that Dead Space has a lot of buttons to keep you busy, and during big media events such as E3 and Games Convention it's been tough to really get comfy with the controls, especially since Isaac's movements take some time to sink in. You'll be pleased to know that the game eases you into your initial battles with the Necromorphs, undead monsters that incessantly pursue you.
We can't speak for how the remaining two-thirds of Dead Space will perform, but it's intriguing to see the ways that EA Redwood Shores lures you in. You'll be afforded certain rookie mistakes, so if you're a mediocre shot, you can get away with a few crappy misfires from your plasma cutter, a basic mining tool that can sever Necromorph parts. You'll discover the laser trail that leads you from one objective to the next (it reminds us of a high-tech version of Fable II's touted "breadcrumb trail"), and it's a subtle but great gameplay addition. We're also fans of the audio and communication logs; they're effective because they're slightly reminiscent of BioShock's audio logs, but the hologram presentation gives them more impact within the setting. Since the game does a great job easing you in with these niceties, it's a bit shocking a few chapters later as Dead Space begins to take things away.
Strategic dismemberment is easier done than said in the early chapters, but around the fourth chapter the pinch begins. We noticed fewer ammo drops for weapons that we'd grown accustomed to using. As new enemies, such as spider-like creatures that crawl into Isaac's armor, started to grow in number, we had to use other weapons such as the flamethrower. By the time we escaped the brutality of the fourth chapter, we discovered just how intricately Dead Space's gameplay hooks you, then plays with you as much as you play with it. Because in-game commerce is so quirky, your weapon and armor investments have quite a profound effect on how you'll play. Or, how badly you might screw yourself over.


text:
No. 14 Georgia 70, Montana 50
Georgia relied on its defense throughout the regular season. No
reason for the first game of the NCAA tournament to be any
Jasmine Hassell scored 16 points, Shacobia Barbee added 13 and
fourth-seeded Georgia used a big run midway through the second half
to pull away from Montana for a 70-50 win on Saturday.
Jasmine James added 11 points for the Lady Bulldogs (26-6), who
will face No. 5 seed Iowa State in the second round on Monday
"It's just focus and holding each other accountable," James
said. "Every time out, at every four minutes, it's just think,
`OK, we go back out this four minutes, let's focus on defense,
let's make sure the pressure is there."'
Georgia led 38-36 with 15 minutes remaining before going on a
21-6 run to grab control and earn a bit of redemption after being
upset by Marist in the first round a year ago. But the Lady
Bulldogs said they didn't talk about what happened in last year's
"Last year wasn't brought up. And personally when it came to
that time I didn't think about it," Hassell said. "I just knew
that our opportunity is now and it's time to go and there's no
reason to think about last year. Last year is in the past. It's
time to move on. We are in a new tournament, new team."
The matchup featured two of the most successful coaches in
women's college basketball. Montana's Robin Selvig and Georgia's
Andy Landers had combined for 1,618 wins at their respective
schools coming into Saturday's game and Selvig was looking for an
upset that would move him within one victory of joining Landers in
the 800-win club.
That upset bid was tossed aside by Georgia's impressive
second-half charge, mostly thanks to the Lady Bulldogs' defense.
Georgia entered the tournament among the best in the country giving
up just 53.3 points per game during the regular season.
The stout defense was on display as the Lady Bulldogs took
command, holding Montana to just two field goals in a 12-minute
span. Montana's drought was finally broken when Hannah Doran hit a
3-pointer with 2:35 left.
Montana became the 15th team to score 50 points or less against
the Lady Bulldogs this season. Landers' goal was to pressure
Montana from the start in the hope it would eventually wear down,
and he hoped the defense would generate some easy baskets for the
Lady Bulldogs.
It all clicked early in the second half.
"I was really pleased with the way our basketball team defended
from the beginning of the game to the end of the game and the
desired effect of that defense probably set in somewhere around the
13-minute mark there in the second half," Landers said. "I feel
like we started to benefit from the playing it the way we played
Torry Hill led 13th-seeded Montana (24-8) with 11 points. But on
a night the Lady Griz needed to hit all their open looks, they shot
just 29 percent and committed 20 turnovers.
"We didn't convert as well as they did, we didn't score off the
steals, we didn't score off of their turnovers and that was a huge
thing for us," Montana's Alyssa Smith said. "It's hard to come
back against a team like that, especially when we do dig ourselves
a hole. We have to be able to convert, which we weren't able to do
Georgia was stunned when it was knocked out of the tournament in
the first round a year ago and vowed it wouldn't overlook its
opening opponent. Still, it was a struggle to shake the pesky
champions of the Big Sky Conference, who were trying for their
first NCAA win since 1995.
The Lady Griz even had a chance to take the lead early in the
second half.
Smith hit a 3 to open the second half as Montana closed to
32-28, the closest it had been since it was 8-4. After Hassell
split a pair of free throws, Katie Baker hit a 17-footer and the
Lady Griz were within three. Baker then split a pair of free throws
and Georgia's lead was just 33-31.
Griffin answered with a corner 3-pointer and Barbee scored on a
drive to push the lead back to seven, but Baker scored and Jordan
Sullivan hit a 3. Montana committed a turnover with a chance to
pull even or take the lead.
That proved to be as close as the Lady Griz would get. Following
a timeout, Georgia ran off 13 of the next 17 points to take a 51-40
lead with 9:10 remaining. Anne Marie Armstrong hit a corner
3-pointer, Erika Ford scored off a steal and Tamika Willis scored
in the lane to extend the lead to eight. James then hit a pair of
short jumpers and Willis scored underneath to run the advantage to
double digits.
"As the game wore on, our quickness on the defense end started
to separate us from them," Landers said.


text:
Two teenage girls who walked away from Dorman High School on Tuesday afternoon, sparking a massive search, have been reunited with their parents.
Two teenage girls who walked away from Dorman High School on Tuesday afternoon, sparking a massive search, have been reunited with their parents.
According to a statement from the Spartanburg County Sheriff's Office, the girls were in good physical condition.
A concerned resident called deputies, saying that he or she had been contacted by one of the girls. The resident told deputies that they could pick up the girls at the resident's house in Boiling Springs.
The investigation into the incident is ongoing, though deputies have said they did not think the girls were being held against their will.
Michaela Davidson, 16, and Taylor Cromer, 15, walked out of Dorman High School at about 2:15 p.m. Tuesday and were seen on surveillance cameras in the school parking lot and at a nearby Burger King.
Lt. Tony Ivey said authorities think the girls planned to leave the state with Michael Harvey Elgin, 19, and 18-year-old Cullen Dale Still — both of whom face charges of contributing to the delinquency of a minor. Elgin remained at the Spartanburg County jail in lieu of a $15,000 bond. Still, who was arrested at his home in Pacolet, was booked into the jail at about 2:45 p.m. His bond has not yet been set.
Elgin hasn't cooperated with investigators, initially denying he had anything to do with the girls' disappearance and then sending deputies to several locations where he said the girls could be found, authorities said.
Elgin has since told deputies that he took the girls to Motel Six, where they spent the night in a room that was reserved in Still's name, and that the group then headed to Gatlinburg, Tenn., where they spent another night, an incident report states.
In 2010, a then 17-year-old Elgin was charged with calling a bomb threat into Broome High School, forcing the school on lockdown.
Michael Davidson, the father of Michaela Davidson, said early Friday that his daughter's disappearance was out of the ordinary for the honor student.
Davidson said he and his wife think the girls might have planned to leave the school campus to grab something to eat at Burger King, but he thinks they intended to be back in time for their parents to pick them up.
Parents of both girls notified police after they arrived at the school to pick them up and the girls never showed.
Davidson said his family has been overwhelmed by community support on Facebook.


text:
Style # 201223
With luxe kimono-style sleeves, perfect round neckline and lightweight drape, this bebe sweater is summer-to-fall staple. Try it with a pair of metallic denim and statement add ons to maximize your look. Center back to hem: 24"/61 cm.
- 100% rayon
- Dry clean
- Imported
- Model is 5'9" and is wearing a US size S


text:
This Sunday, Oct. 7, Trinity Church in Pawtuxet Village will hold a blessing of the animals at 8 and 10 a.m. Pets may attend church in the company of their people, provided that dogs are kept on leashes and cats, bunnies, birds and other critters are in carriers. If your companion animal does not like other animals or is too anxious or ill, bring a photo to be blessed.
Special guests will include Blaze and Spirit, dogs being trained by prisoners at the ACI for assignment to wounded war veterans. Dogs spend weekdays in prison and weekends with families on the outside. NEADS Canines for Combat Veterans program volunteers will explain what they are learning to do for veterans recovering from combat injuries.
A Warwick Animal Shelter volunteer will bring an animal or two that are up for adoption. Guests are encouraged to bring a donation of canned dog food.
Trinity Church is located at 139 Ocean Avenue on the Cranston-Warwick line.


text:
Supervised Practicum
The supervised practicum course is available for students seeking an experiential learning opportunity that is not otherwise available in the Law School's curriculum and a faculty member is willing to supervise the student's work in the field. This is a distinct class from the "Supervised Research" course.
Under Faculty Rules, a student may only enroll in one supervised practicum during his or her career at Washington University Law School and may not be enrolled in a law clinic or externship and a Supervised Practicum in the same semester. A student may earn from 1 to 3 units of academic credit graded credit/no credit. Credits earned in the practicum are considered non-Law Classroom Units (non-LCUs).
The supervised practicum is an exceptional course because the School's recent expansion of externship courses and law clinics provide a wide array of law in practice opportunities that minimize the gaps the supervised practicum course was designed to fill. That said, instances arise when the supervised practicum is a suitable vehicle for academic experiential learning. The practicum does not count against the School's Clinical Program Guarantee.
The work students perform in their practicum placements should be structured primarily for the student's educational benefit. Student assignments should include types of work being done by lawyers at the placement.
Externships and practica are distinct from being a paid law clerk because the paid clerk is there as an employee to meet the employer's objectives. In contrast, students in practica and other academic externships are at the placement for legal practice experience and bring educational objectives to the placement. Thus, the student should determine what the institution has to offer the student. In the process of obtaining that experience, students will undoubtedly provide some valuable service and will, of course, be bound by the rules and norms of the placement. The more actively students seek a good educational experience, the more students will receive from the fieldwork. In choosing placements, and while in them, students should speak with the field supervisor about the primary work of the institution and what role the student may play in it.
Students should try to become involved in the interactive aspects of the practicum. That may require the student to ask to go to meetings and hearings and to sit in on important phone calls. Students should arrange their schedules to make those types of events a priority; these live experiences, as distinct from the other law school experiences, afford many lessons and challenge students to reconcile the law on the books and the law in action. Students should seek these opportunities even if they will not be adding value to the event because just observing and reflecting on lawyers or courts at work can be educational.
Note that students may not receive credit for hours spent doing administrative work, except to the extent that such work is necessary to complete the student's own assignments. If a field supervisor asks students to answer phones, perform word-processing, filing or copying, the student should simply explain that they are at the placement for educational purposes, receiving academic credit, and that the school does not allow students to take on such assignments. If the supervisor asks the student to do more than a modest amount of administrative work, students must raise that with their faculty instructor.
Course Requirements
For each unit of academic credit, a student must complete 52 hours of fieldwork during the semester (i.e., 4 hours/week over the 13 weeks of the semester). Students may schedule time in any way that works for the student and the field supervisor. Students should make sure they and their field supervisor have a clear understanding about the student's schedule.
To participate in a Supervised Practicum, a student must arrange for an appropriate placement site (and supervising lawyer or "field supervisor" in that office) and find a member of the law faculty to supervise the practicum. The student must submit a "Request to Take Supervised Practicum" form to the Associate Dean for Clinical Education and Vice Dean no later then the end of the second week of classes of the semester during which the student seeks credit.
Once the student has arranged the placement, the student should count the number of weeks remaining in the semester, taking account of holidays, and calculate the number of placement work hours per week needed to meet the target number of hours. If a student wishes to finish work at the placement before classes end, and the field supervisor agrees, calculate the weekly hours accordingly.
Students must keep a contemporaneous record of their hours, showing dates, times, work done during each time period, and the location of work done elsewhere than at the organization. Student time logs should list the date, the hours worked, and the tasks completed during those hours. It should include a total of the number of hours recorded for the period covered by the log, and a running total of the number of hours per semester. The time log for any given day should be broken into units to show the amount of time spent on each task. Students must submit a copy of their time log with each journal assignment.
Learning Agenda or Contract
Students will meet with the attorney supervising their practicum and draft a learning agenda (sometimes referred to as a "Learning Contract"). This Contract is essentially a statement of the student's goals in undertaking the practicum and ideas on how to accomplish them. The purpose of this document is for the student to consider what is most important to them in the experience and to encourage students to plot a tentative course to achieve those goals. A student's experience in the field will be shaped primarily by how carefully the student formulates goals. If students engage with the fieldwork passively, waiting to receive whatever comes their way, the field supervisor will determine the student's experience. On the other hand, if students have specific goals and pursue them, these goals will lead the student to the types of experience they desire.
Before drafting the agenda, consider what lawyers in the office might do:
- Case evaluation/planning and problem solving
- Interviewing and counseling clients
- Factual investigation and informal discovery
- Legal drafting, written discovery, and depositions
- Legal research, analysis, and writing
- Negotiation, mediation, and settlement
- Administrative hearings, trials, appellate arguments
- Legislative or other policy advocacy
Students should also consider what, if any, lessons they wish to learn regarding law in action, such as how courts operate, a substantive area of law and practice, how policy is made and who makes it.
After determining their goals, students should explore with their field supervisor the experiences that would help in attaining those goals. A list of planned experiences will help students achieve a more structured, varied, and successful experience. Of course, students will need to be flexible and realize that this agenda will most likely be modified as the semester progresses.
While the format of this learning agenda is not important, students should include two categories of information: 1) goals for the practicum (e.g., "develop my research and writing skills" or "learn about the criminal justice system") and 2) for each goal, list potential/planned experiences or assignments that would help in attaining that goal (e.g., "draft a trial memo" or "observe a felony trial").
After the student has met with the field supervisor and written a final draft of a learning agenda, the student should send a copy of this agenda to the faculty supervisor and schedule an appointment to discuss it.
Weekly Journals
Weekly journals should be about two pages long and include a discussion of: 1) feedback received; 2) new insights about the law, lawyering, and the legal system; 3) progress regarding personal learning objectives; 4) self-assessment of progress; and 5) problems or concerns. The journal should be reflective as well as informative. The journal aids the student in reflecting on and planning for the placement and will help the faculty supervisor monitor and ensure the quality of experience.
Keeping Time
Each week, the student must submit to the faculty supervisor a record of the student's time. The timesheet should include: 1) dates/hours worked; and 2) type and subject matter of work and tasks accomplished. (Of course students should keep privileged communications and attorney work-product out of these submissions.) Students should keep their time records in 15-minute intervals.
Making the most of the practicum:
Whether students receive good supervision and useful feedback on their work is determined by their chosen field supervisor and by how much supervision and feedback the student seeks. A practicum student's goal should be to develop a relationship with the field supervisor that allows the student and supervisor to communicate with each other freely about the work.
Schedule a regular weekly meeting with the field supervisor. This will provide time each week to ask questions about work the student performed or is performing or to discuss other projects, cases, or dynamics in the office. A regular meeting will allow students to reflect and afford an opportunity to review work product or discuss other aspects of the work.
In the middle of the semester, students should schedule a mid-semester evaluation meeting with their field supervisor. At this meeting, a student should ask the field supervisor for feedback on the student's work, and talk about aspects of the experience that have or have not been satisfying. This is an ideal time to identify the types of experience that students had hoped to have that have not yet occurred, and to ask whether that experience is possible (e.g., go to a hearing, interview some clients, write a brief).
At the end of the term, students must schedule an exit interview with their field supervisor. This meeting, like the mid-semester meeting, is an opportunity for mutual feedback. If students are interested in constructive criticism of their work, make sure to apprise the supervisor of that.
End of Semester Checklist
At the end of the semester, students must fill out the End of Semester Checklist Form and submit it during their final meeting with their faculty supervisor. Students should not turn in the form until they have completed all of the items on the list. It offers students an easy way to check whether they have completed the course requirements.


text:
Audit (A-07-10-02764)
The Centers for Medicare & Medicaid Services Did Not Reconcile Medicare Outlier Payments in Accordance With Federal Regulations and Guidance
Executive Summary
Contrary to Federal regulations and guidance, CMS did not reconcile outlier payments associated with 292 of the 305 cost reports that were referred to it by 9 selected Medicare contractors. As a result, the Medicare contractors did not reach final settlement of the 292 cost reports. For the 13 remaining cost reports, CMS evaluated information submitted by the Medicare contractors and correctly determined that reconciliations of outlier payments were not required. CMS adjusts basic prospective payments for unusually high costs. These additional payments, known as outlier payments, are designed to protect hospitals from excessive losses due to unusually high-cost cases. Medicare contractors refer hospitals' cost reports to CMS for reconciliation of outlier payments.
Because CMS did not reconcile the outlier payments, Medicare contractors were unable to reach final settlement of 292 cost reports as of the conclusion of our fieldwork. The delayed payments to Medicare, along with associated interest, represent funds that should have been returned to the Medicare Trust Fund. At the same time, the delayed processing of outlier payments due from Medicare to hospitals, along with associated interest, could have affected those hospitals' financial viability. In addition, Medicare lost the interest that stopped accruing once the Medicare contractors referred the cost reports to CMS for reconciliation of outlier payments.
We recommended that CMS (1) ensure that Medicare contractors reconcile outlier payments and perform final settlement on the 292 cost reports we reviewed in accordance with Federal regulations and guidance, (2) ensure that Medicare contractors reconcile outlier payments and perform final settlement on all cost reports submitted after our audit period in accordance with Federal regulations and guidance, (3) implement an automated system that will recalculate outlier claims to facilitate reconciliations, and (4) work with the Medicare contractors to develop and maintain a complete and accurate list of the cost reports with outlier payments requiring reconciliation. CMS concurred with all of our recommendations and described corrective actions that it had implemented or planned to implement.
Complete Report
Download the complete report
Adobe® Acrobat® is required to read PDF files.
Let's start by choosing a topic
Priority recommendations summarized.
Work Plan
OIG planned projects.
Semiannual Report
Significant OIG activities in 6-month increments.


text:
Hey, I'm new to the forum, and well new to Morrissey and the Smiths as well, I've been into Moz since I first heard him 3 months ago on a music video show, I bought his best of and thought it was great. So I bought a few more of his albums and eventually a couple of the Smiths' albums. I still haven't got them all, but well I'ma teenager without money now that the summer is over, I will get them all eventually. I also saw Moz live on the 22nd of August in Marlay Park, great support acts and an amazing headliner.
Well a little about me, I'm 16, I'm a guy, and I'm from Dublin, Ireland. Currently in my last year of Secondary School. Other bands I like include, U2, The Boomtown Rats, Gary Moore, Aslan, Thin Lizzy, and The Verve, to name but a few.


text:
skip to main
skip to sidebar
No posts.
No posts.
Subscribe to:
Posts (Atom)
Subscribe To TearDrop Weddings
All Comments
All Comments
About Me
Holly Hatam
Toronto, Canada
Holly Hatam, Founder and Creative Director of TearDrop is an accomplished graphic designer and well known in the wedding industry as "the girl with very unique, whimsical designs." She started creating invitations when her friend Melissa pleaded with her to design her wedding invitations. After countless, enjoyable hours of watching Melissa beg like a baby, Holly agreed to the challenge! The response Holly got from her design brought a warm fuzzy feeling in her tummy...and from that day on she constantly had a craving for paper! When designing her invitations, Holly things of the "real" bride and groom and transforms a blank sheet of paper into an original piece of artwork that tells a love story of very original couple. Holly's other loves include, paint fights, silly words, her cat's wet nose, tea and despite not having met one yet, dinosaurs.
View my complete profile
TearDrop Weddings
My Blog List
Alison Events
bliss & that ....the life of an event planner
Elizabeth Anne Designs: The Wedding Blog
Events by Evonne, LLC
Michelle Rago, Ltd.—Blog
Once Wed Blog
snippet & ink: daily wedding inspiration
Southern Weddings Magazine
Style Me Pretty : The Ultimate Wedding Blog
The Bride's Cafe Blog
{ritzy bee blog}


text:
Linked by Thom Holwerda on Wed 6th Jun 2007 20:45 UTC
The European Union's second highest court is expected to rule on Sept. 17 whether the European Commission was right in 2004 to find that Microsoft violated antitrust laws, sources familiar with the matter said. Sept. 17 is the final working day before the retirement of Court of First Instance President Bo Vesterdorf, who is presiding over the landmark case. The ruling is expected to clarify whether the European Commission can continue to pursue the case, or whether it must pull back and permit Microsoft to continue its business practices.
Thread beginning with comment 245729
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
by Ronald Vos on Wed 6th Jun 2007 21:24 UTC
RE: Hopefully


text:
IC-7600 review
The ICOM IC-7600 is an improved version of the IC-756 Pro and Pro II review by N9EWO
Listed in Radio Equipment/HF Transceivers/Icom IC-7600
[ Hits: 223 | Votes: 1 | Rating: 10.00 ]
About IC-7600 reviewThe resource is currently listed in dxzone.com in 1 categories. The main category is ICOM IC-7600 DSP HF - 50 MHz Transceiver that is about ICOM IC-7600. This link is listed in our web site directory since Saturday Nov 30 2013, and till today "IC-7600 review" has been followed for a total of 223 times. So far received 1 votes for a total score of 10.00/10
You may find other interesting sites similar to this one, under the following categories:
- Radio Equipment/HF Transceivers/Icom IC-7600 - ICOM IC-7600
Rate this resourcereceived 1 votes for a total score of 10.00/10
The scale is 1 - 10, with 1 being poor and 10 being excellent.
Webmaster, add a Remote rating
Share IC-7600 reviewShare this link with your friends, publish within popular social networks or send it via email.
IC-7600 review - related linksWe thought you might be interested also in these additional resources, currently listed under our Radio Equipment/HF Transceivers/Icom IC-7600 category:
Search The DXZone.com
About The DXZone.com
The DXZone is the largest human created and maintained library of web sites dedicated to Amateur Radio (Ham Radio), currently lists 20.000+ links organized into 600+ categories and subcategories. Ham Radio operators review new sites every day since 1998, for potential inclusion in the Directory, and to evaluate the best place to list them.
Sign up to our Newsletter
Get the latest news from The DXZone in your email. Service provided by Google FeedBurner


text:
501 E. Hunting Park Ave.
Philadelphia, PA
Mon-Fri 7:00-5:00PM
M-Th: 8-8 | Fri: 8-7 | Sat & Sun: Closed
More warmth. More savings. It's all good.
Cool. Comfortable. Dehumidified. Even on the hottest days.
Learn about our 0% financing options and get a FREE quote.
We're here and ready to deliver, 24/7, 365 days a year.
Take advantage of our special offers and save on your heating oil deliveries.
No need to check your gauge or worry about running out of oil. It's easy to sign-up.
Any time. Day or night. All year.
A comprehensive service contract is your heating and cooling system's best friend.
We'll make sure you're saving with a system that is running safely and efficiently.
Feel the power of choosing your electricity provider.
Check to see if we provide electricity to your town.
We make it easy to switch electric suppliers. Start saving today.
For over 90 years, the people of Bucks and Philadelphia Counties have relied on Major Oil to keep their homes warm in winter and cool in summer. We're your local branch of HOP Energy, a trusted source for home heating oil delivery, high-efficiency heating and cooling equipment sales and installation, and reliable 24-hour emergency service.
Major Oil offers convenient online bill-pay options and affordable budget programs. We're also committed to providing unparalleled service to our valued customers. Being a good neighbor is part of our culture, and many of our employees live and work in the towns we serve.
To find out if we offer service in your town, just enter your zip code on the right. And if you have any questions, or would like to know more about Major Oil, don't hesitate to call us at 800-951-2941. We're here to help.
Become a customer now!
Call our new customer hotline
Or click here to sign up now
Check to see if we serve your neighborhood. Enter your zip code below.
© 2018 - Major Oil - 501 E. Hunting Park Ave. - Philadelphia, PA 19124 - HIC# PA015690
Home About Privacy Policy Site Map


text:
Is REST the future for SOA?
- Share
- |
Read later
Reading List
It seems like everywhere we turn we keep hearing that SOA's future is REST. There are a lot of publications comparing REST to SOAP and WS*[1], but such comparison seems to be too simplistic. There are two main approaches that have emerged lately – true REST and REST as a technology approach for services (aka REST Web Services[2]). In this article I will try to discuss whether either of these approaches can improve SOA implementations.
True REST for SOA
A true REST is effectively an implementation of Resource-Oriented architecture and not a pure technology decision. So the right question to ask when discussing true REST is whether its underpinning – ROA - is a good fit for your SOA implementation.
In order to assess the problem correctly, let's first recall that the SOA architectural style [2] is based on a functional decomposition of enterprise business architecture and introduces two high-level abstractions: enterprise business services and business processes. Enterprise business services represent existing IT capabilities (aligned with the business functions of the enterprise). Business processes, which orchestrate business services, define the overall functioning of the business.
REST, on another hand, is a set of architectural guidelines [3] expressed as Resource-Oriented Architecture (ROA). ROA is based upon the concept of resources; each resource is a directly-accessible distributed component that is handled through a standard, common interface. So, the foundation of ROA is a resource-based decomposition[3].
In order to assess the applicability of true REST for the implementation of SOA, the real question that we need to answer is "What is the relationship between a service and a resource?"
Services vs. Resources
What is a service?
In the simplest case, a service can be defined as a self-contained, independently developed, deployed, managed, and maintained software implementation supporting specific business-relevant functionality for an enterprise as a whole and is "integratable" by design. A "Service" is defined by a verb ( For example, "validate customer's credit score", which describes the business function it implements.)
A service is not a programming construct or a set of APIs, but rather an architectural (unit of design, implementation, and maintenance) and deployment artifact used for implementation of enterprise solutions. The service functionality is defined by a service interface (specific for a given service), which can be supported by multiple implementations. There are two basic ways of defining a service interface – RPC-style and messaging-style. RPC-style implementations use service invocation semantics and are defined through a set of parameters in the service interface. In the case of messaging style, a service interface is effectively fixed – it essentially performs "execute" - with an XML document as input and output (much like the GoF command pattern). A service semantic, in this case, is defined by the semantics of the input and output messages[4].
Historically, services are often defined as a collection of methods, but as explained in [2] these methods are independent from each other[5] and such collection serves as a namespace, simplifying the management of the services.
What is a resource?
In the simplest case, a resource can be defined as a directly-accessible, independently-developed, deployed, managed and maintained software artifact supporting specific data. A resource is defined by a noun for example, "doctor's appointment" that describes the data provided by the resource. A resource can also relateto other resources and provide a reference (link) to them. In effect, a resource is similar to an object[6], but with a predefined (CRUDish) interface semantic.
The semantics in REST are based on the set of HTTP operations and looks as follows [5]:
- createResource - Create a new resource (and the corresponding unique identifier) - PUT
- getResourceRepresentation - Retrieve the representation of the resource - GET
- deleteResource - Delete the resource (optionally including linked resources) - DELETE (referred resource only), POST (can be used if the delete is including linked resources)
- modifyResource - Modify the resource – POST
- getMetaInformation - Obtain meta information about the resource - HEAD
A resource is defined by its URL and definition of inputs/outputs for every operation supported by a resource[7]. Unlike a service, where methods are completely independent and can be deployed as independent endpoints, methods on a resource follow OO semantics, which means that all of them (except createResource) have to exist on the underlying resource (same URL).
Basic differences between Resources and Services
Based on the above definitions of resources and services, it seems intuitively obvious that they are very different. Let's delve into these differences first, and then discuss how they can impact resulting architecture.
As stated in [6]:
"Not only is REST not service oriented, service orientation is irrelevant for REST"
And [7] goes even further explaining the differences between the two as:
"If WS-* is the RPC of the Internet, REST is the DBMS of the internet… Traditional SOA based integration visualizes different software artifacts being able to interact with each other through procedures or methods. REST effectively allows each software artifact to behave as a set of tables, and these artifacts talk to each other using SELECT, INSERT, UPDATE and DELETE. ( or if you wish GET, PUT, POST, DELETE). And where exactly is the business logic? Is it in the stored procedures? Not Quite. It's in the triggers."
Here we will use a slightly different analogy, one based on J2EE. We can think of services as stateless session beans and resources as entity beans.
Services – session beans – serve as controllers allowing execution of a required operation, regardless of the underlying resource. For example, a debit account service might take the account ID and the amount and debit required account. A single service can debit any of the existing accounts.
Resources – aka entity beans – serve as a data access mechanism for a given instance of given data type. For example, in order to debit a certain account, it is necessary to find a resource representing this account and then update it to debit the required amount. An additional caveat here is that unlike an entity bean which can implement any required method, a REST resource has only a single modify resource method. This means that the actual business operation, the debit, has to be encoded as part of the request.
What does this mean?
Based on the above, it is impossible to build an SOA system using true REST. It is possible to build a system, but it won't be SOA. Both will start with the business-aligned decomposition, but because they are using very different decomposition approaches they will result in completely different architectural styles[8] based on different set of components and connectors.
Just because they are trying to solve the same problem – business/IT alignment and are both based on business driven decomposition does not mean that the result will adhere to the same architectural style.
Another question is whether it is possible to build a complete system using true REST. Based on the above, it is a question of whether it is possible to build a complete system using only a database or entity beans. Certainly you could, but it would require adding procedural code in the form of stored procedures (overwriting the meaning of the methods) or triggers (doing post processing based on the data changes). The same is typically true for a true REST implementation – you have to change the meaning of the modifyResource method (often using command pattern) to do more than data update.
As a result, a REST-based implementation is rarely true REST; it typically includes at least some elements of REST Web Services. So what does it mean to be a REST Web Service?
REST Web Services
The REST Web Service approach is an approach for using REST purely as a communication technology to build SOA. In this case, services are defined using SOA style decomposition and REST-based Web Services[9] are leveraged as a transport.
Although commonly referred to as REST, this approach has nothing to do with true REST and is similar to POX (plain old XML over HTTP), with the difference being that in addition to XML, it supports multiple other data marshalling types ranging from JavaScript Object Notation (JSON) to ATOM to binary blobs and leverages additional HTTP methods, compared to POX, which is typically based on GET and PUT.
What is the real difference?
Publications describing differences between SOAP and REST typically point to the following advantages of REST Web Services, for example [11]:
- "Lightweight – not a lot of extra xml markup
- Human Readable Results
- Easy to build – no toolkits required"
Although these differences are important (I will discuss them in detail later in the article), the main difference between SOAP and REST is the fact that while REST is implemented directly on top of the HTTP protocol, SOAP introduces an abstraction layer (SOAP messaging), that can be implemented on top of any transport. Standardized SOAP bindings currently exist for HTTP, SMTP and JMS, but non-standard bindings have been implemented for other transport solutions. This additional abstraction layer that provides decoupling between existing transports and SOAP-based implementations is the root cause of major differences between SOAP and REST Web Services.
The opinions about this abstraction layer vary significantly depending on whom you talk to. The REST camp considers it to be over-engineering and claims that it does not provide any real value. They claim that HTTP already provides all of the features required for implementation of services interactions. The SOAP camp, on the other hand, will argue that HTTP is not the only transport that is typically required for service interactions (especially inside the enterprise) and having a portable, extensible[10] abstraction layer is necessary for building robust, feature-rich service interactions.
Although both points of view have their merits, in my experience trying to limit SOA implementation to a single transport – HTTP - rarely works in practice. Yes, HTTP is ubiquitous and its usage typically does not require any additional infrastructure investments, but it is not reliable (HTTP-R is not widely adopted), synchronous only[11] (creating temporal coupling), does not have transactional semantics and so on.
Additionally, even if HTTP is the only transport used in implementation, the SOAP envelope can become very handy for a clean separation of business (SOAP Body) and infrastructure or out-of-bound (SOAP Headers) data in SOAP messages. And finally, if your original implementation does not require any infrastructure or out-of-bound data, the overhead of the SOAP envelope is minimal – two tags, but provides a well-defined way for adding such data as the need arises.
So, at the end of the day, data enveloping with separation of business and infrastructure concerns is a very powerful paradigm, which is often used even in the REST Web Services implementations. Whether to use a standardized SOAP or a custom enveloping schema[12] has to be decided by a specific implementation.
Other differentiators
Let's take a moment to discuss some of the other differentiators between SOAP and REST Web Services often cited in publications.
A popular opinion is that REST is much simpler then SOAP. According to them, REST simplicity stems from the fact that REST does not require WSDL or any interface definition. Such statements are naïve, at best. No matter which technology is used for communications between service consumer and provider, they must still agree on both syntax and semantic of their message exchange (interface)[13]. This means that in the case of REST, one of two approaches is possible:
- Defining an interface in a text document and "manually" coding of data marshalling/unmarshalling based on a common interface definition described in the interface document. Although such an approach is often promoted by REST advocates, it rarely scales beyond 10 - 15 elements, which is not typical for coarse grained REST services. Besides, such an approach is very error prone and as a result, most of the available REST frameworks have abandoned it in favor of the next approach.
- Defining an interface on the XSD level and generation of the data marshalling/unmarshalling based on the preferred framework (for example, JAXB or Castor in the case of XML payload or Jackson, in the case of JSON payload). Such an approach is, in effect, a minimalistic version of WSDL and requires about the same amount of effort as SOAP-based implementations. In fact, exactly the same approach is often used in the SOAP-based implementation, leveraging a single interface and a command pattern for service execution. The extension of this approach is usage of WSDL2.0 [13] and/or WADL [14] for REST.
Another common complaint about SOAP is perceived complexity of WS* standards [15]. Although there is no single spec that lays out the key WS*standards and their interrelationships, there is a standard for a majority of service interaction use cases. Granted, the choosing of an appropriate WS*standard and its usage might require some extra understanding/implementation time, but [16]:
"Arguing simplicity versus standards is ridiculous in the war between REST and SOA because simplicity without standards is just as detrimental to the costs and manageability of an application "
So, with the exception of the most simplistic examples like "temperature converters", REST is not any more simple than SOAP.
Another reason why many REST proponents are advocating REST as an alternative to SOAP is the fact that in REST, both requests and responses can be short. There are two main reasons for this:
- SOAP requires an XML wrapper around every request and response, which increases the size of a message. Although this is true, the important thing to consider here is not how many bytes the wrapper adds, but rather the percentage of overhead it creates. Because the wrapper size is constant, this percentage decreases as the size of the message grows, eventually becoming negligible. Considering that a typical service is fairly coarse-grained, the size of the request and reply is fairly large and consequently the overhead of a SOAP envelope is rarely an issue.
- SOAP is XML-based messaging, which uses verbose encoding. REST, on the hand, provides a more lightweight messaging alternative – JSON[14]. Although this is true, usage of the Message Transmission Optimization Mechanism (MTOM) [17], supported by most SOAP frameworks, allows for splitting of messages into minimal XML-based SOAP Envelope/Header/Body parts and additional parts containing message content that can be encoded as any MIME types, including JSON, binary streams, etc.
Although in theory, REST is lighter-weight compared to SOAP, in practice, with some advanced SOAP design techniques, the difference between size of realistic SOAP and REST messages can be made minimal.
Easy to build – no toolkits required
Because REST is based on HTTP, one of the claims of its proponents is that one can use familiar technologies like the Java servlet API and Java HTTP support to write REST services implementations and clients without any specialized toolkits. This is true if one wants to "manually" implement building input/output messages and data marshalling. The same can be done for SOAP Web Services as well. However, people rarely want to write such boilerplate code and as a result use toolkits for both SOAP and REST [18].
REST can be used as both system design approach leveraging ROA (true REST approach) and SOA design implementation leveraging REST technologies (REST Web Services). Although both approaches have their merits, they do not change the hardest part– defining business services/resources aligned with the enterprise business model. There are cases for both SOA and ROA, but at the end of the day those are two very different styles.
About the Author
Boris Lublinsky is principal architect at NAVTEQ, where he is working on defining architecture vision for large data management and processing and SOA and implementing various NAVTEQ projects. He is also an SOA editor for InfoQ and a participant of SOA RA working group in OASIS. Boris is an author and frequent speaker, his most recent book "Applied SOA".
I am thankful to my NAVTEQ colleagues, especially Jeffrey Herr for help in writing this article. Also thanks to Stefan Tilkov and Kevin T. Smith for providing interesting feedback (often negative), that helped me to improve the article
1. Cesare Pautasso, Olaf Zimmermann, Frank Leymann - RESTful Web Services vs. "Big" Web Services: Making the Right Architectural Decision
2. Boris Lublinsky –Defining SOA as an architectural style
3. Resource oriented architecture
4. Martin Fowler Richardson Maturity Model: steps toward the glory of REST
5. Resource Oriented Architecture and REST
6. Dhananjay Nene. Service oriented REST architecture is an oxymoron.
7. Dhananjay Nene. REST is the DBMS of the Internet
8. Dhananjay Nene. Musings on REST.
9. Jørgen Thelin. A Comparison of Service-oriented, Resource-oriented, and Object-oriented Architecture Styles
10. Richard Hubert. Convergent Architecture: Building Model Driven J2EE Systems with UML. Wiley, 2001 ISBN: 0471105600
11. Arun Gandhi. SOAP vs. REST – The Best WebService.
13. Lawrence Mandel. Describe REST Web services with WSDL 2.0
14. Web Application Description Language
15. Stefan Tilkov Interview with Sanjiva Weerawarana: Debunking REST/WS-* Myths.
16. Lori MacVittie. SOAP vs REST: The war between simplicity and standards.
18. Mark Little. A Comparison of JAX-RS Implementations.
[1] See, for example, an excellent comparison in [1]
[2] I am using here the term, that technically make no sense, and is not REST, but is widely adopted in industry and is considered to be REST by many people.
[3] By definition, a resource is any component deserving to be directly represented and accessed
[4] A typical implementation of such service is based on "command pattern". An input document defines both command itself and data used by this command.
[5] Method independence stems from the fact that although different methods can be executed on the same data – here this is an enterprise data which exists regardless of whether it is exposed by services, not an object instance specific data as it is used in OO.
[6] For example, [4] makes a direct analogy between OO and REST
[7] Many of the REST proponents claim that the latter is not necessary. We will return to this point later in the article.
[8] Architectural style are "like "design patterns" for the structure and interconnection within and between software systems'' [9]. A more holistic definition of the architectural style, provided by [10] states that "An architectural style is a family of architectures related by common principles and attributes"
[9] Another misnomer popular in industry – Web Services are SOAP by definition.
[10] All of the WS* implementation heavily relies on SOAP, more specifically on SOAP headers.
[11] You can always implement asynchronous messaging on top of HTTP, but you need an additional abstraction layer, for example SOAP with WS-Addressing, on top of it.
[12] Many REST proponents will argue that HTTP already have a set of standard headers thus SOAP headers are completely unnecessary. The issue here is that a predefined set of HTTP headers [12] has a very well defined semantics and any application specific data requires a custom HTTP header, which creates the same level of complexity as custom SOAP header.
[13] An interesting example of this is usage of the client APIs in many JAX-RS implementations, where interface is effectively a java interface – so much for multi language support.
[14] As always, simplicity comes with the price – try to implement polymorphism in JSON messages without manually encoding object types
Rate this Article
Hello stranger!You need to Register an InfoQ account or Login or login to post comments. But there's so much more behind being registered.
Get the most out of the InfoQ experience.
Tell us what you think
Paul Korney
excellent write up
jason ray
REST or SOAP
Gaston Coco
I hope people take more seriously REST Web Services using json.
Re: Excellent!!!
Paul Korney
REST is traversible
Mike Robski
oData is the protocol for 'DBMS of the Web'
Faisal Waris
You can expose a set of interrelated data entities as a model (in metadata) and query and update the entities in more or less arbitrary ways.
Nice article though. I still think we need a new term instead of REST to denote non-REST web interactions.
Nice Job
carlos sobral
Think about the differences between Resource and Services, is crucial in this matter.
Paulo Suzart
Please ignore
Mark Baker
Shame on you, InfoQ editorial staff.
Re: Excellent!!!
William Martinez
I agree and nice example but being you I would not call REST a protocol :)
REST is actually an architectural style and some REST people will tell you it is not a protocol. That is why it makes no sense to compare REST against SOAP.
Re: REST or SOAP
William Martinez
Actually, that simplicity you mention, if I understand correctly, is real, but it is not from REST. You see, REST is hard, actually, as all you should need to know is the initial URL. You should not have any prior knowledge about operations or parameters before hand. It is mentioned in this comments, HATEOAS is a requirement not often met. Knowing about the operations and parameters and even the url format (like templating) before consuming the resource is like having the WSDL not in XML but on your mind, or written in out-of-band.
I also have my opinion about the REST Web Services concept. I do believe the idea is useful but I would not call it REST anyway. Still, JSON is great in web environments using javascript, but in other ones it is requiring a library to parse js to use it, so it is important to check on appropriate technology.
Chuck Hinson
Well structured discussion with odd conclusions
Johan Eltes
General comments and hints of REST misinterpretation...
William Martinez
Very good article. I specially like the idea to clarify that REST and REST-WS are different things.
Here are a couple of comments:
1. I do not like the REST~Resource CRUD idea. You know, HTTP operations have similarities with CRUD, but are essentially different. The GET is not a read, it is a request for a representation. The PUT (often used as an update in REST community) is really a creation operation within the client's control space (it is the client the one that provides the URL or ID of the new resource). The POST is not an update nor a create (as in the REST Community), but an "Send" operation, where you send or post some data TO a resource. What that posting means and affects is totally depending on the actual resource business semantics. Thus, posting may result in a creation of a sub resource, in an update or even in a simple notification without any resource change. You see, not quite CRUD.
2.Nice to have a differentiation between Resource and a Service. Now, there is a difference between a plain Service and a WEB Service. The second is a service delivered through the web. Ha. As web is mentioned, REST is a nice word that may fit here. But, you see, WEB is not just HTTP and web as a delivery system is different to WEB as a System Platform. So... REST Web service looks more to me as a service that is implemented through a set of basic operations on resources that are driven using the HATEOAS constrain. Much more complicated than just saying web as a transport system. Of course, that service has some impedance mismatch associated when used for SOA and may be use sparingly, not as a foundation. See here for my slides on that: www.slideshare.net/willmarpo/explaining-the-soa...
3. REST is more than a set of architectural guidelines, it is actually an architectural style based on the combination of other styles, specially tuned to meet the Web requirements. It is a nice comparison between the resource and a service, but it is also important to compare REST style vs SOA style. REST is for networked applications and SOA for integrated ones, the components and relations are different, etc. And of course, comparing SOAP vr REST makes no sense as they are at different levels.
Re: Please ignore
Paul Korney
I mean no disrespect to your expertise on REST and I claim no such expertise myself. But you must understand that out here in the IT shop shanty towns, anything built with a JAX-RS implementation (or similar) is understood to be RESTful by most developers and managers... You know, it's a buzzword: Use the kit, get the buzz. Good luck trying to convince IT people otherwise...
I think it's very hard to get out of the RPC way of thinking and planning; it's simply faster/easier and more concrete to hack together an RPC style wrapper around some data/function (that's probably RPC like to begin with). Thinking and designing with resources, representations and hypermedia is still hard work and takes time. Most developers and managers can't be bothered because they don't see any immediate value. Sadly this story is not news to anyone.
Re: Rubbish
Boris Lublinsky
Re: General comments and hints of REST misinterpretation...
Boris Lublinsky
Let me try to answer some of your points:
In my mind, and I write this explicitly - SOA is an architectural style, while Web services is a communication mechanism. Moreover, in my mind, Web Services is an extremely unfortunate name - it has nothing to do with Web, hence there are multiple binding, SOAP over HTTP being just one of them. Now what you are describing is, in my mind is true REST, not REST Web Services.
I fully agree true REST represent ROA architectural style. I am in now position to judge whether SOA is better or worse then SOA, I am only saying they are different and should not be confused.
Re: Please ignore
Boris Lublinsky
Name a couple
Re: oData is the protocol for 'DBMS of the Web'
Dilip Krishnan
Re: Please ignore
Dilip Krishnan
It is unfortunate that vendors have made developing SOAP based Web Services very easy to develop and put out into the wild, without any service orientation nor architecture; I like to call these services-that-get-the-job-done. IMO RESTful systems are hard because it makes people think about what they are doing.
InfoQ has some really excellent resources, not particularly listed in this article:
InfoQ: A Brief Introduction to REST
InfoQ Explores: REST
InfoQ: Give it a REST: Mark Baker on Web Services
Re: Please ignore
Dan Creswell
Indeed it isn't news and it's a good chunk of the reason why our industry largely under-achieves.
"A "Service" is defined by a verb ( For example, "validate customer's credit score", which describes the business function it implements.)"
That's one means of defining a service (functional) but there's another one (data). If one follows the rule of thumb that says "don't move lots of data across functions" (research.microsoft.com/apps/pubs/default.aspx?i...) then one can see that splitting services on the basis of function is often (but not always) a poor choice. The point then is that service design (like all design) is a matter of taste and judgement, not fixed process and checklists to be followed blindly with no thought.
I'm sure the author is full of good intentions, unfortunately they're masked behind an article that is inaccurate and mis-representative of the way in which design should be done. A shame...
Re: Please ignore
Boris Lublinsky
I am sorry you feel this way, but lets stick to the facts:
1. I think that one of the reason why our industry is largely under-achieves is because we are not willing to either read or listen. We tend to form our own opinions even before we read or listen to something.
2. For better or worse SOA is based on the functional decomposition which often makes it difficult to accommodate enterprise data www.infoq.com/articles/SOA-enterprise-data. As for the data service, it is typically a data access service, which does not really solve the problem of moving data.
3. An article is not trying to compare functional and data decomposition. It merely states that they are different. I happen to agree that "service design (like all design) is a matter of taste and judgement, not fixed process and checklists to be followed blindly with no thought." I also happen to think that a good service design is still an art, not a science.
4. There is no place in the article that talks about how design should be done. What do I know, I am just an architect.
Re: Please ignore
Jean-Jacques Dubray
Did you really mean to write this?
1) You bring up good points on how seemingly hard it is to design RESTful services.
2) It is unfortunate that vendors have made developing SOAP based Web Services very easy to develop
I may misunderstand what you mean.
I also would like to remind everyone that to the best of my knowledge JAX-RS was designed with Roy Fielding's participating and blessing. Here is the list of "experts"
1.6 Expert Group Members 1
This specification is being developed as part of JSR 311 under the Java Community Process. This specifica- 2
tion is the result of the collaborative work of the members of the JSR 311 Expert Group. The following are 3
the present and former expert group members: 4
Jan Algermissen (Individual Member) 5
Heiko Braun (Red Hat Middleware LLC) 6
Bill Burke (Red Hat Middleware LLC) 7
Larry Cable (BEA Systems) 8
Bill De Hora (Individual Member) 9
Roy Fielding (Day Software, Inc.) 10
Harpreet Geekee (Nortel) 11
Nickolas Grabovas ...
Re: Please ignore
Andrew Wahbe
Very good, but...
Grgic Viktor
It is a good article, but you are wrong about a number of things:
1. Any real world business service that you can possibly think of can be defined as one of the HTTP methods. In fact, in your example ("VALIDATE customer's credit score") I stil don't know what service does for me. The consumer is not interested in validation part, but in the outcome of the validation of the thing that needs to be validated. So, from business perspective, the better service would be: "give me customer's credit score". The validation part is the implementation. What I'm trying to explain is that from business perspective the consumer always wants to give or get something. The "noun" can be important, but is only part of the giving or getting. That's why probably in your experience too, almost any service starts with get, save or something similar. Other noun's are rare or have stupid names like "process". So, it's all about the payload and not the service.
2. The comparison with DMBS is clever, but completely wrong. Similarity in methods says nothing about granularity. Business service can be "give me monthly report" which can based on many systems and databases.
3. You are actually admitting that you never haven seen REST based system: "Another question is whether it is possible to build a complete system using true REST". So, based on what did you wrote this article. A lot of theory? The arguments from REST community comes from practical experience.
4. In your article, I did not find a single example of a situation and service that cannot be solved with REST. All your arguments are about technology. I thought SOA and SOAP is all about business. :-)
5. Simplicity vs. standards. I don't really get it what you are trying to say. So, if we implement all those WS* standards we will have great systems? Well, I would rather bet on simple systems which are easily changeable. This is a fundamental difference in the way we see system engineering. Agile crowd tend to go for simplicity, which proves in practice as a better approach. Standards are important, but so often not needed and only a bottleneck in delivering business value.
Re: Please ignore
Dilip Krishnan
1) You bring up good points on how seemingly hard it is to design RESTful services.
What I mean by this resource oriented design involves re-thinking how one thinks about distributed systems and thats not easy. While the principles of RESTful systems are very simple at a high level, it involves a lot of design thinking. Which is why you see a lot of systems claiming to be RESTFul, that are really RPC systems over the web; where developers try to shoe horn the RPC paradigm onto a web platform.
2) It is unfortunate that vendors have made developing SOAP based Web Services very easy to develop
With tools/frameworks that allow an object oriented system to be exposed as a "web-service" easily and tools that can generate proxies that can be used to talk to these services; it makes it easy to expose a system thats not designed to be distributed, easily exposed for consumption over the wire. I don't mean this in a derogatory way; you can do good SOA with the tools, its the flip side thats unfortunate.
Does it matter?
Jim Siegienski
I agree with the select few here who say REST is not a protocol, nor does it dictate HTTP as a transport. It's a paradigm.
As for the difference between a service and a resource, I think it's valid to differentiate but at the end of the day does it matter? I call a service and get a resource. In many ways I can think of them as the same. REST to me doesn't dictate that it's an extension of the database and therefore restricted in data manipulation as a service would do. I expect a requestee to do what it needs to do to service my requestor. Some of my services are really physical resources (address), some are logical resources (payment). Maybe I'm violating something, but it's working really well to allow variance in my abstractions.
Just my $0.02
Re: Please ignore
Jean-Jacques Dubray
Re: Please ignore
Dilip Krishnan
Re: Please ignore
Jean-Jacques Dubray
Re: Please ignore
Dilip Krishnan
Re: Very good, but...
Boris Lublinsky
Any real world business service that you can possibly think of can be defined as one of the HTTP methods.
There are two issues here. Services in SOA are not necessarily services delivered to end user. The majority of SOA services are the building blocks of the solutions satisfying user's needs. Second is that they can not really be delivered as an HTTP method. They can be delivered using HTTP as a transport and there is a big difference between these two statement.
With all due respect I disagree. In your example, The noun will be "calculate Credit Score" and a customer will be a parameter.
from business perspective, the better service would be: "give me customer's credit score"...The "noun" can be important, but is only part of the giving or getting. That's why probably in your experience too, almost any service starts with get, save or something similar.
The comparison with DMBS is clever, but completely wrong. Similarity in methods says nothing about granularity. Business service can be "give me monthly report" which can based on many systems and databases.First its not mine, its belongs to Nene. Second the comparison is on API not a granularity level. The resource can be as complex as it needs to be.
You are actually admitting that you never haven seen REST based system: "Another question is whether it is possible to build a complete system using true REST". So, based on what did you wrote this article. A lot of theory?Well, I have been an architect for about 15 years, developer before that. I have done quite a few systems implementations. What I am saying is that every REST implementation that I did or have seen always was a mix of True REST with REST Web services, which disqualifies it as a true REST implementation.
In your article, I did not find a single example of a situation and service that cannot be solved with REST.Yes, but it will not be SOA system anymore. That's my point.
Simplicity vs. standards... So, if we implement all those WS* standards we will have great systems? Well, I would rather bet on simple systems which are easily changeable. This is a fundamental difference in the way we see system engineering.The problem is that the absence of standards leads to proprietary implementations, which makes it significantly more complex (more code to write and maintain) and hinders interoperability. As for simplicity - I am all for it. Use only what you need - problem solved
Re: Please ignore
Dan Creswell
I am sorry you feel this way, but lets stick to the facts:
1. I think that one of the reason why our industry is largely under-achieves is because we are not willing to either read or listen. We tend to form our own opinions even before we read or listen to something.
2. For better or worse SOA is based on the functional decomposition which often makes it difficult to accommodate enterprise data www.infoq.com/articles/SOA-enterprise-data. As for the data service, it is typically a data access service, which does not really solve the problem of moving data.
3. An article is not trying to compare functional and data decomposition. It merely states that they are different. I happen to agree that "service design (like all design) is a matter of taste and judgement, not fixed process and checklists to be followed blindly with no thought." I also happen to think that a good service design is still an art, not a science.
4. There is no place in the article that talks about how design should be done. What do I know, I am just an architect.
If you agree service design is a matter of taste why are you prepared to be bound by SOA being defined as a functional decomposition? Presumably some element of the industry has decided this is the rule? There are a number of examples of SOA's that aren't decomposed by pure function and with good reason (see my original reference to Jim Gray's analysis).
More importantly, if one ignores this rule of functional decomposition being the driving design approach for an SOA, services start to look a lot more resource oriented and can thus be made RESTful.
"There is no place in the article that talks about how design should be done."
Except that you insist that SOA is all about functional decomposition, which is an assertion about how design should be done i.e. you cannot focus on a data-based approach.
"As for the data service, it is typically a data access service, which does not really solve the problem of moving data"
Typically is not a rule though, so one can design a data service that isn't about purely data access and thus does address the moving data problem.
Re: Please ignore
Boris Lublinsky
More importantly, if one ignores this rule of functional decomposition being the driving design approach for an SOA, services start to look a lot more resource oriented and can thus be made RESTful.
That is exactly my point. If you do this, then you do not have SOA. You have REST. SOA is an architectural style, which defines services as a result of functional decomposition.
so one can design a data service that isn't about purely data access and thus does address the moving data problem
Yes, but this is yet another architectural style, which I am using a lot lately with my Hadoop - based implementations.
Once again - my point is that there are many architectural styles in a true architect toolbox and he has to pick the one or combination of several to do his job. The is the right thing to do. He also has to know exactly which style and why he is using for solving specific problem.
SOA can be Data Oriented as Well
Faisal Waris
All services are organized around major entities (such as Customer, Part, Vehicle, etc). This organization is apparent in the WSDL target namespaces (e.g. urn:customer/...; urn:part/..; etc). All new services are organized this way.
There is a kind of a macro-level OO'ness present here. Service operations are considered as operations around a major entity. An entity can have multiple services allowing us to grow an entity over time.
Is REST the future of SOA? Yes!
Cesare Pautasso
Re: SOA can be Data Oriented as Well
Dilip Krishnan
Re: Rubbish
Jason Botwick
Fielding, 2006:
Jason Botwick
Re: SOA can be Data Oriented as Well
Faisal Waris
The goal is to build and an 'enterprise api' over time. Realize that enterprise data models are very complex (much more so than say facebook or ebay public data models). So the api we are building is virtual as it is composed of different services implemented by different groups, over time.
The key is that we are using major entities (as opposed to functions) as the organizing principle for services. The api is discoverable via the registry (and we have prototyped ways of making it browsable by entity in a nice Silverlight front-end).
Business processes 'stitch' services together. Most of these are implemented as applications but many are implemented with BPMS tools. We heavliy use intermediaries such as xml gateways and have started to use an ESB for async and pub-sub.
I don't want to give the impression that we are already there and successful. This is a journey that we have been on for over a year now. All I can say is that we are progressing well and have not found any major disconnects, yet.
This is very real - not fluffy pontification.
Re: Fielding, 2006:
Faisal Waris
Re: Please ignore
Jan Algermissen
Besides the mis-information about REST, I think the article mis-represents the very issues of the problem domain. Maybe the problem is more one of the writing than of your knowledge of the problem space? Could it be that the points your are trying to make simply don't come across?
If WS-* is the RPC of the Internet, REST is the DBMS of the internet…
Leo Gan
"If WS-* is the RPC of the Internet, REST is the DBMS of the internet…" - I would rather say:
REST is like a method to manipulate data with set-operations (Insert, Delete, Update, Select), WS-* is like a way to manipulate data with stored procedures. sp-s do create an additional abstraction layer for the same reasons and with the same results as WS-* do.
Re: SOA can be Data Oriented as Well
Boris Lublinsky
Of course this is real, but...
What you are describing is really two level functional decomposition. What you are calling entities, I can call functional areas. The approach that you are describing is actually very close to IBM's SOA definition model. The fact that you are using BPM for orchestrating services, means that your services represent actions - that is what process consumes. I think we are talking about same things but are using different terminology,
Re: Please ignore
Boris Lublinsky
Of course I am not the best writer, at the end of the day my PhD was in EE not English literature, and besides, English is my second language. But may be, just may be not all the blame should be addressed to me. May be some of the problem is the way people are reading this article. Quite a few comments that I see here puzzle me. The article is NOT about benefits or shortcoming of either REST or SOA (sorry, both of them have shortcoming), its about the fact that they are different styles.
Now, what exactly did I mis-inform and mis-represent? If I am blamed for something I prefer this being more specific.
Missed the architectural point
George Ludgate
Re: SOA can be Data Oriented as Well
Faisal Waris
Perhaps you are right but I would like to elaborate further.
Take the entity Part - which appears deceptively simple. However from an enterprise perspective, Part is HUGE. There are so many aspects for Part it's hard to enumerate all, but here is an attempt:
1. Engineering: Part has engineering and design aspects (concept; prototyping; testing; final specification; engineering changes over time; etc.). Parts range from simple (nuts and bolts) to complex sub-assemblies.
2. Purchasing – Managing the sourcing of parts from one or more suppliers (supply chain)
3. Manufacturing – parts eventually are included in an end product (such as engine or transmission) and have to be tracked as part the bill-of-material of the final product. Also part of the supply chain.
4. After Sales – Warranty repairs; 'spare parts'; logistics and retail distribution; supply chain
5. Finance – cost analysis of parts and bill-of-materials; other types of analyses
The above is what we would call functional areas. The entity Part cuts across them all. Each functional area itself is huge in terms of Part data and business processes. The only data element common across all functional areas is the part-number.
While the functional areas appear to be silos they are in fact all linked together with complex interdependencies. For example, warranty repairs may trigger engineering design changes with cascading consequences. There are also interdependencies between different entities such as Part and Vehicle.
Systems in the functional areas were pretty much silos before SOA. With SOA we can link the functional areas better and reduce (but not eliminate) data movement. The approach we have taken gives us a consistent way of building a façade to enterprise data and processing. Operations around Part can be logically grouped together in a coherent view, even when each service/operation is managed by a different functional area.
There is so much metadata that it would be impossible to deal with the data without some kind of metadata description language that is machine readable. Operations are not all CRUD type. There are set operations and other business process specific operations.
Also it is impossible to create a single model for any major entity as that model keeps changing all the time and no one person knows it all. We deal with piecemeal models of each entity in relation to service calls – with contracts and versioning.
The challenges are enormous and I don't want to minimize that. We have our feeble attempt to address these challenges, which seems to be working thus far. Whether we are ultimately successful, we don't know.
Re: SOA can be Data Oriented as Well
Paul Korney
[Service | Resource] Oriented Architecture representing the same level of abstraction? And are they mutually exclusive? Or does 'Service' simply represent a business offering or solution, while 'Resource' represents a business concept or entity? And so, can a Service be a Resource, or vice versa?
Of all the terms here, REST seems the most clearly defined based as it is on other, already well defined Internet characteristics through Fielding's thesis. However, it's level of descriptive abstraction seems to me completely orthogonal to the so-called architectural styles being argued above. It seems to me more like a design technique than an architecture, though it is itself is an abstraction of certain Internet architecture properties.
The use of the word 'protocol' also requires better care in usage: It does not always or only refer to networking and communications. A protocol just describes the discrete steps of some process with well defined results. Consequently, we may use the term at practically any level of descriptive abstraction.
I still think the article is quite useful and well written in that it brings up several points well worth further discussion. And it does take care to try and carefully define terms. Readers just need to be a bit less orthodox and parochial in their reading of it.
Re: SOA can be Data Oriented as Well
Faisal Waris
I will refrain from using the term Entity Orientation :).
In our model, a service is just a container for operations on an entity. New operations can be added to services at any time because that does not break existing contracts.
Entities are virtual but their operations are concrete and may be spread across multiple services (at different hosts). Registry and metadata bring it all together.
PS. The browser equivalent in WS* world is the tool SoapUI which is useful for manually exploring and interacting with services.
Re: Please ignore
John Schlesinger
1. REST is not built on the HTTP verbs. REST is a style and those verbs are part of the HTTP realisation of that style. Rheims Cathedral is built in a gothic style, but that does not mean you have to look like Rheims to be gothic. You can be RESTful without using the HTTP verbs.
2. The descriptions of PUT and POST are confused. A PUT is idempotent, but creating a new resource is not idempotent.
3. REST is not about entity beans. Just because the HTTP verbs can be interpreted as CRUD (Create, Read, Update and Delete) does not mean that REST is just for CRUD. It is for managing resources. Where a resource is directly mapped to an Entity, it will look like an entity. Where the resource is not directly mapped to an entity it will not. For example, you can use a Transaction resource to manage a transaction using REST.
4. The other defining characteristics of REST are ignored. Namely: multiple representations; every resource is a URL; Hypertext as the engine of application state. These are far more important to understand than the universal interface.
5. The context of REST is ignored. This is explicitly a style for mediating between user agents and resource managers. There is no such context for Web services.
6. The reason why RESTafarians believe that WSDL is not needed for RESTful services is completely misunderstood. It is precisely because it is the User Agent's job to represent a resource, but the person's job to understand it, that WSDL is not needed at run time. REST does not need expensive dynamic binding like SOAP.
For these reasons, and a few more, I concur with Mark Baker's assessment of the article.
Re: Please ignore
Boris Lublinsky
1. Technically you can, practically I've never seen it.
2. Sorry, my and inspire.jrc.ec.europa.eu/reports/ImplementingRu... mistake, which does not really change anything in the content.
3 Comparison to Entity beans has nothing to do with CRUD. The difference between Entity beans and Session beans(I know it was long time) is that an instance of Entity bean is associated with the explicit resource (database record), while Session bean is resource independent and resource is passed to it as a parameter.
4. Yes, I did not write about these additional features of REST, because they are not relevant to the topic. I do happen to know about them, but this was REST usage for SOA article, not REST evaluation.
5 I personally think that JAX-WS model with dynamic WSDL processing is a mistake (i prefer JAX-RS model with the static generation). For me WSDL is important for formal definition and client code generation. I still concur that the absence of WSDL in REST is a bad thing, leading to creation of client frameworks in packages like RESTEasy and Metro, which are using annotated Java interface in place of WSDL
Re: SOA can be Data Oriented as Well
Boris Lublinsky
I might be wrong, but it feels like part belongs more to the canonical data model than to service definition.
Also, when you are saying things keep changing, which is normal. The question is whether base entities are changing fast (should not happen) or the processes orchestrating these services are changing (expected).
Re: SOA can be Data Oriented as Well
Faisal Waris
In the meanwhile we can't stop groups building services to support the process they are implementing.
Changes in business process and new processes often do require new data to be kept and managed which many times is associated major entities.
I think the right 'solution' to the modeling problem is to move to semantic models (owl,rdf)that can be grown organically over time. However that is a major shift from where enterprises are today. Perhaps the adoption of NoSql/graph stores will slowly move us in this direction.
Re: SOA can be Data Oriented as Well
Boris Lublinsky
I deal with NoSQL implementation on a daily bases and it is harder to un teach people old habits than teach them the new ones
Unprecise assumptions
Jakob Strauch
It seems, that your are mixing the semantics of "simple" and "easy". The uniform interface is simplistic, which means it is "artles" or "plain".
A priori knowledge
You have to know more, than a single bookmark URI. There must be an agreement on media types and relation semantics. Furthermore, no one hinders you to use a schema to describe you representations.
Did you ever try to consume SOAP service with mobile clients? Microsoft did a pretty good job there on their mobile platforms. But all others have really bad support for SOAP. Why is that? I think due to the restricted resources on the phone.
For AJAX clients its very easy to consume REST "Services" due to JSON support.
REST based on HTTP
Really? from Fieldings Diss.:
"REST does not restrict communication to a particular protocol, but it does constrain the interface between components, and hence the scope of interaction and implementation assumptions that might otherwise be made between components. For example, the Web's primary transfer protocol is HTTP, but the architecture also includes seamless access to resources that originate on pre-existing network servers, including FTP , Gopher , and WAIS ."
Nature of Resources
Resources are not only "things". An activity/task/process can be a resource, too (see pautasso's work). Fielding: "Any information that can be named can be a resource: a document or image, a temporal service (e.g. "today's weather in Los Angeles"), a collection of other resources, a non-virtual object (e.g. a person), and so on. In other words, any concept that might be the target of an author's hypertext reference must fit within the definition of a resource"
I love some stuff in SOAP world (e.g. proxy generation). But i think, REST has some really "cool stuff": The biggest power of HTTP/REST is the linking of things. Through the simplistic nature of the interface, everything is linkable - even task/activities/processes.
Service vs. Resource
Jakob Strauch
The functional complexity is split up on multiple resources. Some of them may be activity resources. I dont see, why a SOA can´t be realized with the REST approach... The functional decomposition is just different in comparision to the SOAP/RPC style. Here, a service is one endpoint with multiple methods.
no helping
liu swan
something like compare white(color) to animal. what's difference between animal and white?
restful is about how to design one service via resources ,
soa is about how to use service or how to organize and admin many services as a whole enterprise business support procedure,
URL to Dr. Roy Thomas Fielding's dissertation on REST
Abhay Bakshi
"REST is the brainchild of Roy T. Fielding, cofounder of the Apache HTTP server project and coauthor of the HTTP and URI standards.
In 2000, he wrote a doctoral dissertation for the University of California at Irvine called 'Architectural Styles and the Design of Network-based Software Architectures', wherein he defined REST."
Re: Excellent!!!
Abhay Bakshi
Well defined status codes
Jossey Jacob


text:
|Kyle Busch Wins ISM Connect 300
|Modified Season Sweep for Santos
|Bell Wins UNOH 175 Truck Series Race
|Mile Kyle: Busch Takes Pole for ISM Connect 300
|Short Track Extravaganza Set for Sept. 2018
|New England Themed Going Away Gift for Junior
Ford Out as Hamlin's Crew Chief
Mike Ford, the crew chief who led Denny Hamlin to the brink of a Sprint Cup championship one year ago, is no longer in that position.
Joe Gibbs Racing announced Tuesday that Ford has been released as Hamlin's crew chief, capping a fall from a near championship-winning effort in 2010 to a 2011 campaign where the No. 11 team needed a wild card entry just to make the Chase. Ford and Hamlin had been a team since the driver first moved up to NASCAR's Cup Series on a limited basis in 2005, and together they won 17 races and qualified for the postseason every year since 2006.
The Associated Press was first to report the story. "I'm kind of relieved," Ford told the wire service. "It had been dragging on for so long, I'm actually relieved there's finally a resolution."
"Everyone at Joe Gibbs Racing appreciates what Mike has done for our organization over the past six seasons as crew chief with our No. 11 team," said team owner Joe Gibbs in a statement. "We've decided it was best to make a change with the team now to allow Mike the opportunity to pursue other opportunities."
While there was no official word as to who would be Ford's successor, all indications pointed toward JGR reaching out to Darian Grubb -- the crew chief who was recently fired from Tony Stewart's No. 14 team, despite winning the Sprint Cup title. Grubb does have a standing offer from Hendrick Motorsports, where he worked prior to joining Stewart-Haas Racing, although that is for an engineering position and not a crew chief's job.
In their six years together, Hamlin and Ford had a successful, but sometimes turbulent, coexistence. When the wins came, they did so in bunches, as evidenced by the 12 races they won together in the 2009 and '10 seasons. But the No. 11 team was also often plagued by mechanical issues and pit stop problems, and lost the 2010 championship in part because it didn't save fuel in that season's penultimate event at Phoenix. Rather than burying the competition, that misstep allowed Jimmie Johnson to pull within 15 points and overtake Hamlin for his fifth title the next week.
Ford has worked as a crew chief on NASCAR's premier circuit for 12 seasons, dating back to the 2000 campaign with Bill Elliott. He has also worked with past series champions Dale Jarrett and Terry Labonte, as well as former Gibbs drivers Jason Leffler and J.J. Yeley. Ford righted the Gibbs No. 11 team after a tumultuous beginning with Leffler, bringing stability to the program and eventually finding success with Hamlin. Ford has won 21 total races during his dozen years as a crew chief on the Cup Series.


text:
How to Have Fun With Your Club Penguin Babies/Toddlers?
Do your Club Penguin babies always run away? This guide will teach you to have fun.
How to Hold a Little Miss Club Penguin Contest in Club Penguin?
Holding a "Little Miss Club Penguin" contest can be fun for you and your contestants. Here's how to hold a great contest.
How to Win a Little Miss Club Penguin Contest on Club Penguin?
Have you noticed people advertising for Little Miss Club Penguin contests in the pet shop? This how to guide will explain the easy ways of winning.
How to Make Club Penguin Idol on Club Penguin?
Want to make a TV show on club penguin? Well now is the chance to. Make penguin idol.
How to Explore Club Penguin (Club Penguin Babies)?
You sit in the pet shop. No matter how cute you act,nobody will come over and look at you? But now,this article will teach you how to explore!


text:
ATLANTA (AP) — The Supreme Court of Georgia has upheld the murder conviction and life sentence of a Georgia man accused of slaying his daughter in a so-called honor killing.
Chaudry Rashid was accused of strangling his 25-year-old daughter because she planned to divorce her husband from an arranged marriage. A jury convicted Rashid in May 2011 on murder and assault charges and he was sentenced to life in prison. He appealed his convictions and sentence to the Georgia Supreme Court, saying the lower court committed several errors.
His lawyers argued jurors were mistakenly allowed to see the videotaped conversation, which took place in a police interrogation room and was recorded by a hidden camera.
The state argued other evidence proved beyond a reasonable doubt that Rashid killed his daughter, and the video merely confirmed it. The state also argued that law enforcement never gave the family the impression that the conversation would be private.
In an opinion published Tuesday, Justice P. Harris Hines wrote that contrary "to Rashid's contention, the evidence was sufficient to authorize a rational trier of fact to find him guilty beyond a reasonable doubt of the malice murder of his daughter." The justices also said it was unreasonable for Rashid to expect privacy in a police interview room.
When Rashid moved to the United States from Pakistan after his wife died, he left his four children with his brother. Once he married a U.S. citizen, Rashid had his children join him. In 2002, his daughter Sandeela Kanwal agreed to an arranged marriage with her cousin, the son of the uncle who had raised her in Pakistan, so that he could also move to the U.S.
Because of delays in the immigration process, her husband didn't arrive in Atlanta until 2008 and then left almost immediately for Chicago. The 25-year-old felt she had fulfilled her duty to her family and contacted a divorce lawyer in July 2008. A friend testified that Kanwal feared her family before and after she secretly filed for divorce.
Police who responded to a call at the family's home found Rashid distraught, sitting in the driveway smoking a cigarette. Kanwal was dead on her bedroom floor in her Walmart uniform, dark marks visible on her neck. Remnants of a burned cord were found in the garage.
Following an interview at the police department, Rashid asked to speak with his family. He spoke in Punjabi and Urdu and talked about his daughter's death. During the conversation he said: "I put the rope around her neck and squeezed her."
"She disgraced our family."
(© Copyright 2013 The Associated Press. All Rights Reserved. This material may not be published, broadcast, rewritten or redistributed.)


text:
Customer Reviews
All reviews are from people who have redeemed deals with this merchant.
What You'll Get
Choose from Six Options
- 12-month access to an online basic Excel course ($199 value)
- 12-month access to an online advanced Excel course ($199 value)
- 12-month access to an online basic Word course ($99 value)
- 12-month access to an online advanced Word course ($199 value)
- 12-month access to an online PowerPoint course ($299 value)
- Microsoft Office bundle with all of the above courses ($995 value)
The Fine Print
Promotional value expires 180 days after purchase. Amount paid never expires. Valid only for option purchased. Online only. Must register by expiration date on voucher; customers have 12 months from redemption to access material. Merchant is solely responsible to purchasers for the care and quality of the advertised goods and services.
About GoSkills
Career advancement is often about having the right skills, and GoSkills.com helps you acquire just the right ones based on your personal goals. The site's courses cover skills used in almost every business, including Excel spreadsheets, PowerPoint presentations, effective business writing and project management, relaying the essentials of each topic through an in-depth, personalized curriculum.
In each course, a series of learning modules cycles through exercises, quizzes, and high-definition video tutorials that last no more than six minutes. Along the way, GoSkills maps your strengths and weaknesses to cater lessons to where you need instruction most. You can take a skills assessment before, during, and after the course to monitor your progress from start to finish. Upon completion, you receive an accredited certificate to include with your CV or résumé (accredited by CPD UK).


text:
SBA Loans and Grants Search API - How To
The Small Business Administration (SBA) strives to act as an engine of opportunity and economic growth in America by providing a variety of programs and support services for both current and prospective small business owners. The Loans and Grants Search API allows developers to connect to SBA.gov's categorized collection of links to federal, state, and local financial assistance programs that aid small businesses in starting or expanding their operations. The search API lets users find loans and grants by a variety of characteristics such as state, industry, or specialty. This RESTful API is free to use, and returns data as either XML or JSON.


text:
Billing Informations
All Databases We Support
Domain Name Tutorials
New Control Panel System
Email Service Tutorials
Frequently Asked Questions
General Hosting Knowledges
Instant Website
Basic Knowledge about Networking
Old Control Panel System
Secure Socket Layer Tutorial
Basic Knowledges about Website
Website Security Knowledges
Most Popular Articles
1. Install WHMCS to your website, you can read and follow the instruction here....What is the signup process for your hosting package ?
There are two scenario for signing up hosting package with us1. You already have your own domain...General WebHostForASP.NET Mail Server Information
WebHostForASP.NET provides all customers with access to send and receive internet email using...3. DotNetPanel Billing System Setup
1. Payment Settings a. Credit Card Payment Method When you want to enable credit card...What steps do I need to take to get my domain transferred from another hosting company?
To transfer the domain from another hosting company to us is easy. Below is the steps on how to...