Skip to content

Changes to BP3 to mention use of language and direction tags and to a… #439

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 5 commits into
base: gh-pages
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions bp.html
Original file line number Diff line number Diff line change
Expand Up @@ -2255,12 +2255,12 @@ <h4 class="subhead">Possible Approach to Implementation</h4>
"currency": "EUR"
}
&hellip;</pre>
<p>Some datasets contain values that are not or cannot be rendered into a locale-neutral format. This is particularly true of any natural language text values. For each data field that can contain locale affected or natural language text, there should be an associated language tag used to indicate the language and locale of the data. This locale information can be used in parsing the data or to ensure proper presentation and processing of the value by the consumer. <abbr title="Best Current Practice">BCP</abbr>47 [[BCP47]] provides the standard for language and locale identification and, informatively, <abbr title="Unicode Common Locale Data Repository">CLDR</abbr> [[CLDR]] is the source for both representing specific localized formats and as a reference for specific locale data values.</p>
<p>Some datasets contain values that are not or cannot be rendered into a locale-neutral format. This is particularly true of any natural language text values. For each data field that can contain locale-affected or natural-language text, there should be an associated language tag used to indicate the language and locale of the data. This locale information can be used in parsing the data or to ensure proper presentation and processing of the value by the consumer. <abbr title="Best Current Practice">BCP</abbr>47 [[BCP47]] provides the standard for language and locale identification and, informatively, <abbr title="Unicode Common Locale Data Repository">CLDR</abbr> [[CLDR]] is the source for both representing specific localized formats and as a reference for specific locale data values.</p>
<aside class="example">
<h5 class="subhead">Machine-readable</h5>
<p>The example below shows the machine-readable metadata for the
bus stops dataset (<code>stops-2015-05-05</code>) with the inclusion of the <strong> locale
parameters </strong> metadata. The property <code>dct:language</code> is used to declare the languages the dataset is published in. If the dataset is available in multiple languages,
parameters</strong> metadata, followed by a <strong>locale-neutral representation</strong> of bus fare data. The property <code>dct:language</code> is used to declare the languages the dataset is published in. If the dataset is available in multiple languages,
use multiple values for this property. The property <code><a href="http://purl.org/dc/terms/conformsTo">dct:conformsTo</a></code> is used to specify the standard adopted for date and time formats. </p>
<pre class="highlight">
:stops-2015-05-05
Expand All @@ -2279,6 +2279,11 @@ <h5 class="subhead">Machine-readable</h5>
&lt;http://id.loc.gov/vocabulary/iso639-1/pt&gt; ;</strong>
<strong>dct:conformsTo &lt;http://www.iso.org/iso/home/standards/iso8601.htm&gt; ; </strong>
.

fare_id,price,currency_type,payment_method,transfers,transfer_duration
p,1.25,USD,0,0,0
a,5.25,USD,0,0,0

</pre>
<h5 class="subhead">Human-readable</h5>
<p><a href="dwbp-example.html#locale-parameters">Example page</a> with
Expand Down