Proposals for HPXML

[shorowit]

There are still a fair number of extension elements used here as well as in OS-ERI. Some of them should probably be moved to official HPXML elements.

There are also some other changes that should be considered regarding min/max constraints, etc.

Some possibilities:

• Require AssemblyEffectiveRvalue > 0 in schema to prevent user error Requires AssemblyEffectiveRValue to be > 0 hpxmlwg/hpxml#257
• Propose ClothesDryer venting element(s) Adds clothes dryer venting fields hpxmlwg/hpxml#255
• Propose Wall/Vented (for WAP) Adds wall vented field hpxmlwg/hpxml#256
• Propose storm window material (WAP) Adds storm window material field hpxmlwg/hpxml#259
• Propose window type (slider, fixed, etc.) (WAP) Adds a window type field hpxmlwg/hpxml#260
• Propose wood stud wall framing type (balloon, platform) (WAP) Adds wood stud wall framing type field hpxmlwg/hpxml#261
• Replace ugly extension/OtherSpaceAboveOrBelow (one proposed path is here) Introduce Ceilings element hpxmlwg/hpxml#264
• Propose shared mechanical ventilation elements w/ preheating/precooling SFA/MF Systems hpxmlwg/hpxml#240
• Propose InteriorFinish inputs (Type, Thickness, ...)? Adds InteriorFinish element for enclosure surfaces hpxmlwg/hpxml#274
• Propose heat pump type of Window/Room Heat pump
• Propose flue/chimney inputs, including location?
• Reconcile Slab/CarpetFraction and Slab/CarpetRValue with Slab/FloorCovering
• Propose HVAC Installation quality inputs (considerations: heating vs cooling airflow rates for heat pumps; elements attached to HVAC systems vs AirDistribution systems)
• Propose NeighboringBuilding? Distances, Heights, and Azimuths/Orientations
• Propose shared hot water recirculation elements

[shorowit]

This is good enough for now; can always search for extension elements to see what other inputs might make sense to incorporate in the HPXML schema.