1 / 16

Trademark terminology control

Trademark terminology control. Gerrit Schutte OHIM 9th of December, 2011. Agenda. Trademark terminology (4 slides) Work areas (4 slides) Examples (5 slides). Terminology versus Trademark. Terminology. Trademarks. id 420139 class 42 term Computer software design.

chaney
Télécharger la présentation

Trademark terminology control

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Trademark terminology control Gerrit Schutte OHIM 9th of December, 2011

  2. Agenda • Trademark terminology (4 slides) • Work areas (4 slides) • Examples (5 slides)

  3. Terminology versus Trademark Terminology Trademarks id 420139 class 42 term Computer software design … domain name formation; Computer software design; services relating to the design of software artefacts…

  4. Volumes Terminology Trademark • 100,000 marks p.a. electronically filed • to contain ~15 input expressions per mark • translated in 22 languages for publication • 17,000 oppositions p.a. • ~30 logical term bases under consideration • ~15 multi-lingual term bases • 22 languages supported in filing • the largest term base being OHIM’s harmonized term base to contain ~50,000 multi-lingual entities

  5. Examination Opposition Translation Filing General public Legal staff Translator Examiner Prominent lifecycle events

  6. Key figures and efforts • Filing of marks • ~ 1.5 * 106 input expression electronically filed per annum • ~ 100.000 persons to explore, choose and “invent” terminology • Examination of marks • ~ 58% of all expressions automatically matched to reference terminology • ~ 50 persons to examine remainder • Translation of marks • ~68% of all input expressions automatically matched to translation memory • ~0.5 * 106 of expressions translated into 21 targets • Opposition to marks • ~17,000 marks opposed to by earlier right holders • ~ 50 persons to take opposition decisions pair wise assessing expressions

  7. Work areas and dependencies Tooling Resource Linguistics

  8. Resource • Consolidation • Establish and enforce syntactic rules • Eliminate duplicates • Expansion • Highly frequent terms • Market reflection • Alignment • Compare across organisations • Collaboratively build common asset • Semantic enrichment • Conceptualize • Impose and maintain relations building ontology • Blacklist • Manage terms that are not acceptable

  9. Tooling • Parsing • Multi field search • Auto completion & spell checking • Drilling • Group and count • Allow to post filter • Alternatives • Re-use previous search input • Re-use previous marks as to propose alternative reference terms • Ranking • Consider multiple weighted fields in result ranking • Performance • Prioritize quick online response in taking feature decisions

  10. Linguistics • Canonization • Agree on rules of equivalency • To comprise capitalization, punctuation, diacritics • Segmentation • Frequent use of non authorized segmentators • Considerate risk of false positives • Morphology • Considerate impact • Needed in 22 languages • Compounding • Significant impact in “germanic” languages • Requires lexical resources • Language resources • Manage synonyms, partial synonyms • Manage functional phrases

  11. Example: Examination assistance

  12. Example: Alignment

  13. Example: Conceptualization

  14. Example: Broad/Narrow relation

  15. Example: Similarity relation • Nature • Purpose • Method of use • Complementary • In competition • Distribution channels • End user • Producer

  16. Conclusions • The more functional features are made available at front office the more efficient and consistent the proceeding at back office becomes • Functional features at large depend on resource maintenance • Full maintenance governance requires native speakers (terminologists) for all languages to be accommodated • Terminology alignment across organisations requires alignment on matching algorithms alike • Linguistic measures taken are domain as well as context of use dependent • Language resources, though, may be shared

More Related