fixup! fixup! fixup! fixup! fixup! fixup! fixup! [feature] Introduce the bitag bbl schema

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
-2025-01-15,FCC,1,fixed,0005937974,F0005937974TIER1,50,Xfinity Internet,Extreme 500,Mbps,2,2,2,2
-2025-11-02,,1,mobile,0003768165,F0005937974ABCD12341234,500,T-Mobile,Turbo 5G Plus,Mbps,75,75,75,75
-2025-06-06,FCC,99,satellite,0005937974,F0005937974ABCDEFGHIJ12345,500,Google Fiber,Fiber 2G,Gbps,500,500,500,500
-2025-06-06,FCC,,something,,,0,randomeValue,,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
+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

src/main/resources/schemas/schema.csvs

@@ -1,5 +1,5 @@
 version 1.1
-@totalColumns 14
+@totalColumns 19
 date_published: xDate
 regulator_name: empty or upperCase
 regulator_version_number: empty or range(1, 99)
@@ -13,4 +13,9 @@ bandwidth_download_units: length(4)
 bandwidth_download_marketed_low: empty or range(1,999)
 bandwidth_download_marketed_high: empty or range(1,999)
 bandwidth_download_typical_low: range(1,999)
-bandwidth_download_typical_high: range(1,999)
+bandwidth_download_typical_high: range(1,999)
+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)

src/main/resources/schemas/schema_specs

@@ -179,6 +179,11 @@ This field MUST be in the file and MUST be populated.
 Name: bandwidth_download_typical_low
 Type/Format: numeric, length(1,3)
 Examples: 2, 75, 500
+
+```
+bandwidth_download_typical_low: range(1,999)
+```
+
 14. Download Bandwidth, Typical, High.
 What the customer typically can expect to receive. Depending on the type of service offered, this MAY be an
 absolute number or MAY be a range. If it is an absolute number, then it should generally be one to three
@@ -189,4 +194,62 @@ This field MUST be in the file and MUST be populated.
 16
 Name: bandwidth_download_typical_high
 Type/Format: numeric, length(1,3)
-Examples: 2, 75, 500
+Examples: 2, 75, 500
+
+```
+bandwidth_download_typical_high: range(1,999)
+```
+
+15. Upload Bandwidth Units.
+The applicable bits per second of bandwidth.
+This field MUST be in the file and MUST be populated.
+Name: bandwidth_upload_units
+Type/Format: string, length(4)
+Examples: kbps, Mbps, Gbps, Tbps, Pbps
+
+```
+bandwidth_upload_units: length(4)
+```
+16. Upload Bandwidth, Marketed, Low.
+What the customer is being or has been sold. Depending on the type of service offered, this MAY be an
+absolute number or MAY be a range. If it is an absolute number, then it should generally be one to three
+digits, because after 999 then a new bandwidth unit is used. 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. Some providers do not market speed per se and only disclose some TYPICAL
+speed range, in which case thuis field can be left blank.
+This field MUST be in the file and MAY be populated.
+Name: bandwidth_upload_marketed_low
+Type/Format: numeric, length(1,3)
+Examples: 2, 75, 500
+17. Upload Bandwidth, Marketed, High.
+What the customer is being or has been sold. Depending on the type of service offered, this MAY be an
+absolute number or MAY be a range. If it is an absolute number, then it should generally be one to three
+digits, because after 999 then a new bandwidth unit is used. 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. Some providers do not market speed per se and only disclose some TYPICAL
+speed range, in which case thuis field can be left blank.
+This field MUST be in the file and MAY be populated.
+Name: bandwidth_upload_marketed_high
+Type/Format: numeric, length(1,3)
+Examples: 2, 75, 500
+18. Upload Bandwidth, Typical, Low.
+What the customer typically can expect to receive. Depending on the type of service offered, this MAY be an
+absolute number or MAY be a range. If it is an absolute number, then it should generally be one to three
+digits, because after 999 then a new bandwidth unit is used. 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.
+17
+Name: bandwidth_upload_typical_low
+Type/Format: numeric, length(1,3)
+Examples: 2, 75, 500
+19. Upload Bandwidth, Typical, High.
+What the customer typically can expect to receive. Depending on the type of service offered, this MAY be an
+absolute number or MAY be a range. If it is an absolute number, then it should generally be one to three
+digits, because after 999 then a new bandwidth unit is used. 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: bandwidth_upload_typical_high
+Type/Format: numeric, length(1,3)
+Examples: 2, 75, 500