Using BMEcat Catalogs as a Lever for Product Master Data on the Semantic Web

author: Alex Stolz, E-Business and Web Science Research Group, Bundeswehr University of Munich
published: July 8, 2013,   recorded: May 2013,   views: 3276
Categories

Slides

Related content

Report a problem or upload files

If you have found a problem with this lecture or would like to send us extra material, articles, exercises, etc., please use our ticket system to describe your request and upload the data.
Enter your e-mail into the 'Cc' field, and we will keep you updated with your request's status.
Lecture popularity: You need to login to cast your vote.
  Delicious Bibliography

Description

To date, the automatic exchange of product information between business partners in a value chain is typically done using Business-to Business (B2B) catalog standards such as EDIFACT, cXML, or BMEcat. At the same time, the Web of Data, in particular the GoodRelations vocabulary, o thers the necessary means to publish highly-structured product data in a machine-readable format. The advantage of the publication of rich product descriptions can be manifold, including better integration and exchange of information between Web applications, high-quality data along the various stages of the value chain, or the opportunity to support more precise and more ef ective searches. In this paper, we (1) stress the importance of rich product master data for e-commerce on the Semantic Web, and (2) present a tool to convert BMEcat XML data sources into an RDF-based data model anchored in the GoodRelations vocabulary. The benefi ts of our proposal are tested using product data collected from a set of 2500+ online retailers of varying sizes and domains.

See Also:

Download slides icon Download slides: eswc2013_stolz_bmecat_01.pdf (1.3 MB)


Help icon Streaming Video Help

Link this page

Would you like to put a link to this lecture on your homepage?
Go ahead! Copy the HTML snippet !

Write your own review or comment:

make sure you have javascript enabled or clear this field: