[CFP - Extended Deadline 20/11] Semantic Web Journal - Special Issue on Quality Management of Semantic Web Assets (Data, Services and Systems)

Sebastian Hellmann <[email protected]> Fri, 23 Oct 2015 13:00:32 +0200
Newsgroups gmane.org.w3c.annotation
Message-ID <[email protected]>
This is a multi-part message in MIME format.
--------------080303020507060209040204
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

*Extended Deadline November 20, 2015

CFP: Semantic Web Journal - Special Issue on Quality Management of 
Semantic Web Assets (Data, Services and Systems):* 
http://www.semantic-web-journal.net/blog/call-papers-special-issue-quality-management-semantic-web-assets-data-services-and-systems


    Submission guidelines

*Deadline:October 31, 2015* > *November 20, 2015**
*

Submissions shall be made through the Semantic Web journal website at 
http://www.semantic-web-journal.net. Prospective authors must take 
notice of the submission guidelines posted at 
http://www.semantic-web-journal.net/authors. Note that you need to 
request an account on the website for submitting a paper. Please 
indicate in the cover letter that it is for the Special Issue on Quality 
Management of Semantic Web Assets (Data, Services and Systems).

Submissions are possible in the following categories: full research 
papers, application reports, reports on tools and systems, and case 
studies. While there is no upper limit, paper length must be justified 
by content.


    Guest editors

  * Amrapali Zaveri, University of Leipzig, AKSW Group, Germany
  * Dimitris Kontokostas, University of Leipzig, AKSW Group, Germany
  * Sebastian Hellmann, University of Leipzig, AKSW Group, Germany
  * Jürgen Umbrich, Vienna University of Economics and Business, Austria

*Overview and Topics*

The standardization and adoption of Semantic Web technologies has 
resulted in a variety of assets, including an unprecedented volume of 
data being semantically enriched and systems and services, which consume 
or publish this data. Although gathering, processing and publishing data 
is a step towards further adoption of Semantic Web, quality does not yet 
play a central role in these assets (e.g., data lifecycle, 
system/service development).

Quality management essentially refers to activities and tasks involved 
to guarantee a certain level of consistency and to meet the quality 
requirements for the assets. In general, quality management consists of 
the following four phases and components: (i) quality planning, (ii) 
quality control, (iii) quality assurance and (iv) quality improvement.

The quality planning phase in the Semantic Web typically involves the 
design of procedures, strategies and policies to support the management 
of the assets. The quality control and assurance components have their 
primary aim in preventing errors and to meet quality requirements 
pertaining to the Semantic Web standards. A core part for both 
components are quality assessment methods which provide the necessary 
input for the controlling and assurance tasks.

Quality assessment of Semantic Web Assets (data, services and systems), 
in particular, presents new challenges that were not handled before in 
other research areas. Thus, adopting existing approaches for data 
quality assessment is not a straightforward solution. These challenges 
are related to the openness of the Semantic Web, the diversity of the 
information and the unbounded, dynamic set of autonomous data sources, 
publishers and consumers (legal and software agents). Additionally, 
detecting the quality of available data sources and making the 
information explicit is yet another challenge. Moreover, noise in one 
data set, or missing links between different data sets, propagates 
throughout the Web of Data, and imposes great challenges on the data 
value chain.

In case of systems and services, different implementations follow the 
specifications for RDF and SPARQL to varying extents, or even propose 
and offer new, non-standardized extensions. This causes strong 
incompatibilities between systems, e.g., between the used SPARQL 
features in the query engines and support features in RDF stores. The 
potential heterogeneity and incompatibility poses several challenges for 
the quality assessments in and for such systems and services.

Eventually, quality improvement methods are used to further enhance the 
value of the Semantic Web Assets. One important step to improve the 
quality of data is identifying the root cause of the problem and then 
designing corresponding data improvement solutions. These solutions 
select the most effective and efficient strategies and related set of 
techniques and tools to improve quality. Quality improvement metrics for 
products and services entails understanding and improving operational 
processes and establishing valid and reliable service performance measures.

This Special Issue is addressed to those members of the community 
interested in providing novel methodologies or frameworks in managing, 
assessing, monitoring, maintaining and improving the quality of the 
Semantic Web data, services and systems and also introduce tools and 
user interfaces which can effectively assist in this management.


    Topics of Interest

We welcome original high quality submissions on (but are not restricted 
to) the following topics:

  * Methodologies and frameworks to plan, control, assure or improve the
    quality of Semantic Web Assets
  * Quality exploration and analysis interfaces
  * Quality monitoring
  * Developing, deploying and managing quality service ecosystems
  * Assessing the quality evolution of Semantic Web Assets
  * Large-scale quality assessment of structured datasets
  * Crowdsourcing data quality assessment
  * Quality assessment leveraging background knowledge
  * Use-case driven quality management
  * Evaluation of trustworthiness of data
  * Web Data and LOD quality benchmarks
  * Data Quality improvement methods and frameworks, e.g., linkage,
    alignment, cleaning, enrichment, correctness
  * Service/system quality improvement methods and frameworks
  * Managing sustainability issues in services
  * Guarantee of service (availability, performance)
  * Systems for transparent management of open data


