The ISO Concept Database

1
(No Transcript)
2

• The ISO Concept Database
• Moscow, 15 August 2008
• Reinhard Weissinger
• ISO Central SecretariatGroup Manager, Project
  management e-services

3
Topics

• Use of databases for standards development in ISO
• TMB Group Standards as databases
• Why a Concepts database? (ISO/CDB)
• Functions expectations re. the ISO/CDB
• Implementation

4
Applicability of the DB approach

• Standard consists in full or in part of a
  collection of items, e.g.
• graphical symbols- terms and definitions-
  product properties- reference data of all
  types- classification systems- codes (for
  various types of objects)- units of
  measurements- etc.

5
Increasing use of DBs in standards development

• Results of surveys done by ISO Central
  Secretariat
• June 2005 Approximately 15 TCs/SCs
• June 2007 Over 40 TCs/SCs
• March 2006 First DIS disseminated in the form of
  a database (ISO/TC 61/SC 1 Plastics vocabulary)
  
• Standards written as  framework documents  with
  reference data maintained in external databases
• ? Emerging approach to standards development

6
Use of databases
Use type 1 For maintenance after development
Publication of a standard as a document
Approved Work Item
traditional
extraction
Database

development process

upload to

Use type 2 For development from scratch
development
Approved Work Item
storage of
concept status set to
Database
Database
proposed/draft concepts
 approved   standard 
7
Current use of databases by ISO committees

• Advantages
• Large number of items can be easier managed and
  maintained
• Consistency can be easier ensured
• Database tools readily available
• Challenges/problems
• Lack of support in terms of IT infrastructure
• Grass root developments
• Lack of compatibility (e.g. regarding data
  categories), maintenance problems
• Access modalities to content are unclear
• No integration in workflow processes

8
TMB AHG Standards as databases- Participation

• Committees represented in the TMB AHG
• ISO/IEC JTC 1 Information technology
• ISO/IEC JWG 1 Product classification
• ISO/TC 10/SC 10 Technical product documentation
• ISO/TC 23/SC 19 Agricultural electronics
• ISO/TC 29 Small tools
• ISO/TC 37 Terminology and other language and
  content resources
• ISO/TC 46 Information and documentation
• ISO/TC 61 Plastics
• ISO/TC 145 Graphical symbols
• ISO/TC 172 Optics and photonics
• ISO/TC 184/SC 4 Industrial automation
• ISO/TC 199 Safety of machinery
• ISO/TC 215 Health informatics
• IEC TC 3 Information structures, documentation
  and graphical symbols
• IEC Central Office
• Representatives from AFNOR, ANSI, BSI, DIN, JISC

9
TMB AHG Main output

• Generic procedure for the development and
  maintenance of standards in database format
  (approved by TMB in June 2007 Annex ST to ISO
  Supplement to the Directives)
• Specification of basic functions of a concept
  database (CDB)
• Initial data model for CDB
• Definition of four access layers related to
  different types of objects in the CDB including a
  public access layer allowing free access to some
  content (approved by CPSG in June 2007)

10
Why a  Concept  database?Concepts
Designations Referents/Objects
Unit of Thinking (Concept)
(Unit of Thought, Unit of Knowledge)
Referent (Concrete Object, Real Thing, Conceived
Object)

• Designation
• (Symbol, Sign,
• Term, Formula
• etc.)
• Different types of
• designations/representations

11
ISO/CDB Main functions expectations

• Hosts concepts, items already standardized
  or currently subject to standardization The
  repository for such content in ISO
• Cross standard cross committee visibility of
  standardized content or content currently under
  development
• Makes inconsistencies, overlaps visible ? Input
  for harmonization
• Supports a structured development process (e.g.
  workflows, version control for items etc.) and
  allows faster development/maintenance
• Integrated with existing IT infrastructure of ISO
  (e.g. role-based access control ISO/GD,
  balloting systems etc.)
• Integration with standards writing tools
  (XML-template project)
• End user access Subscription, download and
  API-access for customers businesses (with
  webstore-integration)
• Independent hosting by ISO members

12
ISO/CDB - Implementation

• Implementation time frame 2007 Q4 2009 Q1
  (first release for production)
• Cooperation agreement with external software
  partner Paradine (Austria) www.paradine.at

13
ISO/CDB (first prototype May 2008)Sample
screen (1)
14
ISO/CDB (first prototype May 2008)Sample
screen (2)
15
ISO/CDB (first prototype May 2008)Sample
screen (3)
16
ISO/CDB (first prototype May 2008)Sample
screen (4)
17
ISO/CDB (first prototype May 2008)Sample
screen (5)
18
ISO/CDB (first prototype May 2008)Sample
screen (6)