Formerly this interesting style of chart was a variant of the Pie chart that was created by using a custom class that resided in the Pie chart library. It also made use of the Rose chart in order to draw a circular background grid.
Now however it has been promoted to a full chart type - the Activity meter - so the code necessary is much smaller. By default, the Activity meter class creates a much different looking chart but with some configuration, you can achieve the style as it's shown here.
You can see the code that creates the chart below and how easy it is to implement.
You can use this style of chart to show one or more values that make more sense when they're arranged in a circle than in a horizontal or vertical arrangement.
If you want to add animation then the grow
effect looks nice.
<script src="RGraph.common.core.js"></script> <script src="RGraph.common.dynamic.js"></script> <script src="RGraph.common.tooltips.js"></script> <script src="RGraph.activity.js"></script>Put this where you want the chart to show up:
<canvas id="cvs" width="400" height="400" style="float: right">[No canvas support]</canvas>This is the code that generates the chart - it should be placed AFTER the
canvas
tag(s):


![hawk Logo](https://raw.github.com/hueniverse/hawk/master/images/hawk.png)
 Hawk is an HTTP authentication scheme using a message authentication code (MAC) algorithm to provide partial HTTP request cryptographic verification. For more complex use cases such as access delegation, see [Oz](https://github.com/hueniverse/oz).
Current version: 3.x
Note: 3.x and 2.x are the same exact protocol as 1.1. The version increments reflect changes in the node API.
[![Build Status](https://secure.travis-ci.org/hueniverse/hawk.png)](http://travis-ci.org/hueniverse/hawk)
# Table of Content
[Introduction](#introduction) - [Replay Protection](#replay-protection) - [Usage Example](#usage-example) - [Protocol Example](#protocol-example)
- [Payload Validation](#payload-validation)
- [Response Payload Validation](#response-payload-validation)
- [Browser Support and Considerations](#browser-support-and-considerations)

 - [Single URI Authorization](#single-uri-authorization)
- [Usage Example](#bewit-usage-example)

 - [Security Considerations](#security-considerations)
- [MAC Keys Transmission](#mac-keys-transmission)
- [Confidentiality of Requests](#confidentiality-of-requests)
- [Spoofing by Counterfeit Servers](#spoofing-by-counterfeit-servers)
- [Plaintext Storage of Credentials](#plaintext-storage-of-credentials)
- [Entropy of Keys](#entropy-of-keys)
- [Coverage Limitations](#coverage-limitations)
- [Future Time Manipulation](#future-time-manipulation)
- [Client Clock Poisoning](#client-clock-poisoning)
- [Bewit Limitations](#bewit-limitations)
- [Host Header Forgery](#host-header-forgery)

 - [Frequently Asked Questions](#frequently-asked-questions)

 - [Implementations](#implementations) - [Acknowledgements](#acknowledgements)
# Introduction
Hawk is an HTTP authentication scheme providing mechanisms for making authenticated HTTP requests with partial cryptographic verification of the request and response, covering the HTTP method, request URI, host, and optionally the request payload.
Similar to the HTTP [Digest access authentication schemes](http://www.ietf.org/rfc/rfc2617.txt), Hawk uses a set of client credentials which include an identifier (e.g. username) and key (e.g. password). Likewise, just as with the Digest scheme, the key is never included in authenticated requests. Instead, it is used to calculate a request MAC value which is included in its place.
However, Hawk has several differences from Digest. In particular, while both use a nonce to limit the possibility of replay attacks, in Hawk the client generates the nonce and uses it in combination with a timestamp, leading to less “chattiness” (interaction with the server).
Also unlike Digest, this scheme is not intended to protect the key itself (the password in Digest) because the client and server must both have access to the key material in the clear.
The primary design goals of this scheme are to: * simplify and improve HTTP authentication for services that are unwilling or unable to deploy TLS for all resources, * secure credentials against leakage (e.g., when the client uses some form of dynamic configuration to determine where
to send an authenticated request), and
- avoid the exposure of credentials sent to a malicious server over an unauthenticated secure channel due to client failure to validate the server’s identity as part of its TLS handshake.
In addition, Hawk supports a method for granting third-parties temporary access to individual resources using a query parameter called _bewit_ (in falconry, a leather strap used to attach a tracking device to the leg of a hawk).
The Hawk scheme requires the establishment of a shared symmetric key between the client and the server, which is beyond the scope of this module. Typically, the shared credentials are established via an initial TLS-protected phase or derived from some other shared confidential information available to both the client and the server.
## Replay Protection
Without replay protection, an attacker can use a compromised (but otherwise valid and authenticated) request more than once, gaining access to a protected resource. To mitigate this, clients include both a nonce and a timestamp when making requests. This gives the server enough information to prevent replay attacks.
The nonce is generated by the client, and is a string unique across all requests with the same timestamp and key identifier combination.
The timestamp enables the server to restrict the validity period of the credentials where requests occuring afterwards are rejected. It also removes the need for the server to retain an unbounded number of nonce values for future checks. By default, Hawk uses a time window of 1 minute to allow for time skew between the client and server (which in practice translates to a maximum of 2 minutes as the skew can be positive or negative).
Using a timestamp requires the client’s clock to be in sync with the server’s clock. Hawk requires both the client clock and the server clock to use NTP to ensure synchronization. However, given the limitations of some client types (e.g. browsers) to deploy NTP, the server provides the client with its current time (in seconds precision) in response to a bad timestamp.
There is no expectation that the client will adjust its system clock to match the server (in fact, this would be a potential attack vector). Instead, the client only uses the server’s time to calculate an offset used only for communications with that particular server. The protocol rewards clients with synchronized clocks by reducing the number of round trips required to authenticate the first request.
## Usage Example
Server code:
```javascript var Http = require(‘http’); var Hawk = require(‘hawk’);
// Credentials lookup function
var credentialsFunc = function (id, callback) {
- var credentials = {
- key: ‘werxhqb98rpaxn39848xrunpaw3489ruxnpa98w4rxn’, algorithm: ‘sha256’, user: ‘Steve’
};
return callback(null, credentials);
};
// Create HTTP server
var handler = function (req, res) {
// Authenticate incoming request
Hawk.server.authenticate(req, credentialsFunc, {}, function (err, credentials, artifacts) {
// Prepare response
var payload = (!err ? ‘Hello ‘ + credentials.user + ‘ ‘ + artifacts.ext : ‘Shoosh!’); var headers = { ‘Content-Type’: ‘text/plain’ };
// Generate Server-Authorization response header
var header = Hawk.server.header(credentials, artifacts, { payload: payload, contentType: headers[‘Content-Type’] }); headers[‘Server-Authorization’] = header;
// Send the response back
res.writeHead(!err ? 200 : 401, headers); res.end(payload);
});
};
// Start server
Http.createServer(handler).listen(8000, ‘example.com’); ```
Client code:
```javascript var Request = require(‘request’); var Hawk = require(‘hawk’);
// Client credentials
- var credentials = {
- id: ‘dh37fgj492je’, key: ‘werxhqb98rpaxn39848xrunpaw3489ruxnpa98w4rxn’, algorithm: ‘sha256’
}
// Request options
- var requestOptions = {
- uri: ‘http://example.com:8000/resource/1?b=1&a=2‘, method: ‘GET’, headers: {}
};
// Generate Authorization request header
var header = Hawk.client.header(‘http://example.com:8000/resource/1?b=1&a=2‘, ‘GET’, { credentials: credentials, ext: ‘some-app-data’ }); requestOptions.headers.Authorization = header.field;
// Send authenticated request
Request(requestOptions, function (error, response, body) {
// Authenticate the server’s response
var isValid = Hawk.client.authenticate(response, credentials, header.artifacts, { payload: body });
// Output results
console.log(response.statusCode + ‘: ‘ + body + (isValid ? ‘ (valid)’ : ‘ (invalid)’));
});¶
Hawk utilized the [SNTP](https://github.com/hueniverse/sntp) module for time sync management. By default, the local machine time is used. To automatically retrieve and synchronice the clock within the application, use the SNTP ‘start()’ method.
`javascript
Hawk.sntp.start();
`
## Protocol Example
The client attempts to access a protected resource without authentication, sending the following HTTP request to the resource server:
`
GET /resource/1?b=1&a=2 HTTP/1.1
Host: example.com:8000
`
The resource server returns an authentication challenge.
`
HTTP/1.1 401 Unauthorized
WWW-Authenticate: Hawk
`
The client has previously obtained a set of Hawk credentials for accessing resources on the “http://example.com/” server. The Hawk credentials issued to the client include the following attributes:
- Key identifier: dh37fgj492je
- Key: werxhqb98rpaxn39848xrunpaw3489ruxnpa98w4rxn
- Algorithm: sha256
The client generates the authentication header by calculating a timestamp (e.g. the number of seconds since January 1, 1970 00:00:00 GMT), generating a nonce, and constructing the normalized request string (each value followed by a newline character):
``` hawk.1.header<PHONE_NUMBER> j4h3g2 GET /resource/1?b=1&a=2 example.com 8000
some-app-ext-data
The request MAC is calculated using HMAC with the specified hash algorithm “sha256” and the key over the normalized request string. The result is base64-encoded to produce the request MAC:
`
6R4rV5iE+NPoym+WwjeHzjAGXUtLNIxmo1vpMofpLAE=
`
The client includes the Hawk key identifier, timestamp, nonce, application specific data, and request MAC with the request using the HTTP Authorization request header field:
`
GET /resource/1?b=1&a=2 HTTP/1.1
Host: example.com:8000
Authorization: Hawk id="dh37fgj492je", ts="1353832234", nonce="j4h3g2", ext="some-app-ext-data", mac="6R4rV5iE+NPoym+WwjeHzjAGXUtLNIxmo1vpMofpLAE="
`
The server validates the request by calculating the request MAC again based on the request received and verifies the validity and scope of the Hawk credentials. If valid, the server responds with the requested resource.
### Payload Validation
Hawk provides optional payload validation. When generating the authentication header, the client calculates a payload hash using the specified hash algorithm. The hash is calculated over the concatenated value of (each followed by a newline character): * hawk.1.payload * the content-type in lowercase, without any parameters (e.g. application/json) * the request payload prior to any content encoding (the exact representation requirements should be specified by the server for payloads other than simple single-part ascii to ensure interoperability)
For example:
- Payload: Thank you for flying Hawk
- Content Type: text/plain
- Hash (sha256): Yi9LfIIFRtBEPt74PVmbTF/xVAwPn7ub15ePICfgnuY=
Results in the following input to the payload hash function (newline terminated values):
``` hawk.1.payload text/plain Thank you for flying Hawk
Which produces the following hash value:
`
Yi9LfIIFRtBEPt74PVmbTF/xVAwPn7ub15ePICfgnuY=
`
The client constructs the normalized request string (newline terminated values):
``` hawk.1.header<PHONE_NUMBER> j4h3g2 POST /resource/1?a=1&b=2 example.com 8000 Yi9LfIIFRtBEPt74PVmbTF/xVAwPn7ub15ePICfgnuY= some-app-ext-data
Then calculates the request MAC and includes the Hawk key identifier, timestamp, nonce, payload hash, application specific data, and request MAC, with the request using the HTTP Authorization request header field:
`
POST /resource/1?a=1&b=2 HTTP/1.1
Host: example.com:8000
Authorization: Hawk id="dh37fgj492je", ts="1353832234", nonce="j4h3g2", hash="Yi9LfIIFRtBEPt74PVmbTF/xVAwPn7ub15ePICfgnuY=", ext="some-app-ext-data", mac="aSe1DERmZuRl3pI36/9BdZmnErTw3sNzOOAUlfeKjVw="
`
It is up to the server if and when it validates the payload for any given request, based solely on it’s security policy and the nature of the data included.
If the payload is available at the time of authentication, the server uses the hash value provided by the client to construct the normalized string and validates the MAC. If the MAC is valid, the server calculates the payload hash and compares the value with the provided payload hash in the header. In many cases, checking the MAC first is faster than calculating the payload hash.
However, if the payload is not available at authentication time (e.g. too large to fit in memory, streamed elsewhere, or processed at a different stage in the application), the server may choose to defer payload validation for later by retaining the hash value provided by the client after validating the MAC.
It is important to note that MAC validation does not mean the hash value provided by the client is valid, only that the value included in the header was not modified. Without calculating the payload hash on the server and comparing it to the value provided by the client, the payload may be modified by an attacker.
## Response Payload Validation
Hawk provides partial response payload validation. The server includes the Server-Authorization response header which enables the client to authenticate the response and ensure it is talking to the right server. Hawk defines the HTTP Server-Authorization header as a response header using the exact same syntax as the Authorization request header field.
The header is contructed using the same process as the client’s request header. The server uses the same credentials and other artifacts provided by the client to constructs the normalized request string. The ext and hash values are replaced with new values based on the server response. The rest as identical to those used by the client.
The result MAC digest is included with the optional hash and ext values:
`
Server-Authorization: Hawk mac="XIJRsMl/4oL+nn+vKoeVZPdCHXB4yJkNnBbTbHFZUYE=", hash="f9cDF/TDm7TkYRLnGwRMfeDzT6LixQVLvrIKhh0vgmM=", ext="response-specific"
`
## Browser Support and Considerations
A browser script is provided for including using a


Citizens connect with the public art commissioned by SFAC for several intentions, as shown below. The SF Arts Commission is the city council that champions the arts. Through art education programs, street activation initiatives, public art work, grant funded performances and more, the SFAC acts as a catalyst for life-changing experiences for the citizens and tourists of one of the most beautiful cities in the world.
The SFAC is looking to be much more transparent in it's plans for public art, and wants to engage the city's inhabitants to help prioritize what it invests in.
We modeled designs for an accessible turnable public voting kiosk which can hold a digital touch device like an iPad which as a public option polling application. These kiosks are located in public spaces in the city where citizens pause.
From our research and collaborative design process, we realized that the best way to engage public participation is by intervening seamlessly in public spaces where citizens might pause. Since citizens interface with the city at several touchpoints like public areas, this gives SFAC more opportunities to connect with people to anonymously vote for at while they pass by or wait.
Our design proposal is based on user research, competitive and comparitive analyses. Our design hypotheses and solution statements were born of surveys, interviews and prototypes, which are described here.
The survey showed diverse and divided opinion about the public art, with citizens expressing views such as:
“While $400K sounds like a lot of money, it's probably a drop in the bucket of the whole project. I don't think that the citizens will "benefit", but perhaps they'll ENJOY it.”
“Not sure. I love public art but we might need that money for more pressing social justice causes.”
“For $ 400,000 does this art include a building??”
We used a heuristic framework to study the websites and processes of other city council bodies from the Bay Area to learn more about how we can improve SFAC's presence
We took inspiration from physical as well as digital applications for ideation
We made prototypes of cardboard and paper, which aided us in illiciting feedback from several users. This helped us rapidly go through several design iterations for the flow and features of the product
We also presented wireframes and clickable prototypes for the "SFAC Forum" - an addition to the SFAC website which will allow users to share opinions and have a moderated discussion about public arts and performances on the website


{% extends "base.html" %} {% block title %} {{ title }} - Dustin Reed Info {% endblock %} {% block content %}
As a Sr. DevOps Engineer with over a decade of experience in enterprise IT,
I have a passion for computing that began at a young age. From creating my first
application in QBasic at age 8 to developing text-based games on my TI-83 calculator
in high school, I have always been drawn to programming. My background in IT Operations
has allowed me to leverage my programming knowledge to automate daily tasks, starting
with batch scripts and eventually mastering PowerShell and Python.
Today, I am focused on utilizing DevOps toolchains and methodologies to design infrastructure
as code and track changes with version control. By implementing CI/CD pipelines,
I can deploy applications to cloud platforms in a fault-tolerant, scalable, and
distributed manner. This approach reduces risk and complexity for software deployments,
enabling businesses to quickly adapt to changing market conditions and be more agile.
Be sure to check out my Projects section for examples of my work.


| TOC |
|
OpenID Attribute Exchange is an OpenID service extension for exchanging identity information between endpoints. Messages for retrieval and storage of identity information are provided.
1.
Terminology
1.1.
Definitions and Conventions
2.
Overview
3.
Information Model
3.1.
Subject Identifier
3.2.
Attribute Type Identifier
3.3.
Attribute Value
3.3.1.
Attribute-Specific Encodings
4.
Discovery
5.
Fetch Message
5.1.
Fetch Request Format
5.2.
Fetch Response Format
6.
Store Message
6.1.
Store Request Format
6.2.
Store Response Format
6.2.1.
Storage Success
6.2.2.
Storage Failure
7.
Security Considerations
8.
Acknowledgements
9.
References
9.1.
Normative References
9.2.
Non-normative References
§
Authors' Addresses
| TOC |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” March 1997.).
| TOC |
- User:
- Also referred to as "End User" or "Subject". A person with a digital identity who participates in OpenID-based identity information exchanges using their client software, typically a web browser.
- Identity Data:
- A property of a digital identity in which the Property Name and Property Value are represented as a name-value pair.
- Attribute
- The base of the information model used to describe the Identity Data, for the purpose of exchanging it.
- Persona:
- A subset of the user's identity data. A user can have multiple personas as part of their identity. For example, a user might have a work persona and a home persona.
- OpenID Provider:
- Also called "OP" or "Server". An OpenID Authentication server on which a Relying Party relies for an assertion that the end user controls an Identifier.
- Relying Party:
- Also called "RP" or "Consumer". A Web application that wants proof that the end user controls an Identifier, and requests identity data associated with the end user.
All OpenID Attribute Exchange messages MUST contain the following extension namespace declaration, as specified in the Extensions section of OpenID-Authentication-2.0:
openid.ns.<extension_alias>=http://openid.net/srv/ax/1.0
The actual extension namespace alias should be determined on a per-message basis by the party composing the messages, in such a manner as to avoid conflicts between multiple extensions. For the purposes of this document, the extension namespace alias for the attribute exchange service will be "ax".
| TOC |
The attribute exchange service extension is identified by the URI "http://openid.net/srv/ax/1.0". This URI MUST be specified in the extension namespace declaration.
An attribute is a unit of personal identity information that is identified by a unique URI. It may refer to any kind of information. A reference example of defining attribute types is provided by [OpenID.axschema] (Hardt, D., “Schema for OpenID Attribute Exchange,” May 2007.).
This service extension defines two message types for transferring attributes: fetch (see Section 5 (Fetch Message)) and store (see Section 6 (Store Message)). Fetch retrieves attribute information from an OpenID Provider, while store saves or updates attribute information on the OpenID Provider. Both messages originate from the Relying Party and are passed to the OpenID Provider via the user agent as per the OpenID Authentication protocol specification.
The request parameters detailed here MUST be sent using the [OpenID.authentication‑2.0]<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007.) extension mechanism.
| TOC |
The OpenID Attribute Exchange service extension provides a mechanism for moving identity information between sites, as such its information model is simple:
An attribute is associated with a Subject Identifier
An attribute has a type identifier and a value
An attribute type identifier is a URI
An attribute value can be any kind of data.
| TOC |
An identifier for a set of attributes. It MUST be a URI. The subject identifier corresponds to the end-user identifier in the authentication portion of the messages. In other words, the subject of the identity attributes in the attribute exchange part of the message is the same as the end-user in the authentication part. The subject identifier is not included in the attribute exchange.
| TOC |
An attribute type identifier MUST be a URI, which is used for referring to property values.
If an attribute type identifier URI can be resolved then it MAY be dereferenced to retrieve a description of the property. OpenID Providers can use the metadata obtained through dereferencing new or unknown attribute types to dynamically assist the user in providing the attribute.
This provides for flexibility and extensibility. Flexibility in that both URNs and URLs can be used to refer to property values. Extensibility allows any individual site, or consortium of sites, to define their own attribute types with agreements on the syntax and semantics of their associated attribute values.
[OpenID.axschema] (Hardt, D., “Schema for OpenID Attribute Exchange,” May 2007.) outlines an example method of defining new attribute type URIs, and also provides a set of attribute types with their associated metadata schema and data formats.
| TOC |
A attribute value MUST be a UTF-8 (Yergeau, F., “UTF-8, a transformation format of ISO 10646,” November 2003.) [RFC3629] string. In order to comply with the data formats defined by the underlying [OpenID.authentication‑2.0]<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007.) protocol, attribute values MUST NOT contain newlines (UCS codepoint 10, "\n").
OpenID Attribute Exchange can be used to transfer any kind of data. If the data contains newlines, is not a UTF-8 string or it is so desired by the parties transferring the data, the data MUST be encoded to a UTF-8 string without newlines.
| TOC |
Attribute-specific encodings can be defined using the attribute metadata descriptions and may be applied by the protocol layer above OpenID Attribute Exchange.
Optionally, attribute-specific encodings may use language tags [OpenID.value‑lang‑1.0] (Wahl, M., “Language Tags for OpenID Values,” April 2007.) for localization.
| TOC |
Discovery of the attribute exchange service extension is achieved via the mechanism described in [OpenID.authentication‑2.0]<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007.). The attribute exchange namespace "http://openid.net/srv/ax/1.0" SHOULD be listed as an <xrd:Type> child element of the <xrd:Service> element in the XRDS discovery document.
| TOC |
The fetch message is used to retrieve personal identity attributes from an OpenID Provider.
| TOC |
With the exception of "openid.ax.mode", all of the following request fields are OPTIONAL, though at least one of "openid.ax.required" or "openid.ax.if_available" MUST be specified in the request, and any attribute alias present in a "openid.ax.required" or "openid.ax.if_available" parameter MUST have an associated "openid.ax.type.<alias>" parameter. The supported length for attribute aliases MUST be at least 32 characters.
Multiple attribute aliases in the "openid.ax.required" and "openid.ax.if_available" directives are separated with a comma, ",".
- openid.ax.mode
REQUIRED. Value: "fetch_request".
- openid.ax.type.<alias>
The value of this parameter specifies the type identifier URI of a requested attribute. The <alias> will further be used to identify the attribute being exchanged.
Attribute aliases MUST NOT contain newline and colon characters, as specified in the Data Formats / Protocol Messages section of [OpenID.authentication‑2.0]<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007.); they also MUST NOT contain commas (",") and periods (".").
- openid.ax.required
Value: an attribute alias, or a list of aliases corresponding to the URIs defined by "openid.ax.type.<alias>" parameters. Multiple attribute aliases are separated with a comma, ",".
By requesting attributes using this field, a hint is sent to the OP about the RP's requirements for offering certain functionality and should be used by the OP to help the user decide what attributes to release. RP's requirements should not be enforced by the OP.
The RP should offer, out of band of attribute exchange, an alternate method of collecting the attributes it needs, if they weren't obtained via attribute exchange.
- openid.ax.if_available
Value: an attribute alias, or a list of aliases corresponding to the URIs defined by "openid.ax.type.<alias>" parameters. Multiple attribute aliases are separated with a comma, ",".
Attributes requested using this field are deemed optional by the RP; the RP should be able to complete the interaction with the user even if values are not provided by the OP for the optional attributes.
- openid.ax.count.<alias>
The number of values for the specified attribute alias the Relying Party wishes to receive from the OpenID Provider. If present, the value MUST be greater than zero, or the special value "unlimited" which signifies that the RP is requesting as many values as the OP has for the attribute. If absent, exactly one value is requested.
OpenID Providers MAY return less than or the exact number of values speficied by this field for the associated attribute, but MUST NOT return more than the number of requested values for the attribute.
- openid.ax.update_url
If present, the OpenID Provider may re-post the fetch response message to the specified URL at some time after the initial response has been sent, using a OpenID Authentication Positive Assertion. If the OpenID Provider supports this feature it MUST return the parameter as part of the fetch response message. If it does not support this feature it may legally ignore this parameter.
The value of the "openid.ax.update_url" field MUST be used as value for "openid.return_to" field of the underlying OpenID Authentication Positive Assertion of the fetch response update.
The "openid.ax.update_url" value MUST also match the realm specified in the underlying OpenID message of the fetch request, if a "openid.realm" field is present. The matching rules are the ones specified in the "Realms" section of the OpenID Authentication protocol.
This "unsolicited" response message would be generated in response to an attribute information update, and would contain the updated data. The OP should obtain the user's consent for resending the updated data to the RPs, as with any OpenID Positive Assertion.
The relying party may include transaction data encoded in the URL such that it contains enough information to match the attribute information to the identity subject. Additional information may be encoded in the URL by the relying party as necessary.
If an RP wishes to receive no further updates for an attribute, it MAY return the HTTP 404 response code to the corresponding "update_url". OPs MAY decide to stop sending updates after encountering 404 response codes.
This example requests the required full name and gender information, and the optional favourite dog and movie information. The Relying Party is interested in up to three favorite movies associated with the subject identifier.
openid.ns.ax=http://openid.net/srv/ax/1.0 openid.ax.mode=fetch_request openid.ax.type.fname=http://example.com/schema/fullname openid.ax.type.gender=http://example.com/schema/gender openid.ax.type.fav_dog=http://example.com/schema/favourite_dog openid.ax.type.fav_movie=http://example.com/schema/favourite_movie openid.ax.count.fav_movie=3 openid.ax.required=fname,gender openid.ax.if_available=fav_dog,fav_movie openid.ax.update_url=http://idconsumer.com/update?transaction_id=a6b5c41
| TOC |
The fetch response message supplies the information requested in the fetch request. Each attribute is supplied with the assigned alias prefixed by "openid.ax.value." as the lvalue and the attribute value as the rvalue. Attribute types are also returned in the "openid.ax.type.<alias>" parameters. The supported length for attribute aliases MUST be at least 32 characters.
With the exception of "openid.ax.mode", all of the following request fields are OPTIONAL, though any attribute value present in a "openid.ax.value.<alias>" parameter MUST have an associated "openid.ax.type.<alias>" parameter.
If a value was not supplied or available from the user, the associated "openid.ax.value.<alias>" field SHOULD NOT be included by the OP in the fetch response. An "openid.ax.count.<alias>" with a value of "0" together with its corresponding "openid.ax.type.<alias>" field MAY be included to explicitly state that no values are provided for an attribute.
Validation of the received data should be performed out of band of attribute exchange by the RP.
- openid.ax.mode
REQUIRED. Value: "fetch_response".
- openid.ax.type.<alias>
The value of this parameter specifies the type identifier URI for an attribute in the fetch response. The <alias> will further be used to identify the attribute being exchanged.
Attribute aliases MUST NOT contain newline and colon characters, as specified in the Data Formats / Protocol Messages section of [OpenID.authentication‑2.0]<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007.); they also MUST NOT contain commas (",") and periods (".").
- openid.ax.count.<alias>
The number of values returned for the attribute referred to as <alias>.
- openid.ax.value.<alias>
Assigns a value to the attribute referred to as <alias>. This parameter format MUST be used if "openid.ax.count.<alias>" is not sent.
- openid.ax.value.<alias>.<number>
Assigns a value to the attribute referred to as <alias>. This parameter format MUST be used if "openid.ax.count.<alias>" is sent and at least one value is provided for the associated attribute.
The <number> uniquely identifies the index of the value, ranging from one to the value specified by "openid.ax.count.<alias>". The number of parameters MUST be equal to the value specified by "openid.ax.count.<alias>". The OP is not required to preserve the order of attribute values among fetch responses.
- openid.ax.update_url
Returns the "update_url" parameter specified in the request. If the OpenID Provider receives an "update_url" parameter and it intends to support the attribute update feature, it MUST present the "update_url" parameter and value as part of the fetch response message.
A fetch response message may also be sent to the "update_url" specified in Section 5.1 (Fetch Request Format) in response to attribute value updates on the OpenID Provider.
The response to the previous request example, in which the required full name information, and the optional favourite dog information are supplied. Even though three movie names were requested, the OP supplied only two values.
openid.ns.ax=http://openid.net/srv/ax/1.0 openid.ax.mode=fetch_response openid.ax.type.fname=http://example.com/schema/fullname openid.ax.type.gender=http://example.com/schema/gender openid.ax.type.fav_dog=http://example.com/schema/favourite_dog openid.ax.type.fav_movie=http://example.com/schema/favourite_movie openid.ax.value.fname=John Smith openid.ax.count.gender=0 openid.ax.value.fav_dog=Spot openid.ax.count.fav_movie=2 openid.ax.value.fav_movie.1=Movie1 openid.ax.value.fav_movie.2=Movie2 openid.ax.update_url=http://idconsumer.com/update?transaction_id=a6b5c41
| TOC |
The store message is used to store personal identity information to the OpenID Provider; it provides the means for an RP to transfer to the OP attributes that the user may consider useful, such as by providing them to other RPs. The supported length for attribute aliases MUST be at least 32 characters.
The manner in which the OP processes the attribute payload in a store request if out of scope of this document.
| TOC |
With the exception of "openid.ax.mode", all of the following request fields are OPTIONAL. Any alias referred to in a "openid.ax.value.<alias>" or "openid.ax.value.<alias>.<number>" parameter MUST have an associated "openid.ax.type.<alias>" parameter.
- openid.ax.mode
REQUIRED. Value: "store_request".
- openid.ax.type.<alias>
The value of this parameter specifies the type identifier URI for an attribute in the sore request. The <alias> will further be used to identify the attribute being exchanged.
Attribute aliases MUST NOT contain newline and colon characters, as specified in the Data Formats / Protocol Messages section of [OpenID.authentication‑2.0]<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007.); they also MUST NOT contain commas (",") and periods (".").
- openid.ax.count.<alias>
The number of values sent for the attribute referred to as <alias>. If present, it MUST be greater than zero.
- openid.ax.value.<alias>
Assigns a value to the attribute referred to as <alias>. This parameter format MUST be used if "openid.ax.count.<alias>" is not sent.
- openid.ax.value.<alias>.<number>
Assigns a value to the attribute referred to as <alias>. The <number> uniquely identifies the index of the value, ranging from one to the value specified by "openid.ax.count.<alias>". This parameter format MUST be used if "openid.ax.count.<alias>" is sent, and the number of these parameters MUST be equal to the value specified by "openid.ax.count.<alias>".
openid.ns.ax=http://openid.net/srv/ax/1.0 openid.ax.mode=store_request openid.ax.type.fname=http://example.com/schema/fullname openid.ax.value.fname=Bob Smith openid.ax.type.fav_movie=http://example.com/schema/favourite_movie openid.ax.count.fav_movie=2 openid.ax.value.fav_movie.1=Movie1 openid.ax.value.fav_movie.2=Movie2
| TOC |
| TOC |
The successful store operation is indicated by the mode parameter in the store response:
- openid.ax.mode
REQUIRED. Value: "store_response_success".
openid.ns.ax=http://openid.net/srv/ax/1.0 openid.ax.mode=store_response_success
| TOC |
A storage failure response has the following format:
- openid.ax.mode
REQUIRED. Value: "store_response_failure".
- openid.ax.error
OPTIONAL. Parameter describing the error condition leading to the failure response, intended to be presented to the user. The locale of the message should match the locale of the HTTP message.
openid.ns.ax=http://openid.net/srv/ax/1.0 openid.ax.mode=store_response_failure openid.ax.error=General storage failure
| TOC |
OpenID Attribute Exchange is an OpenID extension, and thus uses OpenID Authentication request and response messages for exchanging attributes.
See the "Security Considerations" section of [OpenID.authentication‑2.0]<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007.).
| TOC |
John Merrells and other contributors to the document 'draft-merrells-dix'. Portions of that document were re-used for this one.
Mark Wahl advised on how to deal with issues concerning the encoding of attributes.
| TOC |
| TOC |
| [OpenID.authentication-2.0] |<EMAIL_ADDRESS>“OpenID Authentication 2.0 - Final,” August 2007 (TXT, HTML). |
| [OpenID.value-lang-1.0] | Wahl, M., “Language Tags for OpenID Values,” April 2007. |
| [RFC2119] | Bradner, S., “Key words for use in RFCs to Indicate Requirement Levels,” BCP 14, RFC 2119, March 1997 (TXT, HTML, XML). |
| [RFC3629] | Yergeau, F., “UTF-8, a transformation format of ISO 10646,” STD 63, RFC 3629, November 2003 (TXT). |
| TOC |
| [OpenID.axschema] | Hardt, D., “Schema for OpenID Attribute Exchange,” May 2007. |
| TOC |
| Dick Hardt | |
| Sxip Identity | |
| 798 Beatty Street | |
| Vancouver, BC V6B 2M1 | |
| CA | |
| Email: |<EMAIL_ADDRESS>|
| URI: | http://sxip.com/ |
| Johnny Bufu | |
| Sxip Identity | |
| 798 Beatty Street | |
| Vancouver, BC V6B 2M1 | |
| CA | |
| Email: |<EMAIL_ADDRESS>|
| URI: | http://sxip.com/ |
| Josh Hoyt | |
| JanRain | |
| 5331 SW Macadam Ave. #375 | |
| Portland, OR 97239 | |
| US | |
| Email: |<EMAIL_ADDRESS>|
| URI: | http://janrain.com/ |


10 Great Hair Care Tips
In the event that you watch the sensationalist newspapers, you realize that even the stars have terrible hair days. It just appears that when the expert beauticians are good and gone, it is inalienably human to have a not exactly stylish mane. However, you can do your part to remain in front of the fight by following these extraordinary hair care tips.
Utilize an expert conditioner that is planned for your particular hair type. While you can hold back a little on the cleanser, a decent, proficient conditioner is an unquestionable requirement have. Search for items in salons that are tweaked for your hair type. For example: If you have shading or a perm, pick a conditioner that is for synthetically prepared hair. Furthermore, avoid those across the board cleanser and conditioner combos. Pick a slice customized to your face and body shape. The main slip-up that individuals make while picking another haircut is to pick a style dependent on notoriety as opposed to how it will upgrade their highlights. Continuously pick another cut dependent on how it will upgrade or reduce your facial highlights and manufacture. In the event that you have expansive shoulders, pick a full-bodied cut over a neatly trimmed head embracing doo. Remember your UV protectants. Similarly, as your skin gets harmed by wind and sun, so does your hair. To battle this, search for completing items, for example, mousses, gels, and splashes that square UV beams.
Keep your arrangements. Did you realize that your hair will part quicker than it will develop? You have to get a trim each 6 to about two months, regardless of whether it’s only a miniaturized scale trim. A decent beautician makes them great since they comprehend what to leave on the head, not take off. Leave synthetic compounds to the experts. There is a motivation behind why cosmetologists need to go to class to figure out how to deal with synthetic compounds and hair forms. You can do hopeless harm with these items regardless of whether the bundle says that it’s way simple. Furthermore, regardless of whether you don’t make your hair drop out, you could wind up resembling a jokester and paying beautician heaps of cash to fix your wreckage. (Note: Most beauticians charge twofold the rate for restorative shading than they accomplish for typical shading forms).
Get shading for intrigue and body. Each cut needs a tad of shading to make it genuinely amazing. Regardless of whether your taste is unobtrusive or emotional, you can add intrigue and volume to your tresses with a shading procedure. Features, low lights, all-over shading, dim inclusion, and so on, it’s all useful for your look. Do week after week molding medicines. Regardless of whether your hair is incredibly sound, it is continually on the assault from wind, sun, cold, and warmth. Throughout the mid-year months, your hair is battered significantly more when it ingests chlorine and different synthetic compounds from your pool.
Get an ionic clay level iron. Rather than searing your hair with a regular metal-plated level iron. Fix your tresses, include sparkle, and inject dampness with one of the negative ionic level irons. We actually use T3 irons for all our work. Pick your styling items astutely. Stay away from items that leave develop on your hair. In the event that you see white gunk, that implies that your item isn’t water-solvent and might be covering your hair shaft. Develop causes placidness, breakage, and powerlessness to twist also the white chips.
Did you realize that on the off chance that you utilize a towel after your shower to dry your hair you are causing part closes and adding electricity produced via friction to your hair?
While these tips won’t make you appear as though you’ve employed an individual beautician, they will assist you with looking the absolute best that you can every single day. With regards to hair care, recall that you wear your hair regularly. Presently isn’t it worth the time, exertion, and cash that it takes to keep it looking terrific?
Check out this great info about having strong hair.


You must use the constructor new TextFormat()
to create a
TextFormat object before setting its properties. When you apply a
TextFormat object to a text field using the
TextField.defaultTextFormat
property or the
TextField.setTextFormat()
method, only its defined properties
are applied. Use the TextField.defaultTextFormat
property to
apply formatting BEFORE you add text to the TextField
, and the
setTextFormat()
method to add formatting AFTER you add text to
the TextField
. The TextFormat properties are null
by default because if you don't provide values for the properties, Flash
Player uses its own default formatting. The default formatting that Flash
Player uses for each property(if property's value is null
) is
as follows:
The default formatting for each property is also described in each property description.
font
The name of a font for text as a string.size
An integer that indicates the size in pixels.color
The color of text using this text format. A number containing three 8-bit RGB components; for example, 0xFF0000 is red, and 0x00FF00 is green.bold
A Boolean value that indicates whether the text is boldface.italic
A Boolean value that indicates whether the text is italicized.underline
A Boolean value that indicates whether the text is underlined.url
The URL to which the text in this text format hyperlinks. If url
is an empty string, the text does not have a hyperlink.target
The target window where the hyperlink is displayed. If the target window is an empty string, the text is displayed in the default target window _self
. If the url
parameter is set to an empty string or to the value null
, you can get or set this property, but the property will have no effect.align
The alignment of the paragraph, as a TextFormatAlign value.leftMargin
Indicates the left margin of the paragraph, in pixels.rightMargin
Indicates the right margin of the paragraph, in pixels.indent
An integer that indicates the indentation from the left margin to the first character in the paragraph.leading
A number that indicates the amount of leading vertical space between lines.TextFormat.indent
) affects only the first
line of each paragraph. If this property is null
, the
TextFormat object does not specify block indentation(block indentation is
0).null
, which means that Flash Player uses
Times New Roman font for the text.true
) or disabled(false
). Kerning adjusts the
pixels between certain character pairs to improve readability, and should
be used only when necessary, such as with headings in large fonts. Kerning
is supported for embedded fonts only.
Certain fonts such as Verdana and monospaced fonts, such as Courier New, do not support kerning.
The default value is null
, which means that kerning is not
enabled.
null
, which means that 0 pixels of letter spacing is used.
You can use decimal values such as 1.75
._self
. You can choose a custom name or one of
the following four names: _self
specifies the current frame
in the current window, _blank
specifies a new window,
_parent
specifies the parent of the current frame, and
_top
specifies the top-level frame in the current window. If
the TextFormat.url
property is an empty string or
null
, you can get or set this property, but the property will
have no effect.true
) or not(false
). This underlining is
similar to that produced by the
tag, but the latter is
not true underlining, because it does not skip descenders correctly. The
default value is null
, which indicates that underlining is
not used.url
property is an empty string, the text does not have a
hyperlink. The default value is null
, which indicates that
the text does not have a hyperlink.
Note: The text with the assigned text format must be set with
the htmlText
property for the hyperlink to work.
Any parameter may be set to
null
to indicate that it is not defined. All of the parameters are optional; any omitted parameters are treated asnull
.


{% load static %}
Chemical-Easy
CHEMICAL EASY
Homepage
(current)
Chemical Engineering
Vapor-Liquid Equilibrium
Reaction Engineering(soon)
BETA v0.3
{% block content %}{% endblock %}
{% block javascript %}{% endblock %}


1.8.3
Start date 07/27/2012
Due date 11/17/2012
43 days late
Fix pack 3 of 1.8
74%
17 closed
(74%)
6 open
(26%)
Version 1.8.3¶
Fixes some more issues of 1.8 as reported by users.
No breaking changes in terms of configuration or classes for custom tasks, publishers, ....
These fixes did not make it for the 1.8.2 release.


Hi this is the instruction of the catapult game
"A" key to shoot the enemies
"space" key to start the game and to play again
"C" key to change the camera (you can do this twice)
author sina ghiasi using three js and cannon js library
Loading


|
BitShares-Core
6.1.0
BitShares blockchain implementation and command-line interface software
|
This namespace contains the list type, and all of the operations and queries which can be performed upon it. More...
Namespaces | |
| impl | |
| runtime | |
| This namespace contains some utilities that provide runtime operations on typelists. | |
Classes | |
| struct | builder |
| struct | invert_filter |
| Template to invert a filter, i.e. filter<mylist, filter_inverter<myfilter>::type> More... | |
| struct | list |
| The actual list type. More... | |
Typedefs | |
| template<typename List , template< typename... > class Delegate> | |
| using | apply = typename impl::apply< List, Delegate >::type |
| Apply a list of types as arguments to another template. More... | |
| template<typename... Lists> | |
| using | concat = typename impl::concat< Lists... >::type |
| Concatenate two or more typelists together. More... | |
| template<std::size_t count> | |
| using | make_sequence = typename impl::make_sequence< count >::type |
| Create a list of sequential integers ranging from [0, count) More... | |
| template<typename List , typename Transformer > | |
| using | transform = typename impl::transform< List, Transformer >::type |
| Transform elements of a typelist. More... | |
| template<typename... TypeLists> | |
| using | concat_unique = typename impl::concat_unique< list<>, TypeLists... >::type |
| Remove duplicate items from one or more typelists and concatenate them all together. More... | |
| template<typename List , std::size_t index> | |
| using | at = typename impl::at< List, index >::type |
| Get the type at the specified list index. More... | |
| template<typename List > | |
| using | first = at< List, 0 > |
| Get the type at the beginning of the list. More... | |
| template<typename List > | |
| using | last = at< List, length< List >() -1 > |
| Get the type at the end of the list. More... | |
| template<typename List , std::size_t index> | |
| using | remove_at = typename impl::remove_at< list<>, List, index >::type |
| Get the list with the element at the given index removed. More... | |
| template<typename List , typename Remove > | |
| using | remove_element = remove_at< List, index_of< List, Remove >()> |
| Get the list with the given type removed. More... | |
| template<typename List , template< typename > class Filter> | |
| using | filter = typename impl::filter< Filter, list<>, List >::type |
| Get a list with all elements that do not pass a filter removed. More... | |
| template<typename List , std::size_t start, std::size_t end = length<List>()> | |
| using | slice = typename impl::slice< list<>, List, start, end >::type |
| Take the sublist at indexes [start, end) More... | |
| template<typename ListA , typename ListB > | |
| using | zip = typename impl::zip< ListA, ListB >::type |
| Zip two equal-length typelists together, i.e. zip<list<X, Y>, list<A, B>> == list<list<X, A>, list<Y, B>> More... | |
| template<typename List > | |
| using | index = typename impl::zip< typename impl::make_sequence< length< List >()>::type, List >::type |
This namespace contains the list type, and all of the operations and queries which can be performed upon it.
| using fc::typelist::apply = typedef typename impl::apply<List, Delegate>::type |
Apply a list of types as arguments to another template.
Definition at line 142 of file typelist.hpp.
| using fc::typelist::at = typedef typename impl::at<List, index>::type |
Get the type at the specified list index.
Definition at line 186 of file typelist.hpp.
| using fc::typelist::concat = typedef typename impl::concat<Lists...>::type |
Concatenate two or more typelists together.
Definition at line 150 of file typelist.hpp.
| using fc::typelist::concat_unique = typedef typename impl::concat_unique<list<>, TypeLists...>::type |
Remove duplicate items from one or more typelists and concatenate them all together.
Definition at line 182 of file typelist.hpp.
| using fc::typelist::filter = typedef typename impl::filter<Filter, list<>, List>::type |
Get a list with all elements that do not pass a filter removed.
Definition at line 205 of file typelist.hpp.
| using fc::typelist::first = typedef at<List, 0> |
Get the type at the beginning of the list.
Definition at line 190 of file typelist.hpp.
| using fc::typelist::index = typedef typename impl::zip<typename impl::make_sequence<length<List>()>::type, List>::type |
Add indexes to types in the list, i.e. index<list<A, B, C>> == list<list<0, A>, list<1, B>, list<2, C>> where 0, 1, and 2 are std::integral_constants of type std::size_t
Definition at line 225 of file typelist.hpp.
| using fc::typelist::last = typedef at<List, length<List>()-1> |
Get the type at the end of the list.
Definition at line 193 of file typelist.hpp.
| using fc::typelist::make_sequence = typedef typename impl::make_sequence<count>::type |
Create a list of sequential integers ranging from [0, count)
Definition at line 154 of file typelist.hpp.
| using fc::typelist::remove_at = typedef typename impl::remove_at<list<>, List, index>::type |
Get the list with the element at the given index removed.
Definition at line 197 of file typelist.hpp.
| using fc::typelist::remove_element = typedef remove_at<List, index_of<List, Remove>()> |
Get the list with the given type removed.
Definition at line 201 of file typelist.hpp.
| using fc::typelist::slice = typedef typename impl::slice<list<>, List, start, end>::type |
Take the sublist at indexes [start, end)
Definition at line 216 of file typelist.hpp.
| using fc::typelist::transform = typedef typename impl::transform<List, Transformer>::type |
Transform elements of a typelist.
Definition at line 170 of file typelist.hpp.
| using fc::typelist::zip = typedef typename impl::zip<ListA, ListB>::type |
Zip two equal-length typelists together, i.e. zip<list<X, Y>, list<A, B>> == list<list<X, A>, list<Y, B>>
Definition at line 220 of file typelist.hpp.


Variables
Auth flows:
Client Credentials
Code
Implicit
Refresh token
Token Exchange
Role:
Client
Resource
Application:


White to play 52
pips White=77 Black=145
(CorrectAnswer= 0/0, ErrorScore= 0)
1. 7/5 7/2 eq: +0.575 68.90% (G:29.05% B:3.18%) 31.10% (G: 1.02% B:0.03%) 2. 12/5 eq: +0.569 (-0.006) 70.51% (G:25.32% B:2.21%) 29.49% (G: 1.02% B:0.03%) 3. 12/7 5/3 eq: +0.510 (-0.065) 69.62% (G:23.13% B:1.91%) 30.38% (G: 1.27% B:0.04%) 4. 7/2 5/3 eq: +0.118 (-0.457) 54.70% (G:26.44% B:2.82%) 45.30% (G: 7.37% B:0.20%) 5. 12/10 7/2 eq: +0.101 (-0.474) 53.78% (G:26.65% B:2.80%) 46.22% (G: 7.11% B:0.16%)


|
YAGP 0.2
|
Represents a record for a family/relationship (GEDCOM FAM). More...
Inherits SharpGEDParser.Model.GEDCommon, SharpGEDParser.Model.NoteHold, SharpGEDParser.Model.SourceCitHold, and SharpGEDParser.Model.MediaHold.
Properties | |
| int | ChildCount [get, set] |
| The value of the NCHI tag from the GEDCOM. More... | |
| List< Child > | Childs [get] |
| A list of 'CHIL' cross-references to INDI records. More... | |
| List< SourceCit > | Cits [get] |
| Any Source citations associated with the record. More... | |
| List< string > | Dads [get] |
| A list of 'HUSB' cross-references to INDI records. More... | |
| List< FamilyEvent > | FamEvents [get] |
| The events associated to a family. More... | |
| List< string > | FamSubm [get] |
| The list of submitter (SUBM) cross-references for the family. More... | |
| List< LDSEvent > | LDSEvents [get] |
| Any LDS (Mormon) events. More... | |
| List< MediaLink > | Media [get] |
| Any Multimedia objects associated with the record. More... | |
| List< string > | Moms [get] |
| A list of 'WIFE' cross-references to INDI records. More... | |
| List< Note > | Notes [get] |
| Any NOTEs associated with the record. More... | |
| string | Restriction [get, set] |
| Any restriction notice applied to the record. More... | |
| override string | Tag [get] |
| GEDCOM Tag value. More... | |
| Properties inherited from SharpGEDParser.Model.GEDCommon | |
| StringPlus | AFN [get, set] |
| An AFN (ancestral file number) associated with the record. | |
| bool | AnyErrors [get] |
| Are there any errors associated with this record? Returns true if yes. | |
| bool | AnyREFNs [get] |
| Returns true if there are any REFNs associated to the record. | |
| int | BegLine [get, set] |
| The first line of the record in the original GEDCOM. | |
| ChangeRec | CHAN [get] |
| Any change record (CHAN). | |
| int | EndLine [get, set] |
| The last line of the record in the original GEDCOM. | |
| List< UnkRec > | Errors [get] |
| Problems, other than 'unknown'/'custom' tags at this or_children level. | |
| string | Ident [get, set] |
| The record's id. | |
| List< StringPlus > | REFNs [get] |
| Any user reference numbers associated with the record. Will be null if none. | |
| StringPlus | RFN [get, set] |
| An RFN (something file number) associated with the record. | |
| string | RIN [get, set] |
| Any RIN. | |
| abstract string | Tag [get] |
| The record's GEDCOM tag. | |
| string | UID [get] |
| An UID (universal identifier) associated with the record. | |
| List< UnkRec > | Unknowns [get] |
| Unknown and custom tags encountered at this level. | |
| Properties inherited from SharpGEDParser.Model.NoteHold | |
| List< Note > | Notes [get] |
| Any NOTE references associated with a record. More... | |
| Properties inherited from SharpGEDParser.Model.SourceCitHold | |
| List< SourceCit > | Cits [get] |
| Any source citations associated to a record. More... | |
| Properties inherited from SharpGEDParser.Model.MediaHold | |
| List< MediaLink > | Media [get] |
| Any media records associated to the record. More... | |
Represents a record for a family/relationship (GEDCOM FAM).
|
getset |
The value of the NCHI tag from the GEDCOM.
Will be -1 if the NCHI tag was not specified. This field value is not guaranteed to match the number of entries in the Childs list.
If this value is -1 the writer will not emit the NCHI tag.
|
get |
|
get |
Any Source citations associated with the record.
An empty list if none.
|
get |
A list of 'HUSB' cross-references to INDI records.
Will be an empty list if there are none. A single entry is GEDCOM standard conformant, but this is a list because multiple entries are possible from some programs.
|
get |
The events associated to a family.
Will be an empty list if there are none.
Events include the GEDCOM tags MARR, MARB, etc.
|
get |
The list of submitter (SUBM) cross-references for the family.
Will be an empty list if there are none.
|
get |
Any LDS (Mormon) events.
|
get |
Any Multimedia objects associated with the record.
An empty list if none.
|
get |
A list of 'WIFE' cross-references to INDI records.
Will be an empty list if there are none. A single entry is GEDCOM standard conformant, but this is a list because multiple entries are possible from some programs.
|
get |
Any NOTEs associated with the record.
An empty list if none.
|
getset |
Any restriction notice applied to the record.
Will be an empty string if none. The GEDCOM standard values are "confidential", "locked" or "privacy".
|
get |
GEDCOM Tag value.


des petits ruminants virus Peste PPRV PPR diagnostic peste []. test detection diagnosis assay assays protein disease sensitive tests clinical antibodies infection transcription amplification polymerase tools {border-style development rapid based nucleic px;} using #ffffff;} Vet field flow goats used animals antigen compared high highly lateral viral Africa diseases infected reverse sheep specific use ELISA RT-PCR cells early including isolation MinION Oxford RT-LAMP Virol chain cost detect diagnostics nanopore pen-side reaction samples sensitivity small However, University Veterinary al.Development antibody control developed eradication novel virus, wild cell immunosorbent isothermal rinderpest spread vaccine viruses wildlife Health Infect RNA acid confirmation domestic enzyme-linked genome lineage nanobodies proteins recombinase require Methods./j.jviromet... Rapid contagious countries gene molecular outbreak px; recombinant technology {font-family Anim East Emerg PPR. RT-RPA Thus, accurate acid-based field-deployable font-size gel infectious line species veterinary (Table African Animal Asia Diagnostic Dis../tbed. Diseases OIE Reverse World [], [–]. analysis animal available cases characterization competitive culture developing double; expressing global host identification immunochromatographic infections laboratory loop-mediated low methods monoclonal outbreaks region reported research risk sequencers signs single specificity strip susceptible time Agriculture Commons Creative Highly Medicine Molecular Organisation References SACIDS Virus active al.Peste availability binding border-color border-width caprine conventional coupled days easy expensive fusion holds immunoassay immunoprecipitation inexpensive integration large lineages method multiple nanobody nasal presence previously primary reagents real-time regions remote resource-limited ruminants: sequencing settings similar solid; suitable surveillance tool virusJ {font-style {font-weight (Fig. (s) Biology Centre DIVA Global IgG Infectious MAbs Master Microbiol./j.vetmic... Middle PCR Public Rumin SLAM Science Southern Suitable Table Tanzania Vero addition, affected affinity agar al.A animals. antigens assays. bold camels capacity central cold countries. courier; deployable develop different dots economic effect effective em; endemic epidemiology epitopes experimental extremely free hosts included indirect investigation lower luciferase maintenance need new northern perform performed play population primers prototype pt;} range real respectively role ruminant ruminantsVet saiga sensitive, sequence serum significant study technical threat value whilst


Personal game/rendering engine using a Vulkan backend
Introductory workshop covering the basics of the raymarching rendering technique
Real-time strategy game made with five team members in four months
Game Programmer, multiple projects


SF Movie Locations
IMDb
Plot:
Starring:
Directed by:
Genre:
Language:
{% if movie.title %}
Locations
{% if locations %}
{% for location in locations %} {% if location.locations %} {% if location.fun_facts %}
{{ location.locations }} - {{ location.fun_facts }}
{% else %}
{{ location.locations }}
{% endif %} {% else %}
Sorry, we dont have a specific address for this movie.
{% endif %} {% endfor %} {% else %}
Sorry, we dont have a specific address for this movie.
{% endif %}
{% else %}
Sorry, we dont have this movie listed on our database!
{% endif %}


Shipping Information
Email Address
Confrim Email
First Name
Last Name
Address 1
Address 2
City
State
Alabama
Alaska
Arizona
Arkansas
California
Colorado
Connecticut
Delaware
District of Columbia
Florida
Georgia
Hawaii
Idaho
Illinois
Indiana
Iowa
Kansas
Kentucky
Louisiana
Maine
Maryland
Massachusetts
Michigan
Minnesota
Mississippi
Missouri
Montana
Nebraska
Nevada
New Hampshire
New Jersey
New Mexico
New York
North Carolina
North Dakota
Ohio
Oklahoma
Oregon
PA>Pennsylvania
Rhode Island
South Carolina
South Dakota
Tennessee
Texas
Utah
Vermont
Virginia
Washington
West Virginia
Wisconsin
Wyoming
Zip
Phone
Is this address for a business?
Yes, this is a commercial address.
Company Name


I am a self-starter and a highly driven person who is always looking for a new challenge. I love solving problems and trying to find creative solutions that may not be obvious to others. Completing tasks independently and working in group settings are both pleasures for me.
EDUCATION
Fraunhofer Institute IGDJune 2015
Master Student
Master Thesis: Camera based pose estimation of HMD for medical applications.
RWTH Aachen UniversityOct 2013
Master of Electrical Engineering, Information Technology and Computer Engineering
Specialization: Computer Engineering
University of Duisburg-EssenOct 2009
Bachelor of Computer Science and Communications Engineering
China University of MTSept 2007
Bachelor of Information Security
WORK HISTORY
Fraunhofer Institute IGDSept 2015 - NOW
Research Assistant Stereo camera calibration Automatic segmentation algorithms for medical images.
ICE, RWTH AachenJul 2014 -Aug 2015
Research Assistant
Institude of Communication and Embedded System
UI development: Eclipse plug-in for an ASIP profiling and performance estimation tool.
IMST GmbHApr 2012 - Aug 2012
Student Assistant Test and evaluate the updates of Empire XCcel.
Array Antennas design up tp 6 GHz.
IMST GmbHApr 2011 - Mar 2012
Intern Construction of tutorials for FDTD simualtion tool Empire XCcel.
Test and evaluate the updates of Empire XCcel.


Programming Instructions
In order to program your DaisyDriver, first determine whether it has been programmed before.
This can be done by connecting the hardware module to a computer via USB and seeing if it is recognised as a USB device. If it is not recognised, then the module has not been programmed before and requires the bootloader to be loaded before the module can be programmed.
Burning the bootloader
- Remove power to the module and disconnect it from any other devices.
- Connect the module to a computer via a programmer. Many choices of programmer are available, and two suggestions are given below.
- Open the Arduino IDE and go to the tools menu. From there, select your programmer from the programmer drop-down. Select the board as Arduino/Genuino Micro from the Boards menu and finish by selecting burn bootloader.
- Successful programming is indicated by the Arduino IDE.
Suggestions for programmers
Whilst there are many programmers available for the Arduino ecosystem, two programmers are recommended in particular due to their ease of use and availability, respectively.
- The Arduino ISP, a dedicated programmer which is useful for cases where boards are programmed regularly.
- The Arduino as ISP, a method to use standard Arduino boards as programmers.
Once the bootloader is programmed onto the module, the module should be connected directly to power and connected to a computer via USB. It will then be recognised as a USB device, which can be programmed via the Arduino IDE.
Before the program can be uploaded, its libraries must be installed. Do this by
moving the folder Arduino-SerialCommand-Fergboard
into Arduino's libraries
folder. Once this has been done, load the file fergboard_2v2.ino
into the Arduino IDE
and program the board by clicking the Upload icon.


Born and raised in the beautiful town of San Jose, Occidental Mindoro. I moved to Cavite in 2004 and presently residing in Muntinlupa City, Metro Manila.
My career began when I joined Zuitt coding boot camp last January 2020 to learn all about being a software engineer, and I've arrived as a Full-Stack Web Developer.
My goal is to provide quality work and the best service for my clients. I am focused, takes direction and accurate. I'm detail-oriented, result-driven, dedicated, trustworthy, eager, fast, and thorough. Always try to complete my client requirements and deadline.
View ResumeI created a static website showcasing a topic or industry of my choice. I used HTML, and CSS to build the website and hosted this on gitlab.
I created a booking management system using MongoDB, Express.js and Node.js with the following functionalities: User registration and authentication; admin authorization; admin booking management; and user booking enrollment. I hosted the application via Heroku and Gitlab.
(+63)<PHONE_NUMBER>
<EMAIL_ADDRESS>Muntinlupa, Metro Manila, Philippiines


Gold inches lower on cautious optimism over U.S.-China trade
by ReutersGold eased on Monday, pressured by
optimism over U.S.-China trade ties following a report of
“constructive talks” over the weekend, but held within a tight
range as caution set in with investors awaiting concrete signals
on the negotiations.
FUNDAMENTALS
* Spot gold inched down 0.1% to $1,465.62 per ounce
at 0157 GMT, while U.S. gold futures were down 0.1%
at$1,466.80 per ounce.
* The United States and China had a high-level phone call on
Saturday, Chinese state media Xinhua said on Sunday, but it gave
no further details. The two sides discussed each other’s core
issues for the first phase of an initial trade agreement.
* Asian share markets got the week off to a muted start as
investors awaited real evidence on progress in the tariff war,
though sentiment found support from another record close on Wall
Street.
* In Hong Kong, police on Monday trapped hundreds of
protesters inside a major university and demonstrators rampaged
through a tourist district, after almost two straight days of
standoffs that have raised fears of a bloody showdown.
* Hedge funds and money managers reduced their bullish
positions in COMEX gold and silver contracts in the week to Nov.
12, the U.S. Commodity Futures Trading Commission (CFTC) said on
Friday.
* U.S. retail sales rebounded moderately in October
supported by the lowest unemployment rate in nearly 50 years,
data showed on Friday.
* Australia’s Saracen Mineral Holdings Ltd said on
Monday it would buy Canadian-listed Barrick Gold Corp’s
50% stake in the Super Pit gold mine in Western Australia for
$750 million.
* South African miner AngloGold Ashanti suspended
its gold mining operations in Guinea after a community protested
on its Siguiri mining site, its Guinea subsidiary Societe
Aurifère de Guinee (SAG) said in a statement.
DATA/EVENTS (GMT)
1500 US NAHB Housing Market Index Nov
(Reporting by Diptendu Lahiri in Bengaluru; Editing by Shailesh
Kuber)


Discord BOT Dashboard is locked with a secure authentication method that only allows users who are added into the config file to access the dashboard.
Discord BOT Dashboard ensures that your application is secure.
Discord BOT Dashboard is built with a modern UI to ensure its ease of use for anyone.
Discord BOT Dashboard is an open source project meaning anyone can contribute to make it even better.
Running your application using Discord BOT Dashboard ensures that it is stable and you wont have any errors.
Running you application using Discord BOT Dashboard allows you to have 24/7 uptime.
Discord BOT Dashboard is packed with multiple tools that are easy to use.
Develop and share plugins that can be imported into your project.
There is loads of features included in Discord BOT Dashboard but we cannot list them all!


Rename First Order of Knights.
Rename Second Order of Knights.
Rename Third Order of Knights.
Rename Fourth Order of Knights.


Preparation time
less than 30 mins
Cooking time
10 to 30 mins
Serves
Serves 4
A warming soup for a cold day, this easy blend of mussels, fennel and cream is served with toasted garlicky bread.
Clean the mussels by thoroughly scrubbing them under plenty of running water, pulling away and discarding the 'beards', the seaweed-like stringy threads. Discard any broken mussels, and any mussels that don't close tightly when you tap them.
Place the mussels in a saucepan, add the white wine and cook for 3-4 minutes.
Drain, reserving the cooking liquor, and pick the mussels from their shells. Set aside the liquor and the mussels, but discard the shells.
Heat a large frying pan and add the oil. Add the finely chopped shallot, garlic and fennel and cook for 3-4 minutes.
Add the saffron, aniseed liqueur, stock, three-quarters of the mussel meat, finish with the cream
Cook for a further 3-4 minutes until warmed through, then blend with a stick blender until smooth.
Heat a large griddle pan and drizzle the sliced bread with oil and rub with the halved clove of garlic. Toast the bread on the griddle for 2-3 minutes.


| Learning Objective |
| Binary Trees |
| Explain and implement a Binary Tree. |
| Identify the three types of tree traversals: pre-order, in-order, and post-order. |
| Explain and implement a Binary Search Tree. |
| Graphs |
| Explain and implement a Graph. |
| Traverse a graph. |
| Network Models |
| Describe the structure and function of network models from the perspective of a developer. |
| � - TCP/IP Model |
| � - OSI Model |
| IP Suite |
| Identify the correct fields of an IPv6 header. |
| Distinguish an IPv4 packet from an IPv6. |
| Describe the following subjects and how they relate to one another: IP Addresses, Domain Names, and DNS. |
| Identify use cases for the TCP and UDP protocols. |
| Describe the following subjects and how they relate to one another: MAC Address, IP Address, and a port. |
| *** OPTIONAL *** Identify the fields of a TCP segment. |
| *** OPTIONAL *** Describe how a TCP connection is negotiated. |
| Explaining the difference between network devices like a router and a switch. |
| Network Tools - (Not directly assessed) |
| Use traceroute to show routes between your computer and other computers. |
| Use Wireshark to show/inspect network traffic. |


TABLE OF INTERACTIONS WITH
RIVAROXABAN
See also: oral anticoagulants
See also: substrates at risk of CYP3A4
From the French ANSM drug interactions document of
September 2016, pp. 196-197
RIVAROXABAN RxNorm: 1114195 ATC: B01AF01 |
ANTICONVULSANT ENZYME INDUCERS CLASS CODE: N03A-001 |
Decrease of the plasma concentrations of rivaroxaban, with risk of decrease of the therapeutic effect |
Not recommended |
RIVAROXABAN RxNorm: 1114195 ATC: B01AF01 |
FLUCONAZOLE RxNorm: 4450 ATC: D01AC15 J02AC01 |
Increase of the plasma concentrations of the rivaroxaban by the fluconazole, with increase of the risk of bleeding |
Not recommended |
RIVAROXABAN RxNorm: 1114195 ATC: B01AF01 |
STRONG INHIBITORS OF CYP3A4 CLASS CODE: J02-J05 |
Increase of the plasma concentrations of rivaroxaban, with increase of the risk of bleeding |
Not recommended |
RIVAROXABAN RxNorm: 1114195 ATC: B01AF01 |
RIFAMPICIN RxNorm: 9384 ATC: J04AB02 |
Decrease of the plasma concentrations of rivaroxaban, with risk of decrease of the therapeutic effect |
Not recommended |


Home
Gallery
Characters
About
Tickets
Contact
Contact us!
Male
Female
None
Name:*
Last name:*
Address line1:*
Address line2:
Tell us your questions or give us feedback
Home
Gallery
Characters
About
Tickets
Contact


| reduce.nn {class} | R Documentation |
Reduce training set for a k-NN classifier. Used after condense
.
reduce.nn(train, ind, class)
train |
matrix for training set |
ind |
Initial list of members of the training set (from |
class |
vector of classifications for test set |
All the members of the training set are tried in random order. Any which when dropped do not cause any members of the training set to be wrongly classified are dropped.
Index vector of cases to be retained.
Gates, G.W. (1972) The reduced nearest neighbor rule. IEEE Trans. Information Theory IT-18, 431–432.
Ripley, B. D. (1996) Pattern Recognition and Neural Networks. Cambridge.
Venables, W. N. and Ripley, B. D. (2002) Modern Applied Statistics with S. Fourth edition. Springer.
train <- rbind(iris3[1:25,,1], iris3[1:25,,2], iris3[1:25,,3]) test <- rbind(iris3[26:50,,1], iris3[26:50,,2], iris3[26:50,,3]) cl <- factor(c(rep("s",25), rep("c",25), rep("v",25))) keep <- condense(train, cl) knn(train[keep,], test, cl[keep]) keep2 <- reduce.nn(train, keep, cl) knn(train[keep2,], test, cl[keep2])


Home
My Profile
Scripts
Scripts
Random Number from Text (with permalink)
Your 10,000-th Day
back to home


{% macro adv_table(header, columns, rows) %}
| {{c}} | {% endfor %}
|---|
| {{d}} | {% endfor %}
DataTables is a very flexible, advanced tables plugin for jQuery. In SB Admin, we are using a specialized version of DataTables built for Bootstrap 3. We have also customized the table headings to use Font Awesome icons in place of images. For complete documentation on DataTables, visit their website at https://datatables.net/.
View DataTables Documentation


Canadian Financial Reporting
Primary Financial Statements (PFS) Taxonomy
According to Canadian GAAP
|
This taxonomy provides accounting terms that are used in general purpose financial statements that are prepared in accordance with Canadian Generally Accepted Accounting Principles (GAAP). XBRL Canada does not claim that this taxonomy is comprehensive. Organizations using this taxonomy may need to add an extension taxonomy. |
|
|
XBRL Canada |
|
|
2007-01-19 |
|
|
XBRL Canada Acknowledged on 2007-01-19, issued in accordance with XBRL Canada Internal Approval Process. XBRL International Acknowledged on 2007-?-?, issued in accordance with XBRL International Taxonomy Recognition Process. This taxonomy is an update of the previously acknowledged Canadian PFS Taxonomy of 2004-11-20 to incorporate changes in accounting standards in the intervening period and to improve documentation. |
|
|
XBRL International Acknowledged |
|
|
XBRL Specification Version 2.1, dated 2003-12-31 plus errata corrections dated 2006-12-18 |
|
|
Gerald Trites<EMAIL_ADDRESS>Chantal Rassart<EMAIL_ADDRESS>|
|
|
The XBRL Canada Domain workgroup accepted this taxonomy 2007-01-08 and sent it to the Canadian Steering Committee (CSC). The CSC acknowledged it on 2007-01-19 and sent it to the XBRL International Inc for International acknowledgement. XBRL International acknowledged it on 2007-01-24. |
|
|
http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19 |
|
|
ca-gaap-pfs |
|
|
http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.xsd (Schema) http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-reference.xml (Reference linkbase) http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-label.xml (Label linkbase) http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-presentation.xml (Presentation linkbase) http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-calculation.xml (Calculation linkbase) http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-definition.xml (Definition linkbase) |
|
|
http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.pdf (Adobe Acrobat PDF format) |
|
|
http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.zip (zip file containing taxonomy and documentation only) |
|
|
|
A copy of all the taxonomy files will also be available on the XBRL Canada website at www.xbrl.ca. http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.xsd (Schema) http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-reference.xml (Reference linkbase) http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-label.xml (Label linkbase) http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-presentation.xml (Presentation linkbase) http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-calculation.xml (Calculation linkbase) http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19-definition.xml (Definition linkbase) |
|
Physical location of copy of Summary document on www.xbrl.ca
|
A copy of the summary document files will also be available on the XBRL Canada website at www.xbrl.ca. http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.pdf (Adode Acrobat PDF format)
|
|
A copy of a zip file containing the taxonomy and documentation will also be available on the XBRL Canada website at www.xbrl.ca. http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.zip (zip file)
|
|
|
None. |
|
|
Copyright © 2007-01-19, XBRL Canada Copyright © [Date of acknowledgement], XBRL International This taxonomy and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that: 1. The above copyright notice and this paragraph are included on all such copies and derivative works. 2. A link or URL to the original taxonomy is included in all such copies and derivative works. However, this taxonomy itself may not be modified in any way, such as by removing the copyright notice or references to XBRL International or other organizations, except as required to translate it into languages other than English. Members of XBRL International and the taxonomy owners agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal). The name and trademarks of XBRL International may NOT be used in advertising or publicity pertaining to this document or its contents without specific, written prior permission. Title to copyright in this document will at all times remain with copyright holders. By using and/or copying this taxonomy, you (the licensee) agree that you have read, understood, and will comply with the terms and conditions set out in this document and in the Copyright, Intellectual Property and Trademarks documents on www.xbrl.org/legal This taxonomy and its associated files are provided on an "AS IS" basis and XBRL INTERNATIONAL AND THE OWNERS OF THE TAXONOMY DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Recipients of this taxonomy are invited to submit, with their comments, notification of any relevant patent rights and copyrights of which they are aware and to provide supporting documentation. The attention of users of this taxonomy is directed to the possibility that its use may require use of an invention covered by patent rights. XBRL International and the owners of the taxonomy shall not be responsible for identifying patents for which a license may be required by this taxonomy, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. This taxonomy is prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. XBRL International and the owners of this taxonomy takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology defined by implied by the taxonomy or the extent to which any license under such rights might or might not be available; neither do they represent that they has made any effort to identify any such rights. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (www.xbrl.org/legal).  IN NO EVENT WILL XBRL
INTERNATIONAL OR THE OWNERS OR AUTHORS OF THE TAXONOMY BE LIABLE TO ANY USER
OR ANY THIRD PARTY FOR THE COST OF PROCURING SUBSTITUTE GOODS OR SERVICES,
LOST PROFITS, LOSS OF USE, LOSS OF DATA OR ANY DIRECT, INDIRECT,
CONSEQUENTIAL, INCIDENTAL, PUNITIVE OR SPECIAL DAMAGES, WHETHER UNDER
CONTRACT, TORT, WARRANTY OR OTHERWISE, ARISING IN ANY WAY OUT OF THE USE OF
THIS TAXONOMY OR ITS ASSOCIATED FILES, OR THE PERFORMANCE OR IMPLEMENTATION
OF THE CONTENTS THEREOF OF ANY TYPE WHATSOEVER, WHETHER OR NOT SUCH PARTY HAD
ADVANCE NOTICE OF THE POSSIBILITY OF SUCH DAMAGES. |
|
|
This XBRL Canada acknowledged taxonomy and all related
documentation (the “taxonomy”) is made available as a public service only and
on an “as is” basis only, and XBRL Canada and each of its members to the
fullest extent permitted by law make no, and expressly disclaim all,
representations, warranties and conditions, whether express or implied,
regarding same, including without limitation regarding merchantability,
non-infringement of third parties’ rights, and fitness for particular
purpose, and regarding the accuracy, reliability, or completeness of the
taxonomy or results using same. |
Gerald Trites, XBRL Canada
Principal editors of the taxonomy (listed alphabetically)
Eric E. Cohen, CPA, PricewaterhouseCoopers LLP
Grace Lang, CA, Canadian Institute of Chartered Accountants
Chantal Rassart, Deloitte Touche
Gerald Trites, XBRL Canada
Hugh Wallis, Standard Dimensions
Andrew Webber, World Wide Webbers Incorporated
Taxonomy builder software and help provided
Fujitsu Taxonomy Editor and Instance Developer
Taxonomy validation tools and help provided
Fujitsu Taxonomy Editor and Instance Developer
Semansys Taxonomy Viewer
DecisionSoft True North
UBmatrix validator
This taxonomy provides accounting terms that are used in the Primary Financial Statements (PFS) prepared according to Canadian Generally Accepted Accounting Principles (GAAP). This taxonomy is an update of the taxonomy acknowledged in 2004-11-20, which was initially developed from the US GAAP CI taxonomy and uses common element names. The CA-GAAP-PFS Taxonomy has been prepared by the XBRL CA Domain Working Group, with help from other contributors, including other members of XBRL International and XBRL US.
This taxonomy is compliant with the XBRL Specification Version 2.1. (http://www.xbrl.org/resourcecenter/). This taxonomy is to be used in conjunction with other taxonomies to create XBRL instance documents compliant with Canadian GAAP dealing with financial reporting data. Specifically, the CA-GAAP-PFS taxonomy presents the basic concepts used in the Balance Sheet, the Statement of Changes in Equity, the Income Statement, the Statement of Comprehensive Income and the Statement of Cash Flows.
This document assumes a general understanding of accounting and XBRL. Anyone desiring additional information relating to XBRL should consult the XBRL Canada website (http://www.xbrl.ca) and the XBRL International website (http://www.xbrl.org).
Table of Contents
Physical location of taxonomy files
Physical location of copy of taxonomy files on www.xbrl.ca
Physical location of copy of Summary document on www.xbrl.ca
Physical location of copy of Zip file on www.xbrl.ca
References to other taxonomies
Principal editors of the taxonomy (listed alphabetically)
Taxonomy builder software and help provided
Taxonomy validation tools and help provided
Commonality with US GAAP Taxonomy
This taxonomy was prepared by XBRL Canada on behalf of the CICA and the Canadian Accounting Standards Board (AcSB). It is not the intent of this taxonomy to create an accounting standard, but to record the semantics for the Canadian standard (GAAP) in XBRL. However, there has been no examination of the taxonomy by either of the above organizations nor has such an examination been requested and approval or publishing of this taxonomy by XBRL Canada does not indicate or imply any declaration or guarantee of comprehensiveness by XBRL Canada nor any guarantee by the CICA, the Canadian Accounting Standards Board or any of the members of XBRL Canada. (See Disclaimer in documentation summary.)
This taxonomy has been created to be compliant with XBRL Specification Version 2.1. This taxonomy has been made compliant with FRTA (Financial Reporting Taxonomy Architecture).
This taxonomy has been Acknowledged by the Canadian Steering Committee on 2007-01-19 after extensive work by the XBRL Canada’s Domain Workgroup. It was acknowledged by the XBRL International Inc. on 2007-01-24. This taxonomy will be used primarily in conjunction with other taxonomies under development and to be developed, the Canadian Notes taxonomy and the Canadian MD&A (Management’s Discussion and Analysis) taxonomy. While this is an Acknowledged taxonomy, any errata reported will be corrected, comments addressed and any important gaps filled. The authoritative references are primarily to the CICA handbook.
The terminology used in this document frequently overlaps with terminology from other disciplines. The following definitions are provided to help explain the use of basic XBRL terms:
|
Taxonomy |
An XBRL Taxonomy typically consists of an XML Schema-compliant .xsd file that contains XBRL elements (XML elements that are defined by XBRL-specific attributes) and its connected linkbases (.xml files). |
|
Schema |
A schema is a map of the logical data structure of information. |
|
Element |
An XBRL element is the XBRL name of a “fact” or piece of information described in an XBRL taxonomy. |
|
Linkbase |
A linkbase provides additional information about XBRL elements, in particular, relationships between them. Linkbases used by XBRL are compliant with the World Wide Web Consortium’s (W3C) XML Linking Language (XLink) Recommendation. |
|
Instance document |
An instance document is an XML file that includes at least one XBRL element. |
|
DTS (Discoverable Taxonomy Set) |
A DTS consists of several XBRL taxonomies (consisting of schemas and/or linkbases – .xsd and .xml files), which together enable an organization to create a financial or other business report. It is likely that any extensive financial or other business report will use a DTS or combination of taxonomies rather than a single taxonomy alone. |
|
Extension Taxonomy |
An extension taxonomy is one that extends an XBRL taxonomy by adding new schemas containing elements or linkbases containing additional information about the XBRL elements. |
This taxonomy should be used by those who prepare Primary Financial Statements according to Canadian Generally Accepted Accounting Principles (GAAP).
The goal of XBRL Canada is to develop a set of taxonomies to enable organisations to create a comprehensive set of XBRL financial reports in Canada. This will include the ability to create financial statements reports according to Canadian GAAP. The current workplan is to:
The goal in developing the PFS taxonomy, published here, is to build a taxonomy that captures the most commonly used elements in Primary Financial Statements. This is not meant to be a comprehensive set of elements.
With the publication of this taxonomy, XBRL Canada aims to support efforts of the Canadian financial community to report using XBRL. As more organisations report in XBRL, the demand for XBRL reports will expand, more XBRL software will be built, and more financial software will become XBRL-compliant. Preparing documents using this taxonomy will facilitate the understanding, exchange and transparency of financial statements.
Commonality with US GAAP Taxonomy
This taxonomy was originally based on the US GAAP CI taxonomy. It uses many common element names. Common element names are used when the Canadian and US concepts were deemed to be substantially the same by Canadian domain experts. Notwithstanding the above, use of the same element name does not imply any assertion, declaration or guarantee that the concepts are the same. At times, Canadian labels (names of XBRL elements as used by people) differ from those in the US. This should not be taken to indicate that the accounting concepts are different. In cases when the Canadian taxonomy uses concepts that are not the same as those used in the US, the XBRL naming convention was used to create the element names.
The first Internal Working Draft was issued on August 27, 2003. After substantial improvements to the taxonomy, the Domain/Taxonomy workgroup of XBRL Canada requested the Canadian Steering Committee to issue a second Internal Working Draft. At its meeting of October 22, 2003, the Canadian Steering Committee concurred and a Second Internal Working Draft was issued on October 27, 2003. Upon the recommendation of the Canadian Domain/Taxonomy workgroup, the Canadian Steering Committee agreed to publish this as an XBRL Canada Public Working Draft on December 4, 2003. After an extensive Public Working Draft period, revisions were made to the taxonomy. Upon the recommendation of the Canadian Domain/Taxonomy workgroup, it was approved by the Canadian Steering Committee on February 18, 2004. On March 17, 2004, after passing the validation tests set by the Specification workgroup, this PFS taxonomy was granted Acknowledged status by XBRL International. This taxonomy was converted to be compliant with specification 2.1, errors were addressed and the label linkbase was expanded to include both English and French labels and documentation. The original taxonomy was sent to the the Canadian Steering Committee by the Domain workgroup on November 23, 2004, was acknowledged by the CSC on November 25, 2004 and acknowledged by XBRL International Inc on November 29, 2004.
This taxonomy is using the namespace, http://www.xbrl.org/ca/fr/gaap/pfs/ca-gaap-pfs-2007-01-19 and ca-gaap-pfs as the recommended namespace prefix. The authoritative copy of this taxonomy is located on the XBRL International website at http://www.xbrl.org/ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.xsd. An exact copy is available on XBRL Canada’s website at http://www.xbrl.ca/fr/gaap/pfs/2007-01-19/ca-gaap-pfs-2007-01-19.xsd.
This Canadian taxonomy has labels and annotations in both of Canada’s official languages, in English and in French.
Errata in the taxonomy will be published as and when necessary. Corrections will be made to the spec 2.1 version of this taxonomy to be Approved.
This taxonomy and documentation regarding it and any translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to XBRL International or XBRL organizations, except as required to translate it into languages other than English. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (http://www.xbrl.org/Legal2/XBRL-IP-Policy-2003-04-25.pdf).

The attention of users of this document is directed to the possibility that compliance with or adoption of XBRL International specifications may require use of an invention covered by patent rights. XBRL International shall not be responsible for identifying patents for which a license may be required by any XBRL International specification, or for conducting legal inquiries into the legal validity or scope of those patents that are brought to its attention. XBRL International specifications are prospective and advisory only. Prospective users are responsible for protecting themselves against liability for infringement of patents. XBRL International takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Members of XBRL International agree to grant certain licenses under the XBRL International Intellectual Property Policy (http://www.xbrl.org/Legal2/XBRL-IP-Policy-2003-04-25.pdf).
© 2007 XBRL Canada and XBRL International. ® All Rights Reserved. XBRL International liability rules apply.


THE MESSENGER IS A MEDIUM
THE MESSENGER Directed by Luc Besson Screenplay by Besson & Andrew Berkin With Milla Jovovich, John Malkovich
With "The Messenger", Luc Besson fulfills the promise he showed in "The Fifth Element". That one was confused and pretty bad. This one is truly awful. Begin with little 8-year-old Joan (Jan Valentine), after her umpteenth confession of the day, dancing through fields of flowers like a miniature Julie Andrews on the road to Oz, flinging her arms wide and chortling "It's wonderful!" Throw in "Koyaanisqatsi"-esque churning clouds and weird "Paul-is-dead"-ish backwards music on the soundtrack to show that the day is taking an ominous turn, and then home to find the town pillaged by the villainous English, and her sister raped and murdered (not in that order) before her eyes. Then things really get bad. Enter Milla Jovovich (the "big bada-boom" girl from husband Besson's "Fifth Element") as 19-year-old Joan. She's learned to ride a horse and wield a sword, and heard enough voices and made enough waves in her part of France to convince the sniveling Dauphin (John Malkovich) to grant her an audience, although we have no idea why except that his mother-in-law (Faye Dunaway, so refreshed with her puffy lips and taut skin that she looks like she's standing in a wind tunnel) puts him up to it. Half of France, including the part he needs for his coronation, is in the hands of the barbarian English, and he'll try anything once. If the Dauphin seems a bit genetically flawed, Joan is a full-bore nut case. She's so wild-eyed and hysterical you're afraid she'll have a stroke before the English can burn her. She finds the Dauphin in a cute game of hide-and-seek and he gives her an army. The generals take to her with surprisingly little resistance, and soon they're all hacking and hewing away at the English, and for most of the rest of the movie her face is drenched in blood. She's impervious to pain -- "How are you, Joan?" one of her officers asks during a battle. "Me? I'm fine. Why do you ask?" "There's an arrow in your leg." "Oh." If only we were so impervious to pain. By the time she's been betrayed by the Dauphin and captured by the English, visited in her cell by her Conscience in the form of a spectral Dustin Hoffman (sounding like his previous assignment was in the Bronx), been through a few trials and more betrayals, the two-hour mark is a distant memory, and you're feeling as though you're at Zozobra*, waiting with diminishing patience for the main event.
*Zozobra is an annual end-of-summer event at Fiesta in Santa Fe, NM, which involves, after endless preliminary carryings-on, the burning of a giant effigy of Old Man Gloom.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


Across: 1. Perhaps Osama's second car (5) 5. Operation Cheer Celebrity (5) 9. Pit to back up to? (3) 10. Bird barrier in plant (7) 15. Previous note about.. (3) 16. ...old urban centre (2) 17. Cheer for silver lining? (2-2) 18. Heartfelts in doggy type of fiction (4) 20. Return from gratis? (2) 21. Clothing tube (4) 22. That's a ruler (4) 24. Post-movement? (4) 26. Each service relaxes (5) 29. So to arrange source of C60 perhaps (4) 31,46,11-Down. www.machinations (6,6,6) 33. Quarter-flavour (6) 35. Egghead programming style? (2) 36. Confused (34-Down) PC views (7) 37. Note? No no! (2) 38. Batting a bit? (2) 40. Breeze partially returned swing (7) 43. That showed it! (2) 44. Encountered most holy spirit (6) 46. see 31-Across 48. Tolerate animal (4) 49. see 19-Down 50. In 7/11 like 7-11 (4) 52. Tiptop muscles for thumbing (4) 54. Lease sounds superior (4) 56. Should one fail? (2) 58. Still one monster (4) 60. Becomes deficient of first stage (4) 61. Nurse the old (2) 62. Some men rank organisation (3) 64. Magazine has directions with papers (7) 65. Rotary milk? (3) 66. One in grislier extremes - he's doomed (5) 67. One in miserly extremes - basic (34-Down) (5) Down: 1. Farms hunks (5) 2. Suggest sloth, right? (3) 3. Happy state of India (2) 4. Is repeatedly a deity (4) 5. Slow-moving birds (4) 6. About religion (2) 7. Partial / impartial use of media (3) 8. Core male (7-Down) (5) 11. see 31-Across 12. Restricted in Mao's China (2) 13. Some help! (2) 14. Exposes alien origin (6) 17. Chance to jump East (4) 19,49-Across. Cross a hurdle badly, past seats (4,1,4) 21. Cheer for Prancer? (2,2) 23. Cheer for origin (4) 25. Twice as crazy - to wit, me (3-4) 27. Snake-stop surface (7) 28. Shuns directions and considers (7) 30. Narrow as a road on a railway on an estuary top (3,4) 32. Mother near the heart? (5) 34. Possession as arranged (5) 39. Straight one ate heart (4) 41. Assorts cooks? (6) 42. Blemish her instrument (6) 43. With top hotel I have a busy place (4) 45. T-beam bearer (4) 47. Other's (not to return) (4) 48. Provide BO (5) 51 (65-Down) badly in city lacking confidence. (5) 53. Some beverage! (4) 55. Subject - measure object (4) 57. Back loud or back? (3) 59. Wisdom in antiquity (2) 60. Fighter returns (2) 61. View selected selection (3) 63. Article in manual (2) 65. Some porno nurse? (2)