search

TMContent / Lib_Docs

Creative Commons Zero v1.0 Universal
1 stars 2 forks source link

Add full CWE to TeamMentor #13

Open BendixSpring opened 11 years ago

BendixSpring commented 11 years ago

If you ever had to use the full CWE by loading the full dictionary view (http://cwe.mitre.org/data/slices/2000.html), it is very unwieldy and slow.

Even the Development and Research views are awkward.

But the content in the CWE is totally glorious.

If you really want to add value to TM, pull the all the CWE content in. (I believe it is in XML -- should be easy (!) to import.) Make it free, and it will bring people to TM.

tlaloc75 commented 11 years ago

Its not as easy as it looks :). We tried pulling it in and it was still pretty terrible. The CWE library you see in TM represents a lot of manual work by Serge to rewrite and organize the content. Pulling in more CWE content is a good idea for a future release, but it does represent some effort.

On Apr 18, 2013, at 9:07 AM, Danny Harris notifications@github.com wrote:

If you ever had to use the full CWE by loading the full dictionary view (http://cwe.mitre.org/data/slices/2000.html), it is very unwieldy and slow.

Even the Development and Research views are awkward.

But the content in the CWE is totally glorious.

If you really want to add value to TM, pull the all the CWE content in. (I believe it is in XML -- should be easy (!) to import.) Make it free, and it will bring people to TM.

— Reply to this email directly or view it on GitHub.

DinisCruz commented 11 years ago

I did once wrote a script to create a teammentor CWE library from the raw CWE XML file

I agree that we should push a TM CWE library as a way to expose TM to more users/clients

Dinis Cruz

On 18 Apr 2013, at 16:07, Danny Harris notifications@github.com wrote:

If you ever had to use the full CWE by loading the full dictionary view (http://cwe.mitre.org/data/slices/2000.html), it is very unwieldy and slow.

Even the Development and Research views are awkward.

But the content in the CWE is totally glorious.

If you really want to add value to TM, pull the all the CWE content in. (I believe it is in XML -- should be easy (!) to import.) Make it free, and it will bring people to TM.

— Reply to this email directly or view it on GitHub.

DinisCruz commented 11 years ago

Yap Serge's version looked better :)

Dinis Cruz

On 18 Apr 2013, at 16:57, tlaloc75 notifications@github.com wrote:

Its not as easy as it looks :). We tried pulling it in and it was still pretty terrible. The CWE library you see in TM represents a lot of manual work by Serge to rewrite and organize the content. Pulling in more CWE content is a good idea for a future release, but it does represent some effort.

On Apr 18, 2013, at 9:07 AM, Danny Harris notifications@github.com wrote:

If you ever had to use the full CWE by loading the full dictionary view (http://cwe.mitre.org/data/slices/2000.html), it is very unwieldy and slow.

Even the Development and Research views are awkward.

But the content in the CWE is totally glorious.

If you really want to add value to TM, pull the all the CWE content in. (I believe it is in XML -- should be easy (!) to import.) Make it free, and it will bring people to TM.

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub.

SergeTruth commented 11 years ago

It's a nice idea. From experience, I suspect that the CWE structure is actually deeply flawed somewhere, so if we organized it in a logical manner, it would no longer completely correspond to the original, and so no longer really be CWE. For example, there are CWE-xxx things that are just tiny stubs or are extremely vague - if we include them, it'll be harder to be organized and there will be low quality articles, if we don't include them, we just have a subset. Rewriting low quality articles also makes it no longer really CWE. Maybe we can do CWE++ or something.

BendixSpring commented 11 years ago

I’m not sure if it really is a problem to call it CWE or CWE++, but the current CWE page (http://cwe.mitre.org/data/slices/2000.html) that is loaded in a browser is so ponderous, it almost makes the browser crash.

We could call it a “CWE Fork”. But the content is what is so valuable, but currently so hard to use.

--Danny

From: SergeTruth [mailto:notifications@github.com] Sent: Tuesday, April 30, 2013 8:40 AM To: TMContent/Lib_Docs Cc: Danny Harris Subject: Re: [Lib_Docs] Add full CWE to TeamMentor (#13)

It's a nice idea. From experience, I suspect that the CWE structure is actually deeply flawed somewhere, so if we organized it in a logical manner, it would no longer completely correspond to the original, and so no longer really be CWE. For example, there are CWE-xxx things that are just tiny stubs or are extremely vague - if we include them, it'll be harder to be organized and there will be low quality articles, if we don't include them, we just have a subset. Rewriting low quality articles also makes it no longer really CWE. Maybe we can do CWE++ or something.

— Reply to this email directly or view it on GitHub https://github.com/TMContent/Lib_Docs/issues/13#issuecomment-17224523 . https://github.com/notifications/beacon/5F2_eRmNmMOSmJQY77zQB4zTDjApnVFUyesbBFgSaj_bcRdoa1X9vqBm5JcWp5eL.gif