Transducer Electronic Data Sheet

Transcription

1 Transforming TEDS

2 Transducer Electronic Data Sheet XML Files Schemas Defined in IEEE What are TEDS? Schemas in:

3 Interoperability requires: Loosely coupled abstraction Well defined General Stability over time Easy to implement Interoperability

4 TEDS represent: Hard coupled abstraction Errors in XML definitions Namespaces, data types, dates, examples, etc. TEDS are very specific TEDS & Interoperability New use cases require new schemas Difficult to implement and maintain.

5 Can represent all IoT data/actions Including TEDS Can remain unchanged over time New use cases would not require changes to specifications. Is easy to implement Available in public libraries. Is well defined New Abstraction Model needed

6 Solution in the XMPP case XEP 0323: IoT data XEP 0324: Security XEP 0325: Control XEP 0326: Concentrators Data representable by TEDS are representable by above XEPs and form a subset of data representable by XEPs.

7 Examples The Following examples are taken from:

8 Meta-identification TEDS Meta-identification TEDS Annex E

9 Meta-identification TEDS Invalid XML Does not validate against schema repository Shows change in schemas since publication Only string data types Undefined date Case/tag name confusion in different examples/schemas.

10 TEDS to XEP-0323.xslt Transformation using TEDS to XEP-0323.xslt : Transformed into IoT data according to XEP-0323.

11 Corresponding XSLT Following XSLT snippet transforms a MetaIdentificationTEDSDataBlock TEDS to XEP-0323 compliant fields:

12 Corresponding XSLT Converting unspecified date format in examples to XML-compliant date format can be done using the following XSLT template:

13 XEP-0323 to TEDS.xslt Transformation using XEP-0323 to TEDS.xslt : Transformed from IoT data according to XEP-0323.

14 Corresponding XSLT The Following XSLT snippet transforms XEP-0323 compliant fields to a MetaIdentificationTEDSDataBlock TEDS:

15 Corresponding XSLT Converting XML-compliant dates to the unspecified date format in the TEDS examples can be done using the following XSLT template:

16 Transducer Channel-identification TEDS Transducer Channelidentification TEDS Annex F

17 Transducer Channel-identification TEDS Does not validate against schema repository Shows change in schemas since publication Case/tag name confusion in different examples/schemas.

18 TEDS to XEP-0323.xslt Transformation using TEDS to XEP-0323.xslt : Transformed into IoT data according to XEP-0323.

19 Corresponding XSLT Following XSLT snippet transforms a TransfucerChannelIdDataBlock TEDS to XEP-0323 compliant fields:

20 XEP-0323 to TEDS.xslt Transformation using XEP-0323 to TEDS.xslt : Transformed from IoT data according to XEP-0323.

21 Corresponding XSLT The Following XSLT snippet transforms XEP-0323 compliant fields to a TransducerChannelIdDataBlock TEDS:

22 Calibration-identification TEDS Calibration-identification TEDS Annex G

23 Calibration-identification TEDS Invalid XML Does not validate against schema repository Shows change in schemas since publication Only string data types Undefined date

24 TEDS to XEP-0323.xslt Transformation using TEDS to XEP-0323.xslt : Transformed into IoT data according to XEP (Description manually made into two lines for readability.) Unclear what Std means

25 Corresponding XSLT Following XSLT snippet transforms a CalibrationIdentificationTEDSDataBlock TEDS to XEP-0323 compliant fields:

26 XEP-0323 to TEDS.xslt Transformation using XEP-0323 to TEDS.xslt : Transformed from IoT data according to XEP-0323.

27 Corresponding XSLT The Following XSLT snippet transforms XEP-0323 compliant fields to a CalibrationIdentificationTEDSDataBlock TEDS:

28 Location and Title TEDS Location and Title TEDS Annex I

29 Location and Title TEDS Does not validate against schema repository Shows change in schemas since publication Unclear schema definition

30 TEDS to XEP-0323.xslt Transformation using TEDS to XEP-0323.xslt : Transformed into IoT data according to XEP Unclear what TEDS Access Code is Why are titles not human friendly or localizable?

31 Corresponding XSLT Following XSLT snippet transforms a LocationAndTitleDataBlock TEDS to XEP-0323 compliant fields:

32 XEP-0323 to TEDS.xslt Transformation using XEP-0323 to TEDS.xslt : Transformed from IoT data according to XEP-0323.

33 Corresponding XSLT The Following XSLT snippet transforms XEP-0323 compliant fields to a LocationAndTitleDataBlock TEDS:

34 Unit Extension TEDS Unit Extension TEDS Annex J

35 Unit Extension TEDS Does not validate against schema repository Shows change in schemas since publication Could not find schema definition

36 TEDS to XEP-0323.xslt Transformation using TEDS to XEP-0323.xslt : Transformed into IoT data according to XEP Unclear if this is necessary in XEP-0323.

37 Corresponding XSLT Following XSLT snippet transforms a UnitsExtensionDataBlock TEDS to XEP-0323 compliant fields:

38 XEP-0323 to TEDS.xslt Transformation using XEP-0323 to TEDS.xslt : Transformed from IoT data according to XEP-0323.

39 Corresponding XSLT The Following XSLT snippet transforms XEP-0323 compliant fields to a UnitsExtensionDataBlock TEDS:

40 Collections of TEDS Collections of TEDS

41 Collection support Collection support (i.e. XML files containing multiple TEDS data blocks) was added using the following XSLT snippet:

42 Collection of TEDS Fed transformation with:

43 Transformed collection Collection of TEDS transformed to:

44 Collection support Collection support (i.e. transforming XML files containing IoT data from multiple TEDS data blocks) was added using the following XSLT snippet:

45 Re-transformed collection to TEDS Large collection re-transformed back to Collection of TEDS: