Difference between revisions of "License metadata validation web application"

From Creative Commons
Jump to: navigation, search
 
(2 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Tech Challenges]]
 
[[Category:Tech Challenges Completed]]
 
 
[[Category:Developer]]
 
[[Category:Developer]]
[[Category:Technology]]
+
{{Challenge
{{incomplete}}
+
|related_to=Metadata
 +
|challenge_type=Developer
 +
|tags=metadata
 +
|is_complete=yes
 +
}}
  
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. Please see the detail page: [[License metadata validation web application]].
+
{{Infobox|
 +
'''NOTE''' This challenge completed successfully but has since fallen out of date.  If you're interested in working in this area there is now a challenge to [[Rewrite_Metadata_Validator|rewrite the validator]].
 +
}}
 +
 
 +
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.  
  
 
=== Implementations ===
 
=== Implementations ===
  
 
* 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.
 
* 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.
 
* Please add your implementation here :)
 
 
=== Examples ===
 
 
* Please add your example, screenshot, mockup, etc here :)
 
 
=== TODO ===
 
 
* Please add your TODO here :)
 

Latest revision as of 17:49, 26 March 2008


Related To: ,|x|Related To::x}}
Tags: {{#arraymap:metadata|,|x|Has Tag::x}} | (none) }}
Challenge Type: Has Challenge Type::Developer | (none) }}
Is Complete: Is Complete::yes | Is Complete::no }}


NOTE This challenge completed successfully but has since fallen out of date. If you're interested in working in this area there is now a challenge to rewrite the validator.

This application should work much like the 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.

Implementations

  • Nathan Yergler's excellent 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.