[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] Why xml for the manifest file ?
- From: Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 17 Jul 2009 08:21:38 -0400
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=W8x8sy+lW5ocQfaRmD1C+DxWfcY3CRTJOWqvLgs07Xf8XfQjEdEwUMZZdW2pJxh/gT 95D8zJLGoT9lZSwTONMdQYMjRwEol2jpMSBpAfUgtwPKeZ7GJjbfzbygoMxzS7AawZjo Q3AZVes/PV7S4EAqM8zESXM2RZHRV/bx02R7s=
If you want your question answered, you will need to subscribe to the
list (or check it regularly,
I've copied your email on this response so you are aware of the
etiquette for using this kind of list.
On Fri, Jul 17, 2009 at 8:10 AM, Sankar P<sankar.curiosity@xxxxxxxxx> wrote:
> reason that I could think of is, to check for mandatory elements (like
> say plugin-id) which can be easily compared by checking against a
> schema etc.
> So, can someone explain me why XML is chosen and how it is beneficial
> over a simple text file ?
You've hit one of the largest reasons, schema. It allows definitions
and complex data types for each extension point to be published. Now
you can 1) generate documentation, 2) hand craft the XML necessary, 3)
provide *extensive* tooling to help building the files. #3 is really
There are a number of other good reasons.
Hi floor. Make me a sammich! - GIR