This would kill a lot of birds with one stone. Proposal: a pair of properties associated with assets. One would only be settable by the creator, the other by the creator or owner. The properties would be viewable by the client in-world or in inventory (in the properties dialog), and (if practical) by script as well. All assets would have these properties: textures, skins, scripts, notecards, gestures, objects... think of it as the 'mattress tag' or 'back of the picture'... The content of the field would either be a moderate sized free-form text field, or a UUID referring to a notecard. In the latter case the user interface to set it would probably involve dragging the notecard to the object's properties dialog. The creator information for an asset would be presented to the user when they accept the asset from another user. If the asset contains references to other assets containing creator information (eg, an object's inventory contents, or a notecard's contents, or a gesture's sounds and animations) that should be presented as well. The user interface should not be so obtrusive as to allow it to be used for griefing, but the recipient must be aware that they're receiving assets that may be subject to license terms they should know about. The owner information for the asset would contain any information that the owner wants to add, including notes and (if the information is readable by a script) configuration information. Typical creator information might be: "Copyright (c) 2007 Agent Stonecutter, All Rights Reserved. This script is distributed under the modified BSD license." Or: "Copyright (c) 2005 Texture Insanity, see http://textureinsanity.example.com/ for more information." Typical owner information might be: "listen 10; label 'Sit here'" Possible LSL APIs. Two new LSL constants: NOTICE_CREATOR and NOTICE_OWNER. For a text field associated directly with an object: string llGetNotice(integer type); For a notecard: key llGetNoticeUUID(integer type); In this case actually reading the notice would be done using the dataserver. PS: JIRA needs a 'Components' field value for 'Inventory'.