Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

Slides:

Advertisements

Similar presentations

XML Schema Heewon Lee. Contents 1. Introduction 2. Concepts 3. Example 4. Conclusion.

Advertisements

Heppenheim Producer-Archive Interface Specification Status of standardisation project Main characteristics, major changes, items pending.

An Introduction to XML Based on the W3C XML Recommendations.

Call for test suites Group Name: REQ Source: Jiaxin Yin, Huawei Technologies Co., Ltd., Meeting Date: Agenda Item: TBD.

WG 3 Progress Report at TP12 Group Name: oneM2M TP12 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

© 2012 The MITRE Corporation. All rights reserved. For internal MITRE use 11 July 2013 Meeting #6 hData Record Format Task Force 1 © 2012 The MITRE Corporation.

Group:WG3 (PRO) Source:Peter Niblett, IBM, Date: Agenda:PRO#14 TS-0004 Data Representation Proposal Discussion.

XML Schema Describing the structure of XML documents. A very brief introduction 1XML Schema.

OneM2M-MP Data_Model_Repository Establishing Data Model Repository for oneM2M Group Name: Method and Procedure Sub-commitee Source: WG3 chair.

Group:WG3 (PRO) Source:Peter Niblett, IBM, Date: Agenda:PRO#14 TS-0004 Data Representation Proposal Discussion.

® IBM Software Group © 2009 IBM Corporation Rational Publishing Engine RQM Multi Level Report Tutorial David Rennie, IBM Rational Services A/NZ

Why XML ? Problems with HTML HTML design - HTML is intended for presentation of information as Web pages. - HTML contains a fixed set of markup tags. This.

1. 2 Purpose of This Presentation ◆ To explain how spacecraft can be virtualized by using a standard modeling method; ◆ To introduce the basic concept.

2-levels Access control for HTTP binding Group Name: WG4 (& WG2/WG3 for information) Source: Shingo Fujimoto, FUJITSU, Meeting.

Progressing the Work on the MAS TR-0006, TR-0007 Group Name: Management Abstraction and Semantics Source: Tim Carey, ALU,

What is XML?  XML stands for EXtensible Markup Language  XML is a markup language much like HTML  XML was designed to carry data, not to display data.

XML TUTORIAL Portions from w3 schools By Dr. John Abraham.

Thoughts on oneM2M resource tree Group Name: WG2 Architecture at TP#7 (Sophia, October 2013) Source: Nicolas Damour, Sierra Wireless

OneM2M-ARC Enhancement_on_resources Some thoughts on oneM2M resources Group Name: WG2 Source: Norio Uchida, NEC, Barbara.

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

Announcement Resources ARC Announcement_Issues Group Name: WG2 Source: Barbara Pareglio, NEC Meeting Date: Agenda Item: Input Contribution.

Introduction of PRO WG activities Group Name: TP Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item:

Beginning XML 4th Edition. Chapter 5: XML Schemas.

WG 3 Progress Report at TP13 Group Name: oneM2M TP13 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

OneM2M-REQ R03 Proposed simple guidelines for writing use cases and requirements Group Name: oneM2M WG1 / WG2 Source: Joerg Swetina (NEC), Ataru.

PRO R01-URI_mapping_discussion Discussion on URI mapping in protocol context Group Name: PRO and ARC Source: Shingo Fujimoto, FUJITSU,

In-Band Access Control Framework Group Name: WG4 SEC Source: Qualcomm Meeting Date: Agenda Item:

Management of CMDH Policies Group Name: WG5-MAS Source: Wolfgang Granzow, Qualcomm, Meeting Date: Agenda Item: Management.

App-ID Discussion Group Name: ARC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 31 July 2014 Agenda Item: TBD.

Response Status Codes Concepts for oneM2M Group Name: WG3 Source: Philip Jacobs, Cisco, Meeting Date: Agenda Item: TS-0004.

WG5 - MAS Progress Report at TP #9 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang, Chair, Meeting.

Proposal for WG3 & WG5 work area split

ESA UNCLASSIFIED – For Official Use SOIS EDS & Toolchain ESA YGT Study F. Torelli & P. Skrzypek CCSDS Fall Meeting /10/2013.

Customized Resource Types MAS Group Name: MAS + ARC + PRO WGs Source: Wolfgang Granzow, Qualcomm Inc., Meeting Date:

WG5 - MAS Progress Report at TP #10 Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: WG5 Chairs Meeting Date: to

WG 3 Progress Report at TP #7 Group Name: oneM2M TP #7 Source: Raymond Forbes, LM Ericsson, Meeting Date: /18 Agenda.

Node-Specific Resource Group Name: ARC&MAS Source: LGE, Meeting Date: Agenda Item: Contribution.

C. Huc/CNES, D. Boucon/CNES-SILOGIC Producer-Archive Interface Specification.

Matching Resources with CSFs Group Name: WG2 (ARC) Source: Hongbeom Ahn, LG Electronics, Meeting Date:

WG 3 Progress Report at TP15 Group Name: oneM2M TP15 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Discussion on XSD implementation conventions (document number PRO R01) Group Name: PRO Source: Wolfgang Granzow, Meeting.

WG 2 Progress Report at TP#9 Group Name: oneM2M TP #9 Source: WG2 leadership Meeting Date: /21 Agenda Item: WG Reports.

