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

Author: marmoure

src/main/resources/schemas/schema.csvs

@@ -0,0 +1,3 @@
+version 1.1
+@totalColumns
+date_published: xDate

src/main/resources/schemas/schema_specs

@@ -0,0 +1,42 @@
+version 1.1
+@totalColumns TODO unknow at this stage
+
+1. Date Published
+Date when published in Coordinated Universal Time (UTC), in the ISO 8601 format [40], with hyphens.
+Thus the format is YYYY-MM-DD, so 2025-01-15 for example to represent January 15, 2025, according to
+the current date in UTC.
+This field MUST be in the file and MUST be used.
+Name: date_published
+Type/Format: date
+Examples: 2025-01-15, 2025-11-02, 2025-06-06
+
+from the specs I found the following expression that validates date: xDate
+```
+date_published: xDate
+```
+
+2. Regulator Name
+Initially this will only be the FCC, but as it is possible that other regulators may wish to use this format, a
+regulator field is included.
+This field MUST be in the file and MAY be used. If this field is empty, users of the file SHOULD assume the
+regulator is the FCC.
+Name: regulator_name
+Type/Format: string
+Examples: FCC, OFCOM, ECOI, MIC
+so it can be empty or it can be a string of uppercase letters
+```
+regulator_name: upperCase or empty
+```
+
+3. Regulator Version Number
+If requirements ever change, as we expect they will, having a required version field will be very useful. Given
+that labels must be maintained historically, it will be useful to know that a particular historical or current
+label is compatible with a specific regulatory requirement version. This field will begin from 01 for the first
+version, with the next being 02, all the way up to 99.
+This field MUST be in the file and MAY be populated. If this field is not used or is not applicable it SHOULD
+be left empty.
+If and when a regulator changes the requirements for these labels, a new version of the schema will also need
+to be published.
+Field: regulator_version_number
+Type/Format: numeric, range(1, 99)
+Examples: 1, 02, 55, 77