1 / 7

OMA-TP-2008-<XYZ> Technical Plenary Presentation <Group> <City, Country>

OMA-TP-2008-<XYZ> Technical Plenary Presentation <Group> <City, Country>. Submitted To: OMA Technical Plenary Date: <date> Availability: Public OMA Confidential Contact: <Chair> Source: <WG/Committee name>. X.

neve-fry
Download Presentation

OMA-TP-2008-<XYZ> Technical Plenary Presentation <Group> <City, Country>

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OMA-TP-2008-<XYZ> Technical Plenary Presentation<Group><City, Country> Submitted To: OMA Technical Plenary Date: <date> Availability: Public OMA Confidential Contact: <Chair> Source: <WG/Committee name> X USE OF THIS DOCUMENT BY NON-OMA MEMBERS IS SUBJECT TO ALL OF THE TERMS AND CONDITIONS OF THE USE AGREEMENT (located at http://www.openmobilealliance.org/UseAgreement.html) AND IF YOU HAVE NOT AGREED TO THE TERMS OF THE USE AGREEMENT, YOU DO NOT HAVE THE RIGHT TO USE, COPY OR DISTRIBUTE THIS DOCUMENT. THIS DOCUMENT IS PROVIDED ON AN "AS IS" "AS AVAILABLE" AND "WITH ALL FAULTS" BASIS. Intellectual Property Rights Members and their Affiliates (collectively, "Members") agree to use their reasonable endeavours to inform timely the Open Mobile Alliance of Essential IPR as they become aware that the Essential IPR is related to the prepared or published Specification. This obligation does not imply an obligation on Members to conduct IPR searches. This duty is contained in the Open Mobile Alliance application form to which each Member's attention is drawn. Members shall submit to the General Manager of Operations of OMA the IPR Statement and the IPR Licensing Declaration. These forms are available from OMA or online at the OMA website at www.openmobilealliance.org.

  2. Provide high level, but informative, information for each Release. Do not report on Releases in maintenance, unless important changes made Do not make uninformative general statements (e.g. “RD progressing well”) ► WI/Release update:<e.g. PoC Enhancement (2.0)> i/ii ▲ ▼ • WISPR last updated: <e.g. 2006/04/08> • Overall progress status compared to previous report • <e.g. agreement on role of application server> • <e.g. all remaining major issues in AD now addressed> • Problem report / workaround / corrective actions • <e.g. communication / liaison / technical problems for information> • <e.g. User Plane TS: long discussions about how to reconcile presence information with application server rules. Could delay start of Consistency Review. Group urged to come to an agreement soon> • Additional information • <e.g. issues not foreseen when the WID was approved by TP> • <e.g. dependence on other organizations>

  3. Click on the embedded Excel spreadsheet object. Follow Instructions in the spreadsheet to update the chart. Use only 1 chart per slide Do not provide charts for Releases in maintenance WI/Release update:<e.g. PoC Enhancement (2.0)> ii/ii

  4. ► Matters not covered by Work Items ▲ ▼ • <e.g. Best Practices> • <e.g. Specification Reviews> • <e.g. Support to other WGs>

  5. Documents nearing TP approval • <e.g. ABCD Requirements Document> • TP presentation: <e.g. OMA-TP-2008-0789-INP_ABCD_Presentation> • <e.g. XYZ Enabler Release> • TP presentation: <e.g. OMA-TP-2008-0987-INP_XYZ_Presentation>

  6. Items for TP approval • Request to create Liaison Relationship • <e.g. XYZ Forum> • Work Items • <e.g. Data synchronisation privacy> • Other • <e.g. proposal on Optionality handling>

  7. Other issues brought to TP’s attention • <do not repeat any items from previous slides> • <e.g. scope of XYZ WI and overlap with W3C> • <e.g. update Work Programme to identify other fora’s timeframes> • <e.g. request for creation of new mailing list>

More Related