Meeting Structure EBU, Geneva 9am Tuesday 21 February - 3.30pm Wednesday 22 February Rev3 EBU-AMWA FIMS 21-22 February 2012.

Slides:

Advertisements

Similar presentations

Doc.: IEEE /1125r0 Submission September 2010 Marc Emmelmann, Fraunhofer FOKUSSlide 1 How does the (new) Fast Initial Link Set- Up PAR address.

Advertisements

Day anti-virus anti-virus 1 detecting a malicious file malware, detection, hiding, removing.

Achieving Distributed Extensibility and Versioning in XML Dave Orchard W3C Lead BEA Systems.

1. Introduction OASIS Reference Model for Service Oriented Architecture 2. ECF 4.0 Architecture 2.1 Core vs. Profiles 2.2 Major Design Elements 2.3.

Uncovering the TEI and ODD A pedagogical strip-tease Laurent Romary - Max Planck Digital Library.

©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.

CSE9020 / 2004 Wk01 / 1 CSE9020 CASE STUDY Week1 Welcome to unit CSE9020 (and possibly CSE3200) better known as ‘The Case Study’ for Semester 1, 2004 John.

Saturday May 02 PST 4 PM. Saturday May 02 PST 10:00 PM.

AD description template definition Marián Mlynarovič FIIT Lectures 2006.

Chapter 6: Architectural Design

FIMS Repository Interface IBC A Bit of History How did it start? –FIMS members defined the need to standardize repository operations –FIMS business.

DSpace XML UI Project Texas A&M University Digital Initiatives, Research and Technology Scott Phillips, Cody Green, Alexey Maslov, Adam Mikeal, Brian Surratt,

0 Un ited States Environmental Protection Agency Office of Environmental Information Enterprise Architecture Program Enterprise Architecture Working Group.

CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.

Chapter 7: Architecture Design Omar Meqdadi SE 273 Lecture 7 Department of Computer Science and Software Engineering University of Wisconsin-Platteville.

©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 10Slide 1 Chapter 10 Architectural Design.

COMP 523 DIANE POZEFSKY 20 August AGENDA Introductions Logistics Software Engineering Overview Selecting a project Working with a client.

Architectural Design portions ©Ian Sommerville 1995 Establishing the overall structure of a software system.

Action ADAPT / IDM, November 13th, 2008 Dynamic Adaptive Software Components: The MOCAS Approach1.

Report of Methods and Procedures Subcommittee Group Name: Steering Committee Source: Laurent Laporte, Sprint, Meeting Date:

21 August Agenda  Introductions  Logistics  Selecting a project  Working with a client.

