document artifact definition naming convention

[pidydx]

I have noticed there is a lot of variance between the names and labels for similar things. What is the best way to align all of these things?

[joachimmetz]

I'm working on cleaning up the current format #11. Let us know what can be improved and I'll try to see if I can improve the "standard" and the documenation.

[pidydx]

It is mostly things like how most of the OSX artifacts start with OSX, but the Linux ones rarely do. For labels I think just some description around what belongs under each label. Should OSXLaunchDaemons be System because of the system wide ones, or should it be User because of the user ones, or both, or something else? That kind of thing.

[joachimmetz]

Ack I'll add something to to style guide to make that more consistent and clean that up a bit afterwards.

[joachimmetz]

Note to self update documentation to say:

• to keep the name space unique, prefix name of platform specific artifacts with the platform name
• update documentation
• update definitions
  • instead of BrowserHistory use BrowserHistoryFiles

[joachimmetz]

Removing support for labels #463 does not appear to be used outside the stats script.

[joachimmetz]

First stab at a definition naming convention https://artifacts.readthedocs.io/en/latest/sources/Format-specification.html#name