How to model divergent views on one concept?

Such a central model is not only much harder to manage, but there is also the general problem that differerent departments like marketing, quality assurance, R&D, etc. will have divergent views on the model and its concepts. These different perspectives on one and the same concept are hard to unify in a single model.

Think of a company that sells mobile phones and wants to create a model of its line of products. It wants to utilize this model in the context of its online shop as well as in the context of its user support forum. While the structure of the model (i.e. the relationships between the products) might be very similar or the same in both contexts, there will be differences in which properties of the products are actually relevant in the respective contexts.

In the model of the marketing department there might be a concept for a “Phantastax StamiMaxx” cell phone with a definiton “The StamiMaxx has a powerful battery and is great for professionals who travel a lot”. They might relate it to manufacturer “ACME Corporation” and to several concepts representing different features like “Android OS”, “Multi-touch touchscreen”, etc.
The very same phone has different properties that are interesting from the Quality Assurance departement’s perspective. They might call it by a more specific name like “Phantastax i3000 StamiMaxx S”, have a different definition for it like “3G cell phone implementing the new WTF3000 protocol, …” and relate it to concepts representing known problems and their solutions.

Now they face the task to integrate these different models, as it is not desirable to use a bunch of isolated models within one company.

Support of collaborative work on distributed models

To support this kind of collaborative work on distributed knowledge models, we would like to link the concepts of the models, just as is we link documents in the World Wide Web. Fortunately the Simple Knowledge Organisation System (SKOS) offers mapping properties that can be used to define relationships between concepts from different knowledge models.

E.g. when we want to say that concept “Phantastax StamiMaxx” in the product line thesaurus refers to the same real world entity as concept “Phantastax i3000 StamiMaxx S” in the Quality Assurance thesaurus, then we can use skos:exactMatch to express that. If we want to express that the concepts are merly similar, skos:closeMatch could be used.

The other SKOS mapping properties express a hierarchical (narrowMatch, broadMatch) or an associative (relatedMatch) mapping relation between concepts from different concept schemes. With those we can say that my Samsung Galaxy concept has a skos:broadMatch “Smartphone” in the product line vocabulary and a skos:relatedMatch “ACME Corporation” in a controlled vocabulary about Tech companies.

Modularisation of knowledge models

In this way SKOS thesaurus management systems like PoolParty make it possible to modularise knowledge models, represent concepts in their different contexts and consequently enable collaborative work on those models: The marketing guy can work on his model with the concept properties focused on sales without disrupting the work of the quality assurance expert on her own thesaurus. Later one or both of them can create the skos:exactMatch link between the concepts that are the same, like seen in the “Exact Matching Concepts” box in screenshot of PoolParty below.

Enrich your knowledge: Get connected with the LOD Cloud

Going a step further the models could be connected to external knowledge, e.g. a source from the Linked Open Data (LOD) Cloud. Once we establish links to LOD hubs like DBpedia, we can import additional information for their concepts or use it to establish whether similar concepts from different models really refer to the same real world resource.

Digital Identity on the Semantic Web
Thursday, April 7, 2011

While recent developments in ICT make it easier for companies and consumers to reach each other, they can also scatter your personal information more widely, making life easier for criminals. On the other hand public institutions and government agencies are collecting personal data too. So personal data is processed without the consensus (or even the knowledge) of the respective citizen. As we know, leaks in this field may unleash sensible personal data as well. The misuse of personal data can be restricted – this is a challenge to both, the technological and the juridical domain. This meetup takes a look on how Semantic Web Technologies can take over its responsibility in this emerging field.

• Christof Tschohl (BIM)
  Ludwig Boltzmann Institute for Human Rights
• Mischa Tuffield (Garlik)
  A Standards-based, Open and Privacy-aware Social Web (W3C)

>> read more, and register for free



Portals, Apps and Visualizations for Open Government Data
Wednesday, June 15, 2011

Picking up Keith Andrews suggestion, this is a MeetUp focusing on tools, services and projects dealing with Visualization, Apps-creation and Portals/Catalogs for Open [Government] Data. As this MeetUp is on the eve of Austrians first Open Government Data – Conference (OGD2011) we expect to meet experts ans enthusiasts from Austria and abroad.

• Keith Andrews (IICM)
  Institute for Information Processing and Computer Supported New Media at Graz University of Technology
• Andreas Blumauer (SWC)
  Storing, searching, serving Open Government Data – getting an overview on the growing market for open data solutions

