OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

cti-cybox message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [cti-cybox] Email Object


Obviously failed to execute on my intended objective to get some insights on this question from Ivan.  

From our perspective, we expect to be data mining, ingesting, and distributing CTI to/from many sources, and destination, in many formats, for the forseeable future.  Homogenization of taxonomies, at least to the extent of adopting the same terms for the same constructs, greatly eases many challenges.  

Getting everyone to call a "Rose" a "Rose" when describing/correlating data/metadata about Rosaceae (not to be confused with Rosacea), greatly aids in these endeavors.  

A great many things in our domain are based on RFCs, therefore the argument for adoption wherever practical.

Patrick Maroney
President
Integrated Networking Technologies, Inc.
Desk: (856)983-0001
Cell: (609)841-5104
Email: pmaroney@specere.org


From: Patrick Maroney
Sent: Thursday, September 22, 2016 5:11:38 AM
To: cti-cybox@lists.oasis-open.org; Kirillov, Ivan A.
Subject: Re: [cti-cybox] Email Object
 
Ivan,

[Offlist] -  Do you support or oppose adoption of this proposed tenet: 

Adopt RFC names/labels for related CTI TC content wherever practical.

If you don't support, can you share the basis for not adopting them (in a paragraph)?  I recall discussing this very topic at various points historically, but dont recall the outcomes.

Patrick Maroney
President
Integrated Networking Technologies, Inc.
Desk: (856)983-0001
Cell: (609)841-5104
Email: pmaroney@specere.org


From: cti-cybox@lists.oasis-open.org <cti-cybox@lists.oasis-open.org> on behalf of Patrick Maroney <Pmaroney@Specere.org>
Sent: Tuesday, September 20, 2016 7:27:46 AM
To: Kirillov, Ivan A.; cti-cybox@lists.oasis-open.org
Subject: Re: [cti-cybox] Email Object
 

If this is a well whipped horse of the deceased variety (or parrot*), just say “wwhotdv”.  No need to elaborate.

 

(1)     General Comment: Suggest using RFC taxonomies/spelling wherever possible/practical.  This would greatly ease parsing and production/consumption transform processes.

(2)     Specific Comment:  Suggest RFC  5322 “display-name” instead of “display_name”.

 

 

“'E's not pinin'! 'E's passed on! This parrot is no more! He has ceased to be! 'E's expired and gone to meet 'is maker! 'E's a stiff! Bereft of life, 'e rests in peace! If you hadn't nailed 'im to the perch 'e'd be pushing up the daisies! 'Is metabolic processes are now 'istory! 'E's off the twig! 'E's kicked the bucket, 'e's shuffled off 'is mortal coil, run down the curtain and joined the bleedin' choir invisible!! THIS IS AN EX-PARROT!!”

 

Pat

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]