1. World e-Parliament Conference 2016
#eParliament
28-30 June 2016 // Chamber of Deputies of Chile // Valparaiso
Connecting data and
document
Hungarian National Assembly

2.  Mr. Tóth János
– Head of IT internal development and customer
services

3. Parliamentary worklow

4. Legislative Documents
 Proposal
 Proposed amendment
 Comittee decisions, minutes
 Agenda
 Voting result
 Unified proposal
 Verbatim report

5. Meta data
 Type of document
– And its connected documents
 Initiator, author
 Events
– Type of event (filling in, debate, decisions)
– Time of event
 Text
– Original scanned version (non-editable OCR pdf)
– Editable Word document
– Something else

6. Supporting document
 Scheduling calendar
– deadlines
 Invitations
 Cover letters
 Explanations and expert opinions

7. RDBS or XML

8. Software elements
 Internal developed PL/SQL functions, how
to print static/dynamics columname,
rownames, cells)
– Tableprint
– Tablerowprint
– Matrixprint
 Apache projects (XML, Graphics)
– XALAN: XML to HTML
– FOP: XML to PDF (PS, PCL, PNG, etc)

9. Sample matrixprint
Question
addressed to
Ruling parties Opposition
Independent Total
Party1 Party2 Total Party3 Party4 Party5 Total
Prime Minister
0 7 11 5 16 1 17
Minister of
Internal Affairs
14 1 15 17 25 12 37 52
Minister of
Justice
3 3 2 9 1 10 13
Minister of
Defense
6 6 10 4 4 10
Minister of
Foreign Affaris
7 1 8 6 15 2 17 1 26
Minister of
Finance
6 2 8 12 11 4 15 1 24
Total
36 4 40 54 75 24 99 3 142

10. RDBS vs. XML
Relational Database
Systems
 Static Schema
 Any relationship
 Set-oriented-order unimportant
 Ready to use after query
XML
 Self-describing Volatile schema
 „Human readable”
 Hierarchical
 Sequence-oriented-order
important
 It must parse before use
 Null data problems

11. RDBS vs. XML
RDBS
 Better for
– Handling large volumens of
data in the same system
– When downstream processing
of data is relational (data
warehouse, olap, statistics,
data-visualisation)
– When the highest possible
performance is required
– Fast transactions, when lot of
users working on the same
data
– Naturally tabular data
XML
 Better for
– Low-volume data is highly
structured
– Machine to machne
communication
• web-services, API
• Component of distributed
systems
– Content Management
System
– Easy to design

12. Hungarian explaples
 RDBS (Oracle 12c):
– Store all the metadata of documents, events etc.
– Controlling the legislation workflow
 XML
– Store for MP’s declaration of property
– Interface beetween internal and external systems
• MP’s allowances provided by the finance system
• Open-data WEB-API interface on the website
– Mobil applications

13. WEB-API extension

14. Summary
 RDBS vs. XML
– No winner
– Complementary to each other
– Always depends from the queries
 What about others?
– MongoDB
– JSON

15. Bibliograpy
 http://www.rpbourret.com/xml/XMLAndDatabases.htm
 http://xml.coverpages.org/IBM-XML-GC34-2497.pdf
 http://www.room4me.com/index.php?
option=com_content&view=article&id=8:xmlvsdb&catid=2:technology
 http://c2.com/cgi/wiki?AlternativesToXml

16. THANK YOU!
Janos.toth@parlament.hu