XBRL Taxonomy Engineering. Definition of XBRL Taxonomy Development Process Model

The growing number of eXtensible Business Reporting Language (XBRL) projects around the world and strong interest from bodies such as Security Exchange Commission in the United States (SEC), Central European Banking Supervisors in the European Union (CEBS) or International Accounting Standards Board (IASB) in building XBRL taxonomies demonstrate the need for formalisation and methodical approach to the process of the XBRL taxonomy development. Although many approaches exist in favour of software engineering and knowledge engineering, building an XBRL taxonomy is not about creating a software product or a knowledge-based system. It is creating a standardised taxonomy for a particular domain in order to enable standardised exchange of business reports. Nevertheless experiences learned from software and knowledge engineering areas are very useful for what can be called XBRL taxonomy engineering. On the other hand a clear parallel with the ontology engineering appears treating XBRL taxonomies as ontologies. The ontology development process could resemble in many aspects the way that XBRL taxonomies are created. The development process models presented in the literature are either project or software driven. Hence it is difficult to apply them as a generic and formal taxonomy development process model. This paper presents an approach to define a taxonomy development process model. The definition of the model is preceded with the status quo analysis of the existing development models known from software engineering and ontology engineering domains. The model definition itself is also based on empirical analysis of taxonomy development projects.

[1]  Steve G. Sutton,et al.  Enterprise systems and the re-shaping of accounting systems: A call for research , 2006, Int. J. Account. Inf. Syst..

[2]  Michael Gruninger,et al.  Methodology for the Design and Evaluation of Ontologies , 1995, IJCAI 1995.

[3]  Guus Schreiber,et al.  Knowledge Engineering and Management: The CommonKADS Methodology , 1999 .

[4]  Asunción Gómez-Pérez,et al.  Methodologies, tools and languages for building ontologies: Where is their meeting point? , 2003, Data Knowl. Eng..

[5]  Steffen Staab,et al.  Knowledge Processes and Ontologies , 2001, IEEE Intell. Syst..

[6]  Asunción Gómez-Pérez,et al.  Building a chemical ontology using Methontology and the Ontology Design Environment , 1999, IEEE Intell. Syst..

[7]  Julie E. Kendall,et al.  Systems analysis and design , 1981 .

[8]  Daniel D. McCracken,et al.  Life cycle concept considered harmful , 1982, ACM SIGSOFT Softw. Eng. Notes.

[9]  Ieee Standards Board IEEE Standard for developing software life cycle processes , 1992 .

[10]  Richard E. Fairley,et al.  Software engineering concepts , 1985, McGraw-Hill series in software engineering and technology.

[11]  York Sure-Vetter,et al.  On-To-Knowledge Ontology based Knowledge Management Tools and their Application , 2002, Künstliche Intell..

[12]  Morgan Stanley,et al.  XBRL Taxonomy Recognition Process , 2007 .

[13]  Stefan Baldi,et al.  Grundlagen der Wirtschaftsinformatik , 1999 .

[14]  Gustav Pomberger,et al.  Software Engineering - Prototyping und objektorientierte Software-Entwicklung , 1993 .

[15]  Dieter Fensel,et al.  Knowledge Engineering: Principles and Methods , 1998, Data Knowl. Eng..