Download presentation
Presentation is loading. Please wait.
Published byKenneth Nichols Modified over 8 years ago
1
Technical Data Proposal 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 data tables
3
use cases (1) Editing process a.Including technical data at text level (element „techdata“ within mixed content) b.Editing logical tables of technical data (element „techtable“ within topic structure)
4
use cases (2) Publishing a.Filtering or transformation, targeting different unit systems b.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))> alternatively alternatively
7
basic semantic model (3) Logical tables of technical data During publishing, columns are set by the datatype, unit/number-combinations or textdata.
8
examples (1) <techdata> Operating weight Operating weight 481 kg 481 kg </techdata> Rated speed Rated speed 2500 min -1 2500 min -1 </techdata><techdata> Engine manufacturer Engine manufacturer <textdata>MC</textdata></techdata> Operating pressure Operating pressure <!– published e.g. as 210 (+5/-10) bar 210 210<tolerance-asymmetric-value> 5 bar 5 bar 10 bar 10 bar </tolerance-asymmetric-value></number><unit>bar</unit></si-value></techdata>
9
examples (2) Operating weight Operating weight 481 kg 481 kg <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> … … … … … … <techtable> tolerance-symmetric-value lower-value, upper-value language dependent (automatically published) table headers
11
examples (4) techdata elements within CALS tables Prospect/Dev: Prospect/Dev:
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.