From 58d34051cb3702558544930d5673a5fc61e4608c Mon Sep 17 00:00:00 2001 From: Francesco Anselmo Date: Mon, 16 Nov 2020 21:49:44 +0000 Subject: [PATCH] Update BDNS_Specification_naming_syntax.md LTF -> LT --- BDNS_Specification_naming_syntax.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/BDNS_Specification_naming_syntax.md b/BDNS_Specification_naming_syntax.md index 88ab6e9..63c6560 100644 --- a/BDNS_Specification_naming_syntax.md +++ b/BDNS_Specification_naming_syntax.md @@ -182,12 +182,12 @@ The format is composed of a 2 to 6 uppercase alphabetical characters long type a Only numeric and uppercase alphabetic characters are allowed, according to the regular expression below. The separator character between the type enumeration and incremental identifier is a hyphen (`-`). -For practical reasons, at the discretion of the user and as long as there are no name clashes between devices in the same building, the 6 digits forming the second part of the device role name can be assigned following spatial or discipline specific scoping methods. For instance, the lighting fixtures on level 3 of a 20 stories building can all share the same first part of the name `LTF-03####` and the subsequent integer numbers can be attributed incrementally. +For practical reasons, at the discretion of the user and as long as there are no name clashes between devices in the same building, the 6 digits forming the second part of the device role name can be assigned following spatial or discipline specific scoping methods. For instance, the lighting fixtures on level 3 of a 20 stories building can all share the same first part of the name `LT-03####` and the subsequent integer numbers can be attributed incrementally. ### Examples -Name example for a lighting fixture: `LTF-15` +Name example for a lighting fixture: `LT-15` Name example for an air handling unit: `AHU-3`