Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

User terms: brainstorm on tasks and scope:

  • User Terms name

    • "allowable uses"
    • "user submitted terms"
    • "terms of engagement"
    • "term negotiation"
    • Testing with user groups? marketing? who is our target?
    • potential for user terms to specify the kind of consent receipt they want?

  • UX / Product
    • work with end-users to determine means, understand and product market fit
    • work with parties who might offer user terms or receive user terms and respond
    • develop human readable language for each term name, definition
    • develop human meaning and pathways for choosing, reviewing and changing a term choice from MVP
    • Design beginnings: http://customercommons.org/2014/10/27/customer-commons-and-user-submitted-terms/
  • Legal scope:
    • legal descriptions for each term
    • name and definition for each term
    • legal language for contract if terms offered and accepted

  • Engineering scope:
    • develop MVP scope for eng
    • machine readable description of each term
    • expression for names and definitions of terms
    • code or expression for sending and receiving a short list of terms
    • code for responding to a term request


  • No labels