File: CompatFormat180.html

package info (click to toggle)
hdf5 1.8.13%2Bdocs-15
  • links: PTS, VCS
  • area: main
  • in suites: jessie-kfreebsd
  • size: 171,520 kB
  • sloc: ansic: 387,158; f90: 35,195; sh: 20,035; xml: 17,780; cpp: 13,516; makefile: 1,487; perl: 1,299; yacc: 327; lex: 178; ruby: 37
file content (1092 lines) | stat: -rw-r--r-- 26,977 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
1060
1061
1062
1063
1064
1065
1066
1067
1068
1069
1070
1071
1072
1073
1074
1075
1076
1077
1078
1079
1080
1081
1082
1083
1084
1085
1086
1087
1088
1089
1090
1091
1092
<html>
<head><title>
HDF5 Format Compatibility
</title>
<link href="../ed_styles/GenElect.css" rel="stylesheet" type="text/css">
</head>

<body bgcolor="#FFFFFF">
  
<!-- #BeginLibraryItem "/ed_libs/styles_Gen.lbi" -->
<!--
  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
  * Copyright by The HDF Group.                                               *
  * Copyright by the Board of Trustees of the University of Illinois.         *
  * All rights reserved.                                                      *
  *                                                                           *
  * This file is part of HDF5.  The full HDF5 copyright notice, including     *
  * terms governing use, modification, and redistribution, is contained in    *
  * the files COPYING and Copyright.html.  COPYING can be found at the root   *
  * of the source code distribution tree; Copyright.html can be found at the  *
  * root level of an installed copy of the electronic HDF5 document set and   *
  * is linked from the top-level documents page.  It can also be found at     *
  * http://www.hdfgroup.org/HDF5/doc/Copyright.html.  If you do not have      *
  * access to either file, you may request a copy from help@hdfgroup.org.     *
  * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 -->
<!-- #EndLibraryItem --><!-- #BeginLibraryItem "/ed_libs/NavBar_ADevG.lbi" -->
<hr>
<center>
<table border=0 width=98%>
<tr><td valign=top align=left>
    <a href="../index.html">HDF5 documents and links</a>&nbsp;<br>
    <a href="../H5.intro.html">Introduction to HDF5</a>&nbsp;<br>
    <!--
    <a href="Glossary.html">Glossary</a><br>
    -->
</td>
<td valign=top align=right>
    <a href="../UG/index.html">HDF5 User's Guide</a>&nbsp;<br>
    <a href="../RM/RM_H5Front.html">HDF5 Reference Manual</a>&nbsp;<br>
    <a href="../ADGuide.html">HDF5 Application Developer's Guide</a>&nbsp;<br>
</td></tr>
</table>
</center>
<hr>
<!-- #EndLibraryItem --><div align=center>
<h1>New Features in HDF5 Release 1.8.0
and Format Compatibility Considerations</h1>
</div>

<a name="FormatCompatIntro">&nbsp;</a>
<h3>1. Introduction</h3>

This document discusses backward/forward file format compatibility, 
features introduced in HDF5 Release 1.8.0, and corresponding APIs 
that may trigger these features and corresponding incompatibility.

<p>
Forward compatibility relates to the ability of an older HDF5 Library 
to read files created by a newer HDF5 Library. An older library should 
be able to read objects that are known to that library in a file 
created by Release 1.8.0.  This document includes a list of features 
that are designed to create no forward compatibility problems; 
a forward compatibility failure with one of these features is a bug.

<p>
Backward compatibility relates to the ability of a newer HDF5 Library 
to read files created by an older HDF5 Library.  
E.g., if HDF5 Release 1.8.0 is unable to read files created by 
Release 1.6.5, that is a backward compatibility failure.  
An HDF5 design criterion is that the HDF5 Library is always 
backwardly compatible.  A backward compatibilty failure is a bug.

<p>
The table below lists features introduced in HDF5 Release 1.8.0 
and the objects they may act on, 
then indicates combinations in which compatibility conflicts 
might arise.  Some features will always create objects 
or write data that will be incompatible with older versions of the library; 
others will do so only under certain circumstances.

