Octapy3 was developed to create “cooperating communities” of knowledge providers in a distributed environment. Octapy3 is entirely written in Python, it uses the Zope Application Server and the Plone CMS as web publishing tool. The design architecture is a component-based architecture using the Zope3 CA framework. There are components to integrate the OAI protocol in order exchange metadata among applications, to explicitly create relations among documents allocated in different computational node. Also the Octpay3 framework manages cartographic document and RDF/RDFS serialization of documents and content types. In the rest of the paper we describe the component architecture adopted, wit special attention to the functionalities and techniques used to overcome the Zope/Plone environment. Next, the Octpay Configuration Markup Language (OCML) is described together some example of its usage to described the document structure, the component description. OCML allows to personalize the managed contents, to easily extend the environment and to establish relations among documents. The paper describes also the set up used to test it with cultural heritage contents. We developed the napolibniculturali.it network of cultural heritage knowledge providers. To each provider the Octapy3 environment provide them with a set of tools, for example, to implement the cartographic interface for contents mediation, to build intermuseum virtual collections, stressing out either the effective visit or the conceptual features. napolibeniculturali.it is sponsored and used by the Direzione Regionale per i Beni Culturali e Paesaggistici della Campania to promote knowledge about cultural heritage goods of Campania. Currently this community is built of about 50 information node providers, and it interoperates with the Italian cultural heritage portal managed by the Italian Ministers of Cultural Heritage
ECLAP Tutorial first part, ECLAP 2012 conference. the general overviewPaolo Nesi
The document provides an overview of the ECLAP project, which aims to create a social service portal and digital archive for performing arts content. It discusses the goals of providing high quality metadata and tools for libraries, education, and access across different devices. The ECLAP system will include services for content aggregation, semantic searching, recommendations, networking and distribution to partners like Europeana.
Este documento presenta la lista de los 42 estudiantes que integran el Grupo 1°A de la Escuela Secundaria Diurna No. 135 "Unión de Repúblicas Socialistas Soviéticas" para el ciclo escolar 2013-2014, incluyendo sus nombres completos y calificaciones promedio.
The document discusses mast bumping in helicopters. Mast bumping occurs when the rotor head impacts the main rotor shaft, usually due to excessive flapping caused by flying outside the helicopter's safe operating envelope. It most commonly affects two-bladed rotor systems. Mast bumping can result from abrupt cyclic or collective control inputs combined with low or negative G-forces. Under these conditions, there is little thrust generated and the fuselage rolls uncontrollably due to the tail rotor thrust. To recover, positive load must be restored to the rotor by applying back cyclic and collective pitch.
"Open Source for Public Libraries Case Study IBLA Soft Library Automation Sof...eLiberatica
The IOSSPL Project developed an open-source library automation software called IBLA Soft using emerging technologies like OSS, J2EE, and portals. IBLA Soft was implemented in pilot libraries in Romania and is offered free to other public libraries. It provides a portal for centralized management of catalogues, loans, and assets across branches. Future plans include expanding use to educational libraries, integrating mobile services, and improving accessibility.
The document summarizes the Open Archives Initiative (OAI), including its history and key standards/protocols. Specifically, it discusses how OAI:
1) Develops and promotes interoperability standards to facilitate dissemination of scholarly content across repositories.
2) Arose from efforts to increase access to e-print archives and has expanded to generalize across all web-based information.
3) Defines the Open Archives Metadata Set and OAI Metadata Harvesting Protocol to expose metadata for harvesting and development of new services.
The document summarizes the Open Archives Initiative (OAI), including its history, purpose, and key standards/protocols. Specifically:
- OAI develops interoperability standards to facilitate sharing of scholarly content across repositories. It began in 1999 to enhance access to e-print archives.
- Key standards include the OAI Metadata Harvesting Protocol (OAI-PMH), which allows data providers to expose metadata for harvesting by service providers to build new services.
- The initiative also defines standards for describing and exchanging aggregations of web resources through the Open Archives Initiative Object Reuse and Exchange (OAI-ORE).
The document summarizes the Open Archives Initiative (OAI), including its history and key standards/protocols. Specifically, it discusses how OAI:
1) Develops and promotes interoperability standards to facilitate dissemination of scholarly content across repositories.
2) Arose from efforts to increase access to e-print archives and has expanded to generalize across all web-based information.
3) Defines the Open Archives Metadata Set and OAI Metadata Harvesting Protocol to expose metadata for harvesting and development of new services.
The document summarizes the Open Archives Initiative (OAI), including its history and key standards/protocols. Specifically, it discusses how OAI:
1) Develops and promotes interoperability standards to facilitate dissemination of scholarly content across repositories.
2) Arose from efforts to increase access to e-print archives and has expanded to generalize across all web-based information.
3) Defines the Open Archives Metadata Set and OAI Metadata Harvesting Protocol (OAI-PMH) to expose metadata for harvesting and enable new services.
ECLAP Tutorial first part, ECLAP 2012 conference. the general overviewPaolo Nesi
The document provides an overview of the ECLAP project, which aims to create a social service portal and digital archive for performing arts content. It discusses the goals of providing high quality metadata and tools for libraries, education, and access across different devices. The ECLAP system will include services for content aggregation, semantic searching, recommendations, networking and distribution to partners like Europeana.
Este documento presenta la lista de los 42 estudiantes que integran el Grupo 1°A de la Escuela Secundaria Diurna No. 135 "Unión de Repúblicas Socialistas Soviéticas" para el ciclo escolar 2013-2014, incluyendo sus nombres completos y calificaciones promedio.
The document discusses mast bumping in helicopters. Mast bumping occurs when the rotor head impacts the main rotor shaft, usually due to excessive flapping caused by flying outside the helicopter's safe operating envelope. It most commonly affects two-bladed rotor systems. Mast bumping can result from abrupt cyclic or collective control inputs combined with low or negative G-forces. Under these conditions, there is little thrust generated and the fuselage rolls uncontrollably due to the tail rotor thrust. To recover, positive load must be restored to the rotor by applying back cyclic and collective pitch.
"Open Source for Public Libraries Case Study IBLA Soft Library Automation Sof...eLiberatica
The IOSSPL Project developed an open-source library automation software called IBLA Soft using emerging technologies like OSS, J2EE, and portals. IBLA Soft was implemented in pilot libraries in Romania and is offered free to other public libraries. It provides a portal for centralized management of catalogues, loans, and assets across branches. Future plans include expanding use to educational libraries, integrating mobile services, and improving accessibility.
The document summarizes the Open Archives Initiative (OAI), including its history and key standards/protocols. Specifically, it discusses how OAI:
1) Develops and promotes interoperability standards to facilitate dissemination of scholarly content across repositories.
2) Arose from efforts to increase access to e-print archives and has expanded to generalize across all web-based information.
3) Defines the Open Archives Metadata Set and OAI Metadata Harvesting Protocol to expose metadata for harvesting and development of new services.
The document summarizes the Open Archives Initiative (OAI), including its history, purpose, and key standards/protocols. Specifically:
- OAI develops interoperability standards to facilitate sharing of scholarly content across repositories. It began in 1999 to enhance access to e-print archives.
- Key standards include the OAI Metadata Harvesting Protocol (OAI-PMH), which allows data providers to expose metadata for harvesting by service providers to build new services.
- The initiative also defines standards for describing and exchanging aggregations of web resources through the Open Archives Initiative Object Reuse and Exchange (OAI-ORE).
The document summarizes the Open Archives Initiative (OAI), including its history and key standards/protocols. Specifically, it discusses how OAI:
1) Develops and promotes interoperability standards to facilitate dissemination of scholarly content across repositories.
2) Arose from efforts to increase access to e-print archives and has expanded to generalize across all web-based information.
3) Defines the Open Archives Metadata Set and OAI Metadata Harvesting Protocol to expose metadata for harvesting and development of new services.
The document summarizes the Open Archives Initiative (OAI), including its history and key standards/protocols. Specifically, it discusses how OAI:
1) Develops and promotes interoperability standards to facilitate dissemination of scholarly content across repositories.
2) Arose from efforts to increase access to e-print archives and has expanded to generalize across all web-based information.
3) Defines the Open Archives Metadata Set and OAI Metadata Harvesting Protocol (OAI-PMH) to expose metadata for harvesting and enable new services.
The document summarizes the Open Archives Initiative (OAI), including its history, objectives, and standards. It discusses OAI's role in facilitating access to scholarly communications through interoperability standards. The key points are:
1. OAI develops and promotes standards to enable efficient dissemination of content across archives and repositories. It aims to provide a low barrier framework for interoperability.
2. OAI has its origins in efforts to increase access to e-print archives and scholarly communications. It defines standards like the OAI Metadata Harvesting Protocol.
3. The OAI framework includes two main participant types - data providers that expose metadata, and service providers that build services using harvested metadata.
The document discusses the Open Cultural Heritage Platform project, which aims to provide open source tools to help cultural institutions document, share, and integrate their collections online. The project will integrate Omeka and Open Context, two open source content delivery systems. The new tools offered through Open Context that will be included are faceted browsing, informed discovery, item views with high resolution images and user tagging, as well as social context analysis and Atom feeds to make content easily reusable across applications.
New ICT Trends and Issues of LibrarianshipLiaquat Rahoo
The document summarizes a one-day workshop on new ICT trends and issues in librarianship. It will cover topics like the introduction of ICT in libraries, different types of libraries supported by ICT, necessary ICT infrastructure, software for library automation, digital repositories, and web applications. The workshop will be held at the Institute of Modern Sciences and Arts on April 17, 2016.
ECLAP White paper, social network for Cultural Heritage on Peforming artsPaolo Nesi
the experience of a new generation digital content service is presented, namely ECLAP (European Collected Library of Artistic Performance, http://www.eclap.eu). ECLAP is a live lab in which several new technologies and solutions in the area of semantic computing and social media have been developed and put under trial of the final users and institutions. On this regard, ECLAP is open for both content and results experimentations, and presently comprises more than 35 prestigious international institutions; ECLAP provides services and tools for automated content ingestion, adaptation, metadata ingestion and editing, semantic information extraction, indexing and distribution by exploiting the most innovative and consolidated technologies. ECLAP supports the institutions in all their activities: metadata selection and mapping, content ingestion, to the definition and management of permissions and licenses on contents, and finally managing their users on ECLAP services. According to ECLAP workflow, the obtained metadata are sent to Europeana only after that the metadata have been enriched and linked to a reachable digital resource and when the IPR details have been finalized, with needed quality level. An ECLAP IPR Model can be associated with each single content or collection. ECLAP also provides infrastructural connection for direct promotion of content towards a large number of social networks, including: Facebook, LinkedIn, Diggs, Twitter, etc. On ECLAP, each content provider may have its own distribution channel/group (including a forum and a blog in addition to the space for their content collections, and the groups can be open, moderated or private) with the possibility of customizing the group user interface according to their logo and colours. This multitenant modality permits at the institutions to see ECLAP as a non-intrusive service, to reinforce their brand and at the same time to exploit and experiment a number of innovative ECLAP tools, to accelerate the promotion exploiting ECLAP social media, LOD and Europeana channels, and ready to access new users for their content. ECLAP provides the unique videos, images and texts related to more than 50 years of activity of the Dario Fo and Franca Rame theatre company, featuring videos, photos, texts, drawings, paintings, sketches, posters, copies of contracts and of invoices, notes, books, articles. Other unique, irreplaceable material includes video, audio recordings and photos of performances, workshops, seminars, rehearsals of Jerzy Grotowski, Peter Brook, Gennadi Bogdanov, Anatolij Vasil’ev, Alberto Sordi, Carmelo Bene, Giorgio Strehler, Mimmo Cuticchio, Gian Maria Volonté, Judith Malina.
Congresso Sociedade Brasileira de Computação CSBC2016 Porto Alegre (Brazil)
Workshop on Cloud Networks & Cloudscape Brazil
José Luiz Ribeiro Filho, Director of Services and Solutions of the Brazilian National Education and Research Network (RNP), Brazil
Cloud Federation & Open Science Cloud at cross-regional level
SOBOLEO – Editor and Repository for Living OntologiesSimone Braun
presentation of the demo paper "SOBOLEO - Editor and Repository for Living Ontologeis" at ORES 2010 workshop, co-located with ESWC 2010, Crete, May 31 2010
The Open Archives Initiative Protocol for Metadata Harvesting and ePrints UKAndy Powell
UKOLN is a center of expertise in digital information management supported by various organizations. The document discusses the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), including its history and how it allows harvesting of metadata from data providers by service providers through a simple protocol. It also discusses the potential impact of OAI-PMH on institutions, libraries, and researchers.
- The document discusses the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) standard which allows interoperability between digital archives and repositories.
- It describes key aspects of the OAI-PMH standard including verbs, identifiers, sets, data and service providers, and harvesting metadata from multiple sources.
- The document also provides an example of implementing OAI-PMH through the CulturaItalia project in Italy which aggregates metadata about artworks in Tuscany from different source repositories.
SOFIA - Experiences in Implementing a Cross-domain Use Case by Combining Sema...Sofia Eu
This document describes experiences from implementing a cross-domain use case that combines a "Music follows user" use case with a "Read aloud message" use case. It does this by combining services operating on a Service Oriented Architecture (SOA) with agents executing on a smart space architecture. Lessons learned suggest defining simple ontological concepts and associated behaviors to implement similar use cases in a scalable, future-proof manner.
This document discusses rethinking the library services platform (LSP) model to improve interoperability between systems. It notes that while new LSPs have emerged, significant lack of interoperability remains between components of the library technology ecosystem. The author argues that libraries should adopt a platform approach like Windows or Apple, where vendors provide tools and services to allow third parties to build applications on their platforms. This could encourage more applications and make platforms more valuable. Prioritizing the library user perspective may change how libraries think about LSPs. Standards bodies are working on interoperability issues but more remains to be done to fully integrate solutions.
QEBU: AN ADVANCED GRAPHICAL EDITOR FOR THE EBUCORE METADATA SET | Paolo PASIN...FIAT/IFTA
Creation and management of metadata documents can be quite a difficult task to accomplish manually. To address this issue in the context of the EBUCore v1.3 metadata set, we propose a GUI-based metadata editor, QEbu, developed during the Multimedia Archival Techniques course, held at the Polytechnic University of Turin in collaboration with RAI.
The aim is to provide a user-friendly graphical editor to create and manage XML documents, relieving the user from the burden of worrying about the structure of the data and letting him focus on the actual content.
QEbu has been developed in C++ using the cross-platform and open source library Qt 4.8; this framework was chosen in order to exploit its natural features for developing interface-centered applications.
This document summarizes citizen science tools and initiatives for collecting and sharing biodiversity data. It describes an online registry of citizen science tools, the PlutoF citizen science module for creating standardized data collection projects, and the EUBON Portal & Citizen Science Gateway which will include a citizen science tool directory and resources for data providers. It also discusses using DKAN and CKAN to publish and share citizen science datasets and resources in open formats through APIs.
A Comparative Study Ontology Building Tools for Semantic Web Applications IJwest
This document provides a comparative study of four popular ontology building tools: Protégé 3.4, IsaViz, Apollo, and SWOOP. It discusses the features and functionalities of each tool, including their capabilities for ontology editing, browsing, documentation, import/export of formats, and visualization. The document aims to identify existing ontology tools that are freely available and can be used to develop ontologies for various application domains such as transport, tourism, health, and natural language. It evaluates the tools based on criteria like interoperability, openness, ease of updating/maintaining ontologies, and market penetration.
A Comparative Study Ontology Building Tools for Semantic Web Applications dannyijwest
Ontologies have recently received popularity in the area of knowledge management and knowledge sharing, especially after the evolution of the Semantic Web and its supporting technologies. An ontology defines the terms and concepts (meaning) used to describe and represent an area of knowledge.The aim of this paper is to identify all possible existing ontologies and ontology management tools (Protégé 3.4, Apollo, IsaViz & SWOOP) that are freely available and review them in terms of: a) interoperability, b) openness, c) easiness to update and maintain, d) market status and penetration. The results of the review in ontologies are analyzed for each application area, such as transport, tourism, personal services, health and social services, natural languages and other HCI-related domains. Ontology Building/Management Tools are used by different groups of people for performing diverse tasks. Although each tool provides different functionalities, most of the users just use only one, because they are not able to interchange their ontologies from one tool to another. In addition, we considered the compatibility of different ontologies with different development and management tools. The paper is also concerns the detection of commonalities and differences between the examined ontologies, both on the same domain (application area) and among different domains.
A Comparative Study of Ontology building Tools in Semantic Web Applications dannyijwest
Ontologies have recently received popularity in the area of knowledge management and knowledge sharing,
especially after the evolution of the Semantic Web and its supporting technologies. An ontology defines the terms
and concepts (meaning) used to describe and represent an area of knowledge.The aim of this paper is to identify all
possible existing ontologies and ontology management tools (Protégé 3.4, Apollo, IsaViz & SWOOP) that are freely
available and review them in terms of: a) interoperability, b) openness, c) easiness to update and maintain, d)
market status and penetration. The results of the review in ontologies are analyzed for each application area, such
as transport, tourism, personal services, health and social services, natural languages and other HCI-related
domains. Ontology Building/Management Tools are used by different groups of people for performing diverse tasks.
Although each tool provides different functionalities, most of the users just use only one, because they are not able
to interchange their ontologies from one tool to another. In addition, we considered the compatibility of different
ontologies with different development and management tools. The paper is also concerns the detection of
commonalities and differences between the examined ontologies, both on the same domain (application area) and
among different domains.
This presentation was provided by Marshall Breeding of Library Technology for a NISO webinar, Integrating Library Management Systems, held on June 8, 2016
Open Archives Initiative Object Reuse and Exchangelagoze
This document discusses infrastructure to support new models of scholarly publication by enabling interoperability across repositories through common data modeling and services. It proposes building blocks like repositories, digital objects, a common data model, serialization formats, and core services. This would allow components like publications and data to move across repositories and workflows, facilitating reuse and new value-added services that expose the scholarly communication process.
Objeto de conferencia
Hewlett-Packard Chameleon Federation of University Researchers Symposium (Bologna, Italia)
Webservices technology is one of the stilts on which the concept WEB 2.0 is sustained. This technology allows to send information between computers connected to the network, providing a high portability level communication mechanism that permits this interconnection to be made between different hardware platforms and internal data representation, many operative systems, applications developed in several languages or databases and mainly, a very simple language, standardized and efficient for information transport such as XML.
Ver registro completo en: http://sedici.unlp.edu.ar/handle/10915/5550
SOFIA - Smart Objects For Intelligent Applications. INDRA/ESISofia Eu
The SOFIA project aims to create a semantic interoperability platform and applications to enable smart environments based on embedded systems. It involves partners from four EU countries. The key goals are to provide open information storage and common search capabilities for heterogeneous embedded systems. This will allow simple, local applications to be built using open data and devices. The SOFIA Application Development Kit provides tools across the development lifecycle, including a wizard to select ontologies and platforms, and middleware generation.
Sally Kleinfeldt - Plone Application Development PatternsVincenzo Barone
In 2004 The Nature Conservancy adopted Plone as the platform for ConserveOnline.org, a community site for sharing conservation information. Since then, we have gained experience implementing several successful Plone intranet applications, made plenty of mistakes, and learned how to - and how not to - approach new Plone projects. This talk will compare our experiences developing two very different intranet Plone applications that manage conservation information. The first application has a complex data model with a relational database backend and makes minimal use of Archetypes. Its requirements - including data model and user interface - were rigidly specified based on a spreadsheet tool. The second application is Archetypes-based and was developed using UML modeling and ArchGenXML. It has a simple data model, uses the ZODB for storage, and its requirements were more loosely specified. From the lessons we learned on these projects, we have developed a set of application pattern definitions to guide us when choosing technologies and estimating costs. We think these pattern definitions can help managers, integrators, and people new to Plone understand when to use Plone, when not to use Plone, and how to structure their interactions with clients to ensure a successful Plone project.
Where's the source, Luke? : How to find and debug the code behind PloneVincenzo Barone
Plone, being a python based CMS written as a project for the Zope application server, consist almost entirely of python modules and a number of configuration files. Python source code is loved by many in the community for its explicit readablity; however, for many experienced software developers, coming over to the Plone technology stack can be a haunting experience. It seems everything is hidden away as pickled object in the ZODB, and that layers of magic prevent one from understanding how it works and how to affect change. This presentation will explain to the novice: - how to track down the python source behind Plone - how to take advantage of rich open source tools like ctags and pdb - best practices for getting started with file system product development
More Related Content
Similar to Carmine Noviello Octapy3 A Distributed And Cooperative Semantic Web Oriented Cms
The document summarizes the Open Archives Initiative (OAI), including its history, objectives, and standards. It discusses OAI's role in facilitating access to scholarly communications through interoperability standards. The key points are:
1. OAI develops and promotes standards to enable efficient dissemination of content across archives and repositories. It aims to provide a low barrier framework for interoperability.
2. OAI has its origins in efforts to increase access to e-print archives and scholarly communications. It defines standards like the OAI Metadata Harvesting Protocol.
3. The OAI framework includes two main participant types - data providers that expose metadata, and service providers that build services using harvested metadata.
The document discusses the Open Cultural Heritage Platform project, which aims to provide open source tools to help cultural institutions document, share, and integrate their collections online. The project will integrate Omeka and Open Context, two open source content delivery systems. The new tools offered through Open Context that will be included are faceted browsing, informed discovery, item views with high resolution images and user tagging, as well as social context analysis and Atom feeds to make content easily reusable across applications.
New ICT Trends and Issues of LibrarianshipLiaquat Rahoo
The document summarizes a one-day workshop on new ICT trends and issues in librarianship. It will cover topics like the introduction of ICT in libraries, different types of libraries supported by ICT, necessary ICT infrastructure, software for library automation, digital repositories, and web applications. The workshop will be held at the Institute of Modern Sciences and Arts on April 17, 2016.
ECLAP White paper, social network for Cultural Heritage on Peforming artsPaolo Nesi
the experience of a new generation digital content service is presented, namely ECLAP (European Collected Library of Artistic Performance, http://www.eclap.eu). ECLAP is a live lab in which several new technologies and solutions in the area of semantic computing and social media have been developed and put under trial of the final users and institutions. On this regard, ECLAP is open for both content and results experimentations, and presently comprises more than 35 prestigious international institutions; ECLAP provides services and tools for automated content ingestion, adaptation, metadata ingestion and editing, semantic information extraction, indexing and distribution by exploiting the most innovative and consolidated technologies. ECLAP supports the institutions in all their activities: metadata selection and mapping, content ingestion, to the definition and management of permissions and licenses on contents, and finally managing their users on ECLAP services. According to ECLAP workflow, the obtained metadata are sent to Europeana only after that the metadata have been enriched and linked to a reachable digital resource and when the IPR details have been finalized, with needed quality level. An ECLAP IPR Model can be associated with each single content or collection. ECLAP also provides infrastructural connection for direct promotion of content towards a large number of social networks, including: Facebook, LinkedIn, Diggs, Twitter, etc. On ECLAP, each content provider may have its own distribution channel/group (including a forum and a blog in addition to the space for their content collections, and the groups can be open, moderated or private) with the possibility of customizing the group user interface according to their logo and colours. This multitenant modality permits at the institutions to see ECLAP as a non-intrusive service, to reinforce their brand and at the same time to exploit and experiment a number of innovative ECLAP tools, to accelerate the promotion exploiting ECLAP social media, LOD and Europeana channels, and ready to access new users for their content. ECLAP provides the unique videos, images and texts related to more than 50 years of activity of the Dario Fo and Franca Rame theatre company, featuring videos, photos, texts, drawings, paintings, sketches, posters, copies of contracts and of invoices, notes, books, articles. Other unique, irreplaceable material includes video, audio recordings and photos of performances, workshops, seminars, rehearsals of Jerzy Grotowski, Peter Brook, Gennadi Bogdanov, Anatolij Vasil’ev, Alberto Sordi, Carmelo Bene, Giorgio Strehler, Mimmo Cuticchio, Gian Maria Volonté, Judith Malina.
Congresso Sociedade Brasileira de Computação CSBC2016 Porto Alegre (Brazil)
Workshop on Cloud Networks & Cloudscape Brazil
José Luiz Ribeiro Filho, Director of Services and Solutions of the Brazilian National Education and Research Network (RNP), Brazil
Cloud Federation & Open Science Cloud at cross-regional level
SOBOLEO – Editor and Repository for Living OntologiesSimone Braun
presentation of the demo paper "SOBOLEO - Editor and Repository for Living Ontologeis" at ORES 2010 workshop, co-located with ESWC 2010, Crete, May 31 2010
The Open Archives Initiative Protocol for Metadata Harvesting and ePrints UKAndy Powell
UKOLN is a center of expertise in digital information management supported by various organizations. The document discusses the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH), including its history and how it allows harvesting of metadata from data providers by service providers through a simple protocol. It also discusses the potential impact of OAI-PMH on institutions, libraries, and researchers.
- The document discusses the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) standard which allows interoperability between digital archives and repositories.
- It describes key aspects of the OAI-PMH standard including verbs, identifiers, sets, data and service providers, and harvesting metadata from multiple sources.
- The document also provides an example of implementing OAI-PMH through the CulturaItalia project in Italy which aggregates metadata about artworks in Tuscany from different source repositories.
SOFIA - Experiences in Implementing a Cross-domain Use Case by Combining Sema...Sofia Eu
This document describes experiences from implementing a cross-domain use case that combines a "Music follows user" use case with a "Read aloud message" use case. It does this by combining services operating on a Service Oriented Architecture (SOA) with agents executing on a smart space architecture. Lessons learned suggest defining simple ontological concepts and associated behaviors to implement similar use cases in a scalable, future-proof manner.
This document discusses rethinking the library services platform (LSP) model to improve interoperability between systems. It notes that while new LSPs have emerged, significant lack of interoperability remains between components of the library technology ecosystem. The author argues that libraries should adopt a platform approach like Windows or Apple, where vendors provide tools and services to allow third parties to build applications on their platforms. This could encourage more applications and make platforms more valuable. Prioritizing the library user perspective may change how libraries think about LSPs. Standards bodies are working on interoperability issues but more remains to be done to fully integrate solutions.
QEBU: AN ADVANCED GRAPHICAL EDITOR FOR THE EBUCORE METADATA SET | Paolo PASIN...FIAT/IFTA
Creation and management of metadata documents can be quite a difficult task to accomplish manually. To address this issue in the context of the EBUCore v1.3 metadata set, we propose a GUI-based metadata editor, QEbu, developed during the Multimedia Archival Techniques course, held at the Polytechnic University of Turin in collaboration with RAI.
The aim is to provide a user-friendly graphical editor to create and manage XML documents, relieving the user from the burden of worrying about the structure of the data and letting him focus on the actual content.
QEbu has been developed in C++ using the cross-platform and open source library Qt 4.8; this framework was chosen in order to exploit its natural features for developing interface-centered applications.
This document summarizes citizen science tools and initiatives for collecting and sharing biodiversity data. It describes an online registry of citizen science tools, the PlutoF citizen science module for creating standardized data collection projects, and the EUBON Portal & Citizen Science Gateway which will include a citizen science tool directory and resources for data providers. It also discusses using DKAN and CKAN to publish and share citizen science datasets and resources in open formats through APIs.
A Comparative Study Ontology Building Tools for Semantic Web Applications IJwest
This document provides a comparative study of four popular ontology building tools: Protégé 3.4, IsaViz, Apollo, and SWOOP. It discusses the features and functionalities of each tool, including their capabilities for ontology editing, browsing, documentation, import/export of formats, and visualization. The document aims to identify existing ontology tools that are freely available and can be used to develop ontologies for various application domains such as transport, tourism, health, and natural language. It evaluates the tools based on criteria like interoperability, openness, ease of updating/maintaining ontologies, and market penetration.
A Comparative Study Ontology Building Tools for Semantic Web Applications dannyijwest
Ontologies have recently received popularity in the area of knowledge management and knowledge sharing, especially after the evolution of the Semantic Web and its supporting technologies. An ontology defines the terms and concepts (meaning) used to describe and represent an area of knowledge.The aim of this paper is to identify all possible existing ontologies and ontology management tools (Protégé 3.4, Apollo, IsaViz & SWOOP) that are freely available and review them in terms of: a) interoperability, b) openness, c) easiness to update and maintain, d) market status and penetration. The results of the review in ontologies are analyzed for each application area, such as transport, tourism, personal services, health and social services, natural languages and other HCI-related domains. Ontology Building/Management Tools are used by different groups of people for performing diverse tasks. Although each tool provides different functionalities, most of the users just use only one, because they are not able to interchange their ontologies from one tool to another. In addition, we considered the compatibility of different ontologies with different development and management tools. The paper is also concerns the detection of commonalities and differences between the examined ontologies, both on the same domain (application area) and among different domains.
A Comparative Study of Ontology building Tools in Semantic Web Applications dannyijwest
Ontologies have recently received popularity in the area of knowledge management and knowledge sharing,
especially after the evolution of the Semantic Web and its supporting technologies. An ontology defines the terms
and concepts (meaning) used to describe and represent an area of knowledge.The aim of this paper is to identify all
possible existing ontologies and ontology management tools (Protégé 3.4, Apollo, IsaViz & SWOOP) that are freely
available and review them in terms of: a) interoperability, b) openness, c) easiness to update and maintain, d)
market status and penetration. The results of the review in ontologies are analyzed for each application area, such
as transport, tourism, personal services, health and social services, natural languages and other HCI-related
domains. Ontology Building/Management Tools are used by different groups of people for performing diverse tasks.
Although each tool provides different functionalities, most of the users just use only one, because they are not able
to interchange their ontologies from one tool to another. In addition, we considered the compatibility of different
ontologies with different development and management tools. The paper is also concerns the detection of
commonalities and differences between the examined ontologies, both on the same domain (application area) and
among different domains.
This presentation was provided by Marshall Breeding of Library Technology for a NISO webinar, Integrating Library Management Systems, held on June 8, 2016
Open Archives Initiative Object Reuse and Exchangelagoze
This document discusses infrastructure to support new models of scholarly publication by enabling interoperability across repositories through common data modeling and services. It proposes building blocks like repositories, digital objects, a common data model, serialization formats, and core services. This would allow components like publications and data to move across repositories and workflows, facilitating reuse and new value-added services that expose the scholarly communication process.
Objeto de conferencia
Hewlett-Packard Chameleon Federation of University Researchers Symposium (Bologna, Italia)
Webservices technology is one of the stilts on which the concept WEB 2.0 is sustained. This technology allows to send information between computers connected to the network, providing a high portability level communication mechanism that permits this interconnection to be made between different hardware platforms and internal data representation, many operative systems, applications developed in several languages or databases and mainly, a very simple language, standardized and efficient for information transport such as XML.
Ver registro completo en: http://sedici.unlp.edu.ar/handle/10915/5550
SOFIA - Smart Objects For Intelligent Applications. INDRA/ESISofia Eu
The SOFIA project aims to create a semantic interoperability platform and applications to enable smart environments based on embedded systems. It involves partners from four EU countries. The key goals are to provide open information storage and common search capabilities for heterogeneous embedded systems. This will allow simple, local applications to be built using open data and devices. The SOFIA Application Development Kit provides tools across the development lifecycle, including a wizard to select ontologies and platforms, and middleware generation.
Similar to Carmine Noviello Octapy3 A Distributed And Cooperative Semantic Web Oriented Cms (20)
Sally Kleinfeldt - Plone Application Development PatternsVincenzo Barone
In 2004 The Nature Conservancy adopted Plone as the platform for ConserveOnline.org, a community site for sharing conservation information. Since then, we have gained experience implementing several successful Plone intranet applications, made plenty of mistakes, and learned how to - and how not to - approach new Plone projects. This talk will compare our experiences developing two very different intranet Plone applications that manage conservation information. The first application has a complex data model with a relational database backend and makes minimal use of Archetypes. Its requirements - including data model and user interface - were rigidly specified based on a spreadsheet tool. The second application is Archetypes-based and was developed using UML modeling and ArchGenXML. It has a simple data model, uses the ZODB for storage, and its requirements were more loosely specified. From the lessons we learned on these projects, we have developed a set of application pattern definitions to guide us when choosing technologies and estimating costs. We think these pattern definitions can help managers, integrators, and people new to Plone understand when to use Plone, when not to use Plone, and how to structure their interactions with clients to ensure a successful Plone project.
Where's the source, Luke? : How to find and debug the code behind PloneVincenzo Barone
Plone, being a python based CMS written as a project for the Zope application server, consist almost entirely of python modules and a number of configuration files. Python source code is loved by many in the community for its explicit readablity; however, for many experienced software developers, coming over to the Plone technology stack can be a haunting experience. It seems everything is hidden away as pickled object in the ZODB, and that layers of magic prevent one from understanding how it works and how to affect change. This presentation will explain to the novice: - how to track down the python source behind Plone - how to take advantage of rich open source tools like ctags and pdb - best practices for getting started with file system product development
ItalianSkin: an improvement in the accessibility of the Plone interface in or...Vincenzo Barone
The Italian government has made a law specifying the accessibility requirements (the most famous is the usage of the Strict XHTML) for public administration websites. To enable Plone front- and back-end to be compliant with these specifications the ItalianSkin project was initiated, but its development has gone beyond the simple implementation of the law and has continued with the objectives of making Plone wholly functional with screen readers for blind people and providing developers with automatic tools to improve the accessibility of their own sites. We would recommend this talk to anyone developing websites and in particular to those who are responsible for accessibility.
In this session I will describe possibilities for everybody to make Plone more known. This includes how to leverage the power of social media such as blogging, videoblogging and podcasting but also spreading the word about Plone by attending unconferences like Barcamps or being active in Second Life. This talk is targeted to everybody who want to make Plone more popular.
Lennart Regebro What Zope Did Wrong (And What To Do Instead)Vincenzo Barone
Zope did many things right originally by using Python and including batteries, but it had some downfalls like being unpythonic, having too many magical parts, and being too complicated. Zope 3 aimed to address these issues but ended up being too abstract and XML-based, slowing development. The document discusses ideas for improving on Zope by having a low entry threshold, being highly modular, and starting with finished applications that use Python and a component architecture.
Wichert Akkerman Plone Deployment Practices The Plone.Org SetupVincenzo Barone
The plone.org and plone.net websites are the first confrontation with Plone for most users. It is important that they perform well and are stable. With almost 4 million page views per day and thousands of LDAP users plone.org and plone.net are examples of a complex deployment setup requiring LDAP, caching and load balancing - all on a single machine. I will describe how the Plone websites are build and how those practices can be applied to other sites, making it possible to scale upwards to bigger sites or make smaller sites more efficient.
Philipp Von Weitershausen Untested Code Is Broken CodeVincenzo Barone
If you're one of those programmers who think that subtle bugs only happen to other people, or that only bad programmers need extensive testing, this talk is for you.
Any non-trivial piece of software should be accompanied by an appropriate suite of automated tests. Your Plone products are no exception. By understanding approaches to automated testing and following good working practices, you can improve the quality of your code, as well as your confidence in your own work.
In this talk, Philipp von Weitershausen and Martin Aspeli will take you through the theory and practice of unit testing, integration testing and functional testing. Through real-world examples, you will learn that testing is not only necessary: it can be fun too!
Duco Dokter - Plone for the enterprise market: technical musing on caching, C...Vincenzo Barone
This technical presentation will cover many aspects of what one might encounter when a plone site is to be deployed in a highly demanding environment. And for what it's worth, these are not only theoretical examples, but they have also been proven to work in real life. The following items will be presented: * High Availability architecture * Clustering with ZEO * Synchronizing Data.fs * Load Balancing * Sticky Sessions * Caching * Single Sign-On
The document discusses subtyping in Plone and presents an example of creating a new document subtype called "UltraDoc" using the p4a.subtyper package. The example shows how to define a marker interface, descriptor class, template, and ZCML configuration to integrate the new subtype into Plone so it appears as its own content type with a customized view. The presentation aims to demonstrate how subtyping can be used to provide different identities for content and transform content based on events.
Alec Mitchell Relationship Building Defining And Querying Complex Relatio...Vincenzo Barone
The current story for relating content in Plone, via Archetypes reference fields, is limited and known to have poor performance in some cases. This talk will focus on the integration of Zope 3 tools for handling relationships (intids, zc.relationship) in Zope 2 via plone.app.relations. In particular I will be comparing the merits of these tools against existing methods (Archetypes references, using a separate RDBMS for content relationships), discussing particular applications for which they may be useful, and some areas in which they fall short. The comparison to existing relationship modeling tools will cover performance, flexibility, and convenience. To illustrate the relative convenience, I will give a brief overview of the plone.app.relations API, from the lower level index and relationship container to the high level API for making queries and defining relationships. The discussion of applications will focus on a some real world uses. These include social networking, defining complex taxonomies, having content appear attached to multiple locations, and other things for which Plone typically would not be suitable (these tools are in use at http://www.thedailyreel.com). In particular, I'll discuss how the default relationship attributes and query methods from the API can be used to model each of these applications. Finally, I'll discuss the areas in which these tools may fall short in terms of performance and flexibility, and where an RDBMS or specialized catalog may be necessary.
The Wageindicator Foundation deploys Plone for it's world-wide portals on wage information. Moreover, Plone serves as an application platform for most of the web based tools used to create questionnaires, salarychecks and other interactive content. The Wageindicator Foundation was started in 2000 in the Netherlands, and is now the hub of an international collaboration between universities, research institutes, trade unions and commercial parties. The goal of the foundation is to share and compare wage information, and so to contribute to a transparent labor market. The ideological stance of the foundation means that Open Source and free software is preferred. The separate sites collect over 400.000 visitors per month, served by four clusters of two machines each, hosted in the USA, India and the Netherlands. Techniques involved are HA-Clustering, load-balancing, caching, remote distribution of new releases for software.
Tom Lazar Using Zope3 Views And Viewlets For Plone 3.0 Product DevelopmentVincenzo Barone
A hands-on workshop on how to use Zope3 Views and Viewlets in Products targeted for Plone 3.0 (and why you would want to do so). Special emphasis will be on best practices in general, handling and validation of forms and how Zope3's shiny new toys make it easier to write reusable code and cleaner markup. Finally, the talk will deal with how Views and Viewlets can help you make your product better cacheable. Although the talk is targeted at Plone integrators who already have experience using the older CMF-based approach it will also try to address people new to Plone who want to customize it in a future-proof manner.
Xavier Heymans Plone Gov Plone In The Public Sector. Panel Presenting The...Vincenzo Barone
The PloneGov project regroups local and regional governments and SME from over 15 countries and 3 continents. The goals of this close collaboration is to develop in a cooperative manner, applications and websites suited for public organization for their own use as well as for their citizens’. To give an overview of PloneGov project and tools, we propose to make 6 presentations in 2x45 minutes: Xavier Heymans, will introduce the project, potential and strategy of development. Speakers will be experts from the public and private sector collaborating in PloneGov. They will represent the different national branches of PloneGov and will present their project and tools in use by local governments to parliaments.
Brent Lambert Plone In Education A Case Study Of The Use Of Plone And Educa...Vincenzo Barone
In recent years MIT has been releasing course materials online through their OpenCourseware project, making content available all around the world for free. Many people have benefited and continue to benefit today from having these materials available. Other universities are also now beginning to see the value of participating in similar movements, and are publishing OpenCourseware sites of their own. This movement is growing across the world including universities from several countries such as Japan, China, Spain, the Netherlands, Mexico, and the United States. Producing web sites with freely available educational content can be a complicated endeavor for many academic institutions. Work is currently being done to reduce the technological and economic barriers to participating in OpenCourseware. A project called eduCommons, which is built by the Center for Open Sustainable Learning (COSL) at Utah State University, is making it easier for institutions share their course materials. This session will detail the evolution of eduCommons, from its first release on Plone 1.5.2, to the most current version that has just been released on Plone 3. Even if you are not involved in OpenCourseware, but are contemplating making course materials or educational content available on the web, you will want to learn about our approach to writing reusable Plone based educational products, and learn about best practices of how to publish educational content from those who have been involved in the OpenCourseware movement.
The plone.org and plone.net websites are the first confrontation with Plone for most users. It is important that they perform well and are stable. With almost 4 million page views per day and thousands of LDAP users plone.org and plone.net are examples of a complex deployment setup requiring LDAP, caching and load balancing - all on a single machine. I will describe how the Plone websites are build and how those practices can be applied to other sites, making it possible to scale upwards to bigger sites or make smaller sites more efficient.
Philipp Von Weitershausen Plone Age Mammoths, Sabers And Caveen Cant The...Vincenzo Barone
It is the last Plone age. The big and strong but lonely mammoth has led the way for eons. But now it is threatened by a pack of saber-tooth tigers who are quick, agile and work together. Can the friendly caveman save the mammoth and make piece with the sabers? Can Grok help making Zope and Plone more agile? Will Zope and the other web frameworks fall in love, and what do WSGI and Paste have to say about that? From the makers of "Zope on a Paste", coming this October, a comedy for the whole family (developers, integrators and newbiews). Rated PG-13.
Denis Mishunov Making Plone Theme 10 Most Wanted Tips Vincenzo Barone
It will be a chart of 10 small (some are not that small), but I hope useful tips for making new Plone theme. Among those might occur (the exact list might be slightly changed): 1. Center the logo 2. Makin rounded corners 3. Making dropdown shadows 4. *Under-water stones* of testing Plone theme. Places you might want to check before deployment and so on This session is supposed to cover the most wanted tips in Plone skinning process, based on questions on #plone, mailing lists and personal communications with people, making Plone themes. Target group for this session - Plone skinning beginners with basic knowledge of how Plone themes are produced and Plone skinning intermediaries. I hope this session will give people some cool ideas on how to improve their themes and work more productive in the future.
Kupu is the visual editor in Plone. This talk will cover how it came about, what it can do now, and what it might become. The talk will cover the new features in Kupu 1.4, and how to configure Kupu to get the best out of it. It will also look at some of the challenges that Kupu has to meet in the future.
KSS, the new Ajax framework for Plone 3 comes with great components by default. But what if you need to integrate it with legacy Javascript? Or maybe you want to integrate that nice library/widget you found on the web. During this talk I will show you where you can extend KSS and how to do it. You can watch me create both the server side and client side code needed to integrate an existing piece of Javascript. After this talk KSS should have no limits for you.
Jared Whitlock Open Source In The Enterprise Plone @ NovellVincenzo Barone
Novell has used various proprietary CMS solutions over time, including TeamSite and Vignette. None of these solutions met all of our needs, nor were they easy to modify. We began looking at different Open Source CMS options, and decided on Plone. This presentation will briefly discuss Novell's proprietary CMS history, why we chose Plone, what we are currently using and developing, and our plans for the future. It will also discuss our architecture for making Plone successful for enterprise websites.
Unlocking WhatsApp Marketing with HubSpot: Integrating Messaging into Your Ma...Niswey
50 million companies worldwide leverage WhatsApp as a key marketing channel. You may have considered adding it to your marketing mix, or probably already driving impressive conversions with WhatsApp.
But wait. What happens when you fully integrate your WhatsApp campaigns with HubSpot?
That's exactly what we explored in this session.
We take a look at everything that you need to know in order to deploy effective WhatsApp marketing strategies, and integrate it with your buyer journey in HubSpot. From technical requirements to innovative campaign strategies, to advanced campaign reporting - we discuss all that and more, to leverage WhatsApp for maximum impact. Check out more details about the event here https://events.hubspot.com/events/details/hubspot-new-delhi-presents-unlocking-whatsapp-marketing-with-hubspot-integrating-messaging-into-your-marketing-strategy/
Enhancing Adoption of AI in Agri-food: IntroductionCor Verdouw
Introduction to the Panel on: Pathways and Challenges: AI-Driven Technology in Agri-Food, AI4Food, University of Guelph
“Enhancing Adoption of AI in Agri-food: a Path Forward”, 18 June 2024
AI Transformation Playbook: Thinking AI-First for Your BusinessArijit Dutta
I dive into how businesses can stay competitive by integrating AI into their core processes. From identifying the right approach to building collaborative teams and recognizing common pitfalls, this guide has got you covered. AI transformation is a journey, and this playbook is here to help you navigate it successfully.
The Steadfast and Reliable Bull: Taurus Zodiac Signmy Pandit
Explore the steadfast and reliable nature of the Taurus Zodiac Sign. Discover the personality traits, key dates, and horoscope insights that define the determined and practical Taurus, and learn how their grounded nature makes them the anchor of the zodiac.
Presentation by Herman Kienhuis (Curiosity VC) on Investing in AI for ABS Alu...Herman Kienhuis
Presentation by Herman Kienhuis (Curiosity VC) on developments in AI, the venture capital investment landscape and Curiosity VC's approach to investing, at the alumni event of Amsterdam Business School (University of Amsterdam) on June 13, 2024 in Amsterdam.
The Most Inspiring Entrepreneurs to Follow in 2024.pdfthesiliconleaders
In a world where the potential of youth innovation remains vastly untouched, there emerges a guiding light in the form of Norm Goldstein, the Founder and CEO of EduNetwork Partners. His dedication to this cause has earned him recognition as a Congressional Leadership Award recipient.
SATTA MATKA DPBOSS KALYAN MATKA RESULTS KALYAN CHART KALYAN MATKA MATKA RESULT KALYAN MATKA TIPS SATTA MATKA MATKA COM MATKA PANA JODI TODAY BATTA SATKA MATKA PATTI JODI NUMBER MATKA RESULTS MATKA CHART MATKA JODI SATTA COM INDIA SATTA MATKA MATKA TIPS MATKA WAPKA ALL MATKA RESULT LIVE ONLINE MATKA RESULT KALYAN MATKA RESULT DPBOSS MATKA 143 MAIN MATKA KALYAN MATKA RESULTS KALYAN CHART INDIA MATKA KALYAN SATTA MATKA 420 INDIAN MATKA SATTA KING MATKA FIX JODI FIX FIX FIX SATTA NAMBAR MATKA INDIA SATTA BATTA
Best Competitive Marble Pricing in Dubai - ☎ 9928909666Stone Art Hub
Stone Art Hub offers the best competitive Marble Pricing in Dubai, ensuring affordability without compromising quality. With a wide range of exquisite marble options to choose from, you can enhance your spaces with elegance and sophistication. For inquiries or orders, contact us at ☎ 9928909666. Experience luxury at unbeatable prices.
Prescriptive analytics BA4206 Anna University PPTFreelance
Business analysis - Prescriptive analytics Introduction to Prescriptive analytics
Prescriptive Modeling
Non Linear Optimization
Demonstrating Business Performance Improvement
Efficient PHP Development Solutions for Dynamic Web ApplicationsHarwinder Singh
Unlock the full potential of your web projects with our expert PHP development solutions. From robust backend systems to dynamic front-end interfaces, we deliver scalable, secure, and high-performance applications tailored to your needs. Trust our skilled team to transform your ideas into reality with custom PHP programming, ensuring seamless functionality and a superior user experience.
Tired of chasing down expiring contracts and drowning in paperwork? Mastering contract management can significantly enhance your business efficiency and productivity. This guide unveils expert secrets to streamline your contract management process. Learn how to save time, minimize risk, and achieve effortless contract management.
Carmine Noviello Octapy3 A Distributed And Cooperative Semantic Web Oriented Cms
1. Octapy 3: a distributed and
cooperative semantic
web oriented CMS
Mario Mango Furnari, Carmine Ivan Delio Novello, Paolo Acampa
Istituto di Cibernetica “E. Caianiello”
National Research Council
Pozzuoli
Italy
Octapy 3 was developed to create “cooperating communities” of knowledge providers in a distributed
environment. Octapy 3 is entirely written in Python, it uses the Zope Application Server and the Plone
CMS as web publishing tool. The design architecture is a component-based architecture one starting
from the Zope3 CA framework. There are components to integrate the OAI protocol in order exchange
metadata among applications, to create explicit relations among documents allocated in different
computational node. The Octpay3 framework manages cartographic document too.
In the paper we describe the component architecture adopted, wit special attention to the functionalities
and techniques used to overcome the Zope/Plone environment. Next, the Octapy Configuration Mark-
up Language (OCML) is described together some example of its usage to described the document
structure. OCML allow both to personalize the managed contents and to easily extend the environment.
The set up used to test it with cultural heritage contents is also described.
We developed the napolibniculturali.it network of cultural heritage knowledge providers. To each
provider the Octapy3 environment provide them with a set of tools, for example, to implement the
cartographic interface for contents mediation, to build intermuseum virtual collections, stressing out
either the effective visit or the conceptual features. napolibeniculturali.it is sponsored and used
by the Direzione Regionale per i Beni Culturali e Paesaggistici della Campania to promote
knowledge about cultural heritage goods of Campania. Currently this community is built of
about 50 information node providers, and it interoperates with the Italian cultural heritage
portal managed by the Italian Ministers of Cultural Heritage.
Istituto di Cibernetica “E. Caianiello”
via Campi Flegrei, 34
Pozzuoli - Napoli
info@ais.cib.na.cnr.it
2. Cooperative communities and Content Management Systems
Thanks to diffusion of low cost high-speed Internet connections, institutions and organizations
face increasing demands to cooperate in sharing common knowledge. Many public institution,
museum and library publish their contents over network in a digital manner. Much of this
content is dynamically produced using of server side and distributed services technology.
Today content delivery and sharing information across the network is possible using a
variety of technologies, such as distributed databases, service oriented applications, and so
forth. Nevertheless, sharing content technology is only one aspect of content management in
cooperative and distributed settlement. Furthermore, content needs to be created, managed,
revised and finally published. It needs also to be aggregated in digital collection which in turn
are eventually shared. Content Management Systems (CMS) are suitable for this part of content
management. Modern CMS, like Plone, exposes very complete environment to support users
in content production. Thanks to a powerful, complete and user-friendly interface it is very
simple to create, to manage and to store content. However most of CMS has a poor support to
document distribution over the network which it suitable for the system interoperability. They
mainly focus the attention essentially on the users’ interaction and documents use. Documents
do not play an active rule in content sharing.
To share documents in a machine understandable way de facto representation standard for
contents, like XML and RDF technologies, and metadata, like Dublin Core and OAI, are necessary.
Moreover, documents must provide both user and machine oriented different representations,
and play an active rule in sharing of data.
Octapy is a distributed environment for content management that meets these challenges.
It does this by combining a number of key features including:
Powerful component model: Octapy introduces a flexible component model that
enables the creation of content-oriented extension that can be generic and not tightly
coupled with the documents schema. To share contents represented though different
documents schema an abstract model to add context dependent information to metadata
is defined.
Multiple document representations: each document in Octapy provides multiple
representations user and machine oriented. Using the XML and RDF widespread standard,
documents can be exchanged across different web site even if they haven’t the proper
document definition.
Support to semantic web technologies: Octapy brings semantic web technology in
a powerful Content Management System, allowing interoperability to other systems.
It introduces a document model suitable for interoperability with legacy system and
provides a framework for development of custom document interpreters.
Extensible metadata management: Octapy documents contain metadata that can
express any type of relationships such as membership in collections, parent-child
relations or taxonomic relationships. Moreover, Octapy document repositories are fully
conformant with the Open Archive Initiative Protocol for Metadata Harvesting (OAI-
PMH).
Introduction to Octapy 3
Octapy adds new functionalities to the Plone CMS, such as support distributed documents
over the network, fast definition of new content types using a configuration language and a
2
3. component model to easily build new extensions. In Octapy, contents play a central role and
they are active part of the process of interoperability between different systems. Contents aren’t
only data, but active software components that exposes a well-defined API and different kind of
representations both user and machine oriented.
From an architecture point of view, Octapy can be split into three main application levels.
Figure 1 schematizes such levels.
Figure 1 - Octapy 3 Architecture
Documents Definition Layer: Octapy adds functionalities to simplify defining process
for new document types. In Octapy the document definition is carried out during the
configuration phase, introducing a new XML-based format called OCML, in contrast to Plone
where the definition of new content types is achieved using the Archetype framework,
that imply the development of a new product must by carried by the user. Furthermore,
such product must provides all archetypes with their application and presentation logic.
Content Components Layer: one of the main goals of Octapy is to abstract from the content
structure introducing a clear separation among application layers, achieved using the Zope
3 Component Architecture. Starting from configuration file expressed in OCML, Octapy
generates specific components that represent contents, called “content component”, that
expose an interface that describes the structure of document, the relations with other
documents and other kind of information useful for developing additional functionalities.
Distributed and Cooperative Layer: Octapy is designed to build communities of cooperating
web information node providers. Therefore, special attention has been paid to support
standards for interoperability, such as XML for data representation, RDF/RDFS for semantic
interoperability, DC (Dublin Core) metadata set and OAI (Open Archive Initiative) protocol
for metadata exchange among heterogeneous systems. Thanks to these standards and
protocols, web sites build using Plone CMS and the Octapy extension can easily exchange
documents, allow distributed search and other kind of interoperability, even if a web
site hasn’t the proper document definition. In Plone only known type of content types
could be handled while in Octapy remote documents even if a local web site hasn’t the
corresponding content type definition could be managed.
The Octapy Configuration Mark-up Language
One of the Octapy goals is to allow new content types definition during the CMS installation
and setup configuration phase, without requiring to write Python code. To pursue this goal we
defined a new configuration language, called Octapy Configuration Mark-up Language (OCML)
an XML-based configuration language that allows: to define new document types, to choose the
storage methods for documents or part of them and to assign user presentation to contents.
3
4. The OCML tags, called directives, are grouped in three main categories, labelled using
the XML namespaces: data, storage and view. A minimal OCML document structure is:
<octapy xmlns:view=”http://namespaces.remuna.org/octapy-view”
xmlns:data=”http://namespaces.remuna.org/octapy-data”
xmlns:storage=”http://namespaces.remuna.org/octapy-storage”>
…
</octapy>
The OCML:
namespace data. The data directives allow the user to define: new content types
and the associated structure (that is the fields of the content), to express parent-child
relationship among documents. For example, in Octapy, documents can be composed
to form hierarchical structures using the containment relation “is-composed-by” and
the corresponding “is-part-of”. A document that can contain other documents is called
containerish document, and it acts simultaneously in Plone like a simple content and
a folder.
A new content type is defined by the data:document directive, and fields are
defined using data:field directives. Fields can be logically grouped using data:
section directives (they will appear in different archetype schemata).
<octapy xmlns:view=”http://namespaces.remuna.org/octapy-view”
xmlns:data=”http://namespaces.remuna.org/octapy-data”
xmlns:storage=”http://namespaces.remuna.org/octapy-storage”>
<data:document name=”Artistic Object” id=”ArtisticObject”
subtypes=”(localization, status)”>
<data:section name=”General Info”>
<data:field name=”id” type=”String” languageIndependent=”True”
default=”1000” mode=”r” />
<data:field name=”title” type=”String” searchable=”True”
languageIndependent=”false” required=”True”
default=”Title”/>
<data:field name=”oss” type=”Text” searchable=”true”
languageIndependent=”false” required=”false”
metadata=”{‘uiuse’:’description’}” />
<data:field name=”inventory” type=”int” searchable=”true”
languageIndependent=”true” required=”false” />
<data:field name=”image” type=”Image” searchable=”false”
languageIndependent=”true” required=”true” />
</data:section>
</data:document>
</octapy>
The previous OCML code fragment defines a new content type named “Artistic Object”
(a kind of cultural heritage used to catalogue artistic object like paints, furniture, etc)
that can have two subdocuments (localization and status). ArtisticObject
has five fields defined by the data:field directive. Each field has its type, defined
by the name attribute, plus other options that are mainly Archetype schema field
attribute (as described forward in the document, Octapy generates corresponding
4
5. Archetype schema starting from OCML directives). The special attribute metadata will
be further described in next section.
namespace storage. Using the namespace storage directives the user can associate
to a document or a part of it, of a given content type, a storage mechanism. The
following fragment of OCML code defines that ArtisticObject has persistence into a
PostgreSQL database (using the archetype ability to serialize objects into database via
Zope Adapters), but the field image has the specific persistence into the filesystem (at
path specified with the corresponding param).
<octapy xmlns:view=”http://namespaces.remuna.org/octapy-view”
xmlns:data=”http://namespaces.remuna.org/octapy-data”
xmlns:storage=”http://namespaces.remuna.org/octapy-storage”>
<storage:apply
for=”ArtisticObject”
type=”Postgres”>
<param name=”dbname”>preale</param>
<param name=”user”>username</param>
</storage:apply>
<storage:apply
for=”ArtisticObject.image”
type=”FS”>
<param name=”path”>/usr/local/data/images</param>
</storage:apply>
</octapy>
namespace view: Using the namespace view directives the user can define specific
aspects related to the document presentation. It’s possible to define which widget to
use to display a field of a document. Two directives can be used to cover this operation:
view:for, used to specify the widget of a specific field; view:fordata used to
specify the widget of a field type (e.g. Text, Image, ecc). The following fragment of
OCML code shows the view:fordata directive usage.
<octapy xmlns:view=”http://namespaces.remuna.org/octapy-view”
xmlns:data=”http://namespaces.remuna.org/octapy-data”
xmlns:storage=”http://namespaces.remuna.org/octapy-storage”>
<view:widget
fordata=“Text”
type=“StringWidget”
<view:configure>
<view:param name=”maxlength”>255</view:param>
</view:configure>
</view:widget>
</octapy>
The OCML specification allows arranging directives between multiple files using the
special directive <include src=”filename” />. For a more detailed OCML reference, see
5
6. [ACAM07].
The Octapy 3 component model
Thanks to Zope 3 Component Architecture, Octapy utilizes the component model also for
the document contents, so that it is possible to abstract from the specific content schema. To
achieve that we developed the Octapy “content components” that it is in charge to automatically
generate the Zope 3 components starting from OCML document type description. The generation
process is carried out from YODA (Yoda is Octapy Document Assembler) that generates both
the archetype code and the interface describing the document structure. This interface is an
enumeration of attributes for each field of the content type and the corresponding archetype
class implements this interface leading to a “content component”.
Figure 2 – The Octapy component model
Each content component implements, see Figure 2, at least two interfaces: the content
type definition and the IOctapyInterface. IOctapyInterface is an interface common to
all content components and exposes the method getContentInteface() which returns the
interface describing the content type, i.e. it allows to lookup for the specific data interface. The
following Python code snippet illustrates the role of the IOctapyContent interface.
6
7. from Products.Octapy.interfaces import IOctapyContent
contents = aFolder.objectItems()
for c in contents:
if c.directlyProvides(IOctapyContent): #Ok, it’s an Octapy content
iface = c.getContentInterface()
print “Content-component interface: ”, iface
for attr in iface: print “Field: ”, attr
Running this script on a folder, containing instances of “ArtisticObject” so as defined in
the previous paragraph, generates the following output:
Content-Component inteface: IArtisticObject
Field: id
Field: title
Field: oss
Field: inventory
Field: image
The component model introduced in Octapy allows to handle all the managing contents
extensions in a generic way. An adapter, to the fixed interface IOctapyContent, adds the
required functionalities to Octapy system. For example, the presentation interfaces can be
built using Browser Pages component that adapts IOctapyContent and access to the content
interface via getContentInterface() method. Moreover, it also possible to write extensions
for a given data schema simply adapting the content component generated interface.
Interpretation models: the metadata attribute
The component model introduced by Octapy has been designed to make software reusable
and abstract from a particular data schema. All the Octapy extensions must be designed setting
aside from the structure of documents and the way to assign special meaning to field is to use
interpretation models.
In an application data layer, in general, the content fields have no associated meaning, since
they are only container used to store fixed data. For example, in the ArtisticObject defined
previously, the fields oss and title are simply container for lines of text. Nevertheless, to these
fields we can associate special meaning in other context, for example, oss is the description
field of an Artistic Object and in the presentation layer could be displayed to user with a given
layout, maybe under the image of the object with special formatting and typesetting. This
means that a document, or a part of it, can have special interpretation that must be handled
in proper way by the software.
In OCML a special attribute of data:field directive has been introduced: metadata, whose
values can be used to specify which interpretation model is associate to a field. For example,
the value:
<data:field name=”oss “ type=”Text” metadata=”{‘uiuse’:’description’}” />
points out to the presentation layer that the field is the description of an Artistic Object, and
7
8. must be properly processed. The values of metadata attribute are transparent to the data
layer and other application layers: only components that know how treat this information will
use it. The interpretation model is available to extension via the component model, using the
ability of Zope 3 interfaces to annotate attribute and method with tags. The corresponding
content interfaces generated by YODA is annotated with information provided in metadata
attribute using Zope 3 setTaggedValue() method. The following fragment of code shows the
corresponding interface generated from the OCML ArtisticObject content type definition.
from zope.interface import Interface
class IArtisticObject(Interface):
id = Attribute()
id.setTaggedValue(‘datatype’, ‘String’)
title = Attribute()
title.setTaggedValue(‘datatype’, ‘String’)
oss = Attribute()
oss.setTaggedValue(‘datatype’, ‘Text’)
oss.setTaggedValue(‘ui:use’, ’description’)
inventory = Attribute()
inventory.setTaggedValue(‘datatype’, ‘Int’)
IArtisticObject.setTaggedValue(’contenttype’, ’ArtisticObject’)
IArtisticObject.setTaggedValue(’contenttypename’, ‘Artistic Object’)
Extension modules can access to information provided via metadata attribute using the
corresponding getTaggedValue()method. The following snippet of code shows a possible
interpretation models application.
from Products.Octapy.interfaces import IOctapyContent
content = aFolder.objectItems()[0]
if content.directlyProvides(IOctapyContent):
iface = content.getContentInterface()
print “Inspecting contenttype: “, iface.getTaggedValue(“contenttype”)
for attr in iface:
if “uiuse” in iface[attr].getTaggedValues():
#Prints all attributes which have the metadata ‘uiuse’
uiuse = iface[attr].getTaggedVelue(“uiuse”)
value = iface[attr].value
print “Special attr ‘%s’ with uiuse ‘%s’: %s” % (attr, uiuse, value)
else:
value = iface[attr].value
type = iface[attr].getTaggedValue(‘datatype’)
print “Attr ‘%s’: %s(%s)” % (attr, value, type)
Running this script on a folder, that contains instances of “ArtisticObject” defined in the
previous paragraph, generates the following output:
8
9. Inspecting contenttype: ArtisticObject
Attr ‘id’: atoggettoartistico.2007-07-19.0117652569(String)
Attr ‘title’: Morte dell’ammiraglio Cotigly (String)
Special attr ‘oss’ with uiuse ‘description’: Il dipinto raffigura…
Attr ‘inventary’: 2111232(Int)
Attr ‘immge’: <byte data>(Image)
It is important to underline that interpretation models are not only used for presentation
logic, but may be used whenever it is necessary to associate a special meaning to a field. For
example, the Octapy Dublin Core subsystem uses the metadata attribute to map fields name to
the DC metadata set, as shown in the following example:
...
<data:field name=”descrizione_breve” type=”Text” metadata=”{‘dc’:’title’}”/>
<data:field name=”autore_scheda” type=”Text” metadata=”{‘dc’:’author’}”/>
...
Distributed and cooperative functionalities
Octapy has been designed to brings functionalities for content-based interoperability in
order to have communities of distributed contents providers that share common knowledge.
In Octapy the information sharing is achieved exchanging documents, each document has
multiple representations, most of them based on XML. One of the available representations is
called Octapy eXchange Format (OXF), an XML serialization exposed by all object that provide
the IOctapyContent interface. OXF exports both document content and its structure, that
is its content type definition. The following example shows the OXF serialization of an Artistic
Object.
<?xml version=”1.0” encoding=”UTF-8”?>
<octapy-document
xmlns:dc=”http://purl.org/dc/elements/1.1”
xmlns:cmf=”http://cmf.zope.org/namespaces/default”
xmlns:xmp=”http://octapycms.remuna.org/xmp”
xmlns:base=”http://octapycms.remuna.org/oxf” version=”3.0”>
<cmf:type name=”Artistic Object”>ArtisticObject</cmf:type>
<uid>1fa69193d3814971f2d9d0627191d771</uid>
<field
id=”id”
name=”id”
type=”id”>atoggettoartistico.2007-07-19.0117652569</field>
<dc:title>Morte dell’ammiraglio Cotigly</dc:title>
<dc:creator>v.izzo</dc:creator>
<dc:language>it</dc:language>
<translation lang=”en”>
http://preale.napolibeniculturali.it/docs/OA123-en
</translation>
<xmp:CreateDate>2007/07/19 15:00:11.824 GMT+2</xmp:CreateDate>
<xmp:ModifyDate>2007/07/19 15:00:12.113 GMT+2</xmp:ModifyDate>
<field
type=”String”
name=”title”
9
10. label=”Object title”>
<content>Morte dell’ammiraglio Cotigly</content>
</field>
<field
type=”Integer”
name=”inventory”
label=”Inventory number”>
<content>2111232</content>
</field>
<field
type=”Text”
name=”oss”
label=”Description”>
<content>Il dipinto raffigura.......</content>
<metadata name=”ui:use”>description</metadata>
</field>
</octapy-document>
An OXF serialization allows to implement and manage remote contents like local contents,
even in the case if the CMS doesn’t have the definition of the remote content type. OXF reports
the structure of document, its fields and their type, the content of each field and any additional
information necessary to manage a remote content. Octapy adds to default content types an
archetype called RemoteObject: it is used to store the URL of remote document, to parse the OXF
serialization, and to manage properly the document. Octapy manage RemoteObject as a content,
then it provides the IOctapyContent interface. A special base class of RemoteObject, called
OctapyProxy, manages the creation of the content interface, starting from the information
provided by OXF serialization. All interpretation models are properly added to fields providing
them so that presentation layer and other extension module can opportunely treat them.
The following python code snippet shows how it’s simple to manage remote content in Octapy
like a normal archetype stored into the CMS.
>>> from Products.Octapy.container import RemoteContainer
>>> from Products.Octapy.interfaces import IOctapyContainer, IOctapyProxy
#Obtains all documents stored in a remote container (folder)
>>> remoteFolder = RemoteContainer(“http://capodim.remuna.org/contents”)
>>> remoteFolder.directlyProvides(IOctapyContainer)
True
>>> contents = remoteFolder.objectItems()
>>> for c in contents:
... if c.directlyProvides(IOctapyContent): #Ok, it’s an Octapy content
print c.getContentInterface().getTaggedValue(“contenttype”)
...
OggettoArtistico
OggettoArtistico
......
>>> c.directlyProvides(IOctapyProxy)
True
#The content is in read only mode
>>> c.mode
’r’
>>> iface = c.getContentInterface()
#For the Italian National Museum of Capodimonte the description field is ‘oss’
>>> iface[‘oss’].getTaggedValue(‘uiuse’)
10
11. ’description’
>>> remoteFolder = RemoteContainer(“http://preale.remuna.org/contents”)
.......
>>> iface = c.getContentInterface()
#For the King Apartment in Naples the description field is
#‘descrizione_completa’
>>> iface[‘descrizione_completa’].getTaggedValue(‘uiuse’)
’description’
The example highlights also other Octapy interesting features. Folder as well documents can
be exported to other web sites and aggregated using the RemoteContainer class. Moreover,
every container in Octapy implements the IOctapyContainer interface and all remote contents
(documents and folders) implements the IOctapyProxy marker interface, i.e., those objects
are proxy for remote contents. Containerish documents expose both IOctapyContent and
IOctapyContainer interfaces.
Furthermore, the example shows the importance of the interpretation models too. Both
National Museum of Capodimonte and King Apartment in Naples preserve and manage Artistic
Objects although they don’t have an agreement to have the same field name for the heritage
good description field. They calls it oss (abbreviation of the Italian osservazione – in English
means observation) and descrizione_completa (in English means full description). Thanks
to interpretation models, system can treat it in the right way.
RDF/RDFS Serialization
To share data across web sites, Octapy makes available more representations. Some of
them are oriented to the semantic web and are based on RDF/RDFS language. The first step in
RDF serialization is the definition of a document model to be used in order to share a common
interpretation for the RDF classes and entities. Document model can be considered the RDF
equivalent of the Octapy component model: it acts as an abstract model to classify documents
and the associated interpretation. The following example shows a fragment the N3 serialization
of the Octapy document model.
@prefix : <http://octapycms.remuna.org/octapy#>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
:BaseContent a rdfs:Class.
:OctapyContainer a rdfs:Class;
rdfs:subClassOf :BaseContent.
:OctapyContent a rdfs:Class;
rdfs:subClassOf :BaseContent.
:caption a rdfs:datatype;
rdfs:subClassOf xsd:string.
:description a rdfs:datatype;
rdfs:subClassOf xsd:string.
:title a rdfs:Property;
11
12. rdfs:domain :BaseContent;
rdfs:range xsd:string.
For each document in the CMS, two RDF serializations are available: one containing the RDF
schema representing the content type; the other containing the class instances with document
content. The following two examples show, respectively, the RDFS class of an Artistic Object
and its instance.
@prefix : <http://preale.napolibeniculturali.it/docs#>.
@prefix octapy: <http://octapycms.remuna.org/octapy#>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#>.
@prefix xsd: <http://www.w3.org/2001/XMLSchema#>.
:inv a rdfs:Property;
rdfs:label “Invetory”^^<http://www.w3.org/2001/XMLSchema#string>;
rdfs:domain :ArtisticObject;
rdfs:range xsd:integer.
:loc a rdfs:Property;
rdfs:domain :ArtisticObject;
rdfs:range :localization.
:oss a rdfs:Property;
rdfs:label “Description”^^<http://www.w3.org/2001/XMLSchema#string>;
rdfs:domain :ArtisticObject;
rdfs:range octapy:description.
:localizzazione a rdfs:class;
rdfs:label “Localization”^^<http://www.w3.org/2001/XMLSchema#string>;
rdfs:subClassOf octapy:OctapyContent.
:ArtisticObject a rdfs:class;
rdfs:label “Artistic Object”^^<http://www.w3.org/2001/XMLSchema#string>;
rdfs:subClassOf octapy:OctapyContent.
@prefix : <http://preale.napolibeniculturali.it/docs#>.
@prefix contents: <http://preale.napolibeniculturali.it/contents#>.
@prefix dc1: <http://purl.org/dc/elements/1.1#>.
@prefix rdf: <http://www.w3.org/1999/02/22-rdf-syntax-ns#>.
contents:atoggettoartistico.2007-07-19.0117652569 a :ArtisticObject;
:loc [ a :localization];
:oss “Il dipinto raffigura.......”;
dc1:creator “v.izzo”;
dc1:language “it”;
dc1:title “Morte dell’ammiraglio Cotigly”.
It’s important to underline that the previous serializations are automatically generated by
12
13. Octapy, without any user intervention. RDF/RDFS serialization can be used in place of OXF
one.
RemoteObject uses Python rdflib library to parse RDF documents. Starting from RDF schema
it establishes the base class of the document. If it is an OctapyContent or OctapyContainer RDF
class, then it handles the document as Octapy document. Otherwise, it scans a global Zope list
called DIL (Document Interpreter List) finding any additional interpreters that can manage the
document. In this way, it is possible to extend Octapy to support other kind of RDF document,
in order to interoperate with other system, also with legacy systems too. For example, using
SquirrelRDF, a tool that can export database table in RDF graph, conventional DBMS legacy
data can be exported in a form suitable to be managed by Octapy, using the same document
model.
Octapy supports other form of interoperability through standard protocol for metadata
sharing, like the OAI-PMH protocol and the Dublin Core metadata set. Figure 4 shows the
interaction of the OAI Octapy subsystem with the component model. More information can be
found in [NOVI07].
Figure 4 – The integration of a OAI data provider in a Octapy based CMS
The napolibeniculturali.it test bed
We developed CMS Octapy having in mind his use in the context of Cultural Heritage
fostering. We started with the research project “Museo Virtuale di Napoli: Rete dei Musei di
Napoli” (ReMuNa)1 [REMU01]. Beside software and networking infrastructures design and
1
The project “Neapolitan Virtual Museum: the Neapolitan Network Museums” was budgeted by the Italian
Minister of University and Research (MIUR)
13
14. implementation 18 of the major museums in Naples were involved. Among them there were
Archivio di Stato di Napoli, Museo Archeologico Nazionale di Napoli, Museo di Capodimonte,
Certosa e Museo di San Martino, Museo Diego Aragona Pignatelli Cortes, Museo di Palazzo Reale,
Pinacoteca del Pio Monte della Misericordia, Museo del Tesoro di San Gennaro, Parco della Tomba
di Virgilio, Museo dell’opera di Santa Chiara. From the scientific point of view the main goals
were to verify on the field the possibility to create knowledge cooperating communities. Where
each participating could exchange its own managed knowledge so to improve their institutional
cooperation. Next, the Direzione Regionale per i Beni Culturali e Paesaggistici della Campania
decided to adopt both the organizational model, i.e. on one side to guarantee the autonomy of
the museum stakeholder and on the other side to improve the cooperation among the museums
and institutions, and the software platform. To foster the museums cooperation software tools
to aggregate the knowledge, both locally and remotely, were developed. Using these tools the
knowledge stakeholder could organize virtual exhibitions according to some physical or logical
criteria and regarding information, directly managed o shared with other stakeholders, about
cultural heritage goods. Currently the cultural heritage circuit of napolibeniculturali.it participate
more than 50 museums stakeholder. Since the software allow to exchange the contents through
the OAI-PMH then the circuit itself is included in the Italian cultural heritage portal2.
Figura 6 – The network infrastructure of napolibeniculturali.it
The network infrastructure on top of which the distributed CMS for the napolibeniculturali.it
community is running is built as a MPLS based Virtual Private Network (VPN). Each museum ha
an access point at 2 or 10 Mbps connected to its LAN. The VPN is connected to both Internet,
through a 4 Mbps channel, and to the network infrastructure of the Ministero per i Beni e le
Attività Culturali.
The Direzione Regionale per i Beni Culturali e Paesaggistici della Campania started up the
2
The project of Italian Cultural Heritage Portal is budgeted by the Ministero per i Beni e le Attività Culturali, It
collects some of the results obtained in the EU project Michael [MICH02], [MICH01].
14
15. project (campaniabeniculturali.i) to extend the experiment to the other cultural institutions in
Campania. For the end of 2007 the first months of 2008 we plan to extend the infrastructure
to include more than 100 nodes spread in the geographical region of Campania. This large
collection of sites will be organized in circuits, covering the territories around the main cities of
Campania, such as Benevento, Salerno, Caserta and Avellino. The cultural heritage knowledge
offering will be organized according thematic topics, such as the first civilizations in Campania,
the Roman civilization periods, the Gran tour and so on.
References & Bibliography
[ACAM07] P. Acampa, C.Noviello, Specifica OCML, Technical Sheet Octapy CMS
[AIEL06] Aiello A., M. Mango Furnari M., Massarotti A., Brandi S., Caputo V., Barone V., An experimental
Ontology Server for an Information Grid environment, Int. Journal on Parallel Programming, Dec. 2006
[BORG00] C. L. Borgaman, From Gutemberg to the global information infrastructure, MIT Press
[EDDO98] G. Eddon, H. Eddon, Distributed COM, Microsoft Press
[FURN05] M. Mango Furnari, C. Noviello, The integration of cartographic information into a Content
Management System, Proceeding of Internet Imaging VII Conference
[FURN05b] M. Mango Furnari, C. Noviello, Introduction to Octapy MapServer, http://oms.remuna.org
[GAMM95] E. Gamma et al., Design Patterns – Elements of Reusable Object-Oriented Software, Addison
Wesley
[GLUS05] R. J. Glushko, Document Engineering, MIT Press
[ICCD] Specifica ICCD, http://iccd.beniculturali.it
[KIRT99] M. Kirtland, Designing Component Based Applications, Microsoft Press
[MAPS01] MapServer Project Page, http://mapserver.gis.umn.edu/
[MICH01] Progetto MICHAEL, http://www.michael-culture.org
[MICH02] Progetto MICHAEL del Ministero per i Beni e le Attività Culturali, http://michael.beniculturali.it
[NOVI07] C. Noviello, Il Component-Model di Octapy 3, Technical Sheet Octapy CMS
15