Abstract
The Business School of the Polytechnic of Porto, Portugal aiming at following the demands of the region decided to make available a master's degree program in e-business. This paper describes the study held ascertain the most relevant skills to be considered in the master program. In order to obtain relevant feedback, an interview was conducted to professionals working in the field. Also, a questionnaire was applied to the students attending the last year of undergraduate after working programs, since they have already professional experience in related fields. The most relevant skills were identified, and curriculum was defined for the master's degree according to the analysis of the results of these activities.

Abstract
This paper presents the state of the art on methods for the development of a metadata application profile (AP). For this purpose we perform searches in scientific online databases and made other efforts such as global searches on the web and calls on the mailing lists of the metadata communities to find information about AP development and metadata best practices or methods for the development of AP. These searches produced 21 items of which nine have information on how the AP is developed. As a result of this analysis, we came up with small formulas or specific recipes for very particular phases of the process, but none is described in detail. We have also come up with guidelines that were too global and not sufficiently detailed for the AP development. As far as we could determine, there is no comprehensive methodological support for a metadata application profile development. Copyright © 2013 Inderscience Enterprises Ltd.

Abstract
Archaeological discoveries can benefit enormously from linked open data (LOD) technologies since, as new objects are discovered, data about them can be placed in the LOD cloud and instantly accessible to third parties. This article presents a framework developed to publish LOD on arrowheads from the Chalcolithic and Early/Middle Bronze Age chronologies (2800/2900 BC to 1500 BC) found in the last 25 years of excavations on an archaeological site in Portugal. These arrowheads were kept in boxes, hidden from the possibility of being studied and viewed by interested parties. The framework encompasses a metadata application profile (MAP) and tools to be used with this MAP, such as a namespace, two metadata schemas and eight vocabulary coding schemes. The MAP domain model was developed with the support of the scientific literature about this type of arrowheads, and the team integrated two archaeologists. This framework was created with the design philosophy of maximising data interoperability, so terms from the CIDOC CRM conceptual models and other vocabularies widely used in the LOD cloud were used. The MAP was tested using a set of seven arrowheads, which proved, in the first instance, the viability of the developed MAP. The team plans to test the model in future work with arrowheads of other excavations.

Abstract
These files are the recordings and transcripts of 3 interviews made to 3 Dublin Core Application Profiles developers with the aim to understand the process of a DCAP development. These interviews are framed in a PhD project that has as goal the definition of a method for the development of Dublin Core Aplication Profiles. An Application Profile is a construct on the Semantic Web that enhances interoperability.

Abstract
These are the results (datasets) of a study reported in the paper ``A panoramic view on Metadata Application Profiles of the last decade``.

Abstract
The development of Metadata Application Profiles is done in several phases. According to the Me4MAP method, one of these phases is the creation of the domain model. This paper reports the validation process of a domain model developed under the project POSTDATA - Poetry Standardization and Linked Open Data. The development of the domain model ran with two steps of construction and two of validation. The validation steps drew on the participation of specialists in European poetry and the use of real resources. On the first validation we used tables with information about resources related properties and for which the experts had to fill certain fields like, for examples, the values. The second validation used a XML framework to control the input of values in the model. The validation process allowed us to find and fix flaws in the domain model that would otherwise have been passed to the Description Set Profile and possibly would only be found after implementing the application profile in a real case.