Become Part of the Bibleref Community!
The success of bibleref as a standard will depend on widespread cooperation and involvement. This is an opportunity for those who write about the Bible to make their content more accessible to others, and enrich the value of everyone else's content as well.
What you can do to help
Most importantly, use bibleref on your blog and website!
Many other tools will help foster broader adoption of bibleref. Please email bibleref@semanticBABBLE.com (replacing BABBLE with bible in the address) if you're able to help with any of the following.
- Discussion: Join the discussion board to contribute your throughts about the specification, tools, and related issues.
-
Bibleref badge: Many standards and technologies (RSS, Atom, Technorati, etc.) have a small "badge" graphic like this
that bloggers display on their sites to show their adherance to the standard. A bibleref badge would also help educate others who might see the badge and be encouraged to learn what it means. UpdateThanks to Tim Bulkeley for this contribution:
. -
Test suite: a varied collection of positive and negative examples, together with the correct output, that bibleref processors could use to validate performance of their systems.
UpdateThis page is an initial example: more are welcomed. - Reference implementation: a example program in Perl, Python, or some other widely used programming language that could be downloaded to locally validate pages, and to provide an example of processor output. Implementations often also serve to clarify and refine the standard.
-
Validator: a web service that authors could use to validate their bibleref markup, and ensure the references are extracted as intended. This would be similar to e.g., the W3C validation pages for HTML and RSS. UpdateChris Roberts has developed a bibleref test page that you can use to check your markup and ensure references are recognized and output correctly.