DOCSLIB.ORG

ISO/IEC JTC 1 Information Technology

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ISO/IEC JTC 1 Information Technology ISO/IEC JTC 1 Information technology Big data Preliminary Report 2014 Our vision Our process To be the world’s leading provider of high Our standards are developed by experts quality, globally relevant International all over the world who work on a Standards through its members and volunteer or part-time basis. We sell stakeholders. International Standards to recover the costs of organizing this process and Our mission making standards widely available. ISO develops high quality voluntary Please respect our licensing terms and International Standards that facilitate copyright to ensure this system remains international exchange of goods and independent. services, support sustainable and equitable economic growth, promote If you would like to contribute to the innovation and protect health, safety development of ISO standards, please and the environment. contact the ISO Member Body in your country: www.iso.org/iso/home/about/iso_ members.htm This document has been prepared by: Copyright protected document ISO/IEC JTC 1, Information technology All rights reserved. Unless otherwise Cover photo credit: ISO/CS, 2015 be reproduced or utilized otherwise in specified,any form noor partby anyof this means, publication electronic may or mechanical, including photocopy, or posting on the internet or intranet, without prior permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of the requester: © ISO 2015, Published in Switzerland Case postale 56 • CH-1211 Geneva 20 Tel.ISO copyright+41 22 749 office 01 11 Fax. +41 22 749 09 47 E-mail [email protected] Web www.iso.org ii © ISO/IEC 2015 – All rights reserved © ISO/IEC 2015 – All rights reserved iii 1 Scope ...........................................................................................................................................................................................................1 2 Terms and definitions ...............................................................................................................................................................1 ......................................................................................................................................... 1 .................................................................................................................................. 3 2.32.1 TAermsbbreviated defined terms elsewhere and conventions ..............................................................................................................4 2.2 Terms defined in this report 3 Introduction to Big Data .........................................................................................................................................................5 3.1 General concept of Big Data ................................................................................................................................... 6 .................................................................................................................................................. 8 3.3 Organizational drivers of Big Data ...................................................................................................................9 3.23.4 DefinitionKey characteristics of Big Data of Big Data ............................................................................................................................9 3.4.1 Volume ................................................................................................................................................................9 3.4.2 Variety ..............................................................................................................................................................10 3.4.3 Velocity ............................................................................................................................................................10 3.4.4 Variability ......................................................................................................................................................11 3.4.5 Veracity............................................................................................................................................................11 3.5 Roles in Big Data ecosystem ...............................................................................................................................11 3.6 Security and privacy for Big Data...................................................................................................................12 3.6.1 Issues ................................................................................................................................................................12 3.6.2 Recommendations .................................................................................................................................14 4 Relevant standardization activities ........................................................................................................................ 15 4.1 ISO/IEC JTC 1/SC 32 ..................................................................................................................................................16 4.2 ISO/IEC JTC 1/SC 38 ..................................................................................................................................................16 4.3 ITU-T SG13 .........................................................................................................................................................................16 4.4 W3C..........................................................................................................................................................................................17 4.5 Open Geospatial Consortium (OGC) ............................................................................................................18 4.6 Organization for the Advancement of Structured Information Standards (OASIS) .......................................................................................................................................................19 4.7 Transaction Processing Performance Council (TPC) ....................................................................20 4.8 TM Forum ...........................................................................................................................................................................20 5 Market estimation ..................................................................................................................................................................... 20 6 Potential gaps in standardization ............................................................................................................................. 21 7 JTC 1 prospective standardization areas and issues ............................................................................. 23 Annex A Mapping table between SCs and Big Data issues ................................................................................. 24 Annex B Topics and technologies relevant to Big Data standardization ............................................ 27 Bibliography ...................................................................................................................................................................................................... 30 iv © ISO/IEC 2015 – All rights reserved 1 Scope This document does the following: — Survey the existing ICT landscape for key technologies and relevant standards/models/ studies/ use cases and scenarios for Big Data from JTC 1, ISO, IEC and other standard setting organizations; — IAdentifyssess the key current terms statusand definitions of Big Data commonly standardization used in marketthe area requirements, of Big Data; and identify standards gaps, and propose standardization priorities to serve as a basis for future JTC 1 work. 2 Terms and definitions 2.1 Terms defined elsewhere This2.1.1 document uses the following terms defined elsewhere. capability quality of being able to perform a given activity [SOURCE: ISO 15531-1:2004] 2.1.2 cloud computing paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand [SOURCE: Recommendation ITU-T Y.3500 | ISO/IEC 17788:2014] 2.1.3 framework structure expressed in diagrams, text, and formal rules which relates the components of a conceptual entity to each other [SOURCE: ISO 17185-1:2014] 2.1.4 Internet of Things integrated environment, inter-connecting anything, anywhere at anytime [SOURCE: ISO/IEC JTC 1 SWG 5 Report:2013] 2.1.5 lifecycle evolution of a system, product, service, project or other human-made entity from conception through retirement [SOURCE: ISO/IEC/TR 29110-1:2011] © ISO/IEC 2015 – All rights reserved 1 2.1.6 ownership legal right of possession, including the right of disposition, and sharing in all the risks demonstrated by an examination of the substance, rather than the form, of ownership andarrangements profits commensurate with the degree of ownership interest or shareholding, as [SOURCE: ISO 10845-5:2011] 2.1.7 privacy collected and stored and by whom and to whom that information may be disclosed right of individuals to control or influence what information related to them may be [SOURCE: ISO/TS 17574:2009] 2.1.8 provenance information on the place and time of origin or derivation or a resource
Load more

