Widget References & Standards API Routing
[PROPOSED Late 2022] Structured References
Format
To allow forreferences to directly link to relevant standards/codes, a structured array format is proposed for a new field (referencesJSON):
The “description” field will not be part of the first iteration, as further user testing on its benefits will be conducted.
Field Descriptions
Standards API Links
The standards API intention is full search support in the Builder. All metadata can be generated automatically by searching for relevant clauses in a text box.Example Workflow
- Type
AS4100 Cl 5.6.3in search - Standards API suggests matches
- On selection, creates:
id: Relative URL for standards API [www.calcs.com/api/standards/[ID]name: Clause name for the buttondescription: Auto-populated title of specific clause/section/figure/table
Standards Examples
Examples for Standards Australia & AISC integrations:External References
Theid field is mandatory. Many product catalogues, technical notes and standards authorities provide direct links or purchase pages.
External Reference Examples
Transition of Existing Templates
ID Field Standards URL Structure
Format: /Authority/Standard/type/Type-reference/sub-type/Sub-type-reference- Lower-case for enumerations of select types
- Upper-case for dynamic references
Authority
The Standards provider. E.g., SA (Standards Australia), AISC, ACI, etc.Standard
Unique identifier for the standard document with hyphens as separator: PREFIX-CODE-YEAR-REVISION- PREFIX: AS, AISC, ASNZS, etc. [required]
- CODE: 4100 or 1720-1 (for AS), 360 (for AISC) [required]
- YEAR: YYYY (for AS), YY (for AISC) match the standard default [required]
- REVISION: 1 (for AS Amdt 1). Not necessarily correlated with actual amendment number [optional]
Examples:
AS-4100-2020-1(AS4100:2020 incorporating Amdt 1)AS-4100-Supp1-1999(AS4100 Supplement 1 - 1999)AS-1720-1-2010-3(AS1720.1:2010 incorporating Amdt 1-3)
Type / Type-reference
Hyphen-separated clause reference with unique identifiers in standards documents.Section
Main sections within document or appendix (2-4 layers depth: X-X to X-X-X-X):section/5-6-3(Cl 5.6.3 in AS4100)section/H-5-2-2(App H Cl H.5.2.2 in AS4100-2021)section/I-6-1(Clause I6(1) - AISC AS360-16)section/I-6-2-a(Clause I6(2a) - AISC AS360-16)
Table / Figure
Tables with unique title references (2-4 layers depth: X-X to X-X-X-X):table/5-6-2table/5-6-3A(Table 5.6.3(A) in AS4100)table/B-1(Table B1 in appendix B)figure/9.1.10.3B(Figure 9.1.10.3(B) in AS4100)
Equation
Must have unique references (only partially covered in newer Australian standards):equation/9-2-2-4(for 9.2.2.4(2) in AS4100)
Sub-type / Sub-type-reference [OPTIONAL]
1-4 layers depth supported (X to X-X-X-X). Most common islist for section/table/equation list items.
Examples:
section/5-6-2/list/b-i(AS4100 Cl 5.6.2(b)(i))table/A-3-1/list/2-1-a(Table A-3.1 reference 2.1(a) AISC A360-16)equation/9-2-2-4/list/2(for 9.2.2.4(2) in AS4100)
Markdown Support
Supported markdown elements in widget description sections:Not all markdown features are supported in the description sections of widgets.