>> read more, and register for free





What´s obvious for most of the Semantic Web evangelists, isn´t clear for at least 75% of all exhibitors (and their clients) at DMS Expo. For these people who are dealing with core systems of today´s enterprise stacks it´s not quite clear that documents could be a valuable resource for enterprise knowledge management. They still focus rather on the basic idea that documents have to be revision-proof, they should be long-term archived and should be put into a safe. That´s quite the opposite of how content is organised in a (Corporate) Semantic Web. In such an environment each little piece of information at least has the potential to get linked with another piece of information.

Open World Assumption is not only about the way we put ontologies in place.

It is also about the basic assumption that people intend to get their content published and linked in a way that this creates an extra value for their colleagues and their organisations.

Documents are containers, and containers tend to be put into containers which are even bigger. In a world where documents are the atomic elements to get information organised the question always is: What should be in there?

On the Semantic Web information is no longer locked inside documents, same with wikis: The idea is to organise every little piece of information in a way that it can improve constantly because it´s out on the (corporate) web. Part of this evolution are mechanisms which help to get pieces linked in a meaningful way. On the Social Semantic Web this job is partly automatically executed and partly done by human beings. In this world which is based on the assumption that people would like to have their information out there on the stage the question always is: How can this piece of information get linked to other pieces in a meaningful way? Which metadata should be put on top?

It´s the people who make the difference, and for many of them there is still no “business use case” based on the “Open World Assumption”.

Here is my proposal: Appreciating each one´s work as a valuable resource for the whole organisation!

And I can hear the question already: Great, but how can I put this into my Excel?

The survey results also show considerable variation by sector, both of policy and technology implementation. With respect to technologies, ICT companies are also the most willing to consider semantic approaches. The ICT sector has an unusually high interest in all ST components, with 20% or more being willing to consider all of them, and over half of IT respondents looking at Web 2.0 (social computing). [...]  The use of tagging technologies – which overall is the least mature approach in the survey – is most advanced in Life Sciences. The Life Sciences, Media & Entertainment, and ICT sectors all have a reasonably strong interest in Natural Language Processing (roughly 25% on average). Ontologies and RDF/OWL are the technologies least often considered, though the interest in these Semantic Technologies is not insignificant. Taxonomies are slightly more popular, perhaps indicating that companies are taking the first step to prepare for a more semantic approach to IT solutions. The ICT, Energy & Utilities, and Media & Entertainment sectors all have a reasonably strong interest in using taxonomies.

The 190 pages report gives an actual overview of the status quo on European Semantic Technology Market and is now available for download: Final demand driven mapping Report

The interview covers questions like:

• How can Linked Data help to make companies more productive?
• Do you think that the Linked Data Initiative can build upon a stable architecture or will it face more and more problems the bigger the “cloud” will grow?
• What´s the ultimate argument for an Enterprise Architect to use languages like SPARQL at least in addition to SQL?
• How will a “Real Time Semantic Web” change the whole game?
• How will the “Semantic Web” be called in 10 years? Will there still be a “Semantic Web”?

Read the full version of the interview here. ]]> http://blog.semantic-web.at/2010/06/16/kingsley-idehen-i-only-think-in-terms-of-a-web-of-linked-data/feed/ 0 http://blog.semantic-web.at/2009/09/10/webinars-about-business-use-of-semantic-technologies/ http://blog.semantic-web.at/2009/09/10/webinars-about-business-use-of-semantic-technologies/#comments Thu, 10 Sep 2009 11:14:42 +0000 Thomas Schandl http://blog.semantic-web.at/?p=1153 Continue reading →]]> The Semantic Web Company created a series of online seminars (aka webinars) for you to acquire basic and practical knowledge about methologies, technologies and standards of the Semantic Web. In 90 minute sesseions we will cover the business aspects of topics such as content engineering, Knowledge Management, business intelligence, e-Business and more.

In order to allow for a high level of interaction, the attendance is limited to ten participants and ample time for questions and discussion with our experts is designated. Each webinar works as a stand-alone module, so you can pick and choose some of them or book the whole series of 6 webinars.

We’ll kick off with a session about Semantic Wikis on Thursday 22nd of October. A German language version will be held at 9 a.m., alternatively you can atted an English version at 6 p.m. CET.

Each Thursday we cover a different topic such as Semantic Search, Corporate Thesaurus Management, Text Mining on the Corporate Semantic Web, Linking Open Data and Semantic Advertising.