<p>
<strong>
Related document
</strong>
<p>
<a href="../RM/APICompatMacros.html"><cite> API Compatibility Macros 
in HDF5</cite></a> discusses 
    configurable function macros that were introduced in 
        HDF5 Release 1.8.0 to facilitate the adaptation of applications
        to that and future releases,
    criteria for selecting specific configurations, and
    steps required to set them up.

<p>
Whereas <cite>New Features in HDF5 Release 1.8.0 and Format Compatibility 
Considerations</cite> discusses format compatibility issues to consider
when applications using HDF5 Release 1.8.0 (or a later release) will create 
files that might have to be read using older versions of the HDF5 Library,
<cite>API Compatibility Macros in HDF5</cite> discusses an approach 
to resolving API compatibility issues when moving an application 
to that release (or a later release).


<p>
<strong>
Reading the table
</strong>
<p>
New features in HDF5 Release 1.8.0 
are listed across the top of the table. 

<p>
Objects in an HDF5 file that features might affect format compatibility 
are listed on the left-hand side.  If the object is printed in bold, 
the symbols across the row indicate the effect that the feature 
has when it acts directly on that object.  
Associated with several objects are one or more objects 
indented to the right and printed in normal typeface; 
ripple effects of a feature may affect these objects 
when the feature acts on the related bold-faced object.

<p>
Consider the intersection of the <i>Attribute</i> lines and 
<i>Attribute and object headers</i> features.  
The symbols on the <i>Attribute</i> line indicate the effect of the 
feature when it acts on an attribute;  
the symbols on the <i>Object</i> line, immediately below, 
indicate the effect of the feature on an HDF5 object 
when the feature acts on an attribute attached to that object.  
For example, the table indicates that attribute creation order 
can be tracked and indexed with the HDF5 Release 1.8.0 Library 
only with new-format attributes, and those attr
ibutes will not be readable by older libraries.  
The table further indicates that an object 
to which such attributes are attached (a dataset, for example) 
will therefore be unreadable by an older HDF5 library.

<p>
<div align=center>
<a href="CompatFormat1_ReadKey.png" border=0>
<img src="CompatFormat1_ReadKey.png" width=300 alt="How to read symbolic key to table" border=0>
</a>
</div>

<p>
<a name="FormatConcernsTable">&nbsp;</a>
</p>

<h3>2. A Summary Table
<br>
<font size=-1>New Features in HDF5 Release 1.8.0 and Their Impact on Format Compatibility</font>
</h3>

The table below lists new features in HDF5 Release 1.8.0 
that may create forward-compatibility conflicts.
Objects created or modified with any of these features 
may be inaccessible via HDF5 Libraries prior to Release 1.8.0.

<p>
See 
<a href="#FormatCompatibitlityConcerns">section 3</a>, 
&ldquo;<a href="#FormatCompatibitlityConcerns">Features that may create 
(or are known to create) compatibility concerns</a>,&rdquo; 
for further explanation of these functions and 
their format compatiblity implications.

<p>
<div align=right>
<a href="HDF5_CompatFormat180_Concerns.pdf" border=0>
<img src="CompatFormat2_Key.png" width=500 alt="Key for reading table" border=0>
</a>
</div>

<p>
<div align=center>
<a href="HDF5_CompatFormat180_Concerns.pdf" border=0>
<img src="CompatFormat3_UserTable.png" width=700 alt="Table of features 
that can create compatibility concerns" border=0>
</a>
</div>

<p>
<strong>Table footnotes:</strong>
<ol>
<li> Under the new implementation, 
links may be stored as messages in an object header 
or in a type-2 B-tree in the group's local heap.
<br>
<li> By default, a datatype is stored as a message 
in the object header; a named datatype, 
which may be shared by several datasets, 
is stored as an independent object in the file.
<br>
<li> Several new features do not involve new or changed APIs.
<br>
<li> The following elements are stored (or can be stored; 
see notes 2 and 3) as messages in an  object header.
<br>
<li> These APIs create coordinated sets of objects and metadata.  
Though individual elements are quite likely to be accessible 
through an older HDF5 library, that library will have 
no means of understanding the relationships among the various pieces.
<br>
<li> Compatibility problems will arise only if an application 
or the HDF5 Library crashed without properly closing a file with 
which this functionality was being used.
<!--
<br>
<li> An API that was simply missing; 
old libraries always could read the datatype.
-->
</ol>

<!--
<p>
Notes to reviewers:
This entire chart is data-only; if we wish to discuss 
backward-forward application compatibility, 
that would have to be a separate issue.
-->

<p>
An expanded table 
[<a href="HDF5_CompatFormat180_AllFeatures.pdf">PDF</a>, 
large format (11x17 inches)] is available, 
listing all new features in Release 1.8.0, 
including features that create no format compatibility issues.
These additional features are described more fully in
<a href="#NoIncompatibilities">section 4</a>, 
&ldquo;<a href="#NoIncompatibilities">Features that are designed 
to create no compatibility concerns</a>.&rdquo;



<p>
<a name="FormatCompatibitlityConcerns">&nbsp;</a>
</p>

<h3>3. Features that may create (or are known to create) 
    compatibility concerns</h3>

    The following HDF5 Release 1.8.0 features may create 
    new HDF5 objects that cannot be read by an older 
    HDF5 Library or modify existing objects such that 
    they cannot be read by an older HDF5 Library.


    <dir>
    <dl>
        <dt>
        <strong>
        General features
        </strong>
        <dt>
        Object creation using <i>latest available format</i>, specified
        via the <code>H5Pset_libver_bounds</code> function.
        <dd>
            When <code>H5Pset_libver_bounds</code> is called with the
            <code>low</code> argument equal to <code>HDF_LIBVER_LATEST</code>,
            new objects are created using the latest available format versions.
        
            <p>
            This is a file access property, so this object creation behavior 
            can be set for any existing file, and can vary according to 
            application needs each time a file is opened.  
        
            <p>
            Functions:
            <br>  
                <code>H5Pset_libver_bounds( hid_t fapl_id, H5F_libver_t low, H5F_libver_t high )</code> 
            <br>
                <code>H5Pget_libver_bounds( hid_t fapl_id, H5F_libver_t* low, H5F_libver_t* high )</code>
            <p>
            Default behavior:  If <code>H5Pset_libver_bounds</code> is not called with <code>low</code> equal to 
            <code>HDF_LIBVER_LATEST</code>, then the HDF5 Library provides the greatest-possible format
            compatibility. It does this by creating objects with the earliest possible format that 
            will handle the data being stored and accommodate the action being taken.
        
<!--
            <p>
            Compatibility considerations:
            <br>
            &lt;<i>What are the incompatibilities, how do they arise, 
            and what might be the consequences?</i>&gt;
-->
        
            </p>
        <dt>
        <strong>
        Groups and links
        </strong>
        <dt>
        Configurable compact-or-indexed link storage 
        (compact and large groups; new group implementation)
        <dd>
            Compact-or-indexed groups enable much-compressed link 
            storage for groups with very few members and 
            improved efficiency and performance for groups 
            with very large numbers of members.  
            The efficiency and performance impacts are most noticeable 
            at the extremes:  all unnecessary overhead is eliminated 
            for groups with zero members; groups with 
            tens of thousands of members may see as much as 
            a 100-fold performance gain.  
        
            <p>
            This new group implementation also enables user-defined 
            and external links.
        
            <p>
<!--
            Functions: 
        
            <p>
            Default behavior: 
        
            <p>
            Compatibility considerations:
            <br>
            &lt;<i>What are the incompatibilities, how do they arise, 
            and what might be the consequences?</i>&gt;
-->
        
            </p>
        <dt>
        User-defined (UD) and external links
        <dd>
            User-defined links enable fully-customizable linking 
            in an HDF5 file.  External links enable the insertion 
            of a link into an HDF5 group in one file that points 
            to an HDF5 object in a different HDF5 file.  
            In part to provide a model for application developers, 
            external links are implemented as an example of a 
            user-defined link.
        
            <p>
<!--
            Functions: 
            
            <p>
            Default behavior: 
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        Link creation order tracking and indexing
        <dd>
            Links can now be tracked and indexed by creation order.  
            Links can be accessed according to an index by 
            creation order or an index by name.  
        
            <p>
            Note: Link indexing by name is inherent to the 
            HDF5 implementation and requires no special setting.
        
