As schema.org grows, generic names for types and properties leads to unfortunate collisions. The issue will become more problematic when extensions are made a part of the flat namespace.

I am opening this issue as a place to gather ideas for types and properties which should be considered for renaming:

Types

• Series
• Season
• Seat
• Taxi
• Joint
• Vessel
• Artery
• Diet
• Code
• AlignmentObject
• Audience
• Permit
• Ticket

Properties

• affectedBy
• algorithm
• alignmentType
• antagonist
• application
• area
• aspect
• assembly
• audience
• background
• benefits
• branch
• branchOf
• carrier
• catalog
• code
• collection
• configuration
• comment
• cost
• course
• damages
• device
• diet
• doors
• engine
• episode
• event
• followup
• free
• frequency
• function
• functionalClass
• gears
• guideline
• incentives
• indication
• instrument
• intensity
• material
• menu
• object
• option
• origin
• outcome
• overview
• phase
• playerType
• population
• position
• preparation
• procedure
• producer
• produces
• purpose
• requirements
• responsibilities
• result
• risks
• season
• significance
• skills
• source
• specialty
• stage
• status
• study
• subtype
• surface
• target
• temporal
• text
• timezone
• title
• transmission
• tributary
• workLoad