fixup! fixup! fixup! fixup! fixup! fixup! fixup! [feature] building up the schema again from scratch acording the section 11,4,1 in the bitag report

Author: marmoure

src/main/resources/schemas/sample.csv

@@ -1,5 +1,5 @@
-date_published,regulator_name,regulator_version_number,connection_type,fcc_registration_number,unique_plan_identifier,network_technology_type,provider_name,service_plan_name,bandwidth_download_units,bandwidth_download_marketed_low,bandwidth_download_marketed_high,bandwidth_download_typical_low,bandwidth_download_typical_high,bandwidth_upload_units,bandwidth_upload_marketed_low,bandwidth_upload_marketed_high,bandwidth_upload_typical_low,bandwidth_upload_typical_high
-2025-01-15,FCC,1,fixed,0005937974,F0005937974TIER1,50,Xfinity Internet,Extreme 500,Mbps,2,2,2,2,Mbps,2,2,2,2
-2025-11-02,,1,mobile,0003768165,F0005937974ABCD12341234,500,T-Mobile,Turbo 5G Plus,Mbps,75,75,75,75,Mbps,75,75,75,75
-2025-06-06,FCC,99,satellite,0005937974,F0005937974ABCDEFGHIJ12345,500,Google Fiber,Fiber 2G,Gbps,500,500,500,500,Gbps,500,500,500,500
-2025-06-06,FCC,,something,,,0,randomeValue,,kbps,1,1,1,1,kbps,1,1,1,1
+date_published,regulator_name,regulator_version_number,connection_type,fcc_registration_number,unique_plan_identifier,network_technology_type,provider_name,service_plan_name,bandwidth_download_units,bandwidth_download_marketed_low,bandwidth_download_marketed_high,bandwidth_download_typical_low,bandwidth_download_typical_high,bandwidth_upload_units,bandwidth_upload_marketed_low,bandwidth_upload_marketed_high,bandwidth_upload_typical_low,bandwidth_upload_typical_high,latency_idle_low,latency_idle_high
+2025-01-15,FCC,1,fixed,0005937974,F0005937974TIER1,50,Xfinity Internet,Extreme 500,Mbps,2,2,2,2,Mbps,2,2,2,2,2,2
+2025-11-02,,1,mobile,0003768165,F0005937974ABCD12341234,500,T-Mobile,Turbo 5G Plus,Mbps,75,75,75,75,Mbps,75,75,75,75,75,75
+2025-06-06,FCC,99,satellite,0005937974,F0005937974ABCDEFGHIJ12345,500,Google Fiber,Fiber 2G,Gbps,500,500,500,500,Gbps,500,500,500,500,500,500
+2025-06-06,FCC,,something,,,0,randomeValue,,kbps,1,1,1,1,kbps,1,1,1,1,1,1

src/main/resources/schemas/schema.csvs

@@ -1,5 +1,5 @@
 version 1.1
-@totalColumns 19
+@totalColumns 21
 date_published: xDate
 regulator_name: empty or upperCase
 regulator_version_number: empty or range(1, 99)
@@ -18,4 +18,6 @@ bandwidth_upload_units: length(4)
 bandwidth_upload_marketed_low: empty or range(1,999)
 bandwidth_upload_marketed_high: empty or range(1,999)
 bandwidth_upload_typical_low: range(1,999)
-bandwidth_upload_typical_high: range(1,999)
+bandwidth_upload_typical_high: range(1,999)
+latency_idle_low: range(0,1000)
+latency_idle_high: range(0,1000)

src/main/resources/schemas/schema_specs

@@ -253,3 +253,24 @@ This field MUST be in the file and MUST be populated.
 Name: bandwidth_upload_typical_high
 Type/Format: numeric, length(1,3)
 Examples: 2, 75, 500
+
+20. Latency, Idle, Low.
+This is a number, in milliseconds, of the typical idle latency a user will experience. Depending on the type of
+service offered, this MAY be an absolute number or MAY be a range. If there is only one number, then the
+value for the respective “low” and “high” fields MUST be the same. When a range is appropriate, then the
+“low” and “high” numbers will differ.
+This field MUST be in the file and MUST be populated.
+Name: latency_idle_low
+Type/Format: numeric, length(*,10)
+Examples: 2, 75, 500
+
+
+21. Latency, Idle, High.
+This is a number, in milliseconds, of the typical idle latency a user will experience. Depending on the type of
+service offered, this MAY be an absolute number or MAY be a range. If there is only one number, then the
+value for the respective “low” and “high” fields MUST be the same. When a range is appropriate, then the
+“low” and “high” numbers will differ.
+This field MUST be in the file and MUST be populated.
+Name: latency_idle_high
+Type/Format: numeric, length(*,10)
+Examples: 2, 75, 500