Re: Yet another monthly platform email

--===============0851912571==
Content-Type: multipart/signed; boundary="nextPart3612634.5Pvcgg5CeA";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3612634.5Pvcgg5CeA
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 16 March 2005 13:23, Chris Lee wrote:
> I'd be willing to suggest that for the first release of the platform, we
> don't even include any software at all and just go with the
> standards/specs that everyone's using.
>
> For inclusion, specs I'd suggest:
> desktop-file
> basedir
> menu
> mime
> <snip>

This sounds sane to me.  With that in mind, are there any issues people hav=
e=20
with these specs as they currently stand?  I'm thinking here only of cases=
=20
where the spec is ambiguous, and either some existing current practice shou=
ld=20
either be codified, or else explicitly mark that case as undefined.  In=20
particular I'm not suggesting major additions.

=2D ajax=20

--nextPart3612634.5Pvcgg5CeA
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCUbCGW4otUKDs0NMRAkSBAKC24Qpm/ZG05PjiFV2OuN9++uM2aQCeLLlS
BV6o4wvHGK0iemIcpmSgQ6E=
=q8RP
-----END PGP SIGNATURE-----

--nextPart3612634.5Pvcgg5CeA--

--===============0851912571==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
platform mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/platform

--===============0851912571==--