<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>01550nab a2200205   4500</leader>
  <controlfield tag="005">20260520004223.0</controlfield>
  <controlfield tag="008">260224s2008    xxu                      </controlfield>
  <datafield tag="245" ind1="0" ind2="0">
    <subfield code="a">Ontology driven certification of pressure equipments</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a"></subfield>
    <subfield code="b"></subfield>
    <subfield code="c">dic. 2008</subfield>
  </datafield>
  <datafield tag="270" ind1=" " ind2=" ">
    <subfield code="a">11/05/2011 ; 11/05/2011</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">10 p. ; 313-322</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Transcripci&#xF3;n del resumen del autor. Standards and engineering codes rule design, construction and operation of chemical plant equipments to ensure reliability and safety. In this article, we exploit knowledge-based methodologies and technologies to guarantee safety rules compliance of pressure equipments. Specifically, we describe a knowledge-based tool defined on top of a knowledge-based computer-aided design system, which can serve inspection bodies, i.e., for certification purposes, and pressure equipment designers for the verification of the appropriate safety normative (i.e., the pressure equipment directive). The article focuses on the knowledge base of the tool, which has been formalized through the PED&amp;I (Pressure Equipment Design and Inspection) ontology. The ontology has been enriched by logical axioms, which ensure the consistency of the knowledge base, and by reasoning rules, which enable to infer new relationships among the class instances stored in the ontology.</subfield>
  </datafield>
  <datafield tag="581" ind1=" " ind2=" ">
    <subfield code="a">4</subfield>
  </datafield>
  <datafield tag="773" ind1="0" ind2=" ">
    <subfield code="t">Process safety progress</subfield>
    <subfield code="g">27</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">ARTICULO</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Camossi, Elena</subfield>
    <subfield code="9">49821</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Giannini, Franca</subfield>
    <subfield code="9">49822</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Monti, Marina</subfield>
    <subfield code="9">49823</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">181635</subfield>
    <subfield code="d">181635</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="9">249454</subfield>
    <subfield code="a">BAAB</subfield>
    <subfield code="b">BAAB</subfield>
    <subfield code="d">2026-03-05</subfield>
    <subfield code="j">200053668</subfield>
    <subfield code="l">0</subfield>
    <subfield code="p">200053668</subfield>
    <subfield code="r">2026-03-05 23:51:47</subfield>
    <subfield code="w">2026-03-05</subfield>
    <subfield code="y">ARTICULO</subfield>
  </datafield>
</record>
