Ticket #4 (new enhancement)
Opened 6 months ago
Some schema updates
| Reported by: | http://antenore.blogspot.com/ | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Component: | component1 |
| Version: | Keywords: | ||
| Cc: | antenore@… |
Description
Hi all,
I'd like to use DOAP for some projects that (unlucky) are not open source.
These Project are not developed by me, but by other developer/companies that work for my customer and the customer want them released with a closed source license...
For these reasons the DOAP's schema is not the best solution (I think), as it has some attributes that they don't make too much sense for closed source projects.
For example attributes like maintainer, developer, helper they don't make sense in such projects.
Another small issue is the license, it would be fine to have also an attribute value like "others" (but for this maybe I'm wrong).
Well, I know that DOAP has been implemented with OSS development in mind, but IMHO would be great to support also any other kind of projects style. A DOAP schema more generic and adaptable could boost up the use of it.
Would it be possible to rethink it? Or do you have any interesting ideas?
Thanks a lot
Regards Antenore
