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

Review use of talking about standards within documentation #197

Closed
corymosiman12 opened this issue Jul 15, 2020 · 3 comments
Closed

Review use of talking about standards within documentation #197

corymosiman12 opened this issue Jul 15, 2020 · 3 comments
Assignees

Comments

@corymosiman12
Copy link
Contributor

Make sure everything is consistent. Do we use:

@corymosiman12
Copy link
Contributor Author

Terms searched:

  • 211
  • ASHRAE
  • Standard
  • std
  • 2018

References to other ASHRAE topics (i.e. 90.1, etc.) were not considered - this is only for references to the ASHRAE Standard 211 specifically. There are only two instances where it is referred to in the docs:

<xs:documentation>The type of section such as Whole building, Space function data, or other types. * Whole building - describes the whole building, Space function - describes a space function (see ASHRAE standard 211), Component - describes a subspace of a primary premises such as HVAC zone, retails shops in a mall, etc., Tenant - describes a section for a tenant, Virtual - describes a section loosely with potentially overlap with other sections and section types, Other - not well-described by other types.</xs:documentation>

<xs:documentation>Energy audit level as defined in ASHRAE Procedures for Commercial Building Energy Audits.</xs:documentation>

My preference would be to refer to it as ASHRAE Standard 211-[year]. Providing a year ensures that irrespective of new versions, the statement made holds firm. Although I realize if we are following BEDES we should probably use SPC 211 Standard for Commercial Building Energy Audits.

@nllong @markborkum opinions?

@markborkum
Copy link
Contributor

@corymosiman12 Since it exists, I'd prefer to use BEDES term.

@corymosiman12
Copy link
Contributor Author

Addressed in PR #201

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants