throbber
John Hoctor [jhoctor@navic.tv]
`John Hoctor <Thoctor@navic.tv> [jhoctor@navic.tv]
`6/30/2004 11:42:42 AM
`'Nicole Nestel [nicole@nicolenestel.com]
`Len Goldberg [Igoldberg@imageteq.com]; Milton Diaz [mdiaz@bbitv.com]
`RE: Namespace doc
`
`Message
`
`From:
`on behalf of
`Sent:
`To:
`CC:
`Subject:
`
`Nicole,
`
`Here's some feedback on the namespace definition and accompanying diagram.
`
`1.) On the second page of the document you call for a conditional action that controls the display of the
`"Prey" and "Next" buttons. The display of a button can not be determined through the use of a
`conditional action.
`
`2.) On the third page of the document, the comment marked #1 is a bit confusing. If there is an
`i nteractive method call "GetAdDetails" defined, then you would not need to use the generic DoGet.
`
`In order for the Prey and Next buttons to work as I think you intend, you would need to have two
`additional interactive method calls, one "GetAdDetailsPrev" and another "GetAdDetailsNext" The servlet
`would also need to maintain the corresponding AdList in the session so that it could determine the
`appropriate AdDetails to return for each of these method calls.
`
`3.) In the word document you use AdID and CategoryID, but I do not see these defined in
`community_namespace.xml
`
`4.) In community_namespace.xml, the Server_IDs that you have chosen get into three digits rather quickly.
`If possible, you should change the ranges for your IDs in order to keep these under three digits. It's
`just wasting space on the wire, since these IDs are passed back and forth between the settop and the
`servlet
`
`5.) In community_namespace.xml, the Usage value is set to "1" throughout. Usage should only be set to
`"1" if your servlet needs to get this information returned to it, otherwise it should be set to "0" This
`also helps keep the amount of extraneous data off of the wire.
`
`6.) On Page 3 of community_namespace.xml, the SubCategoriesList Index has Type set to "3" This indicates
`an enumeration. There is no enumeration included, so this appears to be an error. This comment also
`hold for AdList Index, also on page 3 of community_namespace.xml.
`
`7.) On page 4 of community_namespace.xml, you include support for dynamic images. If you want to use
`this namespace prior to the platform supporting dynamic images, you may want to take this out.
`
`Regards,
`J ohn
`
` Original Message
`From: Nicole Nestel [mailto:nicole@nicolenestel.com]
`Sent: Wednesday, June 23, 2004 5:09 PM
`To: John Hoctor
`Cc: Len Goldberg; Milton Diaz
`Subject: FW: Namespace doc
`
`Hi John,
`
`Attached you will find a few documents for the upcoming "Classified' applicaiton. The namespace and the
`corresponding description of screens and methods.
`
`Can you please have JP review these documents to ensure that they will work well with the Navic
`application.
`
`Thanks
`Nicole
` Original Message
`From: Len Goldberg [mailto:lgoldberg@imageteq.com]
`Sent: Wednesday, June 23, 2004 10:29 AM
`To: Nicole Nestel
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`BBITV050335
`
`BBiTV EX2159
`DISH v. BBiTV
`IPR2020-01267
`
`PROTECTIVE ORDER MATERIAL
`
`

`

`Cc: Boris Goldberg; Joel Benveniste
`Subject: Re: initial -cut of Namespace doc
`
`Hi Nicole,
`
`Please see the updated namespace doc. It has been updated with the application ID of 58 per your email,
`the use of category-specific method names for GetSubcategories (although there is still one generic
`GetSubcategories method), one fewer enumeration. The number of applications screens (per the earlier
`email) should still be the same.
`
`Please send along any feedback from you and/or Navic.
`
`Thank you!
`Len
`
`HIGHLY CONFIDENTIAL - ATTORNEYS' EYES ONLY
`
`BBITV050336
`
`PROTECTIVE ORDER MATERIAL
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket