A.J. Brown

Just as a note, it appears the field name difference is handled during (de)serialization by the 2 libraries I checked (Go, Java) so it seems there are no portability issues...

Hi @bjones6. That's certainly a risk you take by doing things on the client side. The other risk is that your logging endpoint is exposed as well, so it can...

@jaketodaro This is something on my scratchpad for 1.0. I'll make this the official story for it :-) Thanks!

This can be implemented now simply by generating the session identifier, storing it in the session storage, and adding it as a field using `LogglyLoggerProvider.setExtra( { session: sessionId' } )`...

This is starting to seem like it's out of scope for this project. It might be more suitable for some sort of plugin system.

Re-opening this as part of the 1.0.0 rewrite, which will include middleware.

I noticed there's another pull request for this change open as well. Any chance one of them can get pulled in?

Hi Steve! It does in fact seem that the XSD allows nested dependency objects https://github.com/CycloneDX/specification/blob/c3da323e637e4fbe770126ce3359faa9770f8743/schema/bom-1.4.xsd#L1187-L1202 ```xsd References a component or service by the its bom-ref attribute User-defined attributes may be...

> I think both are true. As in, it should be either a string OR an object? I believe at the moment there are portability issues between Java and JavaScript....

Have you considered using [bintray](https://bintray.com/)/[jcenter](https://jcenter.bintray.com/) for distribution?