DOAP Dependencies
an extension to DOAP for describing a project's requirements
2013-07-30
2013-07-30
2013-07-31
2013-07-31
Toby Inkster
Karsten Schmidt
e66da09c6f6f75f0d512266706ece1647279a52e
Dependency
A condition to be met
Historic Dependency
the range of this property is a little woolly; a doap:Project is certainly fine, as is a literal which acts as an identifier, provided it's qualified with a datatype indicating what scheme it's an identifier in
on
since
until
CPAN Identifier
A module name, optionally followed by a space character and a version.
Examples: `Moose::Role` or `Moose::Role 2.0600`
Debian Package Identifier
Note that architecture-specific modifiers (in square brackets) are not supported yet.
Examples: `libmoose-perl` or `libmoose-perl (>= 2.0600-1)`
RPM Package Identifier
Examples: `perl-Moose` or `perl-Moose >= 2.0600-1`
Pip Identifier
A single line from a requirements.txt file, minus the line break.
Example: `html5lib==0.95`
Gem Identifier
A module name, optionally followed by one or more operator, version number pairs.
Examples: `log4r` or `log4r >= 1.0.5` or `log4r >= 1.0.5, < 2.0.0`
Maven Identifier
A fully qualified Maven artefact name: 'groupID/artefactID version[-classifier]'
Example 'org.clojure/clojure 1.5.1-SNAPSHOT'
configure requirement
configure recommendation
configure suggestion
build requirement
build recommendation
build suggestion
test requirement
test recommendation
test suggestion
runtime requirement
runtime recommendation
runtime suggestion
development requirement
development recommendation
development suggestion