fixed reference to microdata/RDF mapping
authorJeniT
Wed, 21 Dec 2011 12:10:04 +0000
changeset 62 4b3a9ea3ea0a
parent 61 5e26fdd26f07
child 63 063f74830375
fixed reference to microdata/RDF mapping
html-data-guide/index.html
--- a/html-data-guide/index.html	Wed Dec 21 12:07:47 2011 +0000
+++ b/html-data-guide/index.html	Wed Dec 21 12:10:04 2011 +0000
@@ -896,7 +896,7 @@
         You will find it easier to consume and combine data published using a single <a>format</a> (syntax and vocabulary). To decide which to consume, you should first look at what formats your target publishers are currently using. It may be that these contain sufficient information for your application.
       </p>
       <p>
-        If the publishers whom you are targeting are already publishing using multiple formats, you may want to consume from all those formats (see <a href="#consuming-multiple-formats" class="sectionRef"></a>) in order to maximise the data that you can collect while minimising the impact on the publishers who are providing that information. If you are consuming microdata and storing the results as RDF, you should <a href="/wiki/Mapping_Microdata_to_RDF" title="Mapping Microdata to RDF">follow a standard mapping</a>.
+        If the publishers whom you are targeting are already publishing using multiple formats, you may want to consume from all those formats (see <a href="#consuming-multiple-formats" class="sectionRef"></a>) in order to maximise the data that you can collect while minimising the impact on the publishers who are providing that information. If you are consuming microdata and storing the results as RDF, you should follow a <a href=https://dvcs.w3.org/hg/htmldata/raw-file/default/microdata-rdf/index.html">standard mapping</a>.
       </p>
       <p>
         If current <a title="format">formats</a> do not encode the information you need to the detail you need it for your application, publishers will be more likely to publish extra data for you to consume if you: