1,065
edits
User:Prawsthorne/StepxStep: Difference between revisions
Jump to navigation
Jump to search
→Basic Requirements
Prawsthorne (talk | contribs) |
Prawsthorne (talk | contribs) |
||
| Line 109: | Line 109: | ||
=== Basic Requirements === | === Basic Requirements === | ||
The resources here are going to keep things as simple as possible. As with many things technical they can quickly become much larger topics as technologies are built upon each other and discussing lower levels can easily become a part of the discussion. For the time being we are going to stay at the higher levels and loop around to dive deeper as the Open Badges project gets to its 1.0 release sometime in early 2013. | The resources here are going to keep things as simple as possible. As with many things technical they can quickly become much larger topics as technologies are built upon each other and discussing lower levels can easily become a part of the discussion. For the time being we are going to stay at the higher levels and loop around to dive deeper as the Open Badges project gets to its 1.0 release sometime in early 2013. | ||
==== Stability in the URL ==== | ==== 1. Stability in the URL ==== | ||
Having a stable URL is going to be important for being an issuer. The meta-data within the badge (or json file) needs to refer back to an internet domain name. This is so the badge can be validated and the data within the [https://github.com/mozilla/openbadges/wiki/Assertions origin, criteria, and evidence] can be viewed and referenced through time. | Having a stable URL is going to be important for being an issuer. The meta-data within the badge (or json file) needs to refer back to an internet domain name. This is so the badge can be validated and the data within the [https://github.com/mozilla/openbadges/wiki/Assertions origin, criteria, and evidence] can be viewed and referenced through time. | ||
==== Basic web site with the ability to support the json content type ==== | ==== 2. Basic web site with the ability to support the json content type ==== | ||
For manual issue of a badge your web server is going to have to support the '''application/json''' content-type. Ihis is done by some administrative tasks with your servers configuration. A Google search of your server name (Apache, IIS, etc.) and the keyword '''content-type''' should provide the information regarding your server recognizing this content-type. | For manual issue of a badge your web server is going to have to support the '''application/json''' content-type. Ihis is done by some administrative tasks with your servers configuration. A Google search of your server name (Apache, IIS, etc.) and the keyword '''content-type''' should provide the information regarding your server recognizing this content-type. | ||
<pre> | <pre> | ||
| Line 122: | Line 122: | ||
* create a screencast for editing the httpd.conf file in apache... also show the server restart... | * create a screencast for editing the httpd.conf file in apache... also show the server restart... | ||
==== Ability to hash the earners email with the salt ==== | ==== 3. Ability to hash the earners email with the salt ==== | ||
There is currently two approaches to manually issuing a badge to the OBI backpack. These have been referenced in a number of blog posts mentioned above and in step 0 of this step-by-step guide. | There is currently two approaches to manually issuing a badge to the OBI backpack. These have been referenced in a number of blog posts mentioned above and in step 0 of this step-by-step guide. | ||
* One method is to make an http request with the correctly formatted json file as a part of the URL (provide example). | * One method is to make an http request with the correctly formatted json file as a part of the URL (provide example). | ||