Proposal: AI Assisted mark
Chưa có ai nhận issue này.
Đánh giá
- Độ khó
- 5/5
- Thời gian dự kiến
- Hơn một tuần
- Mức phù hợp với người mới
- 20/100
- Loại issue
- Tính năng
- Độ rõ ràng
- Cần làm rõ
- Mức độ hoạt động
- Đình trệ
- Công nghệ
- machine-learning
- Lĩnh vực
- design
Hướng nghiên cứu
Không có tệp, bài kiểm thử hoặc điểm bắt đầu triển khai nào được đề cập. Hãy bắt đầu bằng việc xem xét các phương án thiết kế của đề xuất và hoạt động tham vấn cộng đồng được đề xuất; công việc chỉ hoàn tất khi thuật ngữ, dấu hiệu trực quan, ngưỡng sử dụng và các hướng dẫn đã được thống nhất.
Do mô hình lập chỉ mục viết ra từ nội dung của issue.
Mô tả
Problem
There is currently no widely recognized, standardized method for creators to clearly indicate that their work has been created with significant assistance from Large Language Models (LLMs) or other generative AI. This lack of transparency can be problematic for several reasons:
- For consumers/users: It's difficult to know the origin and nature of the content they are engaging with, which can be important for context, trust, and understanding potential biases or limitations.
- For creators: There's no simple, established way to be transparent about their use of AI tools, which many creators wish to do.
- For the commons: As AI-assisted content becomes more prevalent, clear attribution and understanding of provenance are crucial for maintaining a healthy and trustworthy information ecosystem. Without a standard, a proliferation of inconsistent or unclear disclosure methods may arise.
Description
This proposal is for Creative Commons to develop and introduce a new visual mark, tentatively named "LLM Powered" (or a similar denomination like "AI Assisted"), to specifically designate works created with substantial assistance from Large Language Models.
This feature would solve the problem by:
- Providing a Clear Standard: Offering a simple, universally recognizable visual symbol that creators can use alongside existing CC licenses to signify LLM assistance.
- Promoting Transparency: Enabling creators to easily and clearly communicate the role of LLMs in their work, fostering honesty and trust with their audience.
- Leveraging CC's Ecosystem: Integrating this new mark into the trusted and globally recognized Creative Commons framework would facilitate rapid adoption and understanding.
- Harmonizing with Existing Practices: The design principles would ensure the mark is simple, visually compatible with existing CC logos, flexible, and informative.
Key aspects of the proposed mark:
- Design Inspiration: Concepts would be based on existing CC visual identity, potentially involving an extension of the CC circle logo (e.g., "CC-LLM"), an adjacent symbol (e.g., "CC + [AI Spark icon]"), or a stylized textual mark ("LLM Assisted"). The aim is for clear association with Creative Commons while being distinct enough to convey its specific meaning.
- Guiding Principles: The design would prioritize simplicity, clarity, visual integration with CC's brand, flexibility across media, informative neutrality, and longevity.
By establishing such a mark, Creative Commons can play a crucial role in standardizing how AI assistance is disclosed, benefiting both creators and users of creative works.
Alternatives
Several alternatives to a dedicated CC "LLM Powered" mark exist, but the proposed feature offers distinct advantages:
-
Solely Textual Disclaimers: Creators can (and some do) add text notes like "This text was generated with AI."
- Why the proposed feature is better: A visual mark is more immediate, language-agnostic at a glance, and can be standardized in placement and appearance alongside other CC license marks. It offers a more integrated and less ad-hoc solution.
-
Individual Platform/Creator Markers: Different platforms or individual creators might develop their own proprietary icons or labels for AI-assisted content.
- Why the proposed feature is better: This would lead to a fragmented and confusing landscape of different symbols. A CC-standardized mark provides universality, leverages CC's established trust and global reach, and ensures a consistent meaning.
-
No Specific Indication (Status Quo): Simply not indicating the use of LLMs.
- Why the proposed feature is better: This lacks transparency and can erode trust as AI-assisted content becomes more common. A dedicated mark actively promotes transparency.
Within the proposal for the "LLM Powered" mark itself, several design alternatives are suggested (e.g., "CC-LLM" extension, adjacent symbol, textual mark). This internal flexibility allows for community input and selection of the most effective visual representation, but all these design options fall under the single proposed feature of having a standardized CC mark for this purpose.
Additional context
- Relevance to CC's Mission: Introducing such a mark aligns with Creative Commons' mission to foster a more equitable, accessible, and innovative global commons by promoting clarity and understanding around new forms of creation.
- Growing Need: The rapid advancement and adoption of LLMs in content creation make this a timely and increasingly important issue to address.
- Community Engagement: It's recommended that CC engage in community consultation to refine the need, terminology (e.g., "Powered," "Assisted," "Co-created"), specific visual design, and clear guidelines for when and how the mark should be used (i.e., what constitutes "significant assistance").
- Examples of Use:
- On images/videos generated or significantly modified by an LLM.
- In the credits of texts, articles, or books co-written or assisted by an LLM.
- As metadata for code generated or assisted by an LLM.
- On musical compositions assisted by an LLM.
- Precedent: Creative Commons has a history of successfully introducing symbols that become global standards for communicating information about creative works.
The adoption of an "LLM Powered" mark by Creative Commons would be a proactive step towards navigating the evolving landscape of AI in creativity, reinforcing CC’s role as a leader in promoting transparency and ethical sharing.
Implementation
- I would be interested in implementing this feature.
- Ngôn ngữ chính
- HTML
- Star
- 187
- Fork
- 243
- Chỉ số merge pull request
- Không có pull request nào được merge trong 30 ngày
Chuẩn bị môi trường
- Không có Dockerfile hay tệp Docker Compose
- Không có mẫu pull request
- Đọc hướng dẫn đóng góp
Bắt đầu từ đâu
- Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
- Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
- Fork repository và làm thay đổi trên một nhánh.
- Mở pull request có tham chiếu số hiệu của issue.
Issue khác của creativecommons/creativecommons.org
-
💻 aspect: code 🚦 status: awaiting triage 🛠 goal: fix 🟨 priority: medium
Độ khó 1/5 Dưới một giờ Mức phù hợp với người mới 72/100
-
💻 aspect: code 🚧 status: blocked 🛠 goal: fix 🟨 priority: medium
Độ khó 5/5 Hơn một tuần Mức phù hợp với người mới 35/100
creativecommons/creativecommons.org#1424 · 4 bình luận ·
-
💻 aspect: code 🛠 goal: fix 🟨 priority: medium 🧹 status: ticket work required
Độ khó 4/5 3-5 ngày Mức phù hợp với người mới 45/100
creativecommons/creativecommons.org#1422 · 2 bình luận ·
-
✨ goal: improvement 💻 aspect: code 🟩 priority: low 🧹 status: ticket work required
Độ khó 4/5 3-5 ngày Mức phù hợp với người mới 45/100
-
[Feature] Unambiguously Grant a Copyright License to CC IconsCó thể làm lại được @diyananoory-cc đã nhận 422 ngày trước và không có pull request nào đang mở. Đang mở✨ goal: improvement 🏁 status: ready for work 🔒 staff only 🕹 aspect: interface 🟩 priority: low
creativecommons/creativecommons.org#1308 · 2 bình luận · 3 người được giao ·
Tất cả issue của creativecommons/creativecommons.org
Issue tương tự
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 82/100
Maintainer thường phản hồi trong vòng 1 ngày
-
B10 - Frame: identityĐang mởUI/UX
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 72/100
opencrvs/opencrvs-core#14418 ·
Maintainer thường phản hồi trong vòng 1 ngày
-
Selection improvementsĐang mởenhancement
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 68/100
IacobIonut01/ReFra#1433 ·
Maintainer thường phản hồi trong vòng 17 ngày
-
bug
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 66/100
-
Độ khó 2/5 1-3 giờ Mức phù hợp với người mới 65/100
OREL-group/Project-Management#133 · 1 bình luận ·