Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix various typos #906

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@ IFC4.3.x
========

Repository that shows full history of the IFC4.3 Specification.
This repo still collects minor fixes like spelling errors and aditional clarifications.
This repo still collects minor fixes like spelling errors and additional clarifications.
Every update will automatically be published here:
- http://ifc43-docs.standards.buildingsmart.org/ (html)
- https://github.com/buildingsmart/ifc4.3.x-output (exp + pot + etc.)
Expand Down
2 changes: 1 addition & 1 deletion code/generate_pset_templates.py
Original file line number Diff line number Diff line change
Expand Up @@ -146,7 +146,7 @@ def parse_psets_data(self, schema_name, pset_data_glob, project_name, ifc_output
# 2) enumeration
# 3) property set (also with IFCRELASSOCIATESLIBRARY)
# 4) property definition (also with IFCRELASSOCIATESLIBRARY)
# but in ifc4x3 there is no data for those library refernces
# but in ifc4x3 there is no data for those library references
# TODO: need to add it to .ifc for IFC4X3 too
# if https://github.com/buildingSMART/IFC4.3.x-development/issues/587 is resolved

Expand Down
4 changes: 2 additions & 2 deletions code/mvdXML_V1.1_add1.xsd
Original file line number Diff line number Diff line change
Expand Up @@ -140,7 +140,7 @@
<xs:sequence>
<xs:element ref="mvd:AttributeRule" maxOccurs="unbounded">
<xs:annotation>
<xs:documentation>An atribute rule, defined for an attribute of the applicable entity. It declares the root element of the rule tree. It is allowed to define rules for attributes that are defined at subtypes of the applicable entity.</xs:documentation>
<xs:documentation>An attribute rule, defined for an attribute of the applicable entity. It declares the root element of the rule tree. It is allowed to define rules for attributes that are defined at subtypes of the applicable entity.</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
Expand Down Expand Up @@ -397,7 +397,7 @@
</xs:simpleType>
</xs:attribute>
<xs:attribute name="Description" type="xs:string" use="optional"/>
<!-- new complex type to differenciate from Rules in the Template section -->
<!-- new complex type to differentiate from Rules in the Template section -->
</xs:complexType>
<!-- ======================================== -->
<!-- common complex type definitions-->
Expand Down
2 changes: 1 addition & 1 deletion code/name_improve.py
Original file line number Diff line number Diff line change
Expand Up @@ -198,7 +198,7 @@ def clean(s):

def split_words(s):
"""Split the phrase using the hard-coded list of words found in enumerations
to split the ALLCAPS phrases into indivudual words."""
to split the ALLCAPS phrases into individual words."""
found_words = []
for w in type_words:
# skip if word is contained in previous words (e.g. EXCHANGE in EXCHANGER)
Expand Down
2 changes: 1 addition & 1 deletion code/process_schema.py
Original file line number Diff line number Diff line change
Expand Up @@ -662,7 +662,7 @@ def preproc():

for i in range(4,10):
# keep trying until hc is large enough
# to accomodate all elements
# to accommodate all elements
try:
hc = HC(i, 2)
tex_object = Tex_object(tex_fn)
Expand Down
4 changes: 2 additions & 2 deletions code/to_bsdd.py
Original file line number Diff line number Diff line change
Expand Up @@ -125,7 +125,7 @@ def generalization(pe):

def need_brackets(s):
"""Verify if that name should be annotated with brackets in other definitions.
The criteria: minium 4 letters (skip 'ABC')."""
The criteria: minimum 4 letters (skip 'ABC')."""
if len(s) >= 4:
return True
else:
Expand Down Expand Up @@ -735,7 +735,7 @@ def generate_definitions():
def list_unique_codes(concepts):
### iterate all the results to list all unique codes for translations
codes = set()
for code, content in tqdm(all_concepts.items(), "Lising all unique codes"):
for code, content in tqdm(all_concepts.items(), "Listing all unique codes"):
if need_brackets(code):
codes.add(code)
if content["Psets"]:
Expand Down
2 changes: 1 addition & 1 deletion docs/assets/css/mini-default.css
Original file line number Diff line number Diff line change
Expand Up @@ -1827,7 +1827,7 @@ mark.tag {
/*
Definitions for progress elements and spinners.
*/
/* Progess module CSS variable definitions */
/* Progress module CSS variable definitions */
:root {
--progress-back-color: #ddd;
--progress-fore-color: #555;
Expand Down
2 changes: 1 addition & 1 deletion docs/properties/a/Acknowledge.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
Acknowledge
===========

Indicates acknowledgement status where False indicates acknowlegement is required and outstanding, True indicates condition has been acknowedged, and Unknown indicates no acknowledgement is required. Upon resetting the condition, then acknowledgement reverts to Unknown.
Indicates acknowledgement status where False indicates acknowledgement is required and outstanding, True indicates condition has been acknowledged, and Unknown indicates no acknowledgement is required. Upon resetting the condition, then acknowledgement reverts to Unknown.
2 changes: 1 addition & 1 deletion docs/properties/e/EndShapeType.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
EndShapeType
============

Defines the types of end shapes that can be used for preformed tanks. The convention for reading these enumerated values is that for a vertical cylinder, the first value is the base and the second is the top; for a horizontal cylinder, the order of reading should be left to right. For a speherical tank, the value UNSET should be used.
Defines the types of end shapes that can be used for preformed tanks. The convention for reading these enumerated values is that for a vertical cylinder, the first value is the base and the second is the top; for a horizontal cylinder, the order of reading should be left to right. For a spherical tank, the value UNSET should be used.
2 changes: 1 addition & 1 deletion docs/properties/i/IsLandmarked.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
IsLandmarked
============

This builing is listed as a historic building (TRUE), or not (FALSE), or unknown.
This building is listed as a historic building (TRUE), or not (FALSE), or unknown.
2 changes: 1 addition & 1 deletion docs/properties/l/LoadBearingCapacity.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
LoadBearingCapacity
===================

Maximum load bearing capacity of the floor structure throughtout the storey as designed.
Maximum load bearing capacity of the floor structure throughout the storey as designed.
2 changes: 1 addition & 1 deletion docs/properties/m/MechanicalOperated.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
MechanicalOperated
==================

Indication whether the element is operated machanically (TRUE) or not, i.e. manually (FALSE).
Indication whether the element is operated mechanically (TRUE) or not, i.e. manually (FALSE).
2 changes: 1 addition & 1 deletion docs/schemas/core/IfcKernel/Entities/IfcProduct.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,7 @@ The body or solid model geometric representation of an _IfcProduct_ is typically

The geometric representation of any _IfcProduct_ is provided by the _IfcProductDefinitionShape_ allowing multiple geometric representations. It uses the _Product Placement_ concept utilizing _IfcLocalPlacement_ to establish an object coordinate system, in which all geometric representations are founded.

> NOTE A detailed specification of how to apply the local placement and which shape representaions are applicable is provided at the level of subtypes of _IfcProduct_ and is further determined by the model view definition and implementer agreements.
> NOTE A detailed specification of how to apply the local placement and which shape representations are applicable is provided at the level of subtypes of _IfcProduct_ and is further determined by the model view definition and implementer agreements.

### Product Geometry Colour

Expand Down
2 changes: 1 addition & 1 deletion docs/schemas/core/IfcKernel/Entities/IfcPropertySet.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ Contained set of properties. For property sets defined as part of the IFC Object
## Formal Propositions

### ExistsName
The _Name_ attribute has to be provided. The attribute is used to specify the signifier of the property set. The properties that are allowed to be attached to a particular property set may be given within the property set definition part of the IFC specification. Those property set definitions are references in the semantic definition section of the individal subtypes of _IfcObjectDefinition_.
The _Name_ attribute has to be provided. The attribute is used to specify the signifier of the property set. The properties that are allowed to be attached to a particular property set may be given within the property set definition part of the IFC specification. Those property set definitions are references in the semantic definition section of the individual subtypes of _IfcObjectDefinition_.

### UniquePropertyNames
Every individual subtype of _IfcProperty_ within the property set shall have a unique _Name_ attribute value.
Original file line number Diff line number Diff line change
Expand Up @@ -63,5 +63,5 @@ For building operation scenarios, _IfcProcedure_ may be assigned to a product (_

### Sequential Connectivity

The relationship _IfcRelSequence_ is used to indicate control flow. An _IfcProcedure_ as a successor to an _IfcEvent_ indicates that the procedure should be performed in response to the event. An _IfcProcedure_ as a predecessor to an _IfcEvent_ indicates that the event should be trigerred following the procedure. As procedures have arbitrary duration, the _IfcRelSequence.SequenceType_ attribute has no effect on an _IfcProcedure_ but still applies to the opposite end of the relationship if _IfcTask_ is used.
The relationship _IfcRelSequence_ is used to indicate control flow. An _IfcProcedure_ as a successor to an _IfcEvent_ indicates that the procedure should be performed in response to the event. An _IfcProcedure_ as a predecessor to an _IfcEvent_ indicates that the event should be triggered following the procedure. As procedures have arbitrary duration, the _IfcRelSequence.SequenceType_ attribute has no effect on an _IfcProcedure_ but still applies to the opposite end of the relationship if _IfcTask_ is used.

Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ A mapping between the *business logic* and its *geometry definition* in IFC is d

### Alignment Layouts

A single alignment may be described by one ore more of the following layouts:
A single alignment may be described by one or more of the following layouts:

* a horizontal layout (_IfcAlignmentHorizontal_), defined in the x/y plane of the engineering coordinate system.
* an accompanying vertical layout (_IfcAlignmentVertical_), defined along the horizontal layout in the distance along / z coordinate space.
Expand All @@ -86,7 +86,7 @@ These 3 layouts may be used in different configurations. The most common are:
4. Multiple Vertical layouts based on the same Horizontal Layout
5. Multiple Vertical layouts based on the same Horizontal Layout, with a Cant layout applied

(4) and (5) are used in scenarios where multiple alignments re-use the same horizontal layout definition. See **Alignment Layout - Reusing Horizontal Layout** and **Alignment Geometry - Reusing Horizontal Layout** for details on how to relate parent and child alignments in theses cases.
(4) and (5) are used in scenarios where multiple alignments re-use the same horizontal layout definition. See **Alignment Layout - Reusing Horizontal Layout** and **Alignment Geometry - Reusing Horizontal Layout** for details on how to relate parent and child alignments in these cases.

![Alignment configurations](../../../../figures/IfcAlignment-possible-configurations.png)

Expand Down
4 changes: 2 additions & 2 deletions docs/schemas/core/IfcProductExtension/Entities/IfcElement.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Reference to the _IfcRelAdheresToElement_ relationship that adheres a _IfcSurfac

### Body AdvancedBrep Geometry

An _IfcElement_ (so far no further constraints are defined at the level of its subtypes or by view definitions) may be represented as a single or multiple boundary representation models, which include advanced surfaces, usually refered to as NURBS surfaces. The 'AdvancedBrep' representation allows for the representation of complex free-form element shape.
An _IfcElement_ (so far no further constraints are defined at the level of its subtypes or by view definitions) may be represented as a single or multiple boundary representation models, which include advanced surfaces, usually referred to as NURBS surfaces. The 'AdvancedBrep' representation allows for the representation of complex free-form element shape.

> NOTE View definitions or implementer agreements may restrict or disallow the use of 'AdvancedBrep' geometry.

Expand Down Expand Up @@ -154,7 +154,7 @@ Figure 148 — Building element box representation

### CoG Geometry

The 'CoG', Center of Gravity, shape representation is used as a means to verify the correct import by comparing the CoG of the imported geometry with the explicily provided CoG created during export.
The 'CoG', Center of Gravity, shape representation is used as a means to verify the correct import by comparing the CoG of the imported geometry with the explicitly provided CoG created during export.

### Element Interference

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Either there is no element assembly type object associated, i.e. the _IsTypedBy_

The IfcElementAssembly shall represent an aggregate, i.e. it should have other elements, being subtypes of IfcElement, as contained (sub)parts. The table above only represents a selection of subtypes of IfcElement that are legitimate as parts in an IfcElementAssembly

* The IfcElementAssembly is an aggregate i.e. being composed by other elements and acting as an assembly using the objectified relationship IfcRelAggregates, refering to it by its inverse attribute _SELF\IfcObjectDefinition.IsDecomposedBy_. Components of an assembly are described by instances of subtypes of IfcElement.
* The IfcElementAssembly is an aggregate i.e. being composed by other elements and acting as an assembly using the objectified relationship IfcRelAggregates, referring to it by its inverse attribute _SELF\IfcObjectDefinition.IsDecomposedBy_. Components of an assembly are described by instances of subtypes of IfcElement.
* In this case, the contained subtypes of IfcElement shall not be additionally contained in the project spatial hierarchy, i.e. the inverse attribute _SELF\IfcElement.ContainedInStructure_ of those IfcElement's shall be _NIL._

Figure 1 illustrates spatial containment and element aggregation relationships.
Expand All @@ -67,7 +67,7 @@ Components within the assembly.

### Spatial Containment

The IfcElementAssembly should have a relationship for its containment in the hierachical spatial structure of the project. Only if the IfcElementAssembly is itself a part of another assembly this relationship should be omitted.
The IfcElementAssembly should have a relationship for its containment in the hierarchical spatial structure of the project. Only if the IfcElementAssembly is itself a part of another assembly this relationship should be omitted.

#### IfcBuildingStorey

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The _IfcRelProjectsElement_ implies a Boolean operation of addition for the geom

* existence dependency - the _RelatedFeatureElement_ cannot exist without the _RelatingElement_
* hierarchical and non-cyclical relationship - the _IfcRelProjectsElement_ can only alter a single _IfcElement_
* no spatial containment - the _IfcFeatureElementAddition_ as related element never participates in the hiearchical spatial containment relationship _IfcRelContainedInSpatialStructure_
* no spatial containment - the _IfcFeatureElementAddition_ as related element never participates in the hierarchical spatial containment relationship _IfcRelContainedInSpatialStructure_

> HISTORY New entity in IFC2x2.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ A spatial element is the generalization of all spatial elements that might be us

### LongName
Long name for a spatial structure element, used for informal purposes. It should be used, if available, in conjunction with the inherited _Name_ attribute.
> NOTE In many scenarios the _Name_ attribute refers to the short name or number of a spacial element, and the _LongName_ refers to the full descriptive name.
> NOTE In many scenarios the _Name_ attribute refers to the short name or number of a spatial element, and the _LongName_ refers to the full descriptive name.

### ContainsElements
Set of spatial containment relationships, that holds those elements, which are contained within this element of the project spatial structure.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
Acquisition is made using global positioning system (GPS)

### LASERSCAN_AIRBORNE
Acquisition is made using Airborn Laserscanner
Acquisition is made using Airborne Laserscanner

### LASERSCAN_GROUND
Acquisition is made using Ground Laserscanner
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -52,7 +52,7 @@ The amount incurred for operating the equipment, such as fuel and maintenance.

#### Deployment_IfcCostValue_IfcMonetaryMeasure

The amount incurred for mobilizing and decomissioning the equipment.
The amount incurred for mobilizing and decommissioning the equipment.

### Resource Quantity

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ Neozed
required category not on scale

### NOTKNOWN
Value is unkown
Value is unknown

### UNSET
Value has not been specified
Original file line number Diff line number Diff line change
Expand Up @@ -3,4 +3,4 @@
The characteristics of the supply associated with an electrical device occurrence acting as a source of supply to an electrical distribution system
<!-- end of short definition -->

NOTE: Properties within this property set should ONLY be used in circumstances when an electrical supply is applied. The property set, the properties contained and their values are not applicable to a circumstance where the sypply is not being applied to the eletrical system or is temporarily disconnected. All properties within this property set are considered to represent a steady state situation.
NOTE: Properties within this property set should ONLY be used in circumstances when an electrical supply is applied. The property set, the properties contained and their values are not applicable to a circumstance where the sypply is not being applied to the electrical system or is temporarily disconnected. All properties within this property set are considered to represent a steady state situation.
2 changes: 1 addition & 1 deletion docs/schemas/domain/IfcRailDomain/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,6 @@ Specific rail elements that are not already covered by other schemas are defined

* different types of rails for ensuring guidance of moving for vehicles or other kinds of machineries.
* specific elements used in the track sub-domain, e.g. sleeper, frog, derailer, etc.
* spatial structrue types for breaking down railway projects.
* spatial structure types for breaking down railway projects.

> HISTORY New schema in IFC4.3
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The predefined type container that collects all possible road facility part type
### ROADSIDEPART
A general concept for various parts of the Roadside.

> NOTE Examples of roadside parts may be side slopes, roadside ditches, back slopes, bunds etc.
> NOTE Examples of roadside parts may be side slopes, roadside ditches, back slopes, bounds etc.

### BUS_STOP
Lateral part of Road for stopping buses allowing them to draw out of the traffic lanes and wait for short periods.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ This entity describes edge members with varying profile properties. Each instanc

****Coordinate Systems****:

See definitions at _IfcStructuralItem_ and _IfcStructuralCurveMember_. The local coordinates of the aggregate are derived from those of its parts. Length measures in local x direction of the aggregate depend on continuity and lengths of the parts. The _Axis_ of the aggregate shal be the same as the _Axis_ of the part at the start of the aggregate.
See definitions at _IfcStructuralItem_ and _IfcStructuralCurveMember_. The local coordinates of the aggregate are derived from those of its parts. Length measures in local x direction of the aggregate depend on continuity and lengths of the parts. The _Axis_ of the aggregate shall be the same as the _Axis_ of the part at the start of the aggregate.

****Material Use Definition****

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -30,7 +30,7 @@ Different shape representations may be used, depending on the nature of the feat

* Symbolic representation, such as the two-dimensional bounding box of a tag.
* A geometric set representing the geometric items of a mark.
* Surface representations of treated parts of the lement surface by means of _IfcShellBasedSurfaceModel_. The faces within the surface model may be included into a B-Rep model within a representation map of the parent element type.
* Surface representations of treated parts of the element surface by means of _IfcShellBasedSurfaceModel_. The faces within the surface model may be included into a B-Rep model within a representation map of the parent element type.

Higher-level parameters (geometric and non-geometric) may be provided by property sets based on local agreements.

Expand All @@ -55,7 +55,7 @@ The attribute ObjectType shall be given if the predefined type is set to USERDEF

#### IfcShellBasedSurfaceModel_SurfaceModel

Surface representations of treated parts of the lement surface by means of IfcShellBasedSurfaceModel. The faces within the surface model may be included into a B-Rep model within a representation map of the parent element type.
Surface representations of treated parts of the element surface by means of IfcShellBasedSurfaceModel. The faces within the surface model may be included into a B-Rep model within a representation map of the parent element type.

### Product Local Placement

Expand Down
Loading