Hair Scissor Glossary and Terminology Crosswalk (EN/JA)

What this crosswalk is for

A terminology crosswalk helps a reader move between:

• English and Japanese source material;
• maker manuals and product pages;
• sharpener intake and service reports;
• educator and salon language;
• retailer and marketplace listings;
• ScissorPedia guides and reference pages; and
• historical and current wording.

It does not declare that every term has one permanent English equivalent. It should make uncertainty more visible, not remove it for convenience.

Separate concepts from labels

A concept is the thing, geometry, process, action, state, or claim being described. A label is a word or phrase a source uses for it.

For example, two sources can use the same English label while showing different cross-sections or service methods. They may share a broad concept but not an exact technical specification. Conversely, two different labels can refer to the same exact maker-defined part.

Create the concept record before choosing a preferred label.

Minimum term record

Do not keep only an English word and a Japanese word in adjacent cells.

Use language tags that follow a documented convention. RFC 5646 defines a system for language tags, but choosing a valid tag does not prove a translation is accurate or that one market uses the term uniformly.

Preserve the Japanese source

For Japanese material, keep these elements distinct:

1. exact source text in Japanese script;
2. reading supplied by the source or checked by a competent reviewer;
3. romanisation and the system or source spelling used;
4. literal translation where it clarifies word formation;
5. source-provided English label, if present;
6. context-sensitive editorial explanation; and
7. technical interpretation supported by diagrams, specifications, or qualified review.

Do not reconstruct kanji from a romanised product page and present it as source text. Do not translate a product-family name as though it were a geometry specification. Do not infer a manufacturing process from an English sales adjective.

Translation review questions

• Does the term identify a noun, action, result, quality, or brand expression?
• Is the source addressing manufacturing, sharpening, use, care, or sales?
• Does the same source define it in text, a diagram, measurements, or a product example?
• Is omitted context understood by a Japanese specialist but missing from the English line?
• Does the proposed English term add a geometry, number, material, or performance promise absent from the source?
• Does a source-supplied English label conflict with a literal or technical translation?
• Is the wording current, historical, regional, house style, or product-line specific?
• Can the disagreement remain visible rather than being forced into one answer?

For consequential technical or commercial content, use both competent language review and subject-matter review. Fluency alone does not establish blade-geometry expertise, and technical experience alone does not establish translation accuracy.

Use relationship strength, not a synonym column

The W3C SKOS model distinguishes preferred and alternative labels and supports exact, close, broader, narrower, and related mappings. A local glossary can use similar explicit relationships without claiming that every entry is an ontology.

Record the relationship source, reviewer, date, direction, and scope. Exact match in one maker’s manual does not automatically become exact match across the industry.

Define the evidence hierarchy for each use

Source quality depends on the question.

Exact product or part name

Prefer the current maker’s documentation for the exact model and market. Preserve archived versions when an older record depends on them. A retailer can show market usage, but it should not silently override maker identity or specification.

Service or sharpening wording

Use the provider’s exact intake, report, and process description for what that provider claims to have done. Separate observable salon findings from technical diagnosis. Do not treat one service provider’s house term as a maker specification or universal process.

Haircutting method

Use the named educator, school, curriculum, or publication that defines the method. Another educator’s similar-looking movement may have a different purpose, section logic, or name.

General concept page

Compare multiple identified sources and state the shared core, material differences, and unresolved boundaries. A general page should not flatten exact product or method definitions into one unqualified sentence.

Historical term

Record publication, edition, date, market, and original wording. Label the entry historical and avoid implying current use without evidence.

Capture geometry without adjectives alone

Words such as convex, bevelled, hollow, clamshell, sword, bamboo, mountain, flat, hybrid, semi, micro, and ergonomic may be used differently by different sources.

When a term concerns blade or handle geometry, capture available evidence such as:

• exact object and component;
• side, face, edge, spine, ride area, hollow, or cross-section;
• view orientation and scale;
• named surfaces and transitions;
• dimensions, angles, radii, offsets, thicknesses, tolerances, or ranges when officially specified;
• whether a value is measured, nominal, illustrative, translated, or inferred;
• manufacturing state versus serviced state;
• left, right, true-left, mirrored, or symmetric condition;
• model, size, variant, and production date; and
• source diagram, photo, specification, or inspection method.

Do not invent a universal number of facets, sharpening stages, angles, or steel hardness from the term alone. Do not claim that a profile guarantees a cutting motion, sharpness, durability, comfort, or service result.

Keep anatomy, process, action, and performance separate

