Sponsored Content
Special Forums News, Links, Events and Announcements UNIX and Linux RSS News Oracle and Google Stipulate to a Proposed Protective Order Post 302481662 by Linux Bot on Saturday 18th of December 2010 10:45:05 PM
Old 12-18-2010
Oracle and Google Stipulate to a Proposed Protective Order

After the presiding judge, the Hon. William Alsup, ruled the other day on the parties' remaining disputes over proposed terms for a protective order in the Oracle v. Google litigation, Oracle and Google then got together and have come up with their own solution, a proposed stipulated protective order they are submitting to the court for approval. There is also a scheduling agreement on such things as what format to provide discovery materials in.
The judge had said if either side didn't like his decision, they could file motions, but instead they have resolved the issues that they told the judge they couldn't resolve before. His order gave them a big nudge, and they have now come up with something they can each live with. I think he figured if he gave them a map of his preferences, they could get to their final destination quickly without him having to decide every last detail. And that may explain why he didn't provide any substitute language on a prosecution bar. He was, I gather, trying to prod the parties into settling their remaining issues themselves. And it looks like it worked. They have now done so.
Google won the issue of in-house counsel, but it had to come up with new prosecution bar language. So that is the main change. As for other highly confidential materials, there is a process for allowing up to five in-house counsel to view it, but never source code. And Sun lawyers, now Oracle America lawyers, are defined as house counsel, hence barred from viewing code.
Keep in mind that this is just about who can see what in discovery. It doesn't necessarily indicate what will or won't be sealed in filings, as there is a separate rule about that, but it does mean we won't be seeing properly designated confidential materials. It doesn't tell us what will be admissible as evidence either. That comes later. This is just the first real step in the discovery process, which is the biggest part but still only one part of the whole litigation process.

More...
 

We Also Found This Discussion For You

1. News, Links, Events and Announcements

Wine project and Oracle google trail over aoi copyright

Wine is a project that allow user to run windows apps on linux os. It does that by reimplementation of the windows api. However Oracle claim that API are copyrightable able and sue google for reimplementation of Java api. If they win, then wine project will be in the same problem. ... (0 Replies)
Discussion started by: programAngel
0 Replies
URI::URL(3)						User Contributed Perl Documentation					       URI::URL(3)

NAME
URI::URL - Uniform Resource Locators SYNOPSIS
$u1 = URI::URL->new($str, $base); $u2 = $u1->abs; DESCRIPTION
This module is provided for backwards compatibility with modules that depend on the interface provided by the "URI::URL" class that used to be distributed with the libwww-perl library. The following differences exist compared to the "URI" class interface: o The URI::URL module exports the url() function as an alternate constructor interface. o The constructor takes an optional $base argument. The "URI::URL" class is a subclass of "URI::WithBase". o The URI::URL->newlocal class method is the same as URI::file->new_abs. o URI::URL::strict(1) o $url->print_on method o $url->crack method o $url->full_path: same as ($uri->abs_path || "/") o $url->netloc: same as $uri->authority o $url->epath, $url->equery: same as $uri->path, $uri->query o $url->path and $url->query pass unescaped strings. o $url->path_components: same as $uri->path_segments (if you don't consider path segment parameters) o $url->params and $url->eparams methods o $url->base method. See URI::WithBase. o $url->abs and $url->rel have an optional $base argument. See URI::WithBase. o $url->frag: same as $uri->fragment o $url->keywords: same as $uri->query_keywords o $url->localpath and friends map to $uri->file. o $url->address and $url->encoded822addr: same as $uri->to for mailto URI o $url->groupart method for news URI o $url->article: same as $uri->message SEE ALSO
URI, URI::WithBase COPYRIGHT
Copyright 1998-2000 Gisle Aas. perl v5.12.1 2008-04-04 URI::URL(3)
All times are GMT -4. The time now is 11:20 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy