Requirements

Summary

v0.1.0 — geometry prims

• Connection point prims must be organized under a ConnectionPoints Scope prim.

• Connection point prims must be Plane or Disk geometry only.

• All connection point prims must have purpose = "guide".

• Connection point prims must follow the <vendor>_<type>_<suffix> naming convention.

• Connection points must be saved as <AssetName>_ConnectionPoints.usd and composed as a sublayer.

• Connection point geometry must be positioned and sized to match actual openings on equipment.

v0.2.0 — property vocabulary

• Connection points must be Xform prims under the ConnectionPoints scope with purpose = "guide", carrying at least domain and direction.

• Every connection point must carry all five base namespace properties.

• Domain-specific properties must sit in the namespace named by the connection’s domain value.

The two vocabularies coexist in the data, and assets migrate incrementally with no cutover date. They are kept apart in validation by the feature version a profile selects, since several v0.1.0 requirements contradict v0.2.0 directly. CP.004 requires the <vendor>_<type>_<suffix> prim-name pattern that v0.2.0 stops enforcing, and CP.002 requires Plane or Disk geometry where CP.010 requires an Xform. Neither version’s requirement set is a superset of the other, so a profile selects one feature version and gets a coherent set.

Requirements & Recommendations

Tags	Summary	Compatibility	Validator
🔑	Connection point prims must be organized under a ConnectionPoints Scope prim that is a direct child of the default prim.	other	latest+
❓	Connection point prims must be Plane (rectangular) or Disk (circular) geometry only. The rule belongs to the v0.1.0 vocabulary: a v0.1.0 profile authors Plane and Disk geometry, a v0.2.0 profile authors Xforms under CP.010.	other
❓	All connection point prims must have their purpose attribute set to "guide". The rule carries across both vocabularies: under v0.2.0 CP.010 applies it to connection point Xforms.	other
🔑	All prims under the ConnectionPoints scope must follow the <vendor>_<type>_<suffix> naming pattern using a valid type prefix from the AIF connection point type table.	other	latest+
🔑	Connection points must be saved as a separate <AssetName>_ConnectionPoints.usd file and composed into the main stage as a sublayer.	other	latest+
❓	Connection point geometry must be positioned and sized to match the actual physical openings on the equipment. The requirement is documented normatively and is listed by neither the v0.1.0 nor the v0.2.0 feature.	other
❓	Connection points must be Xform prims under the ConnectionPoints scope with purpose = "guide", each carrying at least simready:connectionPoint:domain and simready:connectionPoint:direction.	other	latest+
❓	Every connection point must carry all five base namespace properties, which together state the semantic identity of the connection.	other	latest+
❓	A connection point’s domain-specific properties must sit in the namespace named by its simready:connectionPoint:domain value, and a production-complete connection point carries every property that namespace defines.	other	latest+