A common glossary failure is using one definition to blend four different things.

A geometry term does not prove a manufacturing method. A process name does not prove a measurable final profile. A cutting action does not prove suitability for every hair state. A product claim does not become a verified outcome because it appears in several retailer descriptions.

Handle common high-risk term groups

Edge and blade profiles

For terms such as convex, bevelled, semi-convex, clam-shaped, hamaguri, hollow, micro-serrated, or hybrid, identify the source-defined object, section, transition, process, and model. Map only what the evidence shows.

Inner blade and ride terminology

For terms associated with an inner blade face, hollow, ride area, contact area, or related service surface, state which face and view the source labels. Do not equate every Japanese term containing a word associated with hollowing or the back side with one generic English phrase.

Handle and handedness terms

Separate handle relationship, thumb movement, finger-ring shape, crane or offset marketing category, true-left blade orientation, reversible grip, and user fit. A label such as ergonomic is a claim category, not proof of comfort or treatment.

Steel and material terms

Record the exact maker grade, standard designation, supplier designation, coating, treatment, and product claim separately. Do not convert an informal family name into a precise chemistry or hardness. Link to steel types while preserving the exact source limits.

Haircutting and texturising terms

Name the educator or curriculum, hair state, section variables, tool action, intended relationship, and review state. Similar words such as slide, slice, point, channel, chip, notch, feather, texture, blend, and thinning can refer to different actions or outcomes.

Maintenance and service terms

Separate clean, disinfect, dry, lubricate, adjust, inspect, repair, hone, sharpen, polish, recondition, remanufacture, and replace. The applicable maker, workplace, public-health, product-label, and service-provider definitions can differ. Use the daily care protocol and sharpener vetting guide for operational decisions.

Term page template

Publish consequential concepts on stable pages with a consistent structure.

[Preferred display label]

• Concept ID:
• Plain-language definition:
• Applies to:
• Does not establish:
• Original-language label or labels:
• Reading and romanisation:
• Source-preferred translation:
• Alternative, historical, and market labels:
• Exact, close, broader, narrower, related, disputed, and non-equivalent concepts:
• Diagram or visual orientation:
• Product, method, market, and date scope:
• Sources and checked dates:
• Reviewer and evidence status:
• Change history:

Put the direct definition near the heading, then qualify it immediately. Avoid opening with a long history that makes the answer difficult to locate.

Crosswalk table template

Do not merge cells for distinct concepts. Export original Unicode text without replacing characters, and test search with script, reading, romanisation, hyphenation, spacing, singular and plural forms, and common misspellings without making misspellings preferred labels.

Editorial workflow

1. Intake

Record the exact source, capture method, rights, context, proposed concept, and why the term matters. Preserve a screenshot or document location only when permitted and necessary.

2. Evidence review

Confirm source identity, model or method, market, version, date, and wording. Look for diagrams, specifications, definitions, and source-supplied translations.

3. Language review

Check script, reading, grammar, romanisation, literal meaning, translation alternatives, and context. Mark machine translation as working material, not authority.

4. Technical review

Check the object, view, geometry, process, action, and consequence. Identify what cannot be inferred.

5. Mapping

Select a relationship strength and cite the evidence. Record dissent or unresolved questions.

6. Plain-language edit

Write the shortest definition that remains accurate, then add scope and exclusions. Digital.gov’s plain-language guidance supports organising for the audience, using familiar words, and testing whether people can use the information.

7. Accessibility and rendering

Set page and language-of-parts metadata where supported. Test Japanese characters, line breaks, vertical or horizontal source extracts where used, zoom, reflow, screen-reader pronunciation limits, table navigation, and copy and paste.

8. Release and propagation

Publish the term version, update dependent guides and structured records, and retain redirects or historical notes where labels changed.

Accessibility and language notes

• Do not place essential Japanese text only inside an image.
• Provide text alternatives for technical diagrams that explain the purpose, orientation, labelled parts, and relevant relationships.
• Mark language changes in page code where the platform supports it.
• Expand unusual abbreviations and explain specialist words on first use.
• Do not use colour alone for verified, disputed, deprecated, or unresolved status.
• Provide a linear list or term page when a wide crosswalk table does not reflow well.
• Test copy, search, and screen-reader behaviour with the actual scripts and supported browsers.
• Do not claim that automated pronunciation or translation is correct merely because a tool produced output.

WCAG 2.2 provides web accessibility requirements including language of page, language of parts, unusual words, abbreviations, headings, labels, text alternatives, reflow, and table relationships. Conformance still requires evaluation of the complete published experience.

