'$RCSfile: eml-softwarePackage.xsd,v $' Copyright: 2000 Regents of the University of California and the National Center for Ecological Analysis and Synthesis For Details: http://knb.ecoinformatics.org/ '$Author: berkley $' '$Date: 2002/04/21 22:45:30 $' '$Revision: 1.6 $' This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA eml-software The eml-softwarePackage module contains general information that describes software resources. Action Describes what action needs to be undertaken (if any) for a software dependency at either the software package or implementation level. This element and its enumerations of assert and install can be used as commands by a software application to carry out these actions on software package dependencies. This is a change from how we have used all previous elements within eml. Up until now all other elements have been simply metadata designed to describe data, literature citations, etc... with the Action element we can use this module as a command to carry out the action. The Action Element was introduced in 2.0.0 beta 9. Dependency Dependency describes the software package(s) that the software package is dependent upon. The dependency element is recursive. It is a sub-element of the SoftwarePackage Element but it also has as a sub-element its parent element Software Package. Dependecy has been made optional because to make it mandatory does not allow the recursion to end. Dependency has also been made a sub-element of implementation because there can be both implementation and package level dependencies within a package. The implementation Element was introduced in 2.0.0 beta 9. Software Package Defines a software distribution and all of its dependent software. The 'softwarePackage' element contains general information about a software resource that is being documented. This field is intended to give information for software tools that are needed to interpret a dataset, software that was written to process a resource, or software as a resource in itself. It is based on eml-resource and Open Software Description (OSD) a W3C submission. There can be multiple implementations within a software package because a physical software package can run on multiple hardware and/or operating systems. See implementation element documentation for a more thorough explanation. Please see the examples for each subelement of the 'softwarePackage' type. The softwarePackage Element was introduced in 2.0.0 beta 9. It replaces the software element. The 'software' element was introduced into EML 2.0, however it was derived from the eml-software module in EML 1.4. Implementation Describes the hardware and/or operating system requirementsfor one implementation of a package. Implementation describes the hardware, operating system resources a package runs on. Note, a package can have multiple implementations. So for example, a package may be written in java and the package may run on numerous hardware and/or operating systems like Pentium/Linux, Pentium/NT and so on... Hardware and Software descriptions that have different requirements can be placed here. Please see the examples for each subelement of the 'implementation' type. The implementation Element was introduced in 2.0.0 beta 9. Distribution Currently under construction in resource module. work in progress filename.jar Size Physical size of an implemetation in Kilo, Mega .... bytes. 100 Megabytes International Language The International Language of the software implementation Language Value The actual value for the language or code The value could be just a text string like english or french or it could be an International Language code like ISO 639-2. 'english' or 'en' Language Code Standard The International Language Code being used See www.loc.gov/standards/iso639-2/ 'que' for Quechua, 'eng' for English and so on... Operating System Operating System(s) an implementation runs on see summary Windows 95, Window NT, Windows XP, Sun Solaris 2.8 Machine Processor The Machine Processor required for implementation see summary Pentium II, Intel 486, SUN Sparc Virtual Machine Virtual Machine implementation requires see summary Java Virtual Machne 1.2 Disk Usage The minimum amount of Disk Space required to install an lmplementation in Kilo, Mega bytes etc... see summary 220 Megabytes Runtime Memory Usage The minimum amount of memory required to run an lmplementation in Kilo, Mega b ytes etc... see summary 32 Megabytes Programming Language The Computer Programming Language the Software Package was programmed in. see summary C++, Java, C, C#, Perl, Cobol, Fortran, Lisp, Visual Basic, VBA, Bourne Shell Script etc.... Checksum The generated checksum value of a software package that is a self-contained module. see summary $sum software.jar 27021 22660 Dependency Dependency describes the software packages that the software package is dependent upon. The dependency element is recursive. It is a sub-element of the SoftwarePackage Element but it also has as a sub-element its parent element Software Package. Dependecy has been made optional because to make it mandatory does not allow the recursion to end. Dependency has also been made a sub-element of implementation because there can be both implementation and package level dependencies within a package. The implementation Element was introduced in 2.0.0 beta 9. Version of the software being packaged. String value corresponding to the major, minor, custom, and build version. The Version element was introduced in 2.0.0 beta 9.