Skip to content

Should add common pitfalls to some of the concepts pages and suggested practices #154

Open

Description

@johnwunder

E.g.

  • Data markings
  • Instances vs. patterns
  • ID namespaces (using example rather than a producer prefix)

Activity

  1. taraxvoid commented on Nov 19, 2014

    @taraxvoid

    Does the page not cover them sufficiently?

  2. johnwunder commented on Jun 30, 2015

    @johnwunder
    MemberAuthor

    New idea: maybe we need a "top 10 mistakes in using STIX" page? Or "12 ways to get the most out of your threat intelligence in STIX"? Basically some succinct way of addressing the most common problems we see.

    Obviously this is a stop-gap until the language can be redesigned to help people avoid them more naturally.

  3. taraxvoid commented on Jun 30, 2015

    @taraxvoid

    Hmm, if there's serious concerns from a bunch of varied user demographics, suggest doing a user-feedback sprint with a small set of enthusiastic users and focusing on changing the things that are most do-able and widest impact.

    Having a 'top 10 mistakes' seems backtrack-y and unreasonable - like I wouldn't expect Chrome devs to have a writeup for "top 5 reasons why you're using tabs wrong" , they would instead make UI changes based on objective user feedback and A|B trials

    relevant

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions