# The Source Term Is Shared. Which Component Does the English Name Identify?

> Resolve shared manufacturing terms using defined concepts, approved labels and part associations before releasing English product content.

- Canonical: https://www.aixindar.com/news/the-source-term-is-shared-which-component-does-the-english-name-identify
- Markdown: https://www.aixindar.com/news/the-source-term-is-shared-which-component-does-the-english-name-identify.md
- Author: Daoyu Guan — https://www.aixindar.com/experts/daoyu-guan
- Published: 2026-11-20T01:21:14.840Z
- Last updated: 2026-11-20T03:53:44.822Z
- Evidence checked: Not separately recorded in CMS
- Editorial status: Published
- Corrections: No correction record supplied by CMS.

A Chinese component list uses the same short term for two parts. The English brochure gives both parts one translation. One supports a moving shaft; the other maintains a distance between assembled components. A buyer searching by the English name can now misunderstand which function the supplier offers.

Resolve the underlying component before approving its wording. A concept record can connect a defined object to its part identifiers, preferred labels, accepted alternatives, source evidence and approval revision. That relationship gives the website editor a specific meaning to preserve across languages and documents.

For an exporter, the immediate task is practical. An English product title, a quotation table and a technical FAQ should identify the intended part consistently. A shared word alone leaves too much work to the reader.

## Give the meaning an identifier

A terminology list often starts with two columns, source wording and translation. That structure works when the intended meaning is already clear. It needs more context when the same expression appears in different product families or engineering roles.

