Matches in ScholarlyData for { ?s ?p ?o. }
- 176 type InProceedings.
- 176 label "Supporting Linked Data Production for Cultural Heritage institutes: The Amsterdam Museum Case Study".
- 176 sameAs 176.
- 176 abstract "Within the cultural heritage field, proprietary metadata and vocabularies are being transformed into public Linked Data. These efforts have mostly been at the level of large-scale aggregators such as Europeana where the original data is abstracted to a common format and schema. Altough this approach ensures a level of consistency and interoperability, the richness of the original data is lost in the process. In this paper, we present a transparent and interactive methodology for ingesting, converting and linking cultural heritage metadata into Linked Data. The methodology is designed to maintain the richness and detail of the original metadata. We introduce the XMLRDF conversion tool and describe how it is integrated in the ClioPatria semantic web toolkit. The methodology and the tools have been validated by converting the Amsterdam Museum metadata to a Linked Data version. In this way, the Amsterdam Museum became the first ‘small’ cultural heritage institution with a node in the Linked Data cloud.".
- 176 hasAuthorList authorList.
- 176 isPartOf proceedings.
- 176 keyword "Cultural Heritage".
- 176 keyword "Linked Data".
- 176 keyword "Museums".
- 176 title "Supporting Linked Data Production for Cultural Heritage institutes: The Amsterdam Museum Case Study".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasItem item-4.
- authorList hasItem item-5.
- authorList hasItem item-6.
- authorList hasItem item-7.
- authorList hasLastItem item-7.
- item-1 type ListItem.
- item-1 hasContent viktor-de-boer.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent jan-wielemaker.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent judith-van-gent.
- item-3 next item-4.
- item-3 previous item-2.
- item-4 type ListItem.
- item-4 hasContent michiel-hildebrand.
- item-4 next item-5.
- item-4 previous item-3.
- item-5 type ListItem.
- item-5 hasContent antoine-isaac.
- item-5 next item-6.
- item-5 previous item-4.
- item-6 type ListItem.
- item-6 hasContent jacco-van-ossenbruggen.
- item-6 next item-7.
- item-6 previous item-5.
- item-7 type ListItem.
- item-7 hasContent guus-schreiber.
- item-7 previous item-6.
- 192 creator annika-wolff.
- 192 creator paul-mulholland.
- 192 creator trevor-collins.
- 192 type InProceedings.
- 192 label "curate and storyspace: An ontology and web-based environment for describing curatorial narratives".
- 192 sameAs 192.
- 192 abstract "Existing metadata schemes and content management systems used by museums focus on describing the heritage objects that the museum holds in its collection. These are used to manage and describe individual heritage objects according to properties such as artist, date and preservation requirements. Curatorial narratives, such as physical or online exhibitions tell a story that spans across heritage objects and have a meaning that does not necessarily reside in the individual heritage objects themselves. Here we present curate, an ontology for describing curatorial narratives. This draws on structuralist accounts that distinguish the narrative from the story and plot, and also a detailed analysis of two museum exhibitions and the curatorial processes that contributed to them. storyspace, our web based interface and API to the ontology, is being used by curatorial staff in two museums to model curatorial narratives and the processes through which they are constructed.".
- 192 hasAuthorList authorList.
- 192 isPartOf proceedings.
- 192 keyword "cultural heritage".
- 192 keyword "museum".
- 192 keyword "narrative".
- 192 keyword "ontology".
- 192 keyword "plot".
- 192 keyword "story".
- 192 title "curate and storyspace: An ontology and web-based environment for describing curatorial narratives".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasLastItem item-3.
- item-1 type ListItem.
- item-1 hasContent paul-mulholland.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent annika-wolff.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent trevor-collins.
- item-3 previous item-2.
- 193 creator damir-vandic.
- 193 creator flavius-frasincar.
- 193 creator lennart-nederstigt.
- 193 creator steven-aanen.
- 193 type InProceedings.
- 193 label "SCHEMA - An Algorithm for Automated Product Taxonomy Mapping in E-commerce".
- 193 sameAs 193.
- 193 abstract "This paper proposes SCHEMA, an algorithm for automated mapping between heterogeneous product taxonomies in the e-commerce domain. It contributes towards effective aggregation of product information from different sources, in order to reduce search failures in online shopping. SCHEMA utilises word sense disambiguation techniques, based on the ideas from the algorithm proposed by Lesk, in combination with the semantic lexicon WordNet. It introduces a node matching function, based on inclusiveness of the categories in conjunction with the Levenshtein distance for class labels, for finding candidate map categories, and for assessing path-similarity. The final mapping quality score is calculated using the Damerau-Levenshtein distance and a node-dissimilarity penalty. The performance of SCHEMA was tested on three real-life datasets and compared with PROMPT and the algorithm proposed by Park & Kim. It is shown that SCHEMA improves considerably on both recall and F1-score, while maintaining similar precision.".
- 193 hasAuthorList authorList.
- 193 isPartOf proceedings.
- 193 keyword "product taxonomy".
- 193 keyword "semantic similarity".
- 193 keyword "taxonomy mapping".
- 193 keyword "word sense disambiguation".
- 193 title "SCHEMA - An Algorithm for Automated Product Taxonomy Mapping in E-commerce".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasItem item-4.
- authorList hasLastItem item-4.