[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [EXT] RE: [cti-users] OWL representation of STIX 2
Hi Ryan!
Can you explain a bit more about the problems you are seeing / running in to?
Bret From: cti-users@lists.oasis-open.org <cti-users@lists.oasis-open.org> on behalf of Ryan Hohimer <rhohimer@champtc.com>
Sent: Thursday, October 5, 2017 6:00:28 PM To: Paul Patrick Cc: cti-users@lists.oasis-open.org Subject: [EXT] RE: [cti-users] OWL representation of STIX 2 I would very much like to talk with you about your experiences. As I mentioned, I’m authoring a STIX 2 owl representation and have found multiple points where I may be making decisions that we
may regret later. For instance, I am twisted around the axle about how to represent observables. These have been first order objects in my previous modeling. Not modeling an Observable class seems problematic at
best. Additionally, I’d like to represent the relationships to other cyber classifications, enumerations, dictionaries, and non-cyber domain models in a smart fashion. Thanks, Ryan E. Hohimer This e-mail (including any attachments) may contain information that is private, confidential,
or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail so our records can be corrected.
From: Paul Patrick [mailto:Paul.Patrick@FireEye.com] Ryan, We’ve been using OWL since before STIX 1 came out and have modeled STIX 1, CybOX, and MAEC 4.1. We’ve more recently updated our OWL model to be able to support STIX 2 as well as the MAEC 5 efforts as well. We’d be happy to talk with you about our experiences. Paul Patrick Chief Architect, Global Services and Intelligence FireEye Corp.
This email and any attachments thereto may contain private, confidential, and/or privileged material for the sole use of the intended recipient. Any review, copying, or distribution of this email (or any attachments thereto) by others is
strictly prohibited. If you are not the intended recipient, please contact the sender immediately and permanently delete the original and any copies of this email and any attachments thereto.
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]