Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Sciences Library Library- QH501.C376 2016

Location: Electronic Resource- 

Dynamic company in the broadcast industry is looking for a PR and Marketing Writer (company located in in Airport City)

To create and maintain content to support companies overall sales and marketing plan, and to increase industry awareness and company brand in order to support and marketing efforts.

Main Accountabilities

• Work with marketing team on preparing and supporting PR and marketing strategy
• Create press releases, case studies, marketing white papers, company briefs and FAQs, and contributed articles/advertorials in support of marketing strategy
• Identify and organize speaking engagements and assist in the preparation of the needed presentations
• Organize and support interviews of companies executives with the print and online media
• Interview clients, managers, engineers, sales staff and others to collect information
• Prepare scripts for videos and similar promotional material
• Prepare content for customer e-newsletter
• Prepare content for internal sales and marketing training and sales and marketing internal portal
• Support the company as needs arise for proofing, writing and other ad hoc projects
• Support presence as exhibitors at trade industry exhibitions by preparing messaging, arranging press interviews, etc.
• To increase media and analyst awareness as measured by articles written about the company or within which they are discussed

• Minimum 3-5 years experience as a marketing writer and with direct international PR responsibilities for a high-tech company preferably in a related field
• Strong written and verbal communication skills in English (mother tongue) with the specific ability to understand and convey technical information in a non-technical manner and to prepare marketing material
• An understanding of the satellite and broadcast industry a definite plus

If you are an "out of the box" creative writer – this position is for you!

Company in Ra'anana seeks a dynamic and quirky creative writer (2 yrs experience)

• Must be sharp, smart and hungry to succeed
• English on a high level (does not have to be mother tongue)
• Previous experience as copywriter in advertising agency – advantage
• Marketing background – advantage

It's not just the pros who want control. Over the weekend the NCAA ejected a Louisville Courier-Journal reporter from a college baseball championship for live-blogging the game. Brian Bennet reports that he had been posting updates throughout the game on his Courier-Journal blog, until, at the bottom of the fifth inning, "an NCAA representative came to my seat on press row and asked for my credential and asked me to leave. I complied."

Apparently, according to a memo NCAA circulated, the college athletic association believes that live-blogging interferes with its revenue streams from broadcast licenses:

The College World Series Media Coordination staff along with the NCAA Broadcasting group needs to remind all media coordinators that any statistical or other live representation of the Super Regional games falls under the exclusive broadcasting and Internet rights granted to the NCAA's official rights holders and therefore is not allowed by any other entity. Since blogs are considered a live representation of the game, any blog that has action photos or game reports, including play-by-play, scores or any in-game updates, is specifically prohibited. In essence, no blog entries are permitted between the first pitch and the final out of each game.

Now there are legal and policy questions here: First off, this wasn't a copyright or misappropriation claim. If the reporter had watched or listened to a broadcast and blogged details from there, the NCAA would have no claim against him (see NBA v. Motorola, where the basketball association lost just such a claim). It can't claim ownership of the facts, even if it currently makes money from selling privileged access to the facts.

