SWID-Generator should provide Tag-ID output

[dbrgn]

Tag-ID consists of regid_uniqueID.

[d22]

Added an inital implementation of tagid output, also argument subparsers to switch between swid and tagid output.

I'm not sure if this solution is good, I don't like how the command is invoked regarding common options and options for subcomands:

• Invoke python main.py --regid regid.2000-03.asdf tagid to get tagid output with a custom regid
• python main.py tagid --regid regid.2000-03.asdfdoes not work, because --regid is a common option

I' didn't add any new tests atm, I just modified the current tests to work with the new setup. I will add tests when we decided how we will proceed.

@cfaessler and @dbrgn, what do you think?

[d22]

BTW. In the new standard, the tagid ist called "software_id" (page 13 in the ISO standard pdf). I couldn't find any reference for the fact, that the tagid/software_id, uniqueid or regid shall not contain underscores. It is clearly allowed to user underscores in the regid, as every space should be replaced with an underscore character. There are no exact rules for the uniqueid (except, it must be a vaild XML attribute), as the uniqueid can contain the regid, the uniqueid must allow underscores. TLDR: We cannot parse the software_id.

[cfaessler]

A not parsable software_id is indeed big problem in the backend. Maybe we could enforce "no-whitespace/underscore" in the regid/uniqueid

Or are we shure that there is a use case for parsing/saving software_id's? Use case could be as follows:

• strongTNC tells IMC to get software_id's
• IMC does a software_id dump and sends it to strongTNC
• strongTNC gets software_id's and tries to map them to existing (full) swid records in the database. If none is found, it tells IMC to get SWID Tag (targeted request)
• IMC does targeted request and sends back full swid
• strongTNC now saves full tag and can do mapping (in future requests)

[d22]

See #84 and #85