CC Signals does not appear to support asset-based AI Preferences
Nobody has claimed this yet.
- #59 by @TimidRobot — closed without merging
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- ai
Research direction
The issue names no files or tests. Start by reading the CC Signals proposal and the IETF AI Preferences discussion, focusing on the asset-based model exemplified by Content Credentials; done is defined by extending CC Signals to cover that model, though the required scope remains unspecified.
Written by the indexing model from the issue text.
Description
Problem
The AI Preferences work of the IETF discusses two different models of attachments for these preferences - location-based (e.g., REP) and asset-based (e.g., Content Credentials). The CC Signals proposal as currently expressed here does not address the second.
Description
Recommend that CC Signals be extended to support asset-based preference specification.
Implementation
- I would be interested in implementing this feature.
- Dominant language
- No language data
- Stars
- 134
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from creativecommons/cc-signals
-
🏁 status: ready for work 💬 talk: discussion 📄 aspect: text 🛠 goal: fix 🟩 priority: low
Difficulty 5/5 Over a week Newbie friendliness 25/100
creativecommons/cc-signals#80 · 1 comment ·
-
🏁 status: ready for work 💻 aspect: code 🛠 goal: fix 🟩 priority: low
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Have a look at this Data Nutrition Label initiative; guidelines for healthy data for training AI.Open✨ goal: improvement 🌟 goal: addition 🏁 status: ready for work 🏷 status: label work required 💬 talk: discussion 🟩 priority: low
Difficulty 5/5 Over a week Newbie friendliness 20/100
creativecommons/cc-signals#71 · 1 reaction ·
-
💬 talk: discussion 💻 aspect: code 🛠 goal: fix 🟨 priority: medium 🧹 status: ticket work required
Difficulty 5/5 Over a week Newbie friendliness 30/100
creativecommons/cc-signals#56 · 1 comment ·
-
Apparent contradiction in guidance on training a proprietary never released model on -ND contentOpen🏁 status: ready for work 📄 aspect: text 🛠 goal: fix 🟨 priority: medium
Difficulty 4/5 3-5 days Newbie friendliness 35/100
creativecommons/cc-signals#46 · 4 comments ·
All issues in creativecommons/cc-signals
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ranxianglei/billion-context#6429 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
volcengine/OpenViking#7485 · 1 comment ·
Maintainers usually reply within 1 day
-
bug priority::low upstream
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug mcp needs-human p2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
WingedGuardian/GENesis-AGI#4393 ·
Maintainers usually reply within 1 day