Search, SEO, and answer-system clarity

Good retrieval follows from clear evidence, not from repeating keywords.

For each term page:

• use one descriptive title and one visible primary heading;
• answer the term question in the opening paragraph;
• retain original script and common source-supported variants;
• state maker, product, method, language, market, and date scope;
• link the definition to primary evidence;
• link to broader and narrower concepts visibly;
• include a revision date and change note;
• use stable concept and page identifiers;
• avoid hiding the definition in an image, script-only widget, or download; and
• ensure structured data matches the visible page rather than adding unsupported synonyms.

Do not use sameAs, exact-match, translation, or alternate-name fields to force a stronger relationship than the visible evidence supports. Search convenience does not justify technical equivalence.

Versioning and change control

Trigger review when:

• a maker changes a product page, manual, model, diagram, translation, or market wording;
• a service provider changes process terminology;
• an educator revises a named method;
• new primary evidence resolves or creates a conflict;
• a user reports a translation, script, accessibility, or technical problem;
• a preferred label creates repeated misidentification; or
• a dependent guide, product record, image, or structured field changes.

When a term changes, record:

• old and new labels or definitions;
• concept IDs affected;
• reason and evidence;
• relationship changes;
• reviewer and effective date;
• dependent pages and records;
• redirect, alias, or deprecation behaviour; and
• whether historical records retain the old wording.

Never rewrite a historical service record to use today’s preferred terminology. Link it to the current concept while preserving what the source actually said.

Quality checks

Before release, ask:

• Is the original wording exact and attributable?
• Is the language tag and script correct for the record?
• Are reading, romanisation, translation, and explanation separated?
• Does the definition identify a concept rather than repeat the label?
• Are object, view, process, product, market, and date boundaries explicit?
• Is every mapping no stronger than its evidence?
• Are conflicts and unknowns visible?
• Are technical diagrams oriented and accessible?
• Can users find the term from relevant variants without turning them into false synonyms?
• Do dependent guides use the concept consistently?
• Can a correction be propagated without erasing history?

Common failure modes

• Two-column equivalence: one English and one Japanese word are treated as universal synonyms.
• Romanisation presented as Japanese source text: original script and context are lost.
• Marketing adjective as geometry: a sales term becomes a fabricated technical specification.
• Part, process, and result collapsed: one definition claims more than the source establishes.
• Retail repetition as verification: copied descriptions are mistaken for independent evidence.
• Brand-wide generalisation: one model’s wording is applied to every tool from the maker or country.
• Silent translation: readers cannot tell which words came from the source and which came from the editor.
• Universal number claim: an angle, hardness, stage count, or lifespan is attached to a term without exact evidence.
• Glossary by committee vote: disagreement is hidden instead of recorded and researched.
• Quarterly theatre: reviews occur on a calendar while material source changes go unnoticed.

Implementation checklist

1. Define concept classes, IDs, relationship types, statuses, and reviewer roles.
2. Create separate concept, label, source, mapping, and change records.
3. Preserve original script and citation location for every translated entry.
4. Establish language and technical review routes.
5. Migrate high-risk anatomy, edge, service, handedness, steel, and technique terms first.
6. Mark unsupported old synonyms as unresolved rather than silently retaining them.
7. Publish stable term pages with direct definitions, scope, evidence, and related concepts.
8. Test Japanese rendering, search, copy, reflow, tables, and assistive technology.
9. Connect guide, reference, product, service, and visual metadata to concept IDs.
10. Monitor source changes and propagate corrections while preserving historical records.

Sources and scope

• W3C: SKOS Simple Knowledge Organization System Reference, for concepts, preferred and alternative labels, notes, and mapping relationships.
• RFC Editor: RFC 5646, Tags for Identifying Languages, for the language-tag framework.
• W3C: Web Content Accessibility Guidelines 2.2, for language, unusual words, abbreviations, text alternatives, structure, reflow, and other web accessibility requirements.
• Digital.gov: Plain Language Guide, for audience-centred organisation, familiar wording, and usability-focused content practice.

Sources checked 22 July 2026. They support knowledge organisation, language identifiers, accessibility, and plain-language practice. They do not determine the correct translation or technical definition for a particular scissor, maker, service, or haircutting method.

Related guides and references

• Scissor anatomy reference
• Edge types reference
• Steel types reference
• Tool mastery: shear anatomy
• Japanese blade-line terminology
• Daily scissor care protocol
• Professional sharpener vetting
• Downloadable toolkit library