How to know supported flex Container type Group

How to know supported flex. Container type Group Name: ARC Source: Hiroyuki Maeomichi – maeomichi. hiroyuki@lab. ntt. co. jp, Kei Harada – harada. kei@lab. ntt. co. jp Meeting Date: 2018 -03 -12 ARC-2018 -0066 -How_to_know_supported_flex. Container_type

Introduction • Flexibility of <flex. Container> is convenient but it could be a cause of less interoperability. • This Input Contribution discuss identified issues. ARC-2018 -0066 -How_to_know_supported_flex. Container_type 2

Current <CSEBase> • <CSEBase> provides supported. Resource. Type attribute for exposing supported range. ARC-2018 -0066 -How_to_know_supported_flex. Container_type 3

Problems for expressing <flex. Container> • Outer AE and CSE cannot know what container. Definition are supported by registered <flex. Container> – Currently there is no attribute like supported. Resource. Type • Relationship between URI for container. Definition and actual XSD files is unclear. – Even if you know container. Definition URI, you could not retrieve implied XSD files. ARC-2018 -0066 -How_to_know_supported_flex. Container_type 4

Current container. Definition TS-0001 9. 6. 35 ARC-2018 -0066 -How_to_know_supported_flex. Container_type 5

Current container. Definition Generic IWK (TS-0030 7. 2) we must look at & have a <content. Instance> ARC-2018 -0066 -How_to_know_supported_flex. Container_type 6

Current container. Definition HAIM (TS-0023 6. 4) using only this information, we cannot retrieve any XSD file. ARC-2018 -0066 -How_to_know_supported_flex. Container_type 7

Possible Solutions • Option 1: add new attribute of <CSEBase> for expressing supported container. Definition. – like “supported. Container. Definition” • Option 2: add more Information to option 1 – providing URL where client can download related XSD files. • Option 3: add more information to option 1 or 2 giving more developer friendly information – like “custom. Attribute. Names” which expresses a list of supporting [custom. Attribute]s as string. ARC-2018 -0066 -How_to_know_supported_flex. Container_type 8

Appendix ARC-2018 -0066 -How_to_know_supported_flex. Container_type 9

Example • • • Option 1: add new attribute of <CSEBase> for expressing supported container. Definition. Option 2: add more Information to option 1 Option 3: add more information to option 1 or 2 giving more developer friendly information supported. Container Definition container. Definition. URI downloadable. URL custom. Attribute Name (parameter of supported. Container. Definition) container. Definition HAIM https: //aaaaa https: //bbbb Heart. Rate, rr…(List of String) container. Definition All. Joyn https: //xxxxx https: //yyyyy objectpath, enabled…(List of String) (parameter of supported. Container. Definition) Option 1 Option 2 Option 3 ARC-2018 -0066 -How_to_know_supported_flex. Container_type 10

Discussion 1 • <flex. Container> supporting = all content. Definition supporting • <flex. Container> speciallizations can be created freely? or only what one. M 2 M has decided? ARC-2018 -0066 -How_to_know_supported_flex. Container_type 11

Discussion 2 • Do we allow vendor specific / domain specific <flex. Container> or not? • Should we handle version of XSDs? ARC-2018 -0066 -How_to_know_supported_flex. Container_type 12