Group Name: REQ Source: Linyi Tian, Huawei, Meeting Date: Feb 18, Agenda Item: METADATA IN EDUCATION.

Different planes for the resource structure Group Name: WG5 – MAS and WG2 – ARC Source: Nicolas Damour, Sierra Wireless

Working with XML. Markup Languages Text-based languages based on SGML Text-based languages based on SGML SGML = Standard Generalized Markup Language SGML.

VOTable agenda Current VOTable status Current VOTable status News from Applications News from Applications Questions about VOTable schema Questions about.

PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:

Device & Device Type Modelling Group Name: WG5 Source: NEC Meeting Date: Agenda Item: WI-0005 MAS Device_&_Device_Type_Modelling.

SEC #11 WG4 Status & Release 1 Outlook Group Name: Source:,, Meeting Date: Agenda Item:

WG5 – MAS#21 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Yongjing Zhang (Huawei, WG5 Chair) Meeting Date:

Proposed Co-convened WG1/2 Objectives, Schedule, and Activities Group Name: TP#1 Source: Omar Elloumi (Alcatel-Lucent), Laurent Laporte (Sprint) Meeting.

WG 3 Progress Report at TP10 Group Name: oneM2M TP10 Source: Raymond Forbes, LM Ericsson, Meeting Date: to

Template proposal Group Name: PRO Source: Barbara PAreglio, NEC, Meeting Date: Agenda Item: input contribution.

Issues of Current Access Control Rule and New Proposal Introduction Group Name: ARC 21 Source: Wei Zhou, Datang, Meeting Date:

Authorization Architecture Discussion Group Name: SEC WG Source: Seongyoon Kim, LG Electronics, Meeting Date: 28 MAY, 2014 Agenda.

Consideration Security Issues on Registration Group Name: WG4 (SEC) Source: Shingo Fujimoto, FUJITSU, Meeting Date:

XML Extensible Markup Language

WG5 – MAS#22 Status Report Group Name: WG5 MAS (Management, Abstraction & Semantics) Source: Tim Carey(Alcatel-Lucent, WG5 Vice Chair) Meeting Date:

Reasons for CSF Clean-up (Issues & Next Steps) Group Name: WG2 Source: Syed Husain – NTT DOCOMO Meeting Date: (ARC_9.3) Agenda Item: 6 DOC#:

WG1 - REQ Progress Report at TP #11 Group Name: WG1 REQ (Requirements) Source: WG1 Vice Chairs Meeting Date: to Agenda Item: TP#11,

TS-0004 guideline for new resource type definition Group Name: PRO WG Source: SeungMyeong JEONG, LG Electronics Meeting Date: Agenda Item: TS.

Discussion about Interoperability (&versioning) Group Name: PRO & ARC Source: FUJITSU Meeting Date: Agenda Item: TS-0004.

IPDA Registry Definitions Project Dan Crichton Pedro Osuna Alain Sarkissian.

Joint PRO/ARC session at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:

Extensible Markup Language (XML) Pat Morin COMP 2405.

MIME Type Definition Group Name: PRO WG

Considering issues regarding handling token

Data Modeling II XML Schema & JAXB Marc Dumontier May 4, 2004

Discussion on XSD open issues

Summary of the MAF and MEF Interface Specification TS-0032

Presentation transcript:

Method of Converting Resource definitions into XSD Group Name: WG3 (PRO) Source: Shingo Fujimoto, FUJITSU, Meeting Date: Agenda Item: Core Protocol TS © 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD

© 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD Introduction Initial version of Resource definitions in Stage 2 are provided We need to map them into XML Schema This contribution propose the method for developing XSD files from Architecture TS This contribution also explain identified issues 2

© 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD Method of conversion Architecture TS contains most of information to generate XSD oneM2M-ARC R02 is implemented for automated processing All we should do is specifying the rule to convert ‘Resource’ definition into XSD 3

© 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD Conversion Rules Resource Types are mapped to the top level node on XSD data Each attributes are mapped as child node of the top level node, and should not have any child nodes Each child resources are mapped as child node of the top level node, and should be referred by ‘ref’ attribute Use of pre-defined types are recommended, but may be restricted by defining oneM2M specific data types Common ‘Simple types’ are collected as dedicated XSD file, which is named ‘ simple_types.xsd’ 4

© 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD Pre-defined Types XSD types – ‘xs:’ prefixed oneM2M IDs, common attributes – ‘m2m:’ prefixed 5

© 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD Identified Issues Description text for simple data type in TS – Template for Resource description in Core TS ? – Dedicated section for ‘common attributes’ ? Organizing XSD files – Top level node (=‘Resource Type’) as XSD file – Child nodes should be part of XSD file for the top level Resource – Work in separate files and finalize as single file ? Handling ‘binary’ data – Base64 encoding is typical way – We may define ‘m2m:binary’ type for comversion 6

© 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD Example <xs:schema xmlns:xs=" xmlns:m2m=" Refer definition in other XSD file..n should be max integer in system ? There are no description in Arch TS for fixed values We better to describe data types for ‘common attributes’ If the data type are not defined yet, should we complete them later ? 7

© 2013 oneM2M Partners oneM2M-PRO Convert_Resource_Defs_into_XSD Conclusion WG member should consider identified issues Volunteers should start drafting description text based on given feedback 8