Merge pull request #77 from sharmatime/patch-7

Update 17-metadata.md

Author: Kaushik Ghose

_episodes/17-metadata.md

@@ -15,10 +15,11 @@ encourage correct citation."
 Implementation extensions not required for correct execution (for example,
 fields related to GUI presentation) and metadata about the tool or workflow
 itself (for example, authorship for use in citations) may be provided as
-additional fields on any object.
-Such extensions fields must use a namespace prefix listed in the `$namespaces`
-section of the document as described in the
-[Schema Salad specification][schema-salad].
+additional fields on any object. Such extensions fields (e.g. format: edam:format_2572 ) 
+must use a namespace prefix listed in the `$namespaces`section of the document 
+(e.g edam: http://edamontology.org/) as described in the [Schema Salad specification][schema-salad].
+Once you add the namespace prefix, you can access it anywhere in the document as shown below.
+
 
 For all developers, we recommend the following minimal metadata for your tool
 and workflows. This example includes metadata allowing others to cite your tool.
@@ -30,6 +31,10 @@ and workflows. This example includes metadata allowing others to cite your tool.
 ~~~
 {: .source}
 
+The equivalent of this CWL description in command line format is:
+
+`wc -l /path/to/aligned_sequences.ext > output.txt`
+
 #### Extended Example
 
 For those that are highly motivated, it is also possible to annotate your tool