Intellectual Property Forum The Intellectual Property Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

We are looking for moderators.  Message the admin if interested.

Author Topic: Change goods/services class to avoid likelihood?  (Read 268 times)

gabriel_dcv

  • Newbie
  • *
  • Posts: 3
    • View Profile
    • Email
Change goods/services class to avoid likelihood?
« on: 12-20-17 at 12:20 pm »

My brand was refused because of likelihood of confusion. My idea is register again in same class but narrowing the list of product/services.

- The brand registered has this:
IC 012. US 019 021 023 031 035 044. G & S: Vehicles, in particular electric vehicles, namely, electric cars, electric motorcycles, electric trucks, electric buses, electric drives for vehicles, electric motors for motor cars, and structural parts therefor

- And my idea is that mine has: IC 012. US 019 021 023 031 035 044. G & S: Electric bike.

Is it possible?
« Last Edit: 12-20-17 at 02:15 pm by gabriel_dcv »
Logged

markatescil

  • Newbie
  • *
  • Posts: 1
    • View Profile
    • Email
Re: Change goods/services class to avoid likelihood?
« Reply #1 on: 01-10-18 at 10:11 am »

No, in your situation class narrowing wont help. Because electric bike is under the subclass of vehicle goods. You have only two options. You can request from prior trademark owner, partial transfer about vehicle subclass or limitation from vehicle goods. Sure firstly you should convince her/his/them about this 
Logged
tmindeks trademark applications and registrations turkey

gabriel_dcv

  • Newbie
  • *
  • Posts: 3
    • View Profile
    • Email
Re: Change goods/services class to avoid likelihood?
« Reply #2 on: 01-10-18 at 11:38 pm »

Hi friend, thanks you! What do you mean with "transfer about vehicule subclass"? I don't got it...
Logged
 



Footer

www.intelproplaw.com

Terms of Use
Feel free to contact us:
Sorry, spam is killing us.

iKnight Technologies Inc.

www.intelproplaw.com

Page created in 0.128 seconds with 20 queries.