[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [cti-users] [cti-stix] [cti-users] MTI Binding
To add my .02 on Semantic models and RDF – Fundamentally, I like it, it could really allow for some powerful analysis when it comes to turning the data into knowledge,
but wow – the change is SO severe vs what we have now in Stix 1.x. Feels like most implementations (tools) would be starting from scratch. If there is ever a time to do that, it is now, but I fear that the time that all of us would lose would (a year or
more) would put us too far behind competitive formats/standards… and that’s if we can all pull it off (appears to be pretty complex from an implementation perspective). From: cti-users@lists.oasis-open.org [mailto:cti-users@lists.oasis-open.org]
On Behalf Of Jacobsen, Jasen W. It would also be useful to see the UML models and/or semantic models used. Abstract->representation->instance. There are some advocating the use of fairly advanced/sophisticated/complex
modeling tools and then generating everything else algorithmically. A bite size example may help those who are not steeped in the practice of that craft and tools. I believe many here are not professional ontologists and data modelers. - Jasen. From:
<cti-users@lists.oasis-open.org> on behalf of Terry MacDonald <terry.macdonald@threatloop.com> +1. Is a nice idea as we can see a size and complexity comparison. Is there any chance each person can document the process that the generation took? I'm thinking it could be useful
to see how complicated the toolchain for developing each type of output is. Cheers > On 3 Oct 2015 6:33 am, "Jordan, Bret" <bret.jordan@bluecoat.com> wrote: DTCC DISCLAIMER: This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error, please notify us immediately and delete the email and any attachments from your system. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]