Specify the text format
See this course’s project requirements
A checked extraction script for fictional equipment tags, dates and log lines, with a mismatch report and exact-match safety boundaries.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- A precise tag grammar with four checked cases.
- A segment-by-segment match explanation.
- A whole-input validation rule with a counterexample.
- An extracted log record with explicit string/number distinctions.
- A semantic date check separate from regex matching.
- A tested tag-and-log extraction tool with semantic limits.
Review and revise
Use these criteria to check your work and choose what to improve.
- The implementation or declared simulation follows the supplied contract and retains inspectable original inputs.
- Normal, boundary and rejected cases are recorded with expected versus observed results.
- The changed case has a correct explanation and does not rely on hidden state.
- The project includes source, outputs, instructions and honest tool, privacy and verification limits.
Want more background?
The idea in everyday life
Tags must be EQ- followed by exactly three ASCII digits: EQ-007 is valid; EQ-07, eq-007 and EQ-007x are invalid.
A pattern describes a declared text shape, not every real-world variation. Separate the exact equipment-tag grammar from the meaning of a calendar date.
Specify the text format — original worked practice
A pattern describes a declared text shape, not every real-world variation. Separate the exact equipment-tag grammar from the meaning of a calendar date.
Tags must be EQ- followed by exactly three ASCII digits: EQ-007 is valid; EQ-07, eq-007 and EQ-007x are invalid.
1. Step 1
Write the fixed prefix and digit count.
You should see: Prefix EQ- and three digits are required.
This keeps the rule and its observable result together.
2. Step 2
Classify the four supplied tags against that rule.
You should see: Only EQ-007 matches.
This keeps the rule and its observable result together.
3. Step 3
Keep letter case and trailing text rules explicit.
You should see: Lowercase and extra suffixes are rejected.
This keeps the rule and its observable result together.
4. Step 4
Create an accepted/rejected example table.
You should see: A precise tag grammar with four checked cases.
This keeps the rule and its observable result together.
What to finish
A precise tag grammar with four checked cases.
Watch for this
Leaving the number of digits unstated and later accepting tags with two or four digits.
How can I tell I understand it?
Explain and demonstrate the required distinction: A pattern describes a declared text shape, not every real-world variation. Separate the exact equipment-tag grammar from the meaning of a calendar date. Show a changed input and the expected result without weakening this contract.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Source & access notes · checked 2026-10-01
Relevant documented module/API behavior inspected during expansion authoring; actual execution evidence is recorded separately. No grant eligibility is established.
Access: Official page retrieved with the web reader on 2026-10-01. Documentation reading does not certify execution in every native tool or browser.
Reuse: Original local practice files, fictional data, worked examples and questions. Concepts paraphrased and linked; source exercises are not copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.