1 / 11

Semantic Data Model for Technical Data Proposal

Develop a semantic data model for automatic transformation of metric and non-metric technical data. Editing and publishing of technical data in various unit systems. Includes publication of logical tables and tolerance data.

darlenerichard
Download Presentation

Semantic Data Model for Technical Data Proposal

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Technical DataProposal MI 10 W. Ziegler University of Applied Sciences, Karlsruhe (15-04-2008)

  2. goal • Semantic data model for technical data • Automatically transformation and processing of metric, none-metric technical data and corresponding tolerance values • Publishing of technical datatables

  3. use cases (1) Editing process • Including technical data at text level (element „techdata“ within mixed content) • Editing logical tables of technical data(element „techtable“ within topic structure)

  4. use cases (2) Publishing • Filtering or transformation, targeting different unit systems • Publishing tables of technical data (logical/“techtable“ or generic/CALS)

  5. basic semantic model (1) • Includes metric („SI“) and non-metric („US“) unit systems • Includes semantics of tolerance data

  6. basic semantic model (2) <!ELEMENT techdata (datatype?, ((%value; (tolerance-asymmetric-value | tolerance-symmetric-value)?) | (lower-value, upper-value) | textdata))> <!ELEMENT datatype (#PCdata | .... )*> <!-- mixed content for the defintition of datatypes --> <!ELEMENT si-value (number, unit)> <!ELEMENT us-value (number, unit)> <!ENTITY % value "si-value?, us-value?"> <!ENTITY % value „((si-value, us-value?)| (si-value?,us-value ))">alternatively <!ENTITY % numberunit "(#PCdata | ....)*"> <!--mixed content for the defintition of units--> <!ELEMENT number (#PCdata | .... )*> <!– only numbers /floating point ? --> <!ELEMENT unit %numberunit;> <!ELEMENT upper-value (%value;)*> <!ELEMENT lower-value (%value;)*> <!ELEMENT tolerance-asymmetric-value ((tolerance-high-value, tolerance-low-value?) |tolerance-low-value)> <!ELEMENT tolerance-high-value (%value;)> <!ELEMENT tolerance-low-value (%value;)> <!ELEMENT tolerance-symmetric-value (%value;)> <!ELEMENT textdata (#PCdata | .... )*>

  7. basic semantic model (3) Logical tables of technical data <ELEMENT techtable (techdata+)> During publishing, columns are set by the datatype, unit/number-combinations or textdata.

  8. examples (1) <techdata> <datatype >Operating weight </datatype> <si-value><number>481 </number><unit>kg </unit></si-value> </techdata> <techdata > <datatype>Rated speed</datatype> <si-value><number>2500 </number><unit>min <superscript>-1 </superscript></unit></si-value> </techdata> <techdata> <datatype>Engine manufacturer </datatype> <textdata>MC</textdata> </techdata> <techdata > <datatype >Operating pressure</datatype> <si-value > <!– published e.g. as 210 (+5/-10) bar <number >210 <tolerance-asymmetric-value> <tolerance-high-value><si-value><number>5<number><unit>bar</unit</si-value></tolerance-high-value> <tolerance-low-value><si-value><number>10<number><unit>bar</unit</si-value></tolerance-low-value> </tolerance-asymmetric-value> </number> <unit>bar</unit> </si-value> </techdata>

  9. examples (2) <techdata > <datatype >Operating weight </datatype> <si-value><number>481 </number><unit>kg </unit></si-value> <us-value><number>1060.4</number><unit>lbs</unit></us-value> </techdata> • Allows output filtering, if both units are included by the author • Allows automatically localization/transformation, if only one unit system is included (unit system must be apparent at topic level/metadata) • Filtering and transformation is triggered by output specification (map attributes)

  10. examples (3) Tables of techdata-elements <techtable> <techdata>…</techdata><techdata>…</techdata><techdata>…</techdata> <techtable> language dependent (automatically published)table headers tolerance-symmetric-value lower-value, upper-value

  11. examples (4) techdata elements within CALS tables Prospect/Dev: <techdata source=“sql:‘select $value from …where…‘ “ > <techdata source=“ws:$value,$ype,…“ >

More Related