Instead, the NCAA was clamping down on the data through a claimed right to control physical access to the game, at least to the press box. Was the NCAA within its legal rights to revoke a press credential? Probably. The NCAA has no obligation to issue press credentials, and apart from anti-discrimination law, can condition them on whatever arbitrary terms it likes. But David Price points out another twist: The University of Louisville, where the game was played, is a public institution, subject to First Amendment limitations on the speech-limiting rules it can impose. Can it ban speech or allow others to do so on its space based on claimed disruption to a business deal? Does it depend whether a baseball stadium is a "public forum"? (Under current law, it's probably not.)

Finally, there's the policy. Even if banning bloggers is legally permissible, it;s silly. Silly of the NCAA to think it can keep up this kind of control, silly of licensees to see blogs as a substitute to what they're licensing, and silly of schools to endorse and accept such policies for their student athletes' games. Exclusivity of facts is unlikely to last long in practice, as the Courier-Journal reports: "The Oregonian newspaper in Portland decided to work around the rules by blogging Oregon State's game against Michigan on Sunday off a radio broadcast in its newsroom, said its executive editor, Peter Bhatia. He said the newspaper heard no objections from the NCAA and planned to do the same yesterday."

"AT&T Inc. has joined Hollywood studios and recording companies in trying to keep pirated films, music and other content off its network — the first major carrier of Internet traffic to do so," the LA Times reports. So customers will pay in added overhead and false positives, while filesharers adapt to evade the filtering (for both infringing and non-infringing traffic). Who wins? The sellers of filtering snake-oil tech, perhaps.

After blogging about ICANN's new gTLD policy or lack thereof, I've had several people ask me why I care so much about ICANN and new top-level domains. Domain names barely matter in a world of search and hyperlinks, I'm told, and new domains would amount to little more than a cash transfer to new registries from those trying to protect their names and brands. While I agree that type-in site-location is less and less relevant, and we haven't yet seen much end-user focused innovation in the use of domain names, I'm not ready to throw in the towel. I think ICANN is still in a position to do affirmative harm to Internet innovation.

You see, I don't concede that we know all the things the Internet will be used for, or all the things that could be done on top of and through its domain name system. I certainly don't claim that I do, and I don't believe that the intelligence gathered in ICANN would make that claim either.

Yet that's what it's doing by bureaucratizing the addition of new domain names: Asserting that no further experiments are possible; that the "show me the code" mode that built the Internet can no longer build enhancements to it. ICANN is unnecessarily ossifying the Internet's DNS at version 1.0, setting in stone a cumbersome model of registries and registrars, a pay-per-database-listing, semantic attachments to character strings, and limited competition for the lot. This structure is fixed in place by the GNSO constituency listing: Those who have interests in the existing setup are unlikely to welcome a new set of competitors bearing disruptions to their established business models. The "PDP" in the headline, ICANN's over-complex "Policy Development Process" (not the early DEC computer), gives too easy a holdout veto.

Meanwhile, we lose the chance to see what else could be done: whether it's making domain names so abundant that every blogger could have a meaningful set on a business card and every school child one for each different face of youthful experimentation, using the DNS hierarchy to store simple data or different kinds of pointers, spawning new services with new naming conventions, or something else entirely.

I don't know if any of these individually will "add value." Historically, however, we leave that question to the market where there's someone willing to give it a shot. Amazingly, after years of delay, there are still plenty of people waiting in ICANN queues to give new gTLDs a try. The collective value in letting them experiment and new services develop is indisputably greater than that constrained by the top-down imaginings of the few on the ICANN board and councils, as by their inability to pronounce .iii.

"How do you get an answer from the web?" the joke goes: "Put your guess into Wikipedia, then wait for the edits." While Wikipedians might prefer you at least source your guess, the joke isn't far from the mark. The lesson of Web 2.0 has been one of user-driven innovation, of launching services in beta and improving them by public experimentation. When your users know more than you or the regulators, the best you can do is often to give them a platform and support their efforts. Plan for the first try to break, and be ready to learn from the experience.

To trust the market, ICANN must be willing to let new TLDs fail. Instead of insisting that every new business have a 100-year plan, we should prepare the businesses and their stakeholders for contingency. Ensuring the "stable and secure operation of the Internet's unique identifier systems" should mean developing predictable responses to failure, not demanding impracticable guarantees of perpetual success. Escrow, clear consumer information, streamlined processes, and flexible responses to the expected unanticipated, can all protect the end-users better than the dubious foresight of ICANN's central regulators. These same regulators, bear in mind, didn't foresee that a five-day add-grace period would swell the ranks of domains with "tasters" gaming the loophole with ad-based parking pages.

At ten years old, we don't think of our mistakes as precedent, but as experience. Kids learn by doing; the ten-year-old ICANN needs to do the same. Instead of believing it can stabilize the Internet against change, ICANN needs to streamline for unpredictability. Expect the unexpected and be able to act quickly in response. Prepare to get some things wrong, at first, and so be ready to acknowledge mistakes and change course.

I anticipate the counter-argument here that I'm focused on the wrong level, that stasis in the core DNS enhances innovative development on top, but I don't think I'm suggesting anything that would destabilize established resources. Verisign is contractually bound to keep .com open for registrations and resolving as it has in the past, even if .foo comes along with a different model. But until Verisign has real competition for .com, stability on its terms thwarts rather than fosters development. I think we can still accommodate change on both levels.

The Internet is too young to be turned into a utility, settled against further innovation. Even for mature layers, ICANN doesn't have the regulatory competence to protect the end-user in the absence of market competition, while preventing change locks out potential competitive models. Instead, we should focus on protecting principles such as interoperability that have already proved their worth, to enhance user-focused innovation at all levels. A thin ICANN should merely coordinate, not regulate.

Location: Main Library- HV6250.4.W65N78 2011

Location: Main Media Collection - Video record 42392 DVD

Location: Main Media Collection - Video record 42302 DVD

Location: Main Media Collection - Video record 42402 BLU

Location: Main Media Collection - Video record 42402 DVD

Location: Main Media Collection - Video record 42297 DVD

Location: Electronic Resource- 

Location: Government Information Storage- HV6793.I8S7 198417-P712SA 2:C929 1976-82

Location: Government Information - J 16.2:P 93/2/953-56

Location: Marvin A Pomerantz Business Library- QA276.4.E423 2016

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource- 

Location: Electronic Resource-