Shawn Walker wrote:
> Joe Di Pol wrote:
> . . .
>> 2) Is there a reason these are scoped to "com.sun.service"? Why not:
>>
>> info.info_url, info.keywords, info.incorporated_changes
>>
>> (I think there was a proposal to use "info" for general optional metadata)
>
> Yes, because it is likely that those will be specific to Sun or
> OpenSolaris. For example, keywords will likely be limited to a
> pre-defined list by Sun. incorporated_changes is likely to refer to
> Sun's bug-tracking system, etc. At least, that's my understanding...
The keyword example from PSARC/2008/190 looks pretty free-form to me
("sort null -n -m -t sort 0x86 separator"). I could see some conventions
for its use, but I wonder if it would really be restricted to a set list.
So I still think the following is worth considering:
info.info_url: URL to additional information, may be txt, html, xml
info.keywords: List of keywords with some established conventions
info.change_db: URL to issue database for product
info.incorporated_changes: Issue IDs relative to change_db
If a package publisher has some specific structured data,
then they can still add publisher specific attributes.
Joe
_______________________________________________
pkg-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