Programming Interface for IP-based Networks Steve Weinstein & Masa Suzuki {sbw, C&C Research Labs., NEC USA, Inc. Feb. 13, 1998.

11 SUPPORTING APPLICATIONS IN WINDOWS XP PROFESSIONAL Chapter 9.

Technical Board Monday/Tuesday 30th - 31st July EBU-AMWA FIMS 30 July 2012.

Technical Team WITSML SIG Dubai - November 2008 John Shields / Gary Masters.

KMIP 1.3 Deprecation February 20, Deprecation 5.1 KMIP Deprecation Rule Items in the normative KMIP Specification [KMIP-Spec] document can be marked.

Architectural Design Yonsei University 2 nd Semester, 2014 Sanghyun Park.

FIMS v1.1 Version numbers in schema Richard Cartwright Quantel July 2013.

FIMS Repository Interface Project Update 01/23/2013.

Lecture 14 Maintaining the System and Managing Software Change SFDV Principles of Information Systems.

FIMS Specification Group EBU-AMWA FIMS August 2011.

Supporting New Business Imperatives Creating a Framework for Interoperable Media Services (FIMS)

1 CCSDS Information Architecture Working Group Daniel J. Crichton, Chair NASA/JPL 14 September 2005.

Copyright © 1997 Pangea Systems, Inc. All rights reserved. Pathway Tools Training Course.

Copyright © 2006 Pilothouse Consulting Inc. All rights reserved. Search Overview Search Features: WSS and Office Search Architecture Content Sources and.

Sacramento Area Council of Governments ITS Partnership Meeting February 2, 2005.

Geography Markup Language (GML). What is GML? – Scope  The Geography Markup Language is  a modeling language for geographic information  an encoding.

©Ian Sommerville, Robin Abraham 2004CS 361, Summer 2004 Slide 1 Architectural Design.

TD/MSD REVIEW CHARGE AND AGENDA Clas12 Torus CCM Production Readiness Review –Dec 4, 2013.

Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.

FIMS Specification Group EBU-AMWA FIMS July 2011.

Submission doc.: IEEE ai September 2012 Lei Wang, InterDigital CommunicationsSlide 1 Ad Hoc Discussions of ai Passive Scanning during.

1 Technical & Business Writing (ENG-715) Muhammad Bilal Bashir UIIT, Rawalpindi.

Systems Analysis and Design in a Changing World, Thursday, Feb 15.

EBIZ302 Jupiter Business Process Automation and Web Services David Fong Program Manager.

Open Smart Grid (OpenSG) Technical Committee Plenary October 20, 2009.

Technical Steering Committee La Jolla, January 2003 Paul Kiel, HR-XML.

Draft-melia-mipshop-mobility-services-ps-01.txt. From IETF #66 Discuss MIH PS (as expressed by the WG chair) Need a single PS at WG level (several drafts.

EbXML Semantic Content Management Mark Crawford Logistics Management Institute

Budget Office Communications Financial Area Representatives Meeting February 18 th, 2008.

COT 4600 Operating Systems Fall 2010 Dan C. Marinescu Office: HEC 439 B Office hours: Tu-Th 3:30-4:30 PM.

Impact Analysis to Refactoring on the Current document Sony Corporation Toshiaki Kojima Mizuki Kanada.

1 © 2003, Cisco Systems, Inc. All rights reserved. DMTF and Cisco Profile overview/comparison August 17, 2005.

Chapter3:Software Processes

WP3: D3.1 status, pending comments and next steps

Chapter 1: Introduction to Systems Analysis and Design

CTI STIX SC Monthly Meeting

Business System Development

Unified Modeling Language

SQL Server Integration Services

Lesson 6 Wrap-Up.

Lesson 6 Wrap-Up.

Jonathan Rosenberg dynamicsoft

S-127 – Marine Traffic Management Release Candidate NIPWG 6 30 January 2019 Raphael Malyankar Eivind Mong Sponsored by IHO.

Vermont Health Information Technology Plan (VHITP) Workgroup Meeting

Chapter 1: Introduction to Systems Analysis and Design

Software Requirements Specification (SRS) Template.

Information Analysis, Organization, and Presentation

Chapter 1: Introduction to Systems Analysis and Design

Presentation transcript:

Meeting Structure EBU, Geneva 9am Tuesday 21 February pm Wednesday 22 February Rev3 EBU-AMWA FIMS February 2012

Principle Objective of the meeting is to finalize the specification. No more technical discussion. –If a critical technical issue(s) are found, we must Leave them as they are or Remove and discuss at the next version Just focus on editorial modification. –Still not easy to scan all parts: Part1 Part2 Base Schema Part2 Service Interfaces (Capture, Transform, Transfer) Review based on the specification –Richard? and/or Kanada-san? to check the schemas in parallel

Day 1 9:20 – 11:00 (Part1) Section# of pagesminTOD Executive Summary129:32 ->9:22 Scope129:34 ->9:24 Conformance language129:36 ->9:26 Reference Documents229:38 ->9:28 Overview129:40 ->9:30 High Level Architecture5109:50 ->9:40 Media Service Management (modified)5 ->710 -> 2110:00 ->10:01 Media Service Awareness (modified)1 ->22 ->610:02 ->10:07 Media Service Behavior (modified)8 ->9 40 ->2710:42 ->10:34 Media Service Overview51010:52 ->10:44 Appendix1210:54 ->10:46 Coffee break6 ->1411:00 Total3484 ->861:24

Day 1 11:00 – 17:30 (Part2 Base) Section# of types# of pagesminTOD Schema Design1511:05 Extension Types221011:15 FIMS-defined references12511:20 FIMS-defined resources :15 Lunch break4514:00 FIMS-defined atoms241014:10 FIMS-defined attribute groups241014:20 FIMS-defined simple types834015:00 FIMS-defined complex types for representing single values :50 Coffee break1016:00 FIMS-defined enumerations :15 Some more as much as possible17:30 Total :20

Day 2 9:05 – 15:05 (Part2 Base + Service Interfaces) Section# of types# of pagesminTOD Base FIMS-defined control data types :20 FIMS-defined messages and faults :30 Coffee break1511:45 Capture FIMS-defined resources261011:55 FIMS-defined enumerations211012:05 FIMS-defined control data types994512:50 FIMS-defined messages and faults542513:15 Lunch break (start/end time may need to be changed)4514:00 Transform FIMS-defined resources221014:10 FIMS-defined enumerations13514:15 FIMS-defined messages and faults442014:35 Transfer FIMS-defined resources221014:45 FIMS-defined enumerations11514:50 FIMS-defined messages and faults321515:05 Total :00