In order to participate you only need broadband access to the internet, Windows or a Mac and a fairly up-to-date browser. For detailed system requirement see the webinar overview.

We hope to talk to you in one or more of these sessions!

Markus Luczak-Rösch and his team from FU Berlin have published loomp, a WYSIWYG annotation tool especially designed for inhouse use. loomp is aiming at the Corporate Semantic Web market, providing a semantic application with low entry barriers and high usability designed for non-techies.

When asked about the concrete application area Markus says:

We have found various use cases especially in knowledge and content intense domains. The most interesting one is the journalists use case. Consider journalists which research and write articles and editors which revise and publish the work of journalists.

Journalists research specific topics on demand and access various information sources for this purpose, e.g. websites, books, related articles, and human informants. Only few journalists use digital devices for this task and even fewer apply information management systems. To transfer the finished article to the responsible editor at the publishing house the people use free text documents and email communication. Finally, an editor revises and releases the articles for his department. loomp can help journalists to manage their notes, interview logs, references, addresses, etc. loomp helps to link an article to its information sources.

Read the full interview here.

Besides an insight in many aspects of the initiative, the interview provides thoughts on how connected business-models, in providing services, could look like.

[read more]

Corporate Semantic Web addresses both the consumer and the produce side, where consumers and producers might be humans as well as automated services, e.g. in business processes and enterprise service networks. This also includes the adequate engineering, modelling, negotiation and controlling of the use of the (meta)data and meaning representations in a (collaborating) community of users or services in enterprise settings where the individual meanings as elements of the internal cognitive structures of the members become attuned to each others’ view in a communicative process. This allows dealing with issues like ambiguity of information and semantic choices, relevance of information, information overload, information hiding and strategic information selection, as well as positive and negative consequences of actions (e.g. in a decision making process).

But, CSW does not only address the technological aspect but also the pragmatic aspect of actually using Semantic Web technologies in enterprises, which includes learning and training aspects as well as economical considerations. Incentives need to be provided to encourage in-house adoption and integration of these new Corporate Semantic Web technologies into the existing IT infrastructures, services and business processes. Decision makers on the operation, tactical and strategic IT management level need to understand the impact of this new technological approach and its adoption costs and return on investment. Therefore, companies will have in mind the economical justifiability of the deployment of new technologies.

I think he addresses some really crucial aspects of this emerging application field. Read the full interview here.

Corporate Semantic Web will also be a major topic at this year’s I-Semantics Conference from Sept. 2 – 4, 2009 in Graz/Austria. Also check out the forthcoming Semantic Web Meetup in Berlin on March 20, 2009, which is organized by Adrian Paschke’s team and the Semantic Web Company.

It’s fashionable to have a corporate wiki installed at the own company. But often – to speak a word of truth – this wikis are not more than a burial ground of vague project memos. This isn’t a big surprise, because often corporate strategy on innovate wikis into company’s every day life, comes in a simple triple jump: (1) buy some software, (2) get a one-day workshop, (3) write a binding memo to employees to use that wiki. Leaving the process in such a kind, wikis are developing the way that is inherent for them: run riot (optimistic case) or run dry (normal case).

But wikis are extensive and powerful instruments in corporate life. You can plan, communicate, document and control everyday corporate processes with them – within a common environment. So wikis are less a chunk of software, they are more the potential future working environment, where employees are “living in”. So, as careful as we are furnish our offices, we should also setup our virtual working place: The corporate wiki.

Andreas Heilwagen points out some tips on innovate corporate wikis right at “Computerwoche”

• clear rules and responsibilities
• do not start with empty wikis
• so called “champions” have to smooth the way
• change your mind on information processing
• be careful with vendor-specific plugins
• do not outsource to professional information brokers
• everybody should be able to edit (nearby) every page
• get your pages connected intern and extern
• always create useful information which others can reuse

Following my statement at the beginning, I would add:

• get a clear definition about the fields you want to use the wiki for
• identify company’s surplus in having a wiki
• see which tools and services bring some very personnel benefit for the employees

It’s the preparation phase which is essential in the quaetion on how effective the work with a future corporate wiki can be. Vienna based Semantic Web Company exemplary runs through such a preparation phase this days. Getting data, using tools like storytelling, personas and usage scenarios, this may end in a “well equipped working environment of the future” – the corporate wiki.

Retated:

• Oracle Fusion ECM: Enterprise Wiki Strategies