1. Does It Fit? Review of the Proposal for OLIF (version 2) DTD Christian Lieske SAP AG - GBU Application Integration – MultiLingual Technology

2. SAP AG 2001, Does it fit?, Christian Lieske 2 Introduction 0.Start to create and validate! 1.Foundations Design goals and decisions Suffixes for parameter entities Data category values as XML 2.High-level view Physical entities Example sections Special mechanisms 3.Low-level view 4.Discussion Issues/loose ends Bugs Enhancement/change requests

3. SAP AG 2001, Does it fit?, Christian Lieske 3 Start to Create and Validate! The OLIF DTD can already be used to create entries with a structure editor validate data

4. SAP AG 2001, Does it fit?, Christian Lieske 4 Foundations

5. SAP AG 2001, Does it fit?, Christian Lieske 5 Design Goals and Decisions 1.Stay close to the prose description Strive for identifical naming in both description and formalization 2.Provide legible, consistent and clear formalization Model identical state-of-affairs the same way; refrain from surrogate representations; uniform representation of data categories as elements 3.Support maintenance and customization Modularize overall solution and write extensive documentation 4.Allow easy implementation Refrain from use of very recent technologies (e.g. Xlink and Resource Description Format) 5.Advance quickly Postpone time-consuming issues (e.g. non-compromising solution to free order of elements and alternative content) 6.Use flexible representation formalism Work with DTD rather than XML schema

6. SAP AG 2001, Does it fit?, Christian Lieske 6 Suffixes for Parameter Entities 1..att for attributes 2..pcd.mix for PCDATA content models 3..olif.fix for list of mandatory OLIF values 4..olif.pending for list of OLIF values pending approval %semReading.user.ext; 5..user.ext for user extensible content models %ptOfSpeech.user.ext; As indicated in the examples, suffixes can be concatenated.

7. SAP AG 2001, Does it fit?, Christian Lieske 7 Data Category Values as XML Creation and checking of OLIF is facilated by machine-readable representations (XML) of all allowed or recommended values

8. SAP AG 2001, Does it fit?, Christian Lieske 8 High-level View

9. SAP AG 2001, Does it fit?, Christian Lieske 9 Physical Entities The OLIF DTD is spread over 3 different levels header resourcesbody noun, verb,... abb, accr,... olifShareRV.mo d olif.dtd olifHeader.mo d olifShareR.mo d olifBody.mod olifBodyV.mo d olifHeaderV.mo d Driver Structure Values

10. SAP AG 2001, Does it fit?, Christian Lieske 10 Example Sections – contentInfo The contentInfo element explicitly states which choices have been made wrt. representation of content (e.g. retention of quotation marks); in addition, it can state default values for certain data categories (DCs)

11. SAP AG 2001, Does it fit?, Christian Lieske 11 Example Sections - entry An individual OLIF entry contains 3 data groups, and can be identified by means of different identifiers

12. SAP AG 2001, Does it fit?, Christian Lieske 12 Example Sections – mono Monolingual information consists of mandatory key data categories, as well as optional additional monolingual DCs, and additional general DCs

13. SAP AG 2001, Does it fit?, Christian Lieske 13 Example Sections – monoDC In order to reflect relationships, the optional additional monolingual data categories have been grouped according to functionality/linguistic level

14. SAP AG 2001, Does it fit?, Christian Lieske 14 Special Mechanisms For user extensions, 2 mechanisms exist: 1.DTD customization %ptOfSpeech.user.ext; 2.Data category specifications <!ELEMENT dataCatReg (inflectionDCS?,inflectionDCS ptOfSpeechDCS?,ptOfSpeechDCS subjFieldDCS?,subjFieldDCS semReadingDCS?,semReadingDCS semTypeDCS? )semTypeDCS

15. SAP AG 2001, Does it fit?, Christian Lieske 15 Low-level View

16. SAP AG 2001, Does it fit?, Christian Lieske 16 Low-level View - Header The header contains general administrative information, and pointers to supplementary information

17. SAP AG 2001, Does it fit?, Christian Lieske 17 Low-level View – Header Attributes

18. SAP AG 2001, Does it fit?, Christian Lieske 18 Low-level View – File Description

19. SAP AG 2001, Does it fit?, Christian Lieske 19 Low-level View – Distributor

20. SAP AG 2001, Does it fit?, Christian Lieske 20 Low-level View – Owner

21. SAP AG 2001, Does it fit?, Christian Lieske 21 Low-level View – Data Category Specifiations

22. SAP AG 2001, Does it fit?, Christian Lieske 22 Low-level View – Choices and Defaults

23. SAP AG 2001, Does it fit?, Christian Lieske 23 Low-level View – Workflow and Miscellaneous

24. SAP AG 2001, Does it fit?, Christian Lieske 24 Low-level View – Entries

25. SAP AG 2001, Does it fit?, Christian Lieske 25 Low-level View – General Data Categories

26. SAP AG 2001, Does it fit?, Christian Lieske 26 Low-level View – Cross-references

27. SAP AG 2001, Does it fit?, Christian Lieske 27 Low-level View - Transfer

28. SAP AG 2001, Does it fit?, Christian Lieske 28 Discussion 1.Issues/Loose Ends Encode language information via xml:lang Promote recommanded values to fixed values Decide on structure for shared resources Decide on structure for workflow information Resource Description Format schema for description data category specifications 2.Bugs 3.Enhancements/Change Requests