Neos CMS Documentation Release Dev-Master

Total Page:16

File Type:pdf, Size:1020Kb

Neos CMS Documentation Release Dev-Master Neos CMS Documentation Release dev-master The Neos Team June 05, 2015 Contents 1 Getting Started 3 1.1 Installation..............................................3 1.2 User Interface Basics.........................................4 2 Integrator Guide 11 2.1 Content Structure........................................... 11 2.2 Rendering A Page.......................................... 27 2.3 Inside TypoScript........................................... 28 2.4 Eel, FlowQuery and Fizzle...................................... 35 2.5 Adjusting Neos Output........................................ 39 2.6 Creating Custom Content Elements................................. 44 2.7 Content Cache............................................ 51 2.8 Node Type Constraints........................................ 56 2.9 Creating a plugin........................................... 57 2.10 Interaction with the Neos backend.................................. 60 2.11 Content Dimensions......................................... 61 2.12 Data sources............................................. 64 3 Integrators Cookbook 67 3.1 Wrapping a List of Content Elements................................ 67 3.2 Creating a simple Content Element................................. 68 3.3 Customizing the Inspector...................................... 70 3.4 Selecting a Page Layout....................................... 72 3.5 Changing the Body Class with a condition............................. 73 3.6 Rendering a Menu.......................................... 74 3.7 Integrating a JavaScript-based slider................................. 75 3.8 Rendering a Meta-Navigation.................................... 77 3.9 Editing a shared footer across all pages............................... 78 3.10 Extending the Page.......................................... 79 3.11 Rendering special formats (CSV, JSON, XML, ...)......................... 80 3.12 Adding A Simple Contact Form................................... 81 3.13 Creating a Plugin........................................... 83 3.14 Translating content.......................................... 83 4 Developer Guide 85 4.1 User Interface Development..................................... 85 4.2 Testing................................................ 94 4.3 Development............................................. 97 5 Appendixes 99 5.1 Neos Command Reference...................................... 99 5.2 Eel Helpers Reference........................................ 106 5.3 FlowQuery Operation Reference................................... 128 i 5.4 Media ViewHelper Reference.................................... 134 5.5 Neos TypoScript Reference..................................... 137 5.6 Neos ViewHelper Reference..................................... 149 5.7 Release Notes............................................ 162 6 Contributors 181 7 Indices and tables 185 ii Neos CMS Documentation, Release dev-master TYPO3 Neos is a free enterprise web content management system licensed under the GPL. This version of the documentation covering Neos dev-master has been rendered at: June 05, 2015 Contents 1 Neos CMS Documentation, Release dev-master 2 Contents CHAPTER 1 Getting Started 1.1 Installation Tip: TYPO3 Neos is built on top of the TYPO3 Flow framework. If you run into technical problems, keep in mind to check the TYPO3 Flow documentation for possible hints as well. 1.1.1 Requirements TYPO3 Neos has at least the same system requirements as TYPO3 Flow. You can find them in the TYPO3 Flow Requirements Documentation. 1.1.2 Fundamental Installation 1. First you need to install the dependency manager Composer (if you don’t have it already): curl -sS https://getcomposer.org/installer | php By issuing this command Composer will get downloaded as composer.phar to your working directory. If you like to have composer installed globally, you can simply move it to a directory within your $PATH environment. mv composer.phar /usr/local/bin/composer Note: If you are on Windows please refer to the offical documentation on how to install Composer on Windows 2. Go to your htdocs directory and create a new project based on the TYPO3 Neos base distribution: cd /your/htdocs/ php /path/to/composer.phar create-project typo3/neos-base-distribution TYPO3-Neos Composer will take care of downloading all dependencies for running your TYPO3 Neos installation to the directory TYPO3-Neos. You can safely delete the vcs files by answering ‘Y’ to the question ‘Do you want to remove the existing VCS (.git, .svn..) history? [Y,n]?’. 3. Next set up a virtual host inside your Apache configuration. Set the DocumentRoot to the Web directory inside the TYPO3 Neos installation. NameVirtualHost *:80 # if needed <VirtualHost *:80> DocumentRoot "/your/htdocs/TYPO3-Neos/Web/" # enable the following line for production context 3 Neos CMS Documentation, Release dev-master #SetEnv FLOW_CONTEXT Production ServerName neos.demo </VirtualHost> Make sure that the mod_rewrite module is loaded and restart apache. For further information on how to set up a virtual host with apache please refer to the Apache Virtual Host documentation. 4. Add an entry to /etc/hosts to make your virtual host reachable: 127.0.0.1 neos.demo Make sure to use the same name you defined in ServerName in the virtual host configuration above. 5. Set file permissions as needed so that the installation is read- and writeable by the webserver’s user and group: sudo ./flow core:setfilepermissions john www-data www-data Replace john with your current username and www-data with the webserver’s user and group. For detailed instructions on setting the needed permissions see TYPO3 Flow File Permissions Note: Setting file permissions is not necessary and not possible on Windows machines. For Apache to be able to create symlinks, you need to use Windows Vista (or newer) and Apache needs to be started with Administrator privileges. 6. Now go to http://neos.demo/setup and follow the on-screen instructions. 1.1.3 The TYPO3 Neos Setup Tool 1. A check for the basic requirements of TYPO3 Flow and Neos will be run. If all is well, you will see a login screen. If a check failed, hints on solving the issue will be shown and you should fix what needs to be fixed. Then just reload the page, until all requirements are met. 2. The login screen will tell you the location of a file with a generated password. Keep that password in some secure place, the generated file will be removed upon login! It is possible to have a new password rendered if you lost it, so don’t worry too much. 3. Fill in the database credentials in the first step. The selector box will be updated with accessible databases to choose from, or you can create a new one. Tip: Configure your MySQL server to use the utf8_unicode_ci collation by default if possible! 4. In the next step a user with administrator privileges for editing with TYPO3 Neos is created. 5. The following step allows you to import an existing site or kickstart a new site. To import the demo site, just make sure it is selected in the selector box and go to the next step. To kickstart a new site, enter a package and site name in the form before going to the next step. If you are new to Neos, we recommend to import the existing demo site so you can follow the next section giving you a basic tour of the user interface. 6. If all went well you’ll get a confirmation the setup is completed, and you can enter the frontend or backend of your Neos website. 1.2 User Interface Basics 1. Toggle button for the Menu 2. The Navigate component 4 Chapter 1. Getting Started Neos CMS Documentation, Release dev-master 3. The Edit/Preview Panel 4. The Page tree 5. Publish button(s) 6. The Property Inspector 7. The Structure tree 8. The content canvas 9. Discard / Apply changes 1.2.1 Toggle button for the Menu Show or hide the Module Menu using this button. 1.2.2 The Navigate component Using the Navigate component you can conveniently find your way through your contents. See ‘The Page tree’. 1.2.3 The Edit/Preview Panel The Edit/Preview Panel gives you the possibility to switch between the (default) ‘In Place’ editing mode to and from the ‘Raw Content’ editing mode. It also contains the Preview section where you can choose between customizable presentation modes, i.e. a print style and a default Desktop style. 1.2. User Interface Basics 5 Neos CMS Documentation, Release dev-master 6 Chapter 1. Getting Started Neos CMS Documentation, Release dev-master 1.2. User Interface Basics 7 Neos CMS Documentation, Release dev-master Fig. 1.1: The TYPO3 Neos start page 8 Chapter 1. Getting Started Neos CMS Documentation, Release dev-master 1.2.4 The Page tree The Page tree is filterable and searchable and can be edited inline. 1.2.5 Publish button(s) These publication buttons aggregate your changes which you can publish at your chosen time. 1.2.6 The Property Inspector The Property Inspector gives you detailed property editing options for the chosen nodetype, whether this be a page or a content element. 1.2.7 The Structure tree The Structure tree is a nodetype tree which gives you detailed information of how your content is structured. It gives you information about which type, its position and its nesting level. This can also be used to navigate the content of a page. 1.2.8 The content canvas The content canvas is where you can add/edit your content. 1.2. User Interface Basics 9 Neos CMS Documentation, Release dev-master 1.2.9 Discard / Apply changes TYPO3 Neos saves your changes on the fly as much as possible. When editing properties you must apply or discard
Recommended publications
  • What Is Aloha Editor? What Aloha Editor Is NOT! Why the HTML5
    06.12.11 Aloha Editor - HTML5 WYSIWYG Editor Features Plugins About Forum Try it Developer Wiki API What is Aloha Editor? Aloha Editor Core Developer Aloha Editor is a semantic Rich Text Editor framework written in Javascript with best support of xHTML5. You can Haymo Meran integrate it in a CMS, blog, wiki software or any other Project leader project where you need to edit content with a web based Italy (South Tirol) tool. Use it like a supersonic textarea. You can edit Clemens Prerovsky almost any DOM element with this supersonic textarea, but Javascript Guru you need to care about configuration and storage. Austria What Aloha Editor is NOT! Nicolas Karageuzian Aloha Editor is NOT a HTML Editor to install on a desktop nor it is a CMS. Javascript Wizard France Why the HTML5 Editor? Thomas Lété Aloha Editor works perfectly in all current Speed and browsers and websites using HTML4! It is optimisations Guru. the HTML5 Editor because it implements Belgium all functionality respecting with no compromise the HTML5 specification. It Norbert Pomaroli aims to generate full compliant xHTML5 content, but you don't need to Javascript Guru use HTML5 specific methods, if you don't want to. The Aloha Editor uses Austria and extends the attribute contenteditable, which was introduced in the HTML standard with version 5. Most current browsers support that Petro Salema attribute, but their implementation is inconsitent due to erroneous Javascript Guru implementations and the lack of detail of the HTML5 specification when it Tanzania comes to DOM manipulation. Aloha Editor makes contenteditable useable.
    [Show full text]
  • Tecnologías Libres Para La Traducción Y Su Evaluación
    FACULTAD DE CIENCIAS HUMANAS Y SOCIALES DEPARTAMENTO DE TRADUCCIÓN Y COMUNICACIÓN Tecnologías libres para la traducción y su evaluación Presentado por: Silvia Andrea Flórez Giraldo Dirigido por: Dra. Amparo Alcina Caudet Universitat Jaume I Castellón de la Plana, diciembre de 2012 AGRADECIMIENTOS Quiero agradecer muy especialmente a la Dra. Amparo Alcina, directora de esta tesis, en primer lugar por haberme acogido en el máster Tecnoloc y el grupo de investigación TecnoLeTTra y por haberme animado luego a continuar con mi investigación como proyecto de doctorado. Sus sugerencias y comentarios fueron fundamentales para el desarrollo de esta tesis. Agradezco también al Dr. Grabriel Quiroz, quien como profesor durante mi último año en la Licenciatura en Traducción en la Universidad de Antioquia (Medellín, Colombia) despertó mi interés por la informática aplicada a la traducción. De igual manera, agradezco a mis estudiantes de Traducción Asistida por Computador en la misma universidad por interesarse en el software libre y por motivarme a buscar herramientas alternativas que pudiéramos utilizar en clase sin tener que depender de versiones de demostración ni recurrir a la piratería. A mi colega Pedro, que comparte conmigo el interés por la informática aplicada a la traducción y por el software libre, le agradezco la oportunidad de llevar la teoría a la práctica profesional durante todos estos años. Quisiera agradecer a Esperanza, Anna, Verónica y Ewelina, compañeras de aventuras en la UJI, por haber sido mi grupo de apoyo y estar siempre ahí para escucharme en los momentos más difíciles. Mis más sinceros agradecimientos también a María por ser esa voz de aliento y cordura que necesitaba escuchar para seguir adelante y llegar a feliz término con este proyecto.
    [Show full text]
  • Revisiting XSS Sanitization
    Revisiting XSS Sanitization Ashar Javed Chair for Network and Data Security Horst G¨ortzInstitute for IT-Security, Ruhr-University Bochum [email protected] Abstract. Cross-Site Scripting (XSS) | around fourteen years old vul- nerability is still on the rise and a continuous threat to the web applica- tions. Only last year, 150505 defacements (this is a least, an XSS can do) have been reported and archived in Zone-H (a cybercrime archive)1. The online WYSIWYG (What You See Is What You Get) or rich-text editors are now a days an essential component of the web applications. They allow users of web applications to edit and enter HTML rich text (i.e., formatted text, images, links and videos etc) inside the web browser window. The web applications use WYSIWYG editors as a part of comment functionality, private messaging among users of applications, blogs, notes, forums post, spellcheck as-you-type, ticketing feature, and other online services. The XSS in WYSIWYG editors is considered more dangerous and exploitable because the user-supplied rich-text con- tents (may be dangerous) are viewable by other users of web applications. In this paper, we present a security analysis of twenty five (25) pop- ular WYSIWYG editors powering thousands of web sites. The anal- ysis includes WYSIWYG editors like Enterprise TinyMCE, EditLive, Lithium, Jive, TinyMCE, PHP HTML Editor, markItUp! universal markup jQuery editor, FreeTextBox (popular ASP.NET editor), Froala Editor, elRTE, and CKEditor. At the same time, we also analyze rich-text ed- itors available on very popular sites like Twitter, Yahoo Mail, Amazon, GitHub and Magento and many more.
    [Show full text]
  • Prioritizing Pull Requests
    Prioritizing pull requests Version of June 17, 2015 Erik van der Veen Prioritizing pull requests THESIS submitted in partial fulfillment of the requirements for the degree of MASTER OF SCIENCE in COMPUTER SCIENCE by Erik van der Veen born in Voorburg, the Netherlands Software Engineering Research Group Q42 Department of Software Technology Waldorpstraat 17F Faculty EEMCS, Delft University of Technology 2521 CA Delft, the Netherlands The Hague, the Netherlands www.ewi.tudelft.nl www.q42.com c 2014 Erik van der Veen. Cover picture: Finding the pull request that needs the most attention. Prioritizing pull requests Author: Erik van der Veen Student id: 1509381 Email: [email protected] Abstract Previous work showed that in the pull-based development model integrators face challenges with regard to prioritizing work in the face of multiple concurrent pull requests. We identified the manual prioritization heuristics applied by integrators and ex- tracted features from these heuristics. The features are used to train a machine learning model, which is capable of predicting a pull request’s importance. The importance is then used to create a prioritized order of the pull requests. Our main contribution is the design and initial implementation of a prototype service, called PRioritizer, which automatically prioritizes pull requests. The service works like a priority inbox for pull requests, recommending the top pull requests the project owner should focus on. It keeps the pull request list up-to-date when pull requests are merged or closed. In addition, the service provides functionality that GitHub is currently lacking. We implemented pairwise pull request conflict detection and several new filter and sorting options e.g.
    [Show full text]
  • USER MANUAL PROJECT WEBSITES Version 2 March 2017 TAKING COOPERATION FORWARD
    USER MANUAL PROJECT WEBSITES Version 2 March 2017 TAKING COOPERATION FORWARD Content INTRODUCTION ........................................................................................... 4 HOW TO USE THIS MANUAL ............................................................................ 5 A. ACCESS AND USER PROFILE ......................................................................... 6 A.1. Log in ......................................................................................... 6 A.2. User profile .................................................................................. 6 A.3. Interface ..................................................................................... 8 B. WORKING WITH CMS ................................................................................10 B.1. Working with folders ......................................................................10 B.1.1. Folder structure and view ........................................................11 B.1.2. Creating folder .....................................................................12 B.1.3. Renaming folder ...................................................................13 B.1.4. Moving folder ......................................................................13 B.1.5. Deleting folder .....................................................................14 B.1.6. Order of folders ...................................................................14 B.2. Working with pages ........................................................................15
    [Show full text]
  • Website and Ektron 9.1
    WEBSITE AND EKTRON 9.1 TRAINING AND REFERENCE DOCUMENTATION Created by Hendrix College 1 Last updated September 18, 2014 TABLE OF CONTENTS Introduction ................................................................................................................................................................... 7 Your role in the Hendrix website ............................................................................................................................... 7 Orientation .................................................................................................................................................................... 8 Parts of a web page ................................................................................................................................................... 8 Page Content ......................................................................................................................................................... 8 Section Menu ......................................................................................................................................................... 8 Header and Footer ................................................................................................................................................. 8 Types of Content........................................................................................................................................................ 8 Content .................................................................................................................................................................
    [Show full text]
  • Best of a Decade on Opensource.Com 2010–2019
    Best of a decade on Opensource.com 2010–2019 In celebration of our 10-year anniversary Opensource.com/yearbook FROM THE EDITOR ............................. FROM THE EDITOR ............................. Dear reader, As we celebrate 10 years of publishing, our focus is on the people from all over the globe, in various roles, from diverse backgrounds, who have helped us explore the multitude of ways in which open source can improve our lives—from technology and programming to farming and design, and so much more. We are celebrating you because we’ve learned that growing this unique storytelling site demands that we do one thing better than all the rest: listen to and talk with our readers and writers. Over the years, we’ve gotten better at it. We regularly hold meetings where we review how articles performed with readers from the week before and discuss why we think that’s so. We brainstorm and pitch new and exciting article ideas to our writer community on a weekly basis. And we build and nurture close relationships with many writers who publish articles for us every month. As an editor, I never would have imagined my biggest responsibility would be community management and relationship building over copy editing and calendar planning. I’m so grateful for this because it’s made being a part of Opensource.com a deeply rewarding experience. In December, we closed out a decade of publishing by reaching a new, all-time record of over 2 million reads and over 1 million readers. For us, this validates and affirms the value we’ve learned to place on relationships with people in a world swirling with metrics and trends.
    [Show full text]
  • Social Media Apps Programming Mobile Apps Using HTML5/CSS3/Javascript
    Tamkang University Social Media Apps Programming Mobile Apps Using HTML5/CSS3/JavaScript 1041SMAP05 TLMXM1A (8687) (M2143) (Fall 2015) (MIS MBA) (2 Credits, Elec9ve) [Full English Course] Wed 9,10 (16:10-18:00) B310 Min-Yuh Day, Ph.D. Assistant Professor Department of Informaon Management Tamkang University h?p://mail.tku.edu.tw/myday 2015-10-14 Course Schedule (1/3) Week Date Subject/Topics 1 2015/09/16 Course Orientaon and Introduc9on to Social Media and Mobile Apps Programming 2 2015/09/23 Introduc9on to Android / iOS Apps Programming 3 2015/09/30 Developing Android Nave Apps with Java (Android Studio) (MIT App Inventor) 4 2015/10/07 Developing iPhone / iPad Nave Apps with Swia (XCode) 5 2015/10/14 Mobile Apps using HTML5/CSS3/JavaScript 6 2015/10/21 jQuery Mobile 2 Course Schedule (2/3) Week Date Subject/Topics 7 2015/10/28 Create Hybrid Apps with Phonegap 8 2015/11/04 jQuery Mobile/Phonegap 9 2015/11/11 jQuery Mobile/Phonegap 10 2015/11/18 Midterm Exam Week (Midterm Project Report) 11 2015/11/25 Case Study on Social Media Apps Programming and Marke9ng in Google Play and App Store 12 2015/12/02 Google Cloud Plaorm 3 Course Schedule (3/3) Week Date Subject/Topics 13 2015/12/09 Google App Engine 14 2015/12/16 Google Map API 15 2015/12/23 Facebook API (Facebook JavaScript SDK) (Integrate Facebook with iOS/Android Apps) 16 2015/12/30 Twi?er API 17 2016/01/06 Final Project Presentaon 18 2016/01/13 Final Exam Week (Final Project Presentaon) 4 Outline • Mobile Apps • HTML5 – Hyper Text Markup Language (version 5)(2014) – Content and Structure
    [Show full text]
  • A2040-442 Exam Dumps with Real Exam Questions
    IBM A2040-442 Assessment- IBM Notes and Domino Fundamentals http://killexams.com/exam-detail/A2040-442 QUESTION: 185 What can an IBM Domino administrator use instead of creating multiple explicit policy documents? A. Server grouppolicies B. Dynamic group policies C. Database group policies D. Intra-domain group policies Answer: A QUESTION: 186 How can an IBM Domino administrator provide access to a help desk team to only modify Person documents in the Domino Directory? A. by giving Editor access in the ACL of the Domino Directory B. by giving Editor access in the ACL of the Domino Directory and checking the User Modifier Role C. by giving Author access in the ACL of the Domino Directory and checking the UserModifier Role D. by giving Editor access in the ACL of the Domino Directory and adding Administrator Access in security tab of the Server document Answer: C QUESTION: 187 How can Cheryl be sure that her Recent Contacts has the most up-to-date information? A. She must manually update the entry in Recent Contacts B. Recent Contacts are automatically maintained with up-to-date detail C. She must use the name in an email chat or calendar entry in order for an update to occur D. She should select to synchronize Recent Contacts with her server's directory on the replication page Answer: B 62 QUESTION: 188 When a Rich Text Core Control is rendered in a browser what technology is used? A. ckEditor B. TinyMCE C. WYMeditor D. Aloha Editor Answer: A Reference: http://www- 10.lotus.com/ldd/ddwiki.nsf/dx/CKEditor_in_XPages_in_NotesDomino_8.5.2 QUESTION: 189 What are two platforms that IBM Domino server supports? A.
    [Show full text]
  • Advanced Features of Collaborative Semantic Annotators -- the 4A System
    Proceedings of the Twenty-Eighth International Florida Artificial Intelligence Research Society Conference Advanced Features of Collaborative Semantic Annotators — The 4A System Pavel Smrz and Jaroslav Dytrych Brno University of Technology, Faculty of Information Technology, IT4Innovations Centre of Excellence Bozetechova 2, 612 66 Brno, Czech Republic Email: fsmrz,idytrychg@fit.vutbr.cz Abstract museum professionals involved in the project. Yet, the 4A framework is generally applicable in other knowledge engi- This paper deals with collaborative knowledge engineering, particularly focusing on collective editing and semantic an- neering contexts, e.g., for biomedical text annotation. notation of hypertext. It discusses state-of-the-art functions of There are three particular cases in which the preferable the 4A (Annotations Anywhere, Annotations Anytime) sys- text mining scenario cannot be (fully) applied. First, a vari- tem that has been recently extended to be applicable in a ability of natural language constructs to express a seman- broad range of annotation contexts. We introduce advanced tic relation can be high and there can be insufficient data to features and recent improvements that make the tool unique train a machine learning model. For example, relations of in many aspects. A special attention is paid to the social way artistic influences (among artists, artworks, themes, styles, of semantic tagging – complex annotations can be created by techniques, places, etc.) have been studied within the DECI- a single click and immediately shared with other interested PHER project and it showed up that despite the effort, ex- users or reused by external systems. We also compare the 4A system to similar software solutions and show their similari- pressions such as pays tribute/homage to are not well cov- ties and differences.
    [Show full text]
  • DECIPHER Semantic Annotator Deliverable Number: D4.3.1 Deliverable Date: 31 August 2013 Partners Responsible: but Status: X Public ! Restricted ! Confidential
    DELIVERABLE SUBMISSION SHEET To: Rainer TYPKE (Project Officer) EUROPEAN COMMISSION Directorate-General Information Society and Media EUFO L-2920 Luxembourg From: Eoin Kilfeather Project acronym: Decipher Project number: 270001 Project manager: Project coordinator Eoin Kilfeather The following deliverable: Deliverable title: DECIPHER Semantic Annotator Deliverable number: D4.3.1 Deliverable date: 31 August 2013 Partners responsible: BUT Status: x Public ! Restricted ! Confidential is now ! It is available for your inspection. complete. x Relevant descriptive documents are attached. The deliverable is: x a document ! a Website (URL:) ! software (...........................) ! an event ! other (...........................) Sent to Project Officer: Sent to functional mail box: On date: [email protected]. [email protected] 06 November eu 2013 ! ! FP7-270001-Decipher DECIPHER Semantic Annotator Document identifier: Decipher-D4.3.1-WP4-BUT Semantic Annotator-PU Project title: Digital Environment for Cultural Interfaces; Promoting Heritage, Education and Research Project acronym: DECIPHER Project identifier: FP7-270001-Decipher Partners: Dublin Institute of Technology National Gallery of Ireland Irish Museum of Modern Art Open University System Simulation Limited Brno University of Technology Royal Irish Academy Author(s): Pavel Smrz, Lubomir Otrusina, Jan Kouril, and Jaroslav Dytrych Brno University of Technology Version: v01 Type: Report (Deliverable D4.3.1) Report availability: Public Date: August 31, 2013 Decipher-D4.3.1-WP4-BUT Semantic Annotator-PU FP7-270001-Decipher Contents 1 Introduction 1 2 Individual data sources and their processing 3 2.1 Getty ULAN . 3 2.2 Freebase . 4 2.3 Wikipedia/DBpedia . 5 2.4 Geonames . 8 3 Semantic integration of datasets 9 3.1 Data consistency issues and overlaps .
    [Show full text]
  • Semantic Modelling and Ontology Integration of the Open Government Systems
    D. Petrušić i dr. Semantičko modeliranje i ontološka integracija sustava otvorene vlade ISSN 1330-3651 (Print), ISSN 1848-6339 (Online) DOI: 10.17559/TV-20150514115428 SEMANTIC MODELLING AND ONTOLOGY INTEGRATION OF THE OPEN GOVERNMENT SYSTEMS Darko Petrušić, Milan Segedinac, Zora Konjović Original scientific paper Open Government Ontology proposed in this paper is an extensive ontology aimed at modelling a wide range of Open Government services. Semantic model of the Open Government opens possibilities for the integration with other semantic and information models, and enables semantic reasoning and resource discovery. Characteristics of the Open Government are transparency, participation and collaboration. Main components of the Open Government are Open Architecture, Open Data and Open Standards. Organizational structure of the Open Government consists of the internal government organizations, associated domains and Open (e)Government services. Open Government Ontology can be used as a semantic meta-data repository for the (e)Government and Open (e)Government services. Using formal methods of reasoning with the proposed ontology we can search for information about Open (e)Government services and infer on gathered knowledge. Also Open Architecture Ontology can be used as Information Architecture framework for the creation of these services as was the case regarding Montenegrin Semantic Science Network. Keywords: e-Government; ontology; Open Architecture; Open Government; Semantic Web Semantičko modeliranje i ontološka integracija sustava otvorene vlade Izvorni znanstveni članak Ontologija otvorene vlade predstavljena u ovom radu je sveobuhvatna ontologija koja za cilj ima modeliranje širokog opsega servisa otvorene vlade. Semantički model otvorene vlade daje mogućnost za integraciju s drugim semantičkim i informatičkim modelima te omogućuje semantičko razmišljanje i pronalaženje resursa.
    [Show full text]