The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The format of manifests (package.xml) is documented in REP-127 ('format 1') and REP-140 ('format 2'). In neither do the author or license element define additional attributes like the ones you show in your example (neither REP includes any text that expressly forbids additional attributes though).
Typically, source files for nodes include both a license header and something like an @author .. line in the comment block at the top. This would allow you to express the same information, although it would not be visible in the manifest, nor to any tools that parse the manifests.
| | 2 | No.2 Revision |
The format of manifests (package.xml) is documented in REP-127 ('format 1') and REP-140 ('format 2'). In neither do the author or license element define additional attributes like the ones you show in your example (neither REP includes any text that expressly forbids additional attributes though).
Typically, source files for nodes include both a license header and something like an @author .. line in the comment block at the top. This would allow you to express the same information, although it would not be visible in the manifest, nor to any tools that parse the manifests.
PS: it is perfectly possible for a package to have multiple license elements (documented here for format 2 fi), so having files in a package that fall under different licenses is also possible. Again, the file header would contain that information.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
