Predicate Proposal - Behance URL

Field Name: Behance URL

Value statement:
The Behance community of over 24 million creatives around the world (proof). Many designers, creatives, and studios have a profile on Behance. That’s where they post their work. This is a very large piece of usefull information. For example, a company is looking for a design creator on Golden. From Golden’s entity page, they could go straight to Behance and see examples of work.

Definition: Behance is popular with designers and illustrators around the world, the social media platform. Many designers, creatives, and studios have a profile on Behance. That’s where they post their work. Behance profile can be owned by both an individual person or a company.

Tooltip definition of the predicate: The Behance URL associated with this entity.

Type of value:

  • “url”

# of accepted values:

  • “single”

Constraints: Should only be applied to:
Company, Organization, Person.

Citation Required?: no

If the field has a limited # of values (enum field), list all possible values: only one value

Also known as: Bēhance

Examples of proper use:

  • Tractorbeam [Company] → Behance URL → Behance
  • Anna Dunn [Person] → Behance URL → Behance

Examples of improper use:

  • Tractorbeam [Company] → Behance URL → Behance // The link leads to a work example, not a profile
  • Anna Dunn [Person] → Behance URL → Behance // The link leads to a appreciated, not a profile

Usage in other schemas: N/A

1 Like

Great proposal! Looks good to me, and nice examples of improper use.

1 Like

Behance URL predicate vote

  • Yes, implement this predicate
  • No - do not implement

0 voters

Based on the voting above, the predicate definition above has been approved. It will be added as a web3 predicate in Golden soon!

This thread will now be closed and tagged appropriately.

1 Like