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
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
// file, You can obtain one at https://mozilla.org/MPL/2.0/.
//! Core traits for IFC parsing
//!
//! These traits define the main abstractions for working with IFC data.
use crate::;
use Arc;
/// Progress callback type for parsing operations
pub type ProgressCallback = ;
/// Main parsing interface - entry point for parsing IFC content
///
/// Implementations of this trait provide the ability to parse IFC file content
/// and return a model that can be queried through various trait interfaces.
///
/// # Example
///
/// ```ignore
/// use bimifc_model::{IfcParser, IfcModel};
///
/// let parser: Box<dyn IfcParser> = get_parser();
/// let model = parser.parse(ifc_content)?;
/// println!("Schema: {}", model.metadata().schema_version);
/// ```
/// Core model interface - read-only access to a parsed IFC model
///
/// This trait provides access to the various aspects of an IFC model through
/// sub-traits that handle specific concerns (entity resolution, properties,
/// spatial structure, etc.)
///
/// The model is thread-safe (`Send + Sync`) to support parallel processing
/// and use in async contexts.
/// Extension trait for models that support geometry processing
///
/// This trait is separate from `IfcModel` to allow for models that only
/// provide metadata/property access without geometry processing capability.
/// Trait for models that can be extended dynamically
///
/// This allows adding capabilities to a model after initial parsing.