Recommended publications
  • Odata Services Company
    PUBLIC 2021-03-09 OData Services company. All rights reserved. All rights company. affiliate THE BEST RUN 2021 SAP SE or an SAP SE or an SAP SAP 2021 © Content 1 SAP Cloud for Customer OData API..............................................4 2 New Features.............................................................. 13 2.1 What's New in OData API v2 Reference.............................................13 2.2 Add Public Solution Model (PSM) Fields to Standard OData Services........................15 2.3 Transport Custom OData Services with Transport Management............................16 2.4 Compatibility Mode for READ Operations........................................... 16 2.5 Support for User-Friendly IDs in Standard OData Services................................16 2.6 Constant Values to Function Imports...............................................17 3 OData API Reference.........................................................18 3.1 OData API v2 Reference........................................................18 3.2 OData API v1 Reference (Deprecated)..............................................20 Account Contact Relationship.................................................21 Account EntityType........................................................22 Appointment Entity Type....................................................40 BusinessPartner Entity Type..................................................46 CodeList Entity Type....................................................... 47 Contextual CodeList Entity Type...............................................48
    [Show full text]
  • Part 2: Data Category Selection (DCS) for Electronic Terminological Resources (ETR)
    © ISO 2003 – All rights reserved Reference number of working document: ISO/TC 37/SC 3 N 486 Date: 2003-10-31 (12620.Part 2.doc ) ISO/CD 12620-2 Committee identification: ISO/TC 37/SC 3 Secretariat: DIN Terminology and other language resources — Data categories — Part 2: Data category selection (DCS) for electronic terminological resources (ETR) Warning This document is not an ISO International Standard. It is distributed for review and comment. It is subject to change without notice and may not be referred to as an International Standard. Recipients of this document are invited to submit, with their comments, notification of any relevant patent rights of which they are aware and to provide supporting documentation. Document type: International standard Document subtype: if applicable Document stage: 00.20 Document language: en M:\dms\dtec\xdom741\iso\12620\Part 2\N486 CD12620pt2 2003.DOC EN2 2000-07-10 © ISO ISO Draft Revision 12620, Part 2:2003(E) Copyright notice This ISO document is a draft revision and is copyright-protected by ISO. While the reproduction of a draft revision in any form for use by participants in the ISO standards development process is permitted without prior permission from ISO, neither this document nor any extract from it may be reproduced, stored or transmitted in any form for any other purpose without prior written permission from ISO. Requests for permission to reproduce this document for the purpose of selling it should be addressed as shown below or to ISO’s member body in the country of the requester: [Indicate : the full address telephone number fax number telex number and electronic mail address as appropriate, of the Copyright Manager of the ISO member body responsible for the secretariat of the TC or SC within the framework of which the draft has been prepared] Reproduction for sales purposes may be subject to royalty payments or a licensing agreement.
    [Show full text]
  • Pyslet Documentation Release 0.6.20160201
    Pyslet Documentation Release 0.6.20160201 Steve Lay February 02, 2016 Contents 1 What’s New? 1 2 Compatibility 7 3 IMS Global Learning Consortium Specifications 13 4 The Open Data Protocol (OData) 101 5 Hypertext Transfer Protocol (RFC2616) 207 6 Other Supporting Standards 247 7 Welcome to Pyslet 357 Python Module Index 359 i ii CHAPTER 1 What’s New? As part of moving towards PEP-8 compliance a number of name changes are being made to methods and class at- tributes with each release. There is a module, pyslet.pep8, which contains a compatibility class for remapping missing class attribute names to their new forms and generating deprecation warnings, run your code with “python -Wd” to force these warnings to appear. As Pyslet makes the transition to Python 3 some of the old names will go away completely. It is still possible that some previously documented names could now fail (module level functions, function arguments, etc.) but I’ve tried to include wrappers or aliases so please raise an issue on Github if you discover a bug caused by the renaming. I’ll restore any missing old-style names to improve backwards compatibility on request. Finally, in some cases you are encouraged to derive classes from those defined by Pyslet and to override default method implementations. If you have done this using old-style names you will have to update your method names to prevent ambiguity. I have added code to automatically detect most problems and force fatal errors at runtime on construction, the error messages should explain which methods need to be renamed.
    [Show full text]
  • Ffimffi Llmub Liks Kord Kuus Alates Lggg
    EESTI STAtrDARNIAMET ffiMffi llmub liks kord kuus alates lggg. aastast tssN 1406-0698 Tdnases numbris : r) EESTI UUDISED 1 tr) Standardikomisjonis 2 + Akred iteeritud katselaborid 3 tr) Tur.ibikinnitused 5 tr) Kval iteed ij u hti mi ne toid uainetoostuses 10 tr) Koolitus DIN-is 11 E> Harmoneeritud standardid 13 tr) IFAN 13 r) CEN UUDISED 14 tr) ISO UUDISED ISO bulletddni lehekulgedelt .... 15 tr+ Juulis saadud ISO standardid ja ISO/DIS 17 IEC standardid 22 CEN standardid 25 r) Eesti standardite koostamisettepanekud . 2a E) Eesti standardite kavandid 28 r) Eesti standardite muugi TOp 10 . 29 r+ Mtiugile saabunr-ld 30 tr) Leiva- ja saiatootjatele 30 tr) Reglstrisse kantud 30 EESTI AUDISBD 3-7. juunil toimus Eesti P6llumajandustilikoolis P6hjarnaade Metsanduse, Veterinaaria ja P6llumajanduse Ulikooli poolt Baltimaadele organiseeritud kursus teemal "Kvaliteedijuhtimise stisteem toiduainetiitistuses", millest v6ite lugeda lk. 10 25. juunil toimus Kaitseministeeriumis standardiseerimisalane seminar. Standardiseerimist NATO raames ja sellealast tegevust Taanis tutvustasid Taani spetsialistid. Standardiameti Standardikomisjoni koosolek toimus 20 A6 96. ,l?, l ''-{a Standardiameti, kui katselaborite ning sertifitseerimis- ja inspektsioonorganite akrediteerimisorgani poolt on seisuga 01 08 96 akditeeritud 2 esimest laboric RAS ARETO toiduainete analiiiisi ning Riigi Veterinaarlaboratoorium toiduainete analiltlsi ja loomhaiguste diagnoosi valdkonnas. Liihemalt lugege lk. 3 STANDARDIKOMISJOMS Standardiameti Standardikomisjoni 20 M 96 koosolekul oli piievakonas: 1. Eestistandarditekomtamisettepanekutearutelu l.l Keevituse koordineerimine. thesanded ja vastutus Ettepaneku esitaja: AS Sele Aluseksvdetavad dokumendid: EN 7 19 i,ilev6tt. OTSUSTATI Ettepanek heaks kiita. Paluda U.Vainul tiipsustada, milles seisneb keevituse koordineerimise olemus. Vdib-olla peaks nimetuses s6na "koordineerimine" asemel olema muu s6na. Kas keevitus v6i keevitusttitid? 1.2 NDT operaatorite kvalifitseerimine ja sertifitseerimine.
    [Show full text]
  • Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, Proposes
    Haris Kurtagic, SL-King Jason Birch, City of Nanaimo Geoff Zeiss, Autodesk Tim Berners-Lee, in Government Data Design Issues, proposes ○ Geodata on the web in raw form. ○ Raw geodata must be searchable How do you find raw geospatial data ? Data Catalogs Wouldn’t it be nice if… And see.. Searchable Raw Geospatial Data www.georest.org Open Data Protocol “The Open Data Protocol (OData) is a Web protocol for querying and updating data that provides a way to unlock your data and free it from silos that exist in applications today.” www.odata.org ODATA HTTP Atom AtomPUB JSON HTTP://.../vancouver/libraries <feed xmlns=http://www.w3.org/2005/Atom … > <title type="text">libraries</title> <id>http://…/vancouver/libraries(10)</id> <title type="text"></title> <entry> <content type="application/xml"> <m:properties> <d:library_name>Britannia</d:library_name> <d:latitude m:type="Edm.Double">49.2756486</d:latitude> <d:longitude m:type="Edm.Double">-123.0737717</d:longitude> <d:address>1661 Napier St</d:address> </m:properties> …..</entry> <entry>…</entry></feed> HTTP://.../vancouver/libraries ?$format=JSON {"d":[{"library_name":"Britannia","latitude":" 49.2756486","longitude":"- 123.0737717","address":"1661 Napier St"} , {..}] } HTTP Header accept: application/json OData Example Live OData Service from Vancouver OData Producers SharePoint 2010, SQL Azure, IBM WebSphere, … GeoREST OData Live Services Netflix, Open Goverment Data Initiative (OGDI), Stack Overflow, Vancouver, Edmonton, … City of Nanaimo OData Consumers Browsers, Odata Explorer, Excel 2010,…
    [Show full text]
  • SAP Analytics Cloud, Analytics Designer Developer Handbook
    SAP Analytics Cloud, analytics designer Developer Handbook Document Version: 5.1 – 2020-04-06 Table of Contents 1 Table of Contents Table of Contents ......................................................................................................................... 1 Figures .......................................................................................................................................... 7 1 About Analytics Designer .............................................................................................10 1.1 What Is an Analytic Application? .....................................................................................10 1.2 What Is Analytics Designer? ............................................................................................10 1.3 What Can You Do with Analytic Applications That You Can’t Do with Stories? ..............10 1.4 How Are Stories and Analytic Applications Related to Each Other? ...............................10 1.5 Why Do We Need Both Stories and Analytic Applications? ............................................11 1.6 What Is the Typical Workflow in Creating an Analytic Application? .................................11 1.7 What Are Typical Analytic Applications? .........................................................................12 1.8 How Does Scripting Work in Analytic Applications? ........................................................12 1.9 What’s the Scripting Language for Analytic Applications? ..............................................13 2 Getting
    [Show full text]
  • Catalogue Open Data Protocol (Odata API) User Guide
    Catalogue Open Data Protocol (OData API) User Guide Content 1. Introduction .......................................................................................................................................... 3 1.1. Purpose......................................................................................................................... 3 1.2. Change register ............................................................................................................. 3 1.3. Structure of the document ............................................................................................. 3 1.4. Acronyms ...................................................................................................................... 4 1.5. Reference Documents ................................................................................................... 4 2. Open Data Protocol overview ............................................................................................................. 6 2.1. Entity Data Model concept ............................................................................................ 6 Entity Type ..................................................................................................................... 7 Entity Set ....................................................................................................................... 7 3. ONDA OData Entity Data Model ......................................................................................................... 8 3.1. ONDA Entity
    [Show full text]
  • Deliverable D7.5: Standards and Methodologies Big Data Guidance
    Project acronym: BYTE Project title: Big data roadmap and cross-disciplinarY community for addressing socieTal Externalities Grant number: 619551 Programme: Seventh Framework Programme for ICT Objective: ICT-2013.4.2 Scalable data analytics Contract type: Co-ordination and Support Action Start date of project: 01 March 2014 Duration: 36 months Website: www.byte-project.eu Deliverable D7.5: Standards and methodologies big data guidance Author(s): Jarl Magnusson, DNV GL AS Erik Stensrud, DNV GL AS Tore Hartvigsen, DNV GL AS Lorenzo Bigagli, National Research Council of Italy Dissemination level: Public Deliverable type: Final Version: 1.1 Submission date: 26 July 2017 Table of Contents Preface ......................................................................................................................................... 3 Task 7.5 Description ............................................................................................................... 3 Executive summary ..................................................................................................................... 4 1 Introduction ......................................................................................................................... 5 2 Big Data Standards Organizations ...................................................................................... 6 3 Big Data Standards ............................................................................................................. 8 4 Big Data Quality Standards .............................................................................................
    [Show full text]
  • Blackbaud CRM Query and Export Guide
    Query and Export Guide 03/23/2016 Blackbaud CRM 4.0 Query and Export US ©2016 Blackbaud, Inc. This publication, or any part thereof, may not be reproduced or transmitted in any form or by any means, electronic, or mechanical, including photocopying, recording, storage in an information retrieval system, or otherwise, without the prior written permission of Blackbaud, Inc. The information in this manual has been carefully checked and is believed to be accurate. Blackbaud, Inc., assumes no responsibility for any inaccuracies, errors, or omissions in this manual. In no event will Blackbaud, Inc., be liable for direct, indirect, special, incidental, or consequential damages resulting from any defect or omission in this manual, even if advised of the possibility of damages. In the interest of continuing product development, Blackbaud, Inc., reserves the right to make improvements in this manual and the products it describes at any time, without notice or obligation. All Blackbaud product names appearing herein are trademarks or registered trademarks of Blackbaud, Inc. All other products and company names mentioned herein are trademarks of their respective holder. QueryExport-2016 Contents Getting Started with Query 4 Query: A Guided Tour 4 Common Query Fields 20 Common Query Filters 22 Query 25 Information Library 27 Ad-Hoc Queries 27 Smart Queries 58 Selections 71 Copy an Existing Query 74 Export Queries 74 Browse Query Results 75 View Query Results 75 Organize Queries 75 Open Data Protocol (OData) 79 Export 82 Exports 82 Export Definitions 86 Export Process Status Page 100 Import Selections 106 Import Selections 106 Import Selection Process Status Page 110 chapter 1 Getting Started with Query Query: A Guided Tour 4 Common Query Fields 20 Constituent Query Fields 20 Revenue Query Fields 21 Registrant Query Fields 22 Common Query Filters 22 Constituent Query Filters 22 Revenue Query Filters 23 Registrant Query Filters 23 Query is a powerful tool you can use to help filter and group records.
    [Show full text]
  • Denodo Odata 2.0 Service User Manual
    Denodo OData 2.0 Service User Manual Revision 20200508 NOTE This document is confidential and proprietary of Denodo Technologies. No part of this document may be reproduced in any form by any means without prior written authorization of Denodo Technologies. Copyright © 2021 Denodo Technologies Proprietary and Confidential Denodo OData 2.0 Service User Manual 20200508 2 of 34 CONTENTS 1 OVERVIEW........................................................................5 2 INSTALLATION..................................................................6 2.1 DEPLOYING INTO THE DENODO EMBEDDED WEB CONTAINER............8 2.2 CONFIGURING JNDI RESOURCES IN APACHE TOMCAT......................10 3 VIRTUAL DATAPORT PRIVILEGE REQUIREMENTS.................12 4 FEATURES.......................................................................13 5 SERVING METADATA........................................................14 6 QUERYING DATA: THE BASICS..........................................16 6.1 QUERYING COLLECTIONS..............................................................16 6.2 OBTAINING ITEMS BY PRIMARY KEY..............................................16 6.3 ACCESSING INDIVIDUAL PROPERTIES............................................16 6.4 ACCESSING INDIVIDUAL PROPERTY VALUES...................................17 6.5 ACCESSING COMPLEX PROPERTIES...............................................17 6.6 COUNTING ELEMENTS IN A COLLECTION: $COUNT..........................18 6.7 ESTABLISHING RESPONSE FORMAT...............................................18 7 NAVIGATING
    [Show full text]
  • Information Technology — Open Data Protocol (Odata) V4.0
    BS ISO/IEC 20802-2:2016 BSI Standards Publication Information technology — Open data protocol (OData) v4.0 Part 2: OData JSON Format WB11885_BSI_StandardCovs_2013_AW.indd 1 15/05/2013 15:06 BS ISO/IEC 20802-2:2016 BRITISH STANDARD National foreword This British Standard is the UK implementation of ISO/IEC 20802-2:2016. The UK participation in its preparation was entrusted to Technical Committee ICT/-/1, Information systems co-ordination. A list of organizations represented on this committee can be obtained on request to its secretary. This publication does not purport to include all the necessary provisions of a contract. Users are responsible for its correct application. © The British Standards Institution 2017. Published by BSI Standards Limited 2017 ISBN 978 0 580 90961 0 ICS 35.100.70 Compliance with a British Standard cannot confer immunity from legal obligations. This British Standard was published under the authority of the Standards Policy and Strategy Committee on 31 March 2017. Amendments/corrigenda issued since publication Date Text affected BS ISO/IEC 20802-2:2016 INTERNATIONAL ISO/IEC STANDARD 20802-2 First edition 2016-12-15 Information technology — Open data protocol (OData) v4.0 Part 2: OData JSON Format Technologies de l'information — Protocole de données ouvertes (OData) v4.0 — Partie 2: Format OData JSON Reference number ISO/IEC 20802-2:2016(E) © ISO/IEC 2016 BS ISO/IEC 20802-2:2016 ISO/IEC 20802-2:2016(E) COPYRIGHT PROTECTED DOCUMENT © ISO/IEC 2016 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior written permission.
    [Show full text]
  • Supplement for Adapters DP Bridge, Hive, HTTP, JDBC, JMS, Mongodb, Odata, Salesforce.Com, Shapefile, and Successfactors Company
    PUBLIC SAP Data Services Document Version: 4.2 Support Package 12 (14.2.12.0) – 2020-02-06 Supplement for Adapters DP Bridge, Hive, HTTP, JDBC, JMS, MongoDB, OData, Salesforce.com, Shapefile, and SuccessFactors company. All rights reserved. All rights company. affiliate THE BEST RUN 2020 SAP SE or an SAP SE or an SAP SAP 2020 © Content 1 Naming Conventions......................................................... 5 2 Data Services adapters....................................................... 9 2.1 Adapter required knowledge and expertise...........................................11 3 Adapter installation and configuration...........................................12 3.1 Adding an adapter instance.....................................................13 3.2 Adapter Configuration options ...................................................14 JDBC adapter-specific configuration settings......................................19 DP Bridge runtime configuration options.........................................23 HTTP adapter specific configuration settings......................................24 JMS adapter-specific configuration settings.......................................25 3.3 Starting and stopping the adapter instance..........................................27 3.4 Monitoring the adapter instances and operations..................................... 28 3.5 Viewing adapter instance statistics................................................29 4 Creating an adapter datastore................................................. 31 5 Adapter datastore
    [Show full text]