Talk:Bundle metadata
Contents
January 2008 metadata proposal discussion
"why not just use rpm?"
Some people have suggested that if any fields are to be added to the current .info file spec, we may as well give up the idea of a simple set of metadata and switch from using .xo/l bundles to using rpms. The latest proposal aims to retain simplicity while capturing information from bundle creators that can easily be gathered and that will be important to those sharing or reusing the bundle later on.
why are any other files required?
Proper attribution and license compliance require a good acknowledgements and copyright accounting. A "Copyrights" file which would not make sense for all bundles, so an "acknowledgements" file is suggested; however either would work for the majority of cases.
A changelog is important in tracking versions and supporting future merging between files and bundles that have been updated during a separation. This is especially important in an environment with spotty network connectivity.
More on this: We don't want to overburden bundle creators with a lot of metadata to maintain. We also want to allow institutions like libraries, NGO's, and universities to add metadata to their collective heart's content. For that reason we have created the optional bib_info file that allows for the library standard Dublin Core format. -- Bryan Berry
Faceted tags
A librarian in Indian, many years ago developed a system to classify books, called Faceted Classification. It's quite simple, you have various facets, each corresponds to a way to look at the object, and each facet can be assigned with one tag, since all its tags are mutually-exclusive.
Debtags is an implementation of the system to tag packages in the Debian repositories. Debtags homepage contains further explanation and background to this system. For the long-term ideal of a world-wide library, a system like this could replace the mix of typical categorization plus simple tags.
An example of the system at work.
