Comments on draft 16 if its not too late in the process. None of these are a big deal, but here it goes.
4.2.9. The "metalink:logo" Element Add an option to base64 encode the logo file. This allows for embedding the logo in the metalink file itself. Reference RFC 2397. This is already well established as it is part of HTML 4.01. 4.2.12. The "metalink:os" Element Is there a use case for this? I'd say if no one plans to use this just take it out. This is where the extensibleness of XML can be used if something better comes along later. Is the current list of OSes/versions sufficient? The IANA list seems lacking, especially when it comes to specific versions. A good example is if I want to download a Linux package that has multiple formats in the metalink file, there is no way for your metalink client to differentiate between a .deb for Ubuntu/Debian and a .rpm for Fedora/RHEL/CentOS. http://www.iana.org/assignments/operating-system-names At the very least a <file> should be able to include multiple OS values instead of the current single value. An example for this is a single Windows .exe that will run on multiple Windows versions. How do ed2k/magnet links fit in? Are they a metaurl or url? If they are a metaurl what are the mime types? And I'm assuming that for the metalinkhttp implementation these will directly map, metaurl=>describedby, url=>duplicate. Neil --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Metalink Discussion" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/metalink-discussion?hl=en -~----------~----~----~----~------~----~------~--~---