The W3C SKOS model represents concepts with identifiers and connects them to labels, definitions and relationships. Its reference allows a preferred label for each language tag, alongside alternative labels. Those mechanisms provide a useful public model for separating the identified concept from its wording. [SKOS Reference](https://www.w3.org/TR/skos-reference/)

An exporter can begin with an ordinary controlled table. The identifier need only remain stable within the agreed terminology system. Record who controls it and how it relates to the manufacturer's existing part and document identifiers.

A concept identifier and a part number serve different purposes. One concept can describe a component type represented by several part numbers. A particular part number can also carry dimensions, material and revision details beyond the terminology concept. Keep those relationships explicit when reusing a term on a product page.

## Work through two fictional components

The following example describes an invented factory's records. Its Chinese and English labels are editorial choices for this exercise.


| Record                    | Source wording in the received list | Defined function                              | Approved English label |
| ------------------------- | ----------------------------------- | --------------------------------------------- | ---------------------- |
| C17, linked to part P-017 | 轴套                                  | Supports a shaft through sliding contact      | sleeve bearing         |
| C29, linked to part P-029 | 轴套                                  | Maintains a specified distance in an assembly | spacer sleeve          |


The received source wording is the same. The functions establish two concepts in this fictional catalogue.

Before publication, an engineering reviewer confirms the intended object using the approved drawing, material record and product description. The terminology editor then records the accepted English label and any permitted alternatives. The website editor uses the appropriate concept-to-part association when preparing the page.

Suppose an older brochure calls P-029 a sleeve bearing. A simple spelling check will accept the words. A concept-aware review can identify that the approved record for P-029 points to C29 and ask for the term to be corrected or reapproved.

The useful distinction is the defined function. A label can look professionally written while identifying the wrong component.

## Record preferred wording and alternatives with language tags

The following original Turtle example illustrates a SKOS record for C17 in the teaching catalogue.

```turtle
@prefix skos: <http://www.w3.org/2004/02/skos/core#> .

<https://example.com/concepts/C17> a skos:Concept ;
    skos:prefLabel "sleeve bearing"@en ;
    skos:prefLabel "滑动轴套"@zh-Hans ;
    skos:altLabel "plain bush"@en ;
    skos:definition "A component that supports a shaft through sliding contact."@en .
```

SKOS restricts a resource to at most one preferred label per language tag. Its preferred, alternative and hidden label properties are pairwise disjoint. A business can adopt additional usage rules for its own publishing process. For example, an accepted alternative can remain searchable while the approved product title uses the preferred wording. [SKOS lexical labelling rules](https://www.w3.org/TR/skos-reference/#labels)

The model's language tag also deserves attention. A language label helps identify the wording's language. The market in which a product is offered, its applicable documentation and the commercial conditions belong to additional records.

Document the policy when English variants are required. A company might approve different labels for particular language tags or use one preferred English label across its catalogue. The editor should be able to identify the selected convention and the evidence supporting an exception.

The SKOS Primer provides examples of multilingual concepts and concept schemes. It supplies a model for organizing the vocabulary; the manufacturer's definition and approval process establish what a particular industrial entry means. [SKOS Primer](https://www.w3.org/TR/skos-primer/)

## Preserve the source evidence behind the decision

An approved label becomes easier to maintain when its decision can be traced to a particular source revision.

For each important term, preserve the source document identifier and revision, the relevant drawing or table location, the component relationship, the approved definition and the approval owner. Include the date or release identifier used by the publishing team.

The location can be modest, such as a drawing view and part callout. It should let another authorized reviewer understand why the entry describes that component. A bare link to a folder leaves the reasoning harder to reconstruct.

When the source changes, review the affected relationship. A dimension correction may leave the terminology concept unchanged. A changed function or a replacement component may require a different concept or definition. Record the actual engineering decision before propagating wording.

For the fictional P-029 example, a correction to its length would update the applicable product data. If a redesign makes the component perform a bearing function, the reviewer needs to reconsider the concept assignment. Both changes deserve a record, with their different effects on the English page explained.

## Use a compact approval table

The following is an editorial proposal for a small export-content project. Equivalent fields can live in an existing terminology system or document workflow.


| Element                               | Publishing decision it supports                             |
| ------------------------------------- | ----------------------------------------------------------- |
| Stable concept identifier             | Which defined meaning is being reused?                      |
| Definition and component context      | Which object or function does the entry describe?           |
| Part and source-document associations | Where does that meaning apply?                              |
| Preferred labels with language tags   | Which wording belongs in the released page?                 |
| Accepted alternatives and usage notes | Which variants are permitted in search or explanatory copy? |
| Approval owner and revision           | Which decision authorized the current wording?              |


A small project can complete these fields for the terms most likely to cause a purchasing misunderstanding. Start with terms appearing in product titles, capability statements, material descriptions and quotation conditions.

The record should make an unresolved term visible. Assigning a polished English phrase before the object is identified moves the ambiguity into the published page. Keeping the issue open gives the engineering and commercial reviewers an opportunity to resolve it at the source.

## Take the record through an actual publishing workflow

1. Select two product records that share source wording. Identify the actual part, its function and the source revision for each record.
2. Ask the technical owner to approve the definitions and concept assignments. Record any evidence still needed to distinguish the components.
3. Approve preferred English wording and permitted alternatives under the chosen language convention. Keep the original received wording for traceability.
4. Prepare the product title, parameter table and one buyer FAQ using the approved record. Include the applicable part and revision details where the reader needs them.
5. Review those surfaces together. Confirm that each label still refers to the intended object, including in downloadable documents and inquiry links.
6. Change one fictional source record in the acceptance exercise. Identify which published references need review and retain the original release history.

This exercise tests the relationship between an approved meaning and the content that reaches the buyer. A software demonstration can use the same packet to show how editors find terms, approve changes, export records and update dependent content.

The existing [manufacturing terminology shortlist](https://www.aixindar.com/news/10-options-for-managing-chinese-english-manufacturing-terminology) compares implementation and terminology-management options. This exercise gives those options a concrete pair of records to handle.

## Keep technical approval and English publication accountable

The manufacturer supplies the engineering meaning and approves the product claim. The content team turns that approved information into a readable English page and checks the released wording against the agreed record.

[Xindar's manufacturing content service](https://www.aixindar.com/industries/manufacturing) is relevant to the second part of this workflow. A proposal can identify the supplied source documents, approval owner, English page set and inquiry handoff. It should make the point of technical approval clear before the content is released.

For an AI-assisted supplier researcher, a page containing the part identifier, intended function and applicable conditions provides more specific material to inspect. Any effect on discovery or recommendations still needs direct observation. The terminology exercise itself establishes content consistency within its stated scope.

## FAQ

### Can two concepts use the same visible word?

A word can occur in different contexts. Keep each concept's definition and application explicit, and review how a reader will distinguish them on the actual page.

### Does every part need a separate terminology concept?

Use the distinction required by the defined meaning. Several dimensional variants can share a component concept while retaining separate part identifiers and product data.

### Should an old translation disappear from the records?

Keep its release history and review the contexts in which it remains useful or misleading. An accepted alternative and a withdrawn translation should have clearly documented treatment.

### Does publishing SKOS make an AI system interpret every part correctly?

SKOS provides a data model. Correct definitions, source associations, readable pages and observed answer quality require their own checks.

## Sources and method

The technical foundation is the W3C SKOS Reference and its companion Primer. The two components, labels, part identifiers and workflow example are fictional teaching material. The approval table and acceptance procedure are editorial proposals. A real manufacturer's terminology release requires its own source documents and technical approval.

## Editorial references

- [Editorial policy](https://www.aixindar.com/editorial-policy)
- [Research methodology](https://www.aixindar.com/research-methodology)
- [Corrections policy](https://www.aixindar.com/corrections)
