1. Clue data model Design team meeting 30/09/2014 Roberta Presta, Simon Romano

2. Outline Open tickets solutions Main updates in version 7

3. Open tickets #35 - Ensure Framework and Data model terminology is consistent V 16 #48 - Linking participant Information with Participant Type #54 – Data model: Security Considerations #62 – Data model: Audio captures #63 - Action: Data model - Remove audio channel format #59 - Action: Change "Capture Scene Entry (CSE)" to “Capture Scene View (CSV)” #60 - Action: Change "Global CSE List" to “Global View List” #61 - Action: Proposal for describing the coordinate system – ToDo #55 – Data model: IANA considerations – ToDo

4. #54 – Data model: Security Considerations Sensitive data – Authenticated access and integrity up to – Clue protocol – Clue data channel

5. #55 – Data model: IANA considerations IANA Considerations: ToDo – XML Schema registration – XML namespace registration This specification defines a new namespace specification for identifying the elements defined in the data model. This namespace is as follows: urn:ietf:params:xml:ns:clue-info – Suggestions for the namespace name are welcome

6. #62 – Data model: Audio captures Updates to audio captures: – sensitivityPattern in place of audioChannelFormat – Updated text in the document Disallowed areaOfCapture “As discussed at IETF-90, the data model needs to be updated to insure that the audio capture list is extensible” - ?

7. Version 7 - other updates Spatial information – capture point optional – text coherent with the framework one Simultaneous set definition – to refer to capture scene identifiers as shortcuts – optional mediaType attribute, mandatory to use when only capture scene identifiers are listed Encoding groups – removed the constraint of the same media type – Updated text about media captures without (optional in the XML schema) mediaType attributes removed where not necessary Extensions

8. Spatially Definable (SD) captures Point of capturePoint on line of captureArea of capture SD video capture OPTIONAL It can be provided only in presence of a capture point. If provided, it MUST be a point in the space between the capture point and the area of capture. YES SD audio capture YESOPTIONAL if the sensitivity is not omnidirectional, the point on line of capture SHOULD be provided. NO

9. Simultaneous set

10. Extensions Example added How to enrich the current schema with new elements definition –  Using any and anyAttribute places How to create new media capture types –  A solution for obtaining XML documents with new media capture types still compatible with the current schema

11. Other capture types Other media capture types can be described by using the CLUE data model – They can be represented by exploiting "otherCaptureType" type otherCaptureType is conceived to be filled with elements defined in the extensions of the current schema – i.e., with elements defined in other XML schemas otherCaptureType inherits from mediaCaptureType

12. Extension example The extension schema file

13. Extension example The XML document – Validated against the current CLUE data model schema …