--------------080303020507060209040204
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div style="color: rgb(34, 34, 34); font-family: arial, sans-serif;
      font-size: 12.8px; font-style: normal; font-variant: normal;
      font-weight: normal; letter-spacing: normal; line-height: normal;
      orphans: auto; text-align: start; text-indent: 0px;
      text-transform: none; white-space: normal; widows: 1;
      word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255);"><b>Extended Deadline
        November 20, 2015<br>
        <br>
        CFP: Semantic Web Journal - Special Issue on Quality Management
        of Semantic Web Assets (Data, Services and Systems):</b> <font
        color="#000000"><a class="moz-txt-link-freetext"
          href="http://www.semantic">http://www.semantic</a>-<wbr>web-journal.net/blog/call-pape<wbr>rs-special-issue-quality-manag<wbr>ement-semantic-web-assets-<wbr>data-services-and-systems</font></div>
    <div style="color: rgb(34, 34, 34); font-family: arial, sans-serif;
      font-size: 12.8px; font-style: normal; font-variant: normal;
      font-weight: normal; letter-spacing: normal; line-height: normal;
      orphans: auto; text-align: start; text-indent: 0px;
      text-transform: none; white-space: normal; widows: 1;
      word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255);"><br>
    </div>
    <div style="color: rgb(34, 34, 34); font-family: arial, sans-serif;
      font-size: 12.8px; font-style: normal; font-variant: normal;
      font-weight: normal; letter-spacing: normal; line-height: normal;
      orphans: auto; text-align: start; text-indent: 0px;
      text-transform: none; white-space: normal; widows: 1;
      word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255);">
      <h2 style="margin: 0px 0px 0.5em; padding: 0px; line-height:
        18.2px;"><font face="arial, helvetica, sans-serif" size="2">Submission

          guidelines</font></h2>
      <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><b><font
            face="arial, helvetica, sans-serif">Deadline:<span> </span><strike><span
                style="border-bottom-width: 1px; border-bottom-style:
                dashed; border-bottom-color: rgb(204, 204, 204);"><span>October

                  31, 2015</span></span></strike></font></b> &gt; <b>November

          20, 2015</b><b><font face="arial, helvetica, sans-serif"><strike><span
                style="border-bottom-width: 1px; border-bottom-style:
                dashed; border-bottom-color: rgb(204, 204, 204);"><span><br>
                </span></span></strike></font></b></p>
      <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
          face="arial, helvetica, sans-serif">Submissions shall be made
          through the Semantic Web journal website at <a
            class="moz-txt-link-freetext"
            href="http://www.semantic-web-jou"><a class="moz-txt-link-freetext" href="http://www.semantic-web-jou">http://www.semantic-web-jou</a></a><wbr>rnal.net.

          Prospective authors must take notice of the submission
          guidelines posted at <a class="moz-txt-link-freetext"
            href="http://www.semantic-web-jou">http://www.semantic-web-jou</a><wbr>rnal.net/authors.

          Note that you need to request an account on the website for
          submitting a paper. Please indicate in the cover letter that
          it is for the Special Issue on Quality Management of Semantic
          Web Assets (Data, Services and Systems).</font></p>
      <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
          face="arial, helvetica, sans-serif">Submissions are possible
          in the following categories: full research papers, application
          reports, reports on tools and systems, and case studies. While
          there is no upper limit, paper length must be justified by
          content.</font></p>
      <span>
        <h2 style="margin: 0px 0px 0.5em; padding: 0px; line-height:
          18.2px;"><font face="arial, helvetica, sans-serif" size="2">Guest

            editors</font></h2>
        <ul style="margin: 0px 0px 1.5em 2em; padding: 0px; line-height:
          18.2px;">
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Amrapali Zaveri,
              University of Leipzig, AKSW Group, Germany</font></li>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Dimitris Kontokostas,
              University of Leipzig, AKSW Group, Germany</font></li>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Sebastian Hellmann,
              University of Leipzig, AKSW Group, Germany</font></li>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Jürgen Umbrich, Vienna
              University of Economics and Business, Austria</font></li>
        </ul>
      </span></div>
    <div class="gmail_extra" style="color: rgb(34, 34, 34); font-family:
      arial, sans-serif; font-size: 12.8px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: normal; orphans: auto; text-align: start;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255);"><b>Overview and Topics</b></div>
    <div class="gmail_extra" style="color: rgb(34, 34, 34); font-family:
      arial, sans-serif; font-size: 12.8px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: normal; orphans: auto; text-align: start;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255);"><br>
    </div>
    <div class="gmail_extra" style="color: rgb(34, 34, 34); font-family:
      arial, sans-serif; font-size: 12.8px; font-style: normal;
      font-variant: normal; font-weight: normal; letter-spacing: normal;
      line-height: normal; orphans: auto; text-align: start;
      text-indent: 0px; text-transform: none; white-space: normal;
      widows: 1; word-spacing: 0px; -webkit-text-stroke-width: 0px;
      background-color: rgb(255, 255, 255);"><span>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">The standardization and
            adoption of Semantic Web technologies has resulted in a
            variety of assets, including an unprecedented volume of data
            being semantically enriched and systems and services, which
            consume or publish this data. Although gathering, processing
            and publishing data is a step towards further adoption of
            Semantic Web, quality does not yet play a central role in
            these assets (e.g., data lifecycle, system/service
            development).</font></p>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">Quality management
            essentially refers to activities and tasks involved to
            guarantee a certain level of consistency and to meet the
            quality requirements for the assets. In general, quality
            management consists of the following four phases and
            components: (i) quality planning, (ii) quality control,
            (iii) quality assurance and (iv) quality improvement.</font></p>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">The quality planning
            phase in the Semantic Web typically involves the design of
            procedures, strategies and policies to support the
            management of the assets. The quality control and assurance
            components have their primary aim in preventing errors and
            to meet quality requirements pertaining to the Semantic Web
            standards. A core part for both components are quality
            assessment methods which provide the necessary input for the
            controlling and assurance tasks.</font></p>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">Quality assessment of
            Semantic Web Assets (data, services and systems), in
            particular, presents new challenges that were not handled
            before in other research areas. Thus, adopting existing
            approaches for data quality assessment is not a
            straightforward solution. These challenges are related to
            the openness of the Semantic Web, the diversity of the
            information and the unbounded, dynamic set of autonomous
            data sources, publishers and consumers (legal and software
            agents). Additionally, detecting the quality of available
            data sources and making the information explicit is yet
            another challenge. Moreover, noise in one data set, or
            missing links between different data sets, propagates
            throughout the Web of Data, and imposes great challenges on
            the data value chain.</font></p>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">In case of systems and
            services, different implementations follow the
            specifications for RDF and SPARQL to varying extents, or
            even propose and offer new, non-standardized extensions.
            This causes strong incompatibilities between systems, e.g.,
            between the used SPARQL features in the query engines and
            support features in RDF stores. The potential heterogeneity
            and incompatibility poses several challenges for the quality
            assessments in and for such systems and services.</font></p>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">Eventually, quality
            improvement methods are used to further enhance the value of
            the Semantic Web Assets. One important step to improve the
            quality of data is identifying the root cause of the problem
            and then designing corresponding data improvement solutions.
            These solutions select the most effective and efficient
            strategies and related set of techniques and tools to
            improve quality. Quality improvement metrics for products
            and services entails understanding and improving operational
            processes and establishing valid and reliable service
            performance measures.</font></p>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">This Special Issue is
            addressed to those members of the community interested in
            providing novel methodologies or frameworks in managing,
            assessing, monitoring, maintaining and improving the quality
            of the Semantic Web data, services and systems and also
            introduce tools and user interfaces which can effectively
            assist in this management.</font></p>
        <h2 style="margin: 0px 0px 0.5em; padding: 0px; line-height:
          18.2px;"><font face="arial, helvetica, sans-serif" size="2">Topics

            of Interest</font></h2>
        <p style="margin: 0.5em 0px; padding: 0px; line-height: 18.2px;"><font
            face="arial, helvetica, sans-serif">We welcome original high
            quality submissions on (but are not restricted to) the
            following topics:</font></p>
      </span>
      <ul style="margin: 0px 0px 1.5em 2em; padding: 0px; line-height:
        18.2px;">
        <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
            face="arial, helvetica, sans-serif">Methodologies and
            frameworks to plan, control, assure or improve the quality
            of Semantic Web Assets</font></li>
        <span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Quality exploration
              and analysis interfaces</font></li>
        </span>
        <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
            face="arial, helvetica, sans-serif">Quality monitoring</font></li>
        <span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Developing, deploying
              and managing quality service ecosystems</font></li>
        </span><span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Assessing the quality
              evolution of Semantic Web Assets</font></li>
        </span><span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Large-scale quality
              assessment of structured datasets</font></li>
        </span>
        <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
            face="arial, helvetica, sans-serif">Crowdsourcing data
            quality assessment</font></li>
        <span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Quality assessment
              leveraging background knowledge</font></li>
        </span>
        <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
            face="arial, helvetica, sans-serif">Use-case driven quality
            management</font></li>
        <span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Evaluation of
              trustworthiness of data</font></li>
        </span><span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Web Data and LOD
              quality benchmarks</font></li>
        </span>
        <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
            face="arial, helvetica, sans-serif">Data Quality improvement
            methods and frameworks, e.g., linkage, alignment, cleaning,
            enrichment, correctness</font></li>
        <span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Service/system quality
              improvement methods and frameworks</font></li>
        </span><span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Managing
              sustainability issues in services</font></li>
        </span><span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Guarantee of service
              (availability, performance)</font></li>
        </span><span>
          <li style="margin: 0px; padding: 0px; line-height: 19.5px;"><font
              face="arial, helvetica, sans-serif">Systems for
              transparent management of open data</font></li>
        </span>
      </ul>
    </div>
  </body>
</html>

--------------080303020507060209040204--