1 / 9

XBRL Panel -- Bill McCarthy

XBRL Panel -- Bill McCarthy. Researcher (?) Professor of Accounting at Michigan State University more IT than accounting more design science than empirical Business Process standards worker Topics: ebXML progress and fit with XBRL Research opportunities Design science Empirical science.

bill
Télécharger la présentation

XBRL Panel -- Bill McCarthy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. XBRL Panel -- Bill McCarthy • Researcher (?) • Professor of Accounting at Michigan State University • more IT than accounting • more design science than empirical • Business Process standards worker • Topics: • ebXML progress and fit with XBRL • Research opportunities • Design science • Empirical science

  2. FSA & ELOISE (KEE & Lisp) knowledge structures semantic modeling in DB, AI, OO AA-AI group work on EDGAR in 86-87 Semantic nets for text Chart of accounts • Semantic Modeling • transactions & commitments • reporting • controls • XBRL • reporting • transactions • controls Origins of my (biased) views

  3. Comparison & connection of ebXML (UN/CEFACT) with XBRL (AICPA) • ebXML progress – Fast start but slow progress and migration (OASIS, OAG, OMG) • Some specs progress to ISO • BP catalog & classification  repository • Business process semantics & choreography • BP metamodel • Business entities (states) & collaboration patterns • ebXML stack • Connection with XBRL • Bill for one year • UN/CEFACT – not much

  4. Research Opportunities – (DS) • XBRL & other XML initiatives are exciting & hard topics (don’t come in with weak skills) • Design Science = building (constructs, models, methods, instantiations) and evaluating (same) HMPR link • DS opportunities • Building of new design artifacts for XBRL (tools, taxonomies) • Evaluating of existing artifacts (XLink, taxonomies, best methods & practices, instantiations)

  5. Research Opportunities – II (empirical) • Traditional Financial reporting with new decision scenarios for analysts & investors • Instant Compustat & other data aggregators • New tool & technology use • Other reporting issues (access accounting, interactive data) • Opportunity not yet ripe but will be soon (AAA report) • XBRL G/L uses • G/L to G/L • Other projected uses ? • New use of G/L • Transaction level interoperability • Other new XBRL use

  6. Research Opportunities – A Final Note • Opportunities in both design and empirical, but beware of establishment biases • Research obligations (?) • Unbounded optimism about adoption is part of the XML landscape, and it is fine for XBRL.org and the AICPA • “Why so few faculty opponents ?” • Heavy learning curve • Non open development process (ODP) makes criticism hard for researchers • Skeptics are hard to identify & quote • Nothing in XBRL needs fixing

  7. UN/CEFACT BP stack back Business Domain View (BDV) Business Area Process Area Business Process ** Business Requirements View (BRV) Agreement Business Collaboration (binary or multiparty) Partner Economic Resources Economic Event *** Business Transaction View (BTV) Requesting Business Activity Authorizing Roles Business Transaction * Responding Business Activity Business Documents Business Service View (BSV) Requesting Service Transaction Business Messages Network Component Responding Service Transaction Source: ebXML TMWG

  8. Environment IS Research Knowledge Base Relevance Rigor • People • Roles • Capabilities • Characteristics • Organizations • Strategies • Structure & Culture • Processes • Technology • Infrastructure • Applications • Communications Architecture • Development Methodologies • Foundations • Theories • Frameworks • Instruments • Constructs • Models • Methods • Instantiations • Methodologies • Data Analysis Techniques • Formalisms • Measures • Validation Criteria • Develop / Build • Theories • Artifacts* Applicable Knowledge Business Needs Assess Refine • Justify / Evaluate • Analytical • Case Study • Experimental • Field Study • Simulation Application in the Appropriate Environment Additions to the Knowledge Base [SOURCE: Hevner, March, Park, and Ram, MISQ, 2004] *artifacts = constructs, models, methods, instantiations

  9. Designed IT Artifacts • Purposes • Improve organizational performance • To make things "as they ought to be." • Objects • Constructs (E-R, OO, BWW, Agents) • Models (Patterns, KR, REA Template) • Methods (SA&D Techniques, CSF, DA) • Instantiations (ES, Vigilant, Emergent KP) • Actions • Build • Evaluate back [SOURCE: Sal March Speech at Gordon Davis Symposium (May 2005)]

More Related