|
|
| (11 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | [[Category:Developer]] | + | #REDIRECT [[:Category:Developer_Challenges]] |
| − | [[Category:Developer:TechChallenges]]
| |
| − | | |
| − | == Developer Aids, Libraries, and Specifications ==
| |
| − | | |
| − | === License metadata validation web application ===
| |
| − | | |
| − | '''1 implementation'''
| |
| − | | |
| − | This application should work much like the [http://www.w3.org/RDF/Validator/ W3C RDF Validation Service]. It may even re-use some of the same code. Instead of parsing RDF from a text input box or URL and displaying represented triples, the license metadata version should extract RDF potentially embedded in HTML from a text input box or URL, parse the RDF, and display license and work properties instead of raw RDF triples.
| |
| − | | |
| − | '''Update:''' Nathan Yergler's excellent [http://www.yergler.net/projects/ccvalidator/ ccValidator] meets the challenge! Please send Nathan bug reports, feature requests, and patches. If you have a different (better, thinks you) implementation in mind, don't be dissuaded by existing code -- the W3C RDF validator has used at least two different implementations.
| |