<!--
            <p>
            Functions: 
        
            <p>
            Default behavior: 
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        <strong>
        Attributes and object headers
        </strong>
        <dt>
        Faster access to large numbers of attributes
        <dd>
            Attribute handling is improved for large numbers of 
            attributes attached to a single object.
        
            <p>
<!--
            Functions: 
        
            <p>
            Default behavior: 
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        Large attributes (over ~64k)
        <dd>
            Very large attributes (generally larger than 64KB) 
            can be attached to an object.  
        
            <p>
<!--
            Functions: 
        
            <p>
            Default behavior: 
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        Attribute creation order tracking and indexing
        <dd>
            Attributes can now be tracked and indexed 
            by creation order.  Attributes can be accessed according  
            to an index by creation order or an index by name.  
        
            <p>
            (Note: Attribute indexing by name is inherent to the 
            HDF5 implementation and requires no special setting.)
        
            <p>
<!--
            Functions:
        
            <p>
            Default behavior:
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        Shared object header messages (SOHM)
        <dd>
            This feature enables the sharing of object header messages 
            (attributes, datatypes, fill values, simple dataspaces, 
            filter pipelines) when they are identical across 
            multiple objects.  For example, if a large text attribute 
            is attached to many datasets or groups, that attribute 
            can be saved once in the file with only a pointer from 
            each dataset or group.
        
            <p>
<!--
            Functions:
        
            <p>
            Default behavior:
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        <strong>
        Miscellaneous
        </strong>
        <dt>
        UNICODE support  (UTF-8; non-ASCII character set encoding)
        <dd>
            Non-ASCII character sets are supported for 
            character strings and link names.  
        
            <p>
            The current implementation includes the 
            ASCII and UTF-8 standard character sets.
        
            <p>
<!--
            Functions:
            
            <p>
            Default behavior:
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        Object creation or copying with 
        <i>create intermediate groups</i> property
        <dd>
            Use of the <i>create intermediate groups</i> property 
            enables the creation of any groups in the 
            specified path that do not yet exist in the file 
            when creating a new object or copying an 
            existing object in an HDF5 file.
        
            <p>
            Note that when this property is set, any 
            missing intermediate groups are created 
            with the properties of the lowest-level, 
            previously existing existing group.  
            I.e., if the object elf is being created at 
            <code>FILE:/a1/b543/cde/d12/elf</code>, 
            and only groups <code>a1</code> and <code>b543</code> 
            in that hierarchy exist in <code>FILE</code>, 
            groups <code>cde</code> and <code>d12</code> 
            will be created with the properties of the 
            group <code>b543</code>.
        
            <p>
<!--
            Functions:
        
            <p>
            Default behavior:
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        Anonymous object creation
        <dd>
            Objects can be created anonymously in a file, 
            i.e., without a location or name, with 
            <code>H5Dcreate_anon</code>, <code>H5Gcreate_anon</code>, 
            or <code>H5Tcommit_anon</code>.  
        
            <p>
            If the object is to be preserved in the file, 
            it must then be linked to a location in the file with 
            <code>H5Llink</code> before the file is closed.
        
            <p>
<!--
            Functions:
        
            <p>
            Default behavior:
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        Compression filters: N-bit and scale-offset
        <dd>
            Two new compression filters are provided:  
            an n-bit filter and a scale-offset filter.   
        
            <p>
            The n-bit filter compresses data from the 
            in-memory datatype to an n-bit datatype in the file.  
            Since data is normally byte- or word-aligned in memory, 
            this can result in substantial savings in the size 
            of stored data.  
        
            <p>
            The scale-offset filter performs a scale and/or 
            offset operation on each data value and truncates 
            the resulting value to a minimum number of bits 
            before storing it. 
        
            <p>
<!--
            Functions:
        
            <p>
            Default behavior:
        
            <p>
            Compatibility considerations:
-->
        
            </p>
        <dt>
        NULL dataspaces (<code>H5Screate</code>) (3)
        <dd>
            The <code>H5S_NULL</code> dataspace class allows an application 
            to use <code>H5Screate</code> to define a dataset or 
            attribute dataspace with no elements.
        
            <p>
            This feature is implemented through the addition 
            of a NULL dataspace, <code>H5S_NULL</code>, 
            to the set of valid dataspace classes.
        
            <p>
<!--
            Functions:
        
            <p>
            Default behavior:
        
            <p>
            Compatibility considerations:
-->
    
    </dl>
    </dir>


<p>
<a name="NoIncompatibilities">&nbsp;</a>
</p>

<h3>4. Features that are designed to create no compatibility concerns</h3>

    The following HDF5 Release 1.8.0 features are designed 
    to create no forward compatibilty conflicts; 
    an older HDF5 Library should always be able to read 
    and manipulate objects that they create or modify.


    </p>
    <dir>
    <dl>
    <dt>
    <strong>
    Groups and links
    </strong>
    <dt>
    Link APIs (H5L) unrelated to user-defined (UD) and external links
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

-->
        <p>

    <dt>
    <strong>
    Attributes and object headers
    </strong>
    <dt>
    Enhanced attribute handling
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Enhanced local heap size management (meta data for group)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

-->
        <p>


    <dt>
    <strong>
    Miscellaneous
    </strong>
    <dt>
    Object API (H5O)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Object copy properties
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Improved object information retrieval
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Name of referenced object
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    New-style object open and object creation functions
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    User-defined identifiers
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Other identifier API (H5I) enhancements
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    User-defined datatype conversion callback functions
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Datatype compiler conversion check
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Integer-to-floating-point conversion support (H5Tconvert) (3)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Dataset array size reduction (H5Dset_extent)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Dataspace equivalence (H5Sextent_equal)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Direct I/O, bypassing system cache
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Parallel I/O optimization (collective chunk I/O)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Enhanced error handling (H5E)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Meta data cache management (6)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    File read/write status (H5Fget_intent)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Arithmetic data transform on I/O
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Dataspace and datatype serial conversion 
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

-->
        <p>

    <dt>
    <strong>
    High-level APIs
    </strong>
    <dt>
    Two-way conversion between datatype and text description 
    of datatype (H5LT)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    New attribute datatype: long long (H5LT)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Dimension Scale API (H5DS) (5)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Packet Table API (H5PT) (5)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    <dt>
    Fortran APIs for HDF5 Light, Image, and Table interfaces 
    (H5LT, H5IM, and H5TB)
    <dd>
<!--
        &lt;<i>description</i>&gt;

        <p>
        Functions:

        <p>
        Default behavior:

        </p>
-->

    </dl>
    </dir>

<p>&nbsp;

</p>
<hr>

<!-- #BeginLibraryItem "/ed_libs/NavBar_ADevG.lbi" -->
<hr>
<center>
<table border=0 width=98%>
<tr><td valign=top align=left>
    <a href="../index.html">HDF5 documents and links</a>&nbsp;<br>
    <a href="../H5.intro.html">Introduction to HDF5</a>&nbsp;<br>
    <!--
    <a href="Glossary.html">Glossary</a><br>
    -->
</td>
<td valign=top align=right>
    <a href="../UG/index.html">HDF5 User's Guide</a>&nbsp;<br>
    <a href="../RM/RM_H5Front.html">HDF5 Reference Manual</a>&nbsp;<br>
    <a href="../ADGuide.html">HDF5 Application Developer's Guide</a>&nbsp;<br>
</td></tr>
</table>
</center>
<hr>
<!-- #EndLibraryItem --><!-- #BeginLibraryItem "/ed_libs/Footer-THGonly.lbi" -->
<address>
<table width="100%" border="0">
  <tr valign="top">
      <td align="left">
          <address>
          The HDF Group Help Desk: <img src="../Graphics/help.png" align=top height=16>
          <br>
          Describes HDF5 Release 1.8.13, May 2014.
          </address>
      </td><td width="5%">&nbsp;</td>
      <td align="right">
          <a href="../Copyright.html">Copyright</a> by
          <a href="http://www.hdfgroup.org">The HDF Group</a>
      </td>   
  </tr>   
</table>
</address>
<!-- #EndLibraryItem --><!-- Created: Spring 1999 -->
<!-- hhmts start -->
Last modified:  23 October 2007
<!-- hhmts end -->

</body>
</html>