[Owasp-data-exchange-format] DEF objects

[Dan Cornell]

Yeah I like Google Docs for the collaborative editing capability.  That has been really helpful in a couple of distributed projects I've worked on lately.

And I'm not smart enough to figure out the wiki formatting markup...  :)

Thanks,

Dan


From: Ferruh Mavituna [mailto:ferruh at mavituna.com]
Sent: Thursday, July 28, 2011 6:12 PM
To: psiinon
Cc: dinis cruz; owasp-data-exchange-format at lists.owasp.org; Dan Cornell
Subject: Re: [Owasp-data-exchange-format] DEF objects

2

Google Docs

On 28 July 2011 11:00, psiinon <psiinon at gmail.com<mailto:psiinon at gmail.com>> wrote:
I like the simplicity of a wiki, but I'm happy to use whatever most people feel comfortable with.
And we will definitely need an XSD + examples (assuming we go down the XML route).

So .. if you want to work on the draft then cast your vote on this list:

1. keep using the wiki for now
2. use Google Docs
3. another option - please specify

And feel free to comment on the structures currently on the wiki, either on the wiki itself or on this list.

Cheers,

Simon

On Thu, Jul 28, 2011 at 12:32 AM, Ferruh Mavituna <ferruh at mavituna.com<mailto:ferruh at mavituna.com>> wrote:
I agree on working on a draft document / definition first, then translate into an XSD and the way Dan did it is really great.

I think you should create that page with a concrete example/discussion document like Dan's example in Google Docs. Google Docs seems like the perfect place to design it, it has revision support, real time chat, discussion and a beautiful real-time editor. Can't get any better than that :)

Depending on how you want to resume, I'll try to contribute that way directly from Google Code or Google Docs or just doing the suggestions over here and leaving the final implementation/decision to you guys.

Cheers,

On 27 July 2011 11:07, psiinon <psiinon at gmail.com<mailto:psiinon at gmail.com>> wrote:
I was trying to avoid working directly on an XSD so that we thought about content rather than formats initially.
And in theory we could still go with another format (like JSON).
Once we agree on the content then we would definitely need to make it concrete.

Cheers,

Simon

On Wed, Jul 27, 2011 at 2:46 PM, dinis cruz <dinis.cruz at owasp.org<mailto:dinis.cruz at owasp.org>> wrote:
Is there a way that we can do this directly on an XSD?

I.e. create this pages from the XSD.

Simon, can you use O2?

Dinis Cruz
On 27 July 2011 13:16, psiinon <psiinon at gmail.com<mailto:psiinon at gmail.com>> wrote:
I've started to define the objects DEF will work with: http://code.google.com/p/owasp-def/wiki/DefObjects

As the blurb on that page says:

"This section of the wiki contains a pseudo definition of the objects that DEF will apply to.

Note that this is WORK IN PROGRESS - this wiki is being used as a scratch-pad!

The element names, descriptions and order are all highly provisional and liable to change.

Feel free to update these pages as you think appropriate and/or argue your case on the mailing list."

Let me know if anything is unclear or if you need write access to the wiki.
Cheers,

Simon
_______________________________________________
Owasp-data-exchange-format mailing list
Owasp-data-exchange-format at lists.owasp.org<mailto:Owasp-data-exchange-format at lists.owasp.org>
https://lists.owasp.org/mailman/listinfo/owasp-data-exchange-format



_______________________________________________
Owasp-data-exchange-format mailing list
Owasp-data-exchange-format at lists.owasp.org<mailto:Owasp-data-exchange-format at lists.owasp.org>
https://lists.owasp.org/mailman/listinfo/owasp-data-exchange-format


--
.fm




--
.fm
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://lists.owasp.org/pipermail/owasp-data-exchange-format/attachments/20110728/fcb7b81c/attachment-0001.html