| Total net profit | -40.59 | Gross profit | 64.79 | Gross loss | -105.38 |
| Profit factor | 0.61 | Expected payoff | -0.26 | ||
| Absolute drawdown | -40.59 | Maximal drawdown (%) | 42.26 (2530.54%) | ||
| Total trades | 157 | Profit trades (% of total) | 60 (38.22%) | Loss trades (% of total) | 97 (61.78%) |
| Long positions (won %) | 69 (53.62%) | Short positions (won %) | 88 (26.14%) | ||
| Largest | profit trade | 2.6 | loss trade | -2.91 | |
| Average | profit trade | 1.08 | loss trade | -1.09 | |
| Minimum | profit trade | 0.09 | loss trade | -0.16 | |
| Maximum | take profit in pips | 26.6 | stop loss in pips | -28.3 | |
| Average | take profit in pips | 12.3 | stop loss in pips | -11.5 | |
| Minimum | take profit in pips | -1.8 | stop loss in pips | -3.3 | |
| Maximum | Reward-Risk | 8.1 | Duration in minutes | 4174 | |
| Average | Reward-Risk | 1.3 | Duration in minutes | 352.4 | |
| Minimum | Reward-Risk | 0.0 | Duration in minutes | 2 | |
| Maximum | consecutive wins (profit in money) | 6.0 (4.11) | consecutive losses (loss in money) | 8.0 (-7.95) | |
| Average | consecutive wins | 1.0 | consecutive losses | 2.0 |
| Total net profit | -3.58 | Gross profit | 35.56 | Gross loss | -39.14 |
| Profit factor | 0.91 | Expected payoff | -0.05 | ||
| Absolute drawdown | -4.35 | Maximal drawdown (%) | 13.17 (149.32%) | ||
| Total trades | 69 | Profit trades (% of total) | 37 (53.62%) | Loss trades (% of total) | 32 (46.38%) |
| Largest | profit trade | 2.23 | loss trade | -2.91 | |
| Average | profit trade | 0.96 | loss trade | -1.22 | |
| Minimum | profit trade | 0.09 | loss trade | -0.16 | |
| Maximum | take profit in pips | 22.4 | stop loss in pips | -28.3 | |
| Average | take profit in pips | 10.4 | stop loss in pips | -13.2 | |
| Minimum | take profit in pips | -1.8 | stop loss in pips | -6.8 | |
| Maximum | Reward-Risk | 3.1 | Duration in minutes | 3087.0 | |
| Average | Reward-Risk | 0.9 | Duration in minutes | 410.9 | |
| Minimum | Reward-Risk | 0.0 | Duration in minutes | 3.0 | |
| Maximum | consecutive wins (profit in money) | 7.0 (5.42) | consecutive losses (loss in money) | 6.0 (-9.1) | |
| Average | consecutive wins | 2.0 | consecutive losses | 2.0 |
| Total net profit | -37.01 | Gross profit | 29.23 | Gross loss | -66.24 |
| Profit factor | 0.44 | Expected payoff | -0.42 | ||
| Absolute drawdown | -37.01 | Maximal drawdown (%) | 35.71 (-2746.92%) | ||
| Total trades | 88 | Profit trades (% of total) | 23 (26.14%) | Loss trades (% of total) | 65 (73.86%) |
| Largest | profit trade | 2.6 | loss trade | -2.04 | |
| Average | profit trade | 1.27 | loss trade | -1.02 | |
| Minimum | profit trade | 0.11 | loss trade | -0.34 | |
| Maximum | take profit in pips | 26.6 | stop loss in pips | -23.3 | |
| Average | take profit in pips | 13.8 | stop loss in pips | -10.2 | |
| Minimum | take profit in pips | 1.0 | stop loss in pips | -3.3 | |
| Maximum | Reward-Risk | 8.1 | Duration in minutes | 4174.0 | |
| Average | Reward-Risk | 1.6 | Duration in minutes | 306.6 | |
| Minimum | Reward-Risk | Duration in minutes | 2.0 | ||
| Maximum | consecutive wins (profit in money) | 3.0 (1.98) | consecutive losses (loss in money) | 10.0 (-8.23) | |
| Average | consecutive wins | 1.0 | consecutive losses | 3.0 |


NF-kappa B controls expression of inhibitor I kappa B alpha: evidence for an inducible autoregulatory pathway.
Abstract
The eukaryotic transcription factor nuclear factor-kappa B (NF-kappa B) participates in many parts of the genetic program mediating T lymphocyte activation and growth. Nuclear expression of NF-kappa B occurs after its induced dissociation from its cytoplasmic inhibitor I kappa B alpha. Phorbol ester and tumor necrosis factor-alpha induction of nuclear NF-kappa B is associated with both the degradation of performed I kappa B alpha and the activation of I kappa B alpha gene expression. Transfection studies indicate that the I kappa B alpha gene is specifically induced by the 65-kilodalton transactivating subunit of NF-kappa B. Association of the newly synthesized I kappa B alpha with p65 restores intracellular inhibition of NF-kappa B DNA binding activity and prolongs the survival of this labile inhibitor. Together, these results show that NF-kappa B controls the expression of I kappa B alpha by means of an inducible autoregulatory pathway.


When you connect the Digital Chroma to a network, and attempt to access the "Chroma1" device from another computer, it will show a single folder called "chroma" (these names may be displayed in upper case) but when you try to open this folder, a login prompt will appear. You may use any username you like\mthe Chroma ignores it\mbut you must also enter the proper password before access is allowed.
Passwords are always 10-digit numbers, and the built-in default password is "1234567890". If you want to change this password, select calibration 42. The display shows ten hyphens, which are replaced as you enter a new ten-digit number using switches 1 through 10 (where 10 means zero). The password isn't actually changed until you exit the calibration mode with STORE; if you don't enter the full ten digits, the password won't be changed.
Note that the Chroma won't show you the current password, but if you forget it, you can just invent a new one; it isn't necessary to know the existing password in order to change it. It is assumed that you have control over your own instrument; the password is only to provide some protection if you plug into a network that has other users on it.


OVRT Chroma Key
Choose File
Connect
Submit Bug
Made by kingofaces2 and Captain Autismo
Your Web browser doesn't support Iframes


--- layout: post status: publish published: true title: Greg Maddux Plaque Will Have Cap Without Logo in Hall of Fame author: display_name: Corey Fineran login: Corey email<EMAIL_ADDRESS>url: '' author_login: Corey author_email<EMAIL_ADDRESS>wordpress_id: 8708 wordpress_url: http://ivyenvy.com/?p=8708 date: '2014-01-23 13:45:59 +0000' date_gmt: '2014-01-23 19:45:59 +0000' categories: - General Baseball - Former Cubs tags: - Greg Maddux - Hall of Fame - Atlanta Braves comments: - id: 9024 author: Arty Bouchez author_email: '' author_url: '' date: '2014-01-23 16:55:51 +0000' date_gmt: '2014-01-23 22:55:51 +0000' content: Wow! The HOF just can't make up their mind can they? I can understand the reasoning behind his & Larussa but what was the problem with Dawson, my favorite player growing up, wanting a Cubs logo but MLB "forced" an Expos logo? Maybe a good decision since a lot of players with be playing for multiple teams and it might be hard for one team to be chosen for the plaque unless it's completely clear what team should be chosen. For example, if and when, Todd Helton gets elected that would be clearly a Colorado Rockies logo. - id: 9025 author: Ivy Envy author_email: '' author_url: '' date: '2014-01-23 17:30:37 +0000' date_gmt: '2014-01-23 23:30:37 +0000' content: I say just leave it up to the player. I don't know at all, but I wonder if the Dawson thing was kind of tossing those poor schmucks up north of the border (Ian from Montreal) a bone. - id: 9463 author: JasonKhounlo author_email<EMAIL_ADDRESS>author_url: '' date: '2014-02-08 03:53:57 +0000' date_gmt: '2014-02-08 09:53:57 +0000' content: "seems good, I always check this website for more info about snapbacks caps. \nhttp://www.snapbackscapscheap.com/" ---
Greg Maddux and Tony LaRussa will both enter the Hall of Fame with no logos on the caps of their plaques. Like most Cubs fans, I expected Maddux to enter the Hall of Fame with an Atlanta Braves cap.
It was his years in Atlanta that put Maddux in the Hall. He is probably the most Hall of Fame worthy player of my lifetime and I consider myself lucky to have been able to see him pitch in a Cubs uniform.
I would assume that most Braves fans feel this is a slap in the face, and I think that it's a justified reaction. Then again, the fact that he didn't pitch all of those years on the North Side is a slap in the face for Cubs fans.
In an era of baseball that will always be tarnished, we will be able to show future generations some of Maddux's unbelievable statistics and tell them what it was like to watch him pitch, regardless of the uniform he wore.


This app has been generated using angular-cli and PrimeNG application blueprint. This uses the newly added option --app-blueprint of angular-cli. Here is a sample example to generate application using primeNG blueprint:
ng new -ab primeng foo
or
ng new --app-blueprint primeng foo


Hypothyroid Predictor
Age
Sex
Male
Female
On Thyroxine
Yes
No
Query on Thyroxine
Yes
No
On Antithyroid medication
Yes
No
Thyroid surgery
Yes
No
Query Hypothyroid
Yes
No
Query Hyperthyroid
Yes
No
Pregnant
Yes
No
Sick
Yes
No
Tumor
Yes
No
OnThyroxine
Yes
No
Lithium
Yes
No
Goitre
Yes
No
TSH measured
Yes
No
TSH
T3 measured
Yes
No
T3
TT4 measured
Yes
No
TT4
T4U measured
Yes
No
T4U
OnThyroxine
Yes
No
FTI measured
Yes
No
FTI
TBG measured
Yes
No
Predict
{{predicted}}
Go to Home Page


| Interface | Description |
|---|---|
| Attr |
The
Attr interface represents an attribute in an
Element object. |
| CDATASection |
CDATA sections are used to escape blocks of text containing characters that
would otherwise be regarded as markup.
|
| CharacterData |
The
CharacterData interface extends Node with a set of
attributes and methods for accessing character data in the DOM. |
| Comment |
This interface inherits from
CharacterData and represents the
content of a comment, i.e., all the characters between the starting '
<!-- ' and ending '--> '. |
| Document |
The
Document interface represents the entire HTML or XML
document. |
| DocumentFragment |
DocumentFragment is a "lightweight" or "minimal"
Document object. |
| DocumentType |
Each
Document has a doctype attribute whose value
is either null or a DocumentType object. |
| DOMConfiguration |
The
DOMConfiguration interface represents the configuration
of a document and maintains a table of recognized parameters. |
| DOMError |
DOMError is an interface that describes an error. |
| DOMErrorHandler |
DOMErrorHandler is a callback interface that the DOM
implementation can call when reporting errors that happens while
processing XML data, or when doing some other processing (e.g. |
| DOMImplementation |
The
DOMImplementation interface provides a number of methods
for performing operations that are independent of any particular instance
of the document object model. |
| DOMImplementationList |
The
DOMImplementationList interface provides the abstraction
of an ordered collection of DOM implementations, without defining or
constraining how this collection is implemented. |
| DOMImplementationSource |
This interface permits a DOM implementer to supply one or more
implementations, based upon requested features and versions, as specified
in DOM
Features.
|
| DOMLocator |
DOMLocator is an interface that describes a location (e.g. |
| DOMStringList |
The
DOMStringList interface provides the abstraction of an
ordered collection of DOMString values, without defining or
constraining how this collection is implemented. |
| Element |
The
Element interface represents an element in an HTML or XML
document. |
| Entity |
This interface represents a known entity, either parsed or unparsed, in an
XML document.
|
| EntityReference |
EntityReference nodes may be used to represent an entity
reference in the tree. |
| NamedNodeMap |
Objects implementing the
NamedNodeMap interface are used to
represent collections of nodes that can be accessed by name. |
| NameList |
The
NameList interface provides the abstraction of an ordered
collection of parallel pairs of name and namespace values (which could be
null values), without defining or constraining how this collection is
implemented. |
| Node |
The
Node interface is the primary datatype for the entire
Document Object Model. |
| NodeList |
The
NodeList interface provides the abstraction of an ordered
collection of nodes, without defining or constraining how this collection
is implemented. |
| Notation |
This interface represents a notation declared in the DTD.
|
| ProcessingInstruction |
The
ProcessingInstruction interface represents a "processing
instruction", used in XML as a way to keep processor-specific information
in the text of the document. |
| Text |
The
Text interface inherits from CharacterData
and represents the textual content (termed character data in XML) of an Element or Attr . |
| TypeInfo |
The
TypeInfo interface represents a type referenced from
Element or Attr nodes, specified in the schemas
associated with the document. |
| UserDataHandler |
When associating an object to a key on a node using
Node.setUserData() the application can provide a handler
that gets called when the node the object is associated to is being
cloned, imported, or renamed. |
| Exception | Description |
|---|---|
| DOMException |
DOM operations only raise exceptions in "exceptional" circumstances, i.e.,
when an operation is impossible to perform (either for logical reasons,
because data is lost, or because the implementation has become unstable).
|
| Class | Description |
|---|---|
| DOMImplementationRegistry |
A factory that enables applications to obtain instances of
DOMImplementation . |
| Interface | Description |
|---|---|
| Counter |
The
Counter interface is used to represent any counter or
counters function value. |
| CSS2Properties |
The
CSS2Properties interface represents a convenience
mechanism for retrieving and setting properties within a
CSSStyleDeclaration . |
| CSSCharsetRule |
The
CSSCharsetRule interface represents a @charset rule in a
CSS style sheet. |
| CSSFontFaceRule |
The
CSSFontFaceRule interface represents a @font-face rule in
a CSS style sheet. |
| CSSImportRule |
The
CSSImportRule interface represents a @import rule within
a CSS style sheet. |
| CSSMediaRule |
The
CSSMediaRule interface represents a @media rule in a CSS
style sheet. |
| CSSPageRule |
The
CSSPageRule interface represents a @page rule within a
CSS style sheet. |
| CSSPrimitiveValue |
The
CSSPrimitiveValue interface represents a single CSS value
. |
| CSSRule |
The
CSSRule interface is the abstract base interface for any
type of CSS statement. |
| CSSRuleList |
The
CSSRuleList interface provides the abstraction of an
ordered collection of CSS rules. |
| CSSStyleDeclaration |
The
CSSStyleDeclaration interface represents a single CSS
declaration block. |
| CSSStyleRule |
The
CSSStyleRule interface represents a single rule set in a
CSS style sheet. |
| CSSStyleSheet |
The
CSSStyleSheet interface is a concrete interface used to
represent a CSS style sheet i.e., a style sheet whose content type is
"text/css". |
| CSSUnknownRule |
The
CSSUnknownRule interface represents an at-rule not
supported by this user agent. |
| CSSValue |
The
CSSValue interface represents a simple or a complex
value. |
| CSSValueList |
The
CSSValueList interface provides the abstraction of an
ordered collection of CSS values. |
| DocumentCSS |
This interface represents a document with a CSS view.
|
| DOMImplementationCSS |
This interface allows the DOM user to create a
CSSStyleSheet
outside the context of a document. |
| ElementCSSInlineStyle |
Inline style information attached to elements is exposed through the
style attribute. |
| Rect |
The
Rect interface is used to represent any rect value. |
| RGBColor |
The
RGBColor interface is used to represent any RGB color
value. |
| ViewCSS |
This interface represents a CSS view.
|
| Interface | Description |
|---|---|
| DocumentEvent |
The
DocumentEvent interface provides a mechanism by which the
user can create an Event of a type supported by the implementation. |
| Event |
The
Event interface is used to provide contextual information
about an event to the handler processing the event. |
| EventListener |
The
EventListener interface is the primary method for
handling events. |
| EventTarget |
The
EventTarget interface is implemented by all
Nodes in an implementation which supports the DOM Event
Model. |
| MouseEvent |
The
MouseEvent interface provides specific contextual
information associated with Mouse events. |
| MutationEvent |
The
MutationEvent interface provides specific contextual
information associated with Mutation events. |
| UIEvent |
The
UIEvent interface provides specific contextual information
associated with User Interface events. |
| Exception | Description |
|---|---|
| EventException |
Event operations may throw an
EventException as specified in
their method descriptions. |
| Interface | Description |
|---|---|
| HTMLAnchorElement |
The anchor element.
|
| HTMLAppletElement |
An embedded Java applet.
|
| HTMLAreaElement |
Client-side image map area definition.
|
| HTMLBaseElement |
Document base URI.
|
| HTMLBaseFontElement |
Base font.
|
| HTMLBodyElement |
The HTML document body.
|
| HTMLBRElement |
Force a line break.
|
| HTMLButtonElement |
Push button.
|
| HTMLCollection |
An
HTMLCollection is a list of nodes. |
| HTMLDirectoryElement |
Directory list.
|
| HTMLDivElement |
Generic block container.
|
| HTMLDListElement |
Definition list.
|
| HTMLDocument |
An
HTMLDocument is the root of the HTML hierarchy and holds
the entire content. |
| HTMLDOMImplementation |
The
HTMLDOMImplementation interface extends the
DOMImplementation interface with a method for creating an
HTML document instance. |
| HTMLElement |
All HTML element interfaces derive from this class.
|
| HTMLFieldSetElement |
Organizes form controls into logical groups.
|
| HTMLFontElement |
Local change to font.
|
| HTMLFormElement |
The
FORM element encompasses behavior similar to a collection
and an element. |
| HTMLFrameElement |
Create a frame.
|
| HTMLFrameSetElement |
Create a grid of frames.
|
| HTMLHeadElement |
Document head information.
|
| HTMLHeadingElement |
For the
H1 to H6 elements. |
| HTMLHRElement |
Create a horizontal rule.
|
| HTMLHtmlElement |
Root of an HTML document.
|
| HTMLIFrameElement |
Inline subwindows.
|
| HTMLImageElement |
Embedded image.
|
| HTMLInputElement |
Form control.
|
| HTMLIsIndexElement |
This element is used for single-line text input.
|
| HTMLLabelElement |
Form field label text.
|
| HTMLLegendElement |
Provides a caption for a
FIELDSET grouping. |
| HTMLLIElement |
List item.
|
| HTMLLinkElement |
The
LINK element specifies a link to an external resource,
and defines this document's relationship to that resource (or vice versa). |
| HTMLMapElement |
Client-side image map.
|
| HTMLMenuElement |
Menu list.
|
| HTMLMetaElement |
This contains generic meta-information about the document.
|
| HTMLModElement |
Notice of modification to part of a document.
|
| HTMLObjectElement |
Generic embedded object.
|
| HTMLOListElement |
Ordered list.
|
| HTMLOptGroupElement |
Group options together in logical subdivisions.
|
| HTMLOptionElement |
A selectable choice.
|
| HTMLParagraphElement |
Paragraphs.
|
| HTMLParamElement |
Parameters fed to the
OBJECT element. |
| HTMLPreElement |
Preformatted text.
|
| HTMLQuoteElement |
For the
Q and BLOCKQUOTE elements. |
| HTMLScriptElement |
Script statements.
|
| HTMLSelectElement |
The select element allows the selection of an option.
|
| HTMLStyleElement |
Style information.
|
| HTMLTableCaptionElement |
Table caption See the CAPTION element definition in HTML 4.0.
|
| HTMLTableCellElement |
The object used to represent the
TH and TD
elements. |
| HTMLTableColElement |
Regroups the
COL and COLGROUP elements. |
| HTMLTableElement |
The create* and delete* methods on the table allow authors to construct
and modify tables.
|
| HTMLTableRowElement |
A row in a table.
|
| HTMLTableSectionElement |
The
THEAD , TFOOT , and TBODY
elements. |
| HTMLTextAreaElement |
Multi-line text field.
|
| HTMLTitleElement |
The document title.
|
| HTMLUListElement |
Unordered list.
|
| Interface | Description |
|---|---|
| DOMImplementationLS |
DOMImplementationLS contains the factory methods for creating
Load and Save objects. |
| LSInput |
This interface represents an input source for data.
|
| LSLoadEvent |
This interface represents a load event object that signals the completion
of a document load.
|
| LSOutput |
This interface represents an output destination for data.
|
| LSParser |
An interface to an object that is able to build, or augment, a DOM tree
from various input sources.
|
| LSParserFilter |
LSParserFilter s provide applications the ability to examine
nodes as they are being constructed while parsing. |
| LSProgressEvent |
This interface represents a progress event object that notifies the
application about progress as a document is parsed.
|
| LSResourceResolver |
LSResourceResolver provides a way for applications to
redirect references to external resources. |
| LSSerializer |
A
LSSerializer provides an API for serializing (writing) a
DOM document out into XML. |
| LSSerializerFilter |
LSSerializerFilter s provide applications the ability to
examine nodes as they are being serialized and decide what nodes should
be serialized or not. |
| Exception | Description |
|---|---|
| LSException |
Parser or write operations may throw an
LSException if the
processing is stopped. |
| Interface | Description |
|---|---|
| DocumentRange | |
| Range |
| Exception | Description |
|---|---|
| RangeException |
Range operations may throw a
RangeException as specified in
their method descriptions. |
| Interface | Description |
|---|---|
| DocumentStyle |
The
DocumentStyle interface provides a mechanism by which the
style sheets embedded in a document can be retrieved. |
| LinkStyle |
The
LinkStyle interface provides a mechanism by which a style
sheet can be retrieved from the node responsible for linking it into a
document. |
| MediaList |
The
MediaList interface provides the abstraction of an
ordered collection of media, without defining or constraining how this
collection is implemented. |
| StyleSheet |
The
StyleSheet interface is the abstract base interface for
any type of style sheet. |
| StyleSheetList |
The
StyleSheetList interface provides the abstraction of an
ordered collection of style sheets. |
| Interface | Description |
|---|---|
| DocumentTraversal |
DocumentTraversal contains methods that create
NodeIterators and TreeWalkers to traverse a
node and its children in document order (depth first, pre-order
traversal, which is equivalent to the order in which the start tags occur
in the text representation of the document). |
| NodeFilter |
Filters are objects that know how to "filter out" nodes.
|
| NodeIterator |
NodeIterators are used to step through a set of nodes, e.g. |
| TreeWalker |
TreeWalker objects are used to navigate a document tree or
subtree using the view of the document defined by their
whatToShow flags and filter (if any). |
| Interface | Description |
|---|---|
| AbstractView |
A base interface that all views shall derive from.
|
| DocumentView |
The
DocumentView interface is implemented by
Document objects in DOM implementations supporting DOM
Views. |
Submit a bug or feature
Java is a trademark or registered trademark of Oracle and/or its affiliates in the US and other countries.
Copyright © 2005, 2019, Oracle and/or its affiliates. 500 Oracle Parkway
Redwood Shores, CA 94065 USA. All rights reserved.


What are you searching for?
You can simply type in hashtags or terms. You can also build more complicated search terms, see here for more details.
Term:


As part of our commitment to members, RTO/ERO gives you the opportunity to post your classified advertisements on this page, free of charge.
Tour Israel & Petra, Jordan with a small group of women and meet Israeli women of many backgrounds. I created and lead this unique, secular, unaffiliated tour. Visit most popular sites and go off the beaten path. Great for 1st time and return...
Read moreTour Israel & Petra, Jordan with a small group of women and meet Israeli women of many backgrounds. I created and lead this unique, secular, unaffiliated tour. Visit most popular sites and go off the beaten path. Great for 1st time and return...
Read moreTour Israel & Petra, Jordan with a small group of women and meet Israeli women of many backgrounds. I created and lead this unique, secular, unaffiliated tour. Visit most popular sites and go off the beaten path. Great for 1st time and return...
Read moreWhen creating an opportunity, please include contact information, start and end dates, and whether the position is on-going.
NOTE: Posts that do not include contact information will be removed. Posts will automatically expire after three months. Opportunities that need to be listed for longer must be reposted by the organization/person.
Post an AdDam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua.


| ICNRG | M. Mosko |
| Internet-Draft | PARC, Inc. |
| Intended status: Experimental | C. Wood |
| Expires: September 14, 2017 | University of California Irvine |
| March 13, 2017 |
The CCNx URI Scheme
draft-mosko-icnrg-ccnxurischeme-02
This document defines an RFC3986 URI compliant identifier called a Labeled Segment URI in which name segments carry a label. This allows differentiation between unrelated resources with similar identifiers. This document also specifies the CCNx URI scheme, called "ccnx:," which conforms to the labeled segment encoding rules presented here. The CCNx URI scheme applies specific labels to each name segment of a URI to disambiguate between resources with similar names. This document defines a specific set of segment labels with label semantics.
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 14, 2017.
Copyright (c) 2017 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
A Labeled Segment is an URI [RFC3986] compliant convention that allows an application or protocol to embed labels in name segments, thus disambiguating the resource identified by the path. Labeled Segment URIs also allow for query and fragment components to follow the Labeled Segment form.
Some protocols may wish to disambiguate name segments between different identifier spaces, such as "version" and "page". Other protocols may wish to use a type system such as "/str=parc/int=7" and "/str=parc/str=7". Labeled Segment URIs provide an unambiguous and flexible representation in systems that allow resources with otherwise similar names.
It is not sufficient to leave the determination of type to application-specific conventions. In a networked system with multiple applications accessing resources generated by other applications, there needs to be a set of common conventions. For example, if one application uses a base 64 encoding of a frame number, e.g. base64(0xbdea), and another uses "ver=" to represent a document version, there is an ambiguity because base64(0xbdea) is the string "ver=".
Labeled Segments defines "ls-segment" as "label[:param]=value", where the value only contains unreserved, percent-encoded, or certain sub-delim characters. In the previous example, one application would say "/frame=%BD%EA" and the other would say "/ver=".
In this document, we use URI [RFC3986] terminology, therefore a URI and CCNx Name are both composed of a URI path, which is a collection of name segments. We do not use the term "name component" as was common in old CCNx. In this document, the word "segment" alone means "name segment."
URIs conforming to the CCNx URI scheme carry a label for each name segment. The contents of each name segment must conform to the label semantics. Example segment types are "Binary Segment", "Name", and "KeyId".
We use Labeled Segment URIs as the canonical, human-readable representation. There is an unambiguous, one-to-one correspondence between an absolute LS-URI path and a Labeled Name. Relative URI representations are removed during encoding, so no relative name ends up in wire format. Some labels are URIs that are IRI [RFC3987] compatible.
Labeled Names shall be used everywhere a Name is used in CCNx, such as in the Name of an Interest or Content Object. They are also used in Links, KeyLocators, or any other place requiring a name. When encoded for the wire, a binary representation is used, depending on the specific wire format codec, which is outside the scope of this document.
This document specifies:
Formal grammars use the ABNF [RFC5234] notation.
TODO: We have not adopted Requirements Language yet.
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 RFC 2119 [RFC2119].
This section describes the formal grammar for Labeled Segments using ABNF [RFC5234] notation. We do not impose restrictions on the length of labels or values. The semantics of values are URI scheme specific, here we only describe the meta-structure of Labeled Segments. We begin by reviewing some definitions from [RFC3986] that define an absolute path URI.
URI = scheme ":" hier-part [ "?" query ] [ "#" fragment ] hier-part = "//" authority path-abempty / path-absolute / <other path types> path-absolute = "/" [ segment-nz *( "/" segment ) ] segment = *pchar segment-nz = 1*pchar pchar = unreserved / pct-encoded / sub-delims / ":" / "@" query = *( pchar / "/" / "?" ) fragment = *( pchar / "/" / "?" ) pct-encoded = "%" HEXDIG HEXDIG unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~" reserved = gen-delims / sub-delims gen-delims = ":" / "/" / "?" / "#" / "[" / "]" / "@" sub-delims = "!" / "$" / "&" / "'" / "(" / ")" / "*" / "+" / "," / ";" / "="
Labeled Segments defines a new segment type that provides unambiguous representation of a segment's label and its value. We define the top-level LS-URI as the same form as a URI, wherein each part conforms to the Label Segment grammar, which is a subset of the URI grammar.
LS-URI = scheme ":" ls-hier-part ["?" ls-query] ["#" fragment] ls-hier-part = ["//" authority] ls-path-absolute ls-path-absolute = "/" [ first-segment *( "/" ls-segment ) ] first-segment = *lpv-segment-nz ls-segment = lpv-segment / v-segment lpv-segment = label [":" param] "=" *s-value-nz v-segment = *s-value-nz ls-segment-nz = lpv-segment-nz / v-segment-nz lpv-segment-nz = label [":" param] "=" s-value-nz v-segment-nz = s-value-nz label = alpha-t / num-t param = alpha-t / num-t s-value-nz = 1*(s-pchar) ls-query = *1 ( lpv-component / v-component *( "&" (lpv-component / v-component) ) ) lpv-component = label [":" param] "=" q-value v-component = q-value q-value = *(q-pchar) alpha-t = ALPHA *(ALPHA / DIGIT) num-t = dec-t / hex-t dec-t = 1*(DIGIT) hex-t = "0x" 1*(HEXDIG) ls-pchar = unreserved / pct-encoded / ls-sub-delims s-pchar = ls-pchar / ":" / "@" / "&" q-pchar = ls-pchar / ":" / "@" / "/" ls-sub-delims = "!" / "$" / "'" / "(" / ")" / "*" / "+" / "," / ";"
A Labeled Segment URI (LS-URI) contains a scheme that uses Labeled Segments, an optional authority, a labeled segment absolute path (ls-path-aboslute), an optional labeled segment query (ls-query), and a fragment. The authority is URI scheme specific and the fragment is independent of the URI scheme.
the ls-path-aboslute is a first-segment followed by zero or more "/" ls-segment. The first-segment may be empty or a non-zero lpv-segment (lpv-segment-nz). If it is empty, it corresponds to a 0-lenght name which typically is a default route. It is distinct from a 1-segment name with no value. The first-segment MUST either be empty (the 0-lenght name) or MUST have a value. If the first-segment is an lpv-segment-nz, then it will have a value.
An ls-segment may (lpv-segment) or may not (v-segment) have a label. A particular LS-URI scheme MUST define how unlabeled segments are processed, and MAY disallow them. A v-segment is an implied type. Once the implied type is resolved, it functions like an lpv-segment.
An lpv-segment has a label, optional parameter, and optional value (s-value-nz). An empty value is a 0-length name segment with a defined type. This is distinct from a 0-length first-segment, which has neither type nor value.
lpv-segment values come from the s-pchar set, which excludes the "=" equal sign. This means that the only equal sign in a name segment must be the delimiter between the label:param and the value. Within the value, an equal sign must be percent encoded.
lpv-segment labels and values may be alpha-numeric identifiers or numbers (decimal or hexadecimal). For example, one scheme may define the labels "name", "version", and "frame". A version may be of types "date" or "serial", meaning that the version is either a date or a monotonic serial number. Some examples of resulting LS-URIs are: "/name=parc/name=csl/version:date=20130930" or "/name=alice_smith/version:serial=299". The parameters may also indicate an instance of a label, such as "/name=books/year:1=1920/year:3=1940", where there are scheme or application semantics associated with "year:1" and "year:3".
lpv-segment labels and parameters may also be numbers. For example, a protocol with a binary and URI representation may not have pre-defined all possible labels. In such cases, it could render unknown labels as their binary value, such as "/name=marc/x2003=green".
The ls-query component is a non-hierarchical set of components separated by "&". Each ls-query component is either a lpv-component or a v-component, similar to segments. They are based on q-value, which uses q-pchar that excludes "&", but includes "/". This allows an LS-URI scheme to use type query parameters.
Labeled Segments allow for dot-segments "." and ".." in a v-segment. They operate as normal. A single dot "." refers to the current hierarchy level and may be elided when the URI is resolved. Double dot ".." segments pop off the previous non-dot segment. An lpv-segment with a value of "." or ".." is not a dot-segment. It means that the value of the given label is "." or "..". For example /a=parc/b=csl/.. is equivalent to "/a=parc/b=csl", but the LS-URI "/a=parc/b=csl/c=.." does not contain a dot-segment.
An LS-URI scheme MUST specify the normalization rules to be used, following the methods of Section 6 [RFC3986]. At minimum, an LS-URI scheme SHOULD do the following:
This section describes the CCNx URI scheme "ccnx:" for Labeled Names. A Labeled Name assigns a semantic type or label to each segment of the hierarchical content Name.
Unless otherwise specified, a name segment is an arbitrary sequence of octets.
Several name segment labels are binary unsigned integers. These are always encoded as variable length sequences of 1 or more octets in network byte order using the shortest representation (i.e. no leading %x00). The value of "0" is encoded as the single byte of "%x00". A zero-length sequence must be interpreted as "not present."
The CCNx Name segment types are:
It is common for an information centric networking protocol, such as CCNx or NDN, to use a binary on-the-wire representation for messages. Such protocols, if they use the ccnx: scheme, must have an appropriate codec that unambiguously represents Labeled Content Information in the chosen wire format. Relative dot-segments should not occur in the wire format, they should be resolved before encoding.
Typed Names use a standard RFC 3986 representation following the LS-URI convention. A name segment consists of any "unreserved" characters plus percent-encoded characters. Reserved characters must be percent encoded.
Within an absolute path, each segment consists of an "ls-segment" (c.f. LS-URI). A labeled segment is a type and a name component value, with a URI representation of "type=value". The "type=" portion may be omitted if it is type Name.
Some name types take a parameter, such as the Application types. They are represented as "A:nnn=value", where the "nnn" is the application type number and value is the name component.
A CCNx URI MUST NOT include an Authority, Query, or Fragment. It is an error to include them.
Dot-segments (relative name components) are resolved when the URI is converted to a Typed Name. The "." dot-segment is removed. The ".." dot-segment is removed along with the previous non-dot-segment.
| Type | Display | Name |
|---|---|---|
| 'Name' | Hexadecimal | Name Segment |
| 'IPID' | Hexadecimal | Interest Payload Identifier segment |
| 'App:0' - 'App:255' | Hexadecimal | Application Component |
A name / is ccnx:/ and is a 0-length name. A name /Name= is ccnx:/Name= and is a 1-segment name of 0-length. A name /foo/bar. ccnx:/Name=foo/Name=bar ccnx:/foo/Name=bar ccnx:/foo/bar A name /foo/bar with key %xA0. ccnx:/Name=foo/Name=bar/App:1=0xA0 A name /foo/bar with version %xA0 and App:2 value 0x09. ccnx:/foo/bar/Version=0xA0/App:2=0x09 A name /foo/.., where the ".." is a literal name component, not a relative dot-segment. ccnx:/foo/Name=.. A name /foo/bar with application type 0 "hello" and application type 1 "world". ccnx:/Name=foo/Name=bar/App:0=hello/App:1=world
While most comparisons are done using a wire format representation of a ccnx: URI, some applications may compare the CCNx URI using their URI representation. This section defines the rules for comparing ccnx: URIs using the methods of Section 6 [RFC3986]
Comparing typed name URIs must be done with:
International Resource Identifiers extend the unreserved character set to include characters above U+07F and encode them using percent encoding. This extension is compatible with the ccnx: schema. It applies only to the "value" portion of an ls-segment.
The canonical name is determined by the URI representation of the IRI, after applying the rules of Section 3.1 of [RFC3987] and resolving dot-segments. The canonical name thus includes the URI representation of language markers, including the bidirectional components.
The value of a UTF-8 Name segment should be interpreted using IRI rules, including bidirectional markers. They may be displayed using localized formats.
Binary unsigned integer types are not interpreted under IRI rules, they are specifically percent encoded numbers. They may be displayed using a localized format.
This memo includes no request to IANA.
All drafts are required to have an IANA considerations section (see Guidelines for Writing an IANA Considerations Section in RFCs [RFC5226] for a guide). If the draft does not require IANA to do anything, the section contains an explicit statement that this is the case (as above). If there are no requirements for IANA, the section will be removed during conversion into an RFC by the RFC Editor.
All drafts are required to have a security considerations section. See RFC 3552 [RFC3552] for a guide.
| [RFC2119] | Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, March 1997. |
| [RFC3552] | Rescorla, E. and B. Korver, "Guidelines for Writing RFC Text on Security Considerations", BCP 72, RFC 3552, DOI 10.17487/RFC3552, July 2003. |
| [RFC3986] | Berners-Lee, T., Fielding, R. and L. Masinter, "Uniform Resource Identifier (URI): Generic Syntax", STD 66, RFC 3986, DOI 10.17487/RFC3986, January 2005. |
| [RFC3987] | Duerst, M. and M. Suignard, "Internationalized Resource Identifiers (IRIs)", RFC 3987, DOI 10.17487/RFC3987, January 2005. |
| [RFC5226] | Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, DOI 10.17487/RFC5226, May 2008. |
| [RFC5234] | Crocker, D. and P. Overell, "Augmented BNF for Syntax Specifications: ABNF", STD 68, RFC 5234, DOI 10.17487/RFC5234, January 2008. |


Canvas Designer is a tool aimed to give you a full-fledged drawing surface and also auto generate appropriate code for you in different formats!
It targets Canvas 2D Context – i.e. it gives you a built-in IDE for Canvas 2D APIs!
Obviously, it is developed & designed solely by Muaz Khan!
Each task or feature has a unique JavaScript file. It simplifies not only coding but also later edits and additions!
Common task like output in textarea, global variables/objects etc. have been placed in common.js file.
Dragging relevant code has been placed in drag-helper.js and drawing relevant code has been placed in draw-helper.js file. (Note: draw-helper.js is most important file in this project because functions it contains are repeatedly called from all portions of the project!)
events-handler.js is used to handle global events like mousemove, mouseup, mousedown and their touch relevant!
There is a file decorator.js which is aimed to decorate the designer; i.e. to decorate the design surface, toolbox, etc.
There is a global variable named points of type array which stores all x/y coordinates plus extra values in the following style:
var points = [['shape', [x, y], [lineWidth, strokeStyle, fillStyle, globalAlpha, globalCompositeOperation, lineCap, lineJoin]]];
i.e.
var points = [path-name, path-coordinates, path-options];
Where:
path-name
can be line/arc/rect/quadratic/bezier etc.
path-coordinates
are the shape's x/y coordinates + width, height, radius etc.
path-options
are line-width, stroke/fill styles, global alpha/composite-operation, line cap/join etc.
draw-helper.js defines a method named "redraw
" that is one of the most called functions in this project. redraw
aimed to refresh all points on the drawing surface! By default, this function is called on each mousedown
/mouseup
event; however, in some cases, it is also called in mousemove
event. (See drag-helper.js file)
common.js defines second most called function "updateTextArea
" which is aimed to update the output accordingly.
In the top of common.js file; there is an object "is
" which contains Boolean
properties for selected toolbox shape(s). Mouse/Touch events in the events-handler.js are using these properties to call appropriate objects!
You can use Ctrl + C
for copy and Ctrl + V
for paste. You can also use Ctrl + MouseDown
for directly copy and paste!
You can copy in two formats:
Remember: Ctrl + MouseDown
will only work if one option is selected: DragAllPaths
or DragLastPath
(from tool-box!)
You can undo using Ctrl + Z.
You can also use Ctrl + A to select all drawing for dragging purpose!
If you want to add new features in the Canvas Designer; follow these steps:
You've to add something through which end-users can use/access your feature – you can add any HTML element for this purpose (e.g. checkbox, radio-button, button, etc.) – however I recommend you add new toolbox icon instead! (which is a <canvas>
element!)
<div id="tool-box" class="tool-box">
........................................
<canvas id="icon-unique-id" width="40" height="40"></canvas>
</div>
After adding above HTML code, if you refresh the page; you'll see an empty icon appended in the bottom of the toolbox. Now you've to decorate this icon so end users can understand it!
Open decorator.js file and append following code anywhere in the file.
function givenName() { var context = getContext('icon-unique-id'); // 2d context relevant code here! (decoration code!!!) bindEvent(context, 'FeatureSelected'); } givenName();
FeatureSelected
is a global property used to understand the current state of your new toolbox icon (whether icon is selected or not). (Open common.js file)
var is = { ...................... isFeatureSelected: false, set: function (shape) { ...................... = is.isFeatureSelected = false; ............................................. } };
Now you've to create a new javascript file where you'll put all your "new feature" relevant code! Name the file like this: feature-handler.js
var featureHandler = {
ismousedown: false,
mousedown: function(e) {
this.ismousedown = true;
},
mouseup: function(e) {
this.ismousedown = false;
},
mousemove: function(e) {
if(this.ismousedown) { ... }
}
};
Now you've to bind mouse events to your newly created object. Open events-handler.js and append following code:
addEvent(canvas, isTouch ? 'touchstart' : 'mousedown', function (e) { ............................................................ else if (is.isFeatureSelected) featureHandler.mousedown(e); ............................................................ }); addEvent(document, isTouch ? 'touchend' : 'mouseup', function (e) { ............................................................ else if (is.isFeatureSelected) featureHandler.mouseup(e); ............................................................ }); addEvent(canvas, isTouch ? 'touchmove' : 'mousemove', function (e) { ............................................................ else if (is.isFeatureSelected) featureHandler.mousemove(e); ............................................................ });
Now you are 80% done! I strongly recommend you place your feature's drawing relevant code in the draw-helper.js file as I did for other features! - Reusability!!
This is the last step. You've to handle the output for textarea.
Open common.js file; there is a function "updateTextArea" in the "common" object – which is aimed to output into textarea element.
You don't have to change "updateTextArea". For simplicity purpose, code is separated in different functions/properties that you've to edit:
common.forLoop
common.absoluteNOTShortened
common.relativeShortened
common.relativeNOTShortened
Wait! – You've to edit "init
" function and drag-helper.js file too! – See below div.
This function is aimed to draw little transparent-red circles around the stretchable points of the shape so end-user can stretch the shape using those points! (To test it; draw a line, then click arrow [first-icon] on toolbox!) – This function is called on mousemove
event.
if (p[0] === 'your-shape') { tempContext.beginPath(); tempContext.arc(point[0], point[1], 10, Math.PI * 2, 0, !1); tempContext.arc(point[2], point[3], 10, Math.PI * 2, 0, !1); // For additional circles, copy above line and only change point's index! tempContext.fill(); }
You've to edit other two functions in the drag-helper.js file (It is absolutely necessary because it helps change points accordingly while dragging the shape!):
dragHelper.dragLastPath
dragHelper.dragAllPaths
/*≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡*/ // in "dragAllPaths": if (p[0] === 'your-shape-name') { points[i] = [p[0], [ getPoint(x, prevX, point[0]), getPoint(y, prevY, point[1]), ], p[2]]; } /*≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡*/ // in "dragLastPath": if (p[0] === 'your-shape-name') { if (g.pointsToMove === 'moveTo-points' || isMoveAllPoints) { point[0] = getPoint(x, prevX, point[0]); point[1] = getPoint(y, prevY, point[1]); } points[points.length - 1] = [p[0], point, p[2]]; } /*≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡*/ // in "mousedown" event (in the same file!) if (p[0] === 'your-shape-name') { if (dHelper.isPointInPath(x, y, point[0], point[1])) { g.pointsToMove = 'moveTo-points'; } } /*≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡*/
Now you're 100% done!
I did a detailed post about this: Dragging/Moving shapes smoothly using Canvas 2d APIs
In the drag-helper.js file – "global
" object contains following three properties:
prevX
prevY
pointsToMove
prevX/prevY
aimed to save previous mousedown
points so we can extract the dragged distance accordingly!
pointsToMove
aimed to understand which point of the shape is to move – e.g. first control points of the last Bezier curve or second control points (or moving/ending points!)
dragHelper.getPoint: function (point, prev, otherPoint) {
if (point > prev) point = otherPoint + (point - prev);
else point = otherPoint - (prev - point);
return point;
}
dragHelper.getPoint
returns the dragged distance!
By default, output in the textarea is provided in absolute coordinates. However, you can choose relative option too. Relative means points are relative to each other. If one or two points changes; all subsequent also changes, accordingly. Relative coordinates help you drag/move shape(s) at any portion of the screen without any bit of disturbance in the original shape!
You can set pageX/pageY (or offset top/left) values to x-y objects and move whole shape on mousemove/mouseup/mousedown or at any other event!
You can get shortened code for both formats: relative and absolute! Normal code is also provided there!


WE ARE LIVING IN A SCHOOL COMPOUND NOW AS OUR HOUSE HAVE BEEN DESTROYED DURING THE WAR. WE DON'T HAVE ANY HELPER , MY FATHER ALSO TOLD ME NEVER TO INVEST IN IRAQ TO AVOID DANGER , FOR HE WAS ABOUT TO INVEST IN UNITED ARAB EMIRATES BEFORE HE WAS KILLED .


title=Introducing Spring Boot date=2013-08-07 type=post tags=blog status=published ~~~~~~
Also, have you seen the amazing news? We just released Spring Boot, which makes it dead simple to do application development with Spring.
A working REST application (its entirety!) can fit in a single tweet! Here's a groovy-language @Controller
:
@Controller
class ThisWillActuallyRun {
@RequestMapping("/")
@ResponseBody
String home() {
return "Hello World!"
}
}


|
|---|
| And straightway in the morning the chief priests held a consultation with the elders and scribes and the whole council, and bound Jesus, and carried him away, and delivered him to Pilate.
|
|---|
| ᎩᎳᏉᏃ ᎢᏴᏛ ᏭᎩᏨᏅ ᏄᏂᎬᏫᏳᏒ ᎠᏥᎸ-ᎠᏁᎶᎯ, ᎠᎴ ᏧᎾᏛᏐᏅᎯ, ᎠᎴ ᏗᏃᏪᎵᏍᎩ, ᎠᎴ ᏂᎦᏛ ᏗᏂᎳᏫᎩ ᎤᎾᎵᏃᎮᎸ ᎤᎾᎸᎴ ᏥᏌ, ᎠᎴ ᎤᎾᏘᎾᏫᏛᎮᎢ, ᎠᎴ ᏆᎴᏗ ᏫᏚᏂᏲᎯᏎᎴᎢ.
|
|---|
Gi-la-quo-no i-yv-dv wu-gi-tsv-nv nu-ni-gv-wi-yu-sv a-tsi-lv--a-ne-lo-hi, a-le tsu-na-dv-so-nv-hi, a-le di-no-we-li-s-gi, a-le ni-ga-dv di-ni-la-wi-gi u-na-li-no-he-lv u-na-lv-le Tsi-sa, a-le u-na-ti-na-wi-dv-he-i, a-le Qua-le-di wi-du-ni-yo-hi-se-le-i.
|
|---|
|
|---|
| And Pilate asked him, Art thou the King of the Jews? And he answering said unto him, Thou sayest it.
|
|---|
| ᏆᎴᏗᏃ ᎤᏛᏛᏁ ᎯᎠ ᏄᏪᏎᎴᎢ, ᏂᎯᏍᎪ ᏣᎬᏫᏳᎯ ᎠᏂᏧᏏ ᎤᎾᏤᎵᎦ? ᎤᏁᏨᏃ ᎯᎠ ᏄᏪᏎᎴᎢ, ᏰᎵᏉ ᏂᏫ.
|
|---|
Qua-le-di-no u-dv-dv-ne hi-a nu-we-se-le-i, Ni-hi-s-go Tsa-gv-wi-yu-hi A-ni-tsu-si u-na-tse-li-ga? U-ne-tsv-no hi-a nu-we-se-le-i, Ye-li-quo ni-wi.
|
|---|
|
|---|
| And the chief priests accused him of many things: but he answered nothing.
|
|---|
| ᏄᏂᎬᏫᏳᏒᏃ ᎠᏥᎸ-ᎠᏁᎶᎯ ᎤᏣᏖ ᏧᏓᎴᏅᏛ ᎬᏭᎯᏍᏗᏍᎨᎢ.
|
|---|
Nu-ni-gv-wi-yu-sv-no a-tsi-lv--a-ne-lo-hi u-tsa-te tsu-da-le-nv-dv gv-wu-hi-s-di-s-ge-i.
|
|---|
|
|---|
| And Pilate asked him again, saying, Answerest thou nothing? behold how many things they witness against thee.
|
|---|
| ᏆᎴᏗᏃ ᏔᎵᏁ ᎤᏛᏛᏁ ᎯᎠ ᏄᏪᏎᎢ; ᏝᏍᎪ ᎪᎱᏍᏗ ᏯᏗᎭ? ᎬᏂᏳᏉ ᎤᏣᏘ ᏧᏓᎴᏅᏛ ᎠᏂᏃᎮᎭ ᎨᏣᏡᏗᎭ.
|
|---|
Qua-le-di-no ta-li-ne u-dv-dv-ne hi-a nu-we-se-i; Tla-s-go go-hu-s-di ya-di-ha? Gv-ni-yu-quo u-tsa-ti tsu-da-le-nv-dv a-ni-no-he-ha ge-tsa-tlu-di-ha.
|
|---|
|
|---|
| But Jesus yet answered nothing; so that Pilate marvelled.
|
|---|
| ᎠᏎᏃ ᏥᏌ ᎠᏏ ᎥᏝ ᎪᎱᏍᏗ ᏯᏗᏍᎨᎢ; ᎾᏍᎩ ᎢᏳᏍᏗ ᏆᎴᏗ ᎤᏍᏆᏂᎪᏎᎢ.
|
|---|
A-se-no Tsi-sa a-si v-tla go-hu-s-di ya-di-s-ge-i; na-s-gi i-yu-s-di Qua-le-di u-s-qua-ni-go-se-i.
|
|---|
|
|---|
| Now at that feast he released unto them one prisoner, whomsoever they desired.
|
|---|
| ᏓᎾᎵᏍᏓᏴᎲᏍᎬᏃ ᎢᏳᎢ ᏓᏲᎯᏎᎮ ᎠᏏᏴᏫ ᎠᏴᎩ, ᎾᏍᎩᏉ ᎠᏂᏔᏲᎭ.
|
|---|
Da-na-li-s-da-yv-hv-s-gv-no i-yu-i da-yo-hi-se-he a-si-yv-wi a-yv-gi, na-s-gi-quo a-ni-ta-yo-ha.
|
|---|
|
|---|
| And there was one named Barabbas, which lay bound with them that had made insurrection with him, who had committed murder in the insurrection.
|
|---|
| ᎠᏏᏴᏫᏃ ᎡᎮ ᏆᎳᏆ ᏧᏙᎢᏛ ᎾᏍᎩ ᎢᏧᎳᎭ ᏕᎨᎦᎸᎡ ᎬᏩᎵᎪᏁᎸᎯ ᎤᎾᏓᏑᏰᏛ ᎤᎾᎵᏖᎸᏅᎯ, ᎾᏍᎩ ᎤᎾᏓᎸᎯ ᎨᏎ ᎾᎯᏳ ᎤᎾᏓᏑᏰᏛ ᎤᎾᎵᏖᎸᏅᎢ.
|
|---|
A-si-yv-wi-no e-he Qua-la-qua tsu-do-i-dv na-s-gi i-tsu-la-ha de-ge-ga-lv-e gv-wa-li-go-ne-lv-hi u-na-da-su-ye-dv u-na-li-te-lv-nv-hi, na-s-gi u-na-da-lv-hi ge-se na-hi-yu u-na-da-su-ye-dv u-na-li-te-lv-nv-i.
|
|---|
|
|---|
| And the multitude crying aloud began to desire him to do as he had ever done unto them.
|
|---|
| ᎤᏂᏣᏘᏃ ᎠᏍᏓᏯ ᎤᎾᎵᏍᏕᎢ, ᎤᎾᎴᏅᎮ ᎤᏂᏔᏲᎴ ᎾᏍᎩᏯ ᏂᏚᏛᏁᎸ ᏧᏩᎫᏔᏅᏒ ᎢᏧᏛᏁᏗᏱ.
|
|---|
U-ni-tsa-ti-no a-s-da-ya u-na-li-s-de-i, u-na-le-nv-he u-ni-ta-yo-le na-s-gi-ya ni-du-dv-ne-lv tsu-wa-gu-ta-nv-sv i-tsu-dv-ne-di-yi.
|
|---|
|
|---|
| But Pilate answered them, saying, Will ye that I release unto you the King of the Jews?
|
|---|
| ᏆᎴᏗᏃ ᏚᏁᏤᎴ ᎯᎠ ᏄᏪᏎᎢ, ᎢᏣᏚᎵᏍᎪ ᎤᎬᏫᏳᎯ ᎠᏂᏧᏏ ᎤᎾᏤᎵᎦ ᏗᏳᏲᎯᏎᏗᏱ.
|
|---|
Qua-le-di-no du-ne-tse-le hi-a nu-we-se-i, I-tsa-du-li-s-go U-gv-wi-yu-hi A-ni-tsu-si u-na-tse-li-ga di-yu-yo-hi-se-di-yi.
|
|---|
|
|---|
| For he knew that the chief priests had delivered him for envy.
|
|---|
| ᎠᎦᏔᎮᏰᏃ ᎾᏍᎩ ᏄᏂᎬᏫᏳᏒ ᎠᏥᎸ-ᎠᏁᎶᎯ ᎠᏅᏳᏤᎲᏉ ᏅᏗᎦᎵᏍᏙᏗᏍᎬ ᏕᎬᏩᏲᏒᎢ.
|
|---|
A-ga-ta-he-ye-no na-s-gi nu-ni-gv-wi-yu-sv a-tsi-lv--a-ne-lo-hi a-nv-yu-tse-hv-quo nv-di-ga-li-s-do-di-s-gv de-gv-wa-yo-sv-i.
|
|---|
|
|---|
| But the chief priests moved the people, that he should rather release Barabbas unto them.
|
|---|
| ᎠᏎᏃ ᏄᏂᎬᏳᏒ ᎠᏥᎸ-ᎠᏁᎶᎯ ᏄᏅᏂᏌᏁ ᎤᏂᏣᏘ ᏴᏫ, ᎾᏍᎩ ᏆᎳᏆ ᎤᏂᏔᏲᏍᏗᏱ ᏧᏲᎯᏎᏗᏱ.
|
|---|
A-se-no nu-ni-gv-yu-sv a-tsi-lv--a-ne-lo-hi nu-nv-ni-sa-ne u-ni-tsa-ti yv-wi, na-s-gi Qua-la-qua u-ni-ta-yo-s-di-yi tsu-yo-hi-se-di-yi.
|
|---|
|
|---|
| And Pilate answered and said again unto them, What will ye then that I shall do unto him whom ye call the King of the Jews?
|
|---|
| ᏆᎴᏗᏃ ᏔᎵᏁ ᎤᏁᏨ, ᎯᎠ ᏂᏚᏪᏎᎴᎢ, ᎦᏙᏃ ᎢᏣᏚᎵ ᏥᏴᏁᏗᏱ ᎾᏍᎩ Ꮎ ᎤᎬᏫᏳᎯ ᎠᏂᏧᏏ ᎤᎾᏤᎵᎦ ᏤᏦᏎᎭ?
|
|---|
Qua-le-di-no ta-li-ne u-ne-tsv, hi-a ni-du-we-se-le-i, Ga-do-no i-tsa-du-li tsi-yv-ne-di-yi na-s-gi na U-gv-wi-yu-hi A-ni-tsu-si u-na-tse-li-ga tse-tso-se-ha?
|
|---|
|
|---|
| And they cried out again, Crucify him.
|
|---|
| ᏔᎵᏁᏃ ᎤᏁᎷᏁᎢ ᎯᏯᏛᎥᎦ ᎤᎾᏛᏁᎢ.
|
|---|
Ta-li-ne-no u-ne-lu-ne-i hi-ya-dv-v-ga u-na-dv-ne-i.
|
|---|
|
|---|
| Then Pilate said unto them, Why, what evil hath he done? And they cried out the more exceedingly, Crucify him.
|
|---|
| ᏆᎴᏗᏃ ᎯᎠ ᏂᏚᏪᏎᎴᎢ, ᎦᏙᏃ, ᎦᏙ ᎤᏍᏗ ᎤᏲ ᏚᎸᏫᏍᏓᏁᎸ? ᎠᏎᏃ ᎤᏟᏉ ᎢᏯᏍᏓᏯ ᎤᏁᎷᏁᎢ, ᎯᏯᏛᎥᎦ, ᎤᎾᏛᏁᎢ.
|
|---|
Qua-le-di-no hi-a ni-du-we-se-le-i, Ga-do-no, ga-do u-s-di u-yo du-lv-wi-s-da-ne-lv? A-se-no u-tli-quo i-ya-s-da-ya u-ne-lu-ne-i, hi-ya-dv-v-ga, u-na-dv-ne-i.
|
|---|
|
|---|
| And so Pilate, willing to content the people, released Barabbas unto them, and delivered Jesus, when he had scourged him, to be crucified.
|
|---|
| ᏆᎴᏗᏃ ᎣᏏᏳ ᎤᏰᎸᏎ ᎣᏍᏛ ᏧᏓᏅᏓᏗᏍᏙᏗᏱ ᎤᏂᏣᏘ, ᏚᏲᎯᏎᎴ ᏆᎳᏆ, ᏥᏌᏃ ᎤᎵᎥᏂᎸ ᏚᏲᏎ ᎠᎦᏛᏗᏱ.
|
|---|
Qua-le-di-no o-si-yu u-ye-lv-se o-s-dv tsu-da-nv-da-di-s-do-di-yi u-ni-tsa-ti, du-yo-hi-se-le Qua-la-qua, Tsi-sa-no u-li-v-ni-lv du-yo-se a-ga-dv-di-yi.
|
|---|
|
|---|
| And the soldiers led him away into the hall, called Praetorium; and they call together the whole band.
|
|---|
| ᎠᏂᏯᏫᏍᎩᏃ ᎬᏩᏘᎾᏫᏛᎮ ᏫᎬᏩᏴᏔᏁ ᎤᎬᏫᏳᎯᏱ ᎠᏓᏁᎸᎢ ᎾᏍᎩ ᎤᎬᏫᏳᎯ ᏣᏥᎳᏫᏤᏗᏱ, ᏂᎦᏛᏃ ᏑᎾᏓᏡᎩ ᏫᏚᏂᏯᏅᎮᎢ.
|
|---|
A-ni-ya-wi-s-gi-no gv-wa-ti-na-wi-dv-he wi-gv-wa-yv-ta-ne u-gv-wi-yu-hi-yi a-da-ne-lv-i na-s-gi u-gv-wi-yu-hi tsa-tsi-la-wi-tse-di-yi, ni-ga-dv-no su-na-da-tlu-gi wi-du-ni-ya-nv-he-i.
|
|---|
|
|---|
| And they clothed him with purple, and platted a crown of thorns, and put it about his head,
|
|---|
| ᎩᎦᎨᏃ ᎬᏩᏄᏪᎡᎢ, ᎠᎴ ᎠᎵᏍᏚᎶ ᏧᏣᏲᏍᏗ ᎪᏢᏔᏅᎯ ᎤᏂᏍᏕᏲᏅ, ᎾᏍᎩ ᎤᏂᏍᏚᎶᏔᏁᎢ.
|
|---|
Gi-ga-ge-no gv-wa-nu-we-e-i, a-le a-li-s-du-lo tsu-tsa-yo-s-di go-tlv-ta-nv-hi u-ni-s-de-yo-nv, na-s-gi u-ni-s-du-lo-ta-ne-i.
|
|---|
|
|---|
| And began to salute him, Hail, King of the Jews!
|
|---|
| ᎠᎴ ᎤᎾᎴᏅᎮ ᎠᏂᏲᎵᎮᎢ, ᎢᏨᏲᎵᎦ, ᏣᎬᏫᏳᎯ ᎠᏂᏧᏏ ᎤᎾᏤᎵᎦ, ᎠᎾᏗᏍᎨᎢ.
|
|---|
A-le u-na-le-nv-he a-ni-yo-li-he-i, i-tsv-yo-li-ga, Tsa-gv-wi-yu-hi A-ni-tsu-si u-na-tse-li-ga, a-na-di-s-ge-i.
|
|---|
|
|---|
| And they smote him on the head with a reed, and did spit upon him, and bowing their knees worshipped him.
|
|---|
| ᎠᏍᎪᎵᏃ ᏕᎬᏩᏂᎮ ᎦᎾᏍᏓ ᎬᏗ, ᎠᎴ ᏕᎬᏩᎵᏥᏍᏆᏍᎨᎢ, ᎠᎴ ᏓᎾᎵᏂᏆᏅᎥᏍᎨ ᎬᏩᏓᏙᎵᏍᏓᏁᎮᎢ.
|
|---|
A-s-go-li-no de-gv-wa-ni-he ga-na-s-da gv-di, a-le de-gv-wa-li-tsi-s-qua-s-ge-i, a-le da-na-li-ni-qua-nv-v-s-ge gv-wa-da-do-li-s-da-ne-he-i.
|
|---|
|
|---|
| And when they had mocked him, they took off the purple from him, and put his own clothes on him, and led him out to crucify him.
|
|---|
| ᎤᎾᏕᎰᏔᏃᏅᏃ, ᎬᏩᏄᏪᏎ ᎩᎦᎨᎢ, ᎠᎴ ᎤᏩᏒ ᏧᏄᏬ ᏕᎬᏩᏄᏬᎡᎢ, ᎠᎴ ᏫᎬᏩᏘᏅᏍᏔᏁ ᎬᏩᏛᏗᏱ.
|
|---|
U-na-de-ho-ta-no-nv-no, gv-wa-nu-we-se gi-ga-ge-i, a-le u-wa-sv tsu-nu-wo de-gv-wa-nu-wo-e-i, a-le wi-gv-wa-ti-nv-s-ta-ne gv-wa-dv-di-yi.
|
|---|
|
|---|
| And they compel one Simon a Cyrenian, who passed by, coming out of the country, the father of Alexander and Rufus, to bear his cross.
|
|---|
| ᎩᎶᏃ ᎢᏳᏍᏗ ᏌᏩᏂ ᏧᏙᎢᏛ ᏌᎵᏂ ᎡᎯ ᎠᎢᏎᎢ, ᏙᏗᎦᎶᎨᏒ ᏅᏓᏳᎶᏒᎯ, ᎾᏍᎩ ᎡᎵᎩ ᎠᎴ ᎷᏆᏏ ᎤᏂᏙᏓ, ᎾᏍᎩ ᎤᏤᎵ ᏧᏓᎿᎭᏩᏛ ᎤᏪᏅᏍᏗᏱ ᏄᏅᏁᎴᎢ.
|
|---|
Gi-lo-no i-yu-s-di Sa-wa-ni tsu-do-i-dv Sa-li-ni e-hi a-i-se-i, do-di-ga-lo-ge-sv nv-da-yu-lo-sv-hi, na-s-gi E-li-gi a-le Lu-qua-si u-ni-do-da, na-s-gi u-tse-li tsu-da-hna-wa-dv u-we-nv-s-di-yi nu-nv-ne-le-i.
|
|---|
|
|---|
| And they bring him unto the place Golgotha, which is, being interpreted, The place of a skull.
|
|---|
| ᎪᎵᎦᏓᏃ ᏚᏙᎥ ᏫᎬᏩᏘᏅᏔᏁᎢ, ᎾᏍᎩ ᎠᏁᏢᏔᏅᎯ ᎨᏒ ᎤᏍᏆᎷᎪ ᎦᏛᎦ.
|
|---|
Go-li-ga-da-no du-do-v wi-gv-wa-ti-nv-ta-ne-i, na-s-gi a-ne-tlv-ta-nv-hi ge-sv u-s-qua-lu-go ga-dv-ga.
|
|---|
|
|---|
| And they gave him to drink wine mingled with myrrh: but he received it not.
|
|---|
| ᎬᏩᏁᏁᎴᏃ ᎤᏗᏔᏍᏗ ᎩᎦᎨᎠᏗᏔᏍᏗ ᎻᎳ ᎠᏑᎵ; ᎠᏎᏃ ᎥᏝ ᏳᏁᎩᏎᎢ.
|
|---|
Gv-wa-ne-ne-le-no u-di-ta-s-di gi-ga-ge-a-di-ta-s-di mi-la a-su-li; a-se-no v-tla yu-ne-gi-se-i.
|
|---|
|
|---|
| And when they had crucified him, they parted his garments, casting lots upon them, what every man should take.
|
|---|
| ᎿᎭᏉᏃ ᏓᏓᎿᎭᏩᏍᏛ ᎬᏩᏛᏅ ᎤᏂᏯᏙᎴ ᏧᏄᏬᎢ, ᎤᎾᏎᏒᎮ ᎤᎾᏙᎴᎰᎯᏍᏗᏱ ᎾᏍᎩ ᎠᏂᏏᏴᏫᎭ ᏧᏂᏁᏒᏍᏗ ᎨᏒᎢ.
|
|---|
Hna-quo-no da-da-hna-wa-s-dv gv-wa-dv-nv u-ni-ya-do-le tsu-nu-wo-i, u-na-se-sv-he u-na-do-le-ho-hi-s-di-yi na-s-gi a-ni-si-yv-wi-ha tsu-ni-ne-sv-s-di ge-sv-i.
|
|---|
|
|---|
| And it was the third hour, and they crucified him.
|
|---|
| ᏐᎣᏁᎳᏃ ᎢᏳᏟᎶᏛ ᎧᎳᏩᏗᏒ ᎨᏎᎢ, ᎠᎴ ᎬᏩᏛᏁᎢ.
|
|---|
So-o-ne-la-no i-yu-tli-lo-dv ka-la-wa-di-sv ge-se-i, a-le gv-wa-dv-ne-i.
|
|---|
|
|---|
| And the superscription of his accusation was written over, THE KING OF THE JEWS.
|
|---|
| ᎦᎸᎳᏗᏢᏃ ᎪᏪᎴ ᏄᏍᏛ ᎠᎫᎢᏍᏛᎢ, ᎯᎠ ᏂᎬᏁᎢ, ᎤᎬᏫᏳᎯ ᎠᏂᏧᏏ ᎤᎾᏤᎵᎦ.
|
|---|
Ga-lv-la-di-tlv-no go-we-le nu-s-dv a-gu-i-s-dv-i, hi-a ni-gv-ne-i, U-Gv-Wi-Yu-Hi A-Ni-Tsu-Si U-Na-Tse-Li-Ga.
|
|---|
|
|---|
| And with him they crucify two thieves; the one on his right hand, and the other on his left.
|
|---|
| ᎢᏧᎳᎭᏃ ᏕᎨᎦᏛᏁ ᎠᏂᏔᎵ ᏗᎾᏓᎾᏌᎲᏍᎩ; ᎠᏏᏴᏫ ᎠᎦᏘᏏᏗᏢ, ᏐᎢᏃ ᎠᎦᏍᎦᏂ ᎢᏗᏢ.
|
|---|
I-tsu-la-ha-no de-ge-ga-dv-ne a-ni-ta-li di-na-da-na-sa-hv-s-gi; a-si-yv-wi a-ga-ti-si-di-tlv, so-i-no a-ga-s-ga-ni i-di-tlv.
|
|---|
|
|---|
| And the scripture was fulfilled, which saith, And he was numbered with the transgressors.
|
|---|
| ᎪᏪᎸᏃ ᎤᏙᎯᏳᏁᎢ, ᎯᎠ ᏥᏂᎦᏪᎭ, ᎤᏂᏍᎦᏅᏨᎯ ᎨᎦᏎᎸ ᎠᎦᏠᏯᏍᏔᏅᎩ.
|
|---|
Go-we-lv-no u-do-hi-yu-ne-i, hi-a tsi-ni-ga-we-ha, u-ni-s-ga-nv-tsv-hi ge-ga-se-lv a-ga-tlo-ya-s-ta-nv-gi.
|
|---|
|
|---|
| And they that passed by railed on him, wagging their heads, and saying, Ah, thou that destroyest the temple, and buildest it in three days,
|
|---|
| ᎠᏂᎶᏍᎩᏃ ᎦᎬᏩᏐᏢᏗᏍᎨᎢ, ᎠᎴ ᏓᎾᎵᏍᏛᏂᎮ ᎯᎠ ᎾᏂᏪᏍᎨᎢ, Ᏺ, ᎤᏛᏅ-ᏗᎦᎳᏫᎢᏍᏗᏱ ᎯᏲᏍᏗᏍᎩ, ᎠᎴ ᏦᎢᏉᏉ ᎢᎦ ᎯᏱᎵᏙᎯ ᎭᏁᏍᎨᏍᎩ,
|
|---|
A-ni-lo-s-gi-no ga-gv-wa-so-tlv-di-s-ge-i, a-le da-na-li-s-dv-ni-he hi-a na-ni-we-s-ge-i, Yo, u-dv-nv--di-ga-la-wi-i-s-di-yi hi-yo-s-di-s-gi, a-le tso-i-quo-quo i-ga hi-yi-li-do-hi ha-ne-s-ge-s-gi,
|
|---|
|
|---|
| Save thyself, and come down from the cross.
|
|---|
| ᏨᏒ ᎭᎵᏍᏕᎸ, ᎠᎴ ᎡᎭᏠᎠᎯ ᏓᏓᎿᎭᏩᏍᏛᎢ.
|
|---|
Tsv-sv ha-li-s-de-lv, a-le e-ha-tlo-a-hi da-da-hna-wa-s-dv-i.
|
|---|
|
|---|
| Likewise also the chief priests mocking said among themselves with the scribes, He saved others; himself he cannot save.
|
|---|
| ᎾᏍᎩᏯ ᎾᏍᏉ ᏄᏂᎬᏫᏳᏒ ᎠᏥᎸ ᎠᏁᎶᎯ ᎠᎴ ᏗᏃᏪᎵᏍᎩ ᎬᏩᏕᎰᏗᏍᎬ, ᎯᎠ ᏂᏓᎾᏓᏪᏎᎮᎢ, ᏅᏩᎾᏓᎴ ᏓᏍᏕᎵᏍᎬᎩ; ᎤᏩᏒ ᎥᏝ ᏴᎬᎵᏍᏕᎸ.
|
|---|
Na-s-gi-ya na-s-quo nu-ni-gv-wi-yu-sv a-tsi-lv a-ne-lo-hi a-le di-no-we-li-s-gi gv-wa-de-ho-di-s-gv, hi-a ni-da-na-da-we-se-he-i, Nv-wa-na-da-le da-s-de-li-s-gv-gi; u-wa-sv v-tla yv-gv-li-s-de-lv.
|
|---|
|
|---|
| Let Christ the King of Israel descend now from the cross, that we may see and believe. And they that were crucified with him reviled him.
|
|---|
| ᎦᎶᏁᏛ ᎤᎬᏫᏳᎯ ᎢᏏᎵ ᎤᎾᏤᎵᎦ ᎿᎭᏉ ᏩᏠᎠᎯ ᏓᏓᎿᎭᏩᏍᏛᎢ, ᎾᏍᎩ ᎣᎩᎪᏩᏛᏗᏱ ᎠᎴ ᎣᎪᎯᏳᏗᏱ. ᎠᎴ ᎾᏍᎩ ᎢᏧᎳᎭ ᏗᎨᎦᏛᏅᎯ ᎦᎬᏩᏐᏢᏕᎢ.
|
|---|
Ga-lo-ne-dv U-gv-wi-yu-hi I-si-li u-na-tse-li-ga hna-quo wa-tlo-a-hi da-da-hna-wa-s-dv-i, na-s-gi o-gi-go-wa-dv-di-yi a-le o-go-hi-yu-di-yi. A-le na-s-gi i-tsu-la-ha di-ge-ga-dv-nv-hi ga-gv-wa-so-tlv-de-i.
|
|---|
|
|---|
| And when the sixth hour was come, there was darkness over the whole land until the ninth hour.
|
|---|
| ᏔᎳᏚᏃ ᎢᏳᏟᎶᏛ ᎤᎵᏰᎢᎶᎸ ᎤᎵᏏᎲᏎ ᏂᎬᎾᏛ ᎾᎿᎭᎦᏙᎯ, ᏦᎢ ᎢᏳᏟᎶᏛ ᎢᏯᏍᏘ.
|
|---|
Ta-la-du-no i-yu-tli-lo-dv u-li-ye-i-lo-lv u-li-si-hv-se ni-gv-na-dv na-hna ga-do-hi, tso-i i-yu-tli-lo-dv i-ya-s-ti.
|
|---|
|
|---|
| And at the ninth hour Jesus cried with a loud voice, saying, Eloi, Eloi, lama sabachthani? which is, being interpreted, My God, my God, why hast thou forsaken me?
|
|---|
| ᏦᎢᏁ ᎢᏳᏟᎶᏛ ᎤᎵᏰᎢᎶᎸ ᏥᏌ ᎠᏍᏓᏯ ᎤᏪᎷᏁᎢ, ᎯᎠ ᏄᏪᏎᎢ, ᎢᎶᎢ, ᎢᎶᎢ, ᎳᎹ ᏌᏆᏓᏂ? ᎾᏍᎩ ᎠᏁᏢᏔᏅᎯ ᎯᎠ ᏄᏍᏗ ᎦᏛᎦ, ᎠᏆᏁᎳᏅᎯ, ᎠᏆᏁᎳᏅᎯ, ᎦᏙᏃ ᎥᏍᏋᏕᎩ?
|
|---|
Tso-i-ne i-yu-tli-lo-dv u-li-ye-i-lo-lv Tsi-sa a-s-da-ya u-we-lu-ne-i, hi-a nu-we-se-i, I-lo-i, I-lo-i, la-ma sa-qua-da-ni? Na-s-gi a-ne-tlv-ta-nv-hi hi-a nu-s-di ga-dv-ga, A-qua-ne-la-nv-hi, A-qua-ne-la-nv-hi, ga-do-no v-s-quv-de-gi?
|
|---|
|
|---|
| And some of them that stood by, when they heard it, said, Behold, he calleth Elias.
|
|---|
| ᎢᎦᏛᏃ ᎾᎥ ᎠᏂᏙᎾᎢ ᎤᎾᏛᎦᏅ, ᎯᎠ ᏄᏂᏪᏎᎢ, ᎬᏂᏳᏉ, ᎢᎳᏯ ᎠᏯᏂᎭ.
|
|---|
I-ga-dv-no na-v a-ni-do-na-i u-na-dv-ga-nv, hi-a nu-ni-we-se-i, Gv-ni-yu-quo, I-la-ya a-ya-ni-ha.
|
|---|
|
|---|
| And one ran and filled a spunge full of vinegar, and put it on a reed, and gave him to drink, saying, Let alone; let us see whether Elias will come to take him down.
|
|---|
| ᎠᏎᏴᏫᏃ ᏚᏍᏆᎸᏔᏅ, ᎠᎴ ᏚᏬᎵ ᏧᏂᏦᏯᏍᏗ ᏭᎧᎵᎢᏍᏔᏅ, ᎠᎴ ᎦᎾᏍᏙᎯ ᎤᏪᏆᏔᏅ, ᎤᏁᏁᎸ ᎤᏗᏔᏍᏗ; ᎯᎠ ᏄᏪᏎᎢ, ᎤᏁᎳᎩ, ᎢᏓᏙᎴᎰᎯ, ᏥᎪᏃ ᎢᎳᏯ ᏓᎦᎷᏥ ᏓᏳᏠᎥᏔᏂᎵ.
|
|---|
A-se-yv-wi-no du-s-qua-lv-ta-nv, a-le du-wo-li tsu-ni-tso-ya-s-di wu-ka-li-i-s-ta-nv, a-le ga-na-s-do-hi u-we-qua-ta-nv, u-ne-ne-lv u-di-ta-s-di; hi-a nu-we-se-i, U-ne-la-gi, i-da-do-le-ho-hi, tsi-go-no I-la-ya da-ga-lu-tsi da-yu-tlo-v-ta-ni-li.
|
|---|
|
|---|
| And Jesus cried with a loud voice, and gave up the ghost.
|
|---|
| ᏥᏌᏃ ᎠᏍᏓᏯ ᎤᏪᎷᏅ, ᎤᎵᏍᏆᏕᎴᎢ.
|
|---|
Tsi-sa-no a-s-da-ya u-we-lu-nv, u-li-s-qua-de-le-i.
|
|---|
|
|---|
| And the veil of the temple was rent in twain from the top to the bottom.
|
|---|
| ᎠᏰᏙᎳᏛᏗᏃ ᎤᏛᏅ-ᏗᎦᎳᏫᎢᏍᏗᏱ ᎦᏛ ᎤᏓᏣᎦᎸᎮ ᏔᎵ ᏄᏓᏕᎢ, ᎦᎸᎳᏗ ᏅᏓᏳᏓᎴᏅᏛ ᎡᎳᏗ ᏩᏍᏗ.
|
|---|
A-ye-do-la-dv-di-no u-dv-nv--di-ga-la-wi-i-s-di-yi ga-dv u-da-tsa-ga-lv-he ta-li nu-da-de-i, ga-lv-la-di nv-da-yu-da-le-nv-dv e-la-di wa-s-di.
|
|---|
|
|---|
| And when the centurion, which stood over against him, saw that he so cried out, and gave up the ghost, he said, Truly this man was the Son of God.
|
|---|
| ᎠᏍᎪᎯᏧᏈᏃ ᏗᏘᏂᏙᎯ ᎠᎢᏗᏢ ᏧᏳᎪᏗ ᎦᏙᎩ, ᎤᏙᎴᎰᏒ ᎾᏍᎩ ᎤᏪᎷᏅᎢ, ᎠᎴ ᎤᎵᏍᏆᏕᎸᎢ, ᎯᎠ ᏄᏪᏎᎢ, ᎤᏙᎯᏳᎯ ᎯᎠ ᎠᏍᎦᏯ ᎤᏁᎳᏅᎯ ᎤᏪᏥ ᎨᏎᎢ.
|
|---|
A-s-go-hi-tsu-qui-no di-ti-ni-do-hi a-i-di-tlv tsu-yu-go-di ga-do-gi, u-do-le-ho-sv na-s-gi u-we-lu-nv-i, a-le u-li-s-qua-de-lv-i, hi-a nu-we-se-i, U-do-hi-yu-hi hi-a a-s-ga-ya U-ne-la-nv-hi U-we-tsi ge-se-i.
|
|---|
|
|---|
| There were also women looking on afar off: among whom was Mary Magdalene, and Mary the mother of James the less and of Joses, and Salome;
|
|---|
| ᎠᏂᎨᏴᏃ ᎾᏍᏉ Ꭸ ᎢᏴᏛ ᏙᏗᏂᎧᏁᎢ; ᎾᎿᎭᏃ ᎠᏁᎴ ᎺᎵ ᏑᎩᏕᎵ ᎡᎯ, ᎠᎴ ᎺᎵ ᏥᎻ ᎤᏍᏗ ᎠᎴ ᏦᏏ ᎤᏂᏥᎢ, ᎠᎴ ᏌᎶᎻ.
|
|---|
A-ni-ge-yv-no na-s-quo ge i-yv-dv do-di-ni-ka-ne-i; na-hna-no a-ne-le Me-li Su-gi-de-li e-hi, a-le Me-li Tsi-mi u-s-di a-le Tso-si u-ni-tsi-i, a-le Sa-lo-mi.
|
|---|
|
|---|
| (Who also, when he was in Galilee, followed him, and ministered unto him;) and many other women which came up with him unto Jerusalem.
|
|---|
| ᎾᏍᎩ ᎾᏍᏉ ᎨᎵᎵ ᏤᏙᎮ ᎬᏩᏍᏓᏩᏗᏙᎮ ᎠᎴ ᎬᏩᏍᏕᎸᎯᏙᎮᎢ; ᎠᎴ ᎤᏂᏣᏖ ᏅᏩᎾᏓᎴ ᎠᏂᎨᏴ ᏥᎷᏏᎵᎻ ᏅᏓᎬᏩᏍᏓᏩᏙᎸᎯ.
|
|---|
Na-s-gi na-s-quo Ge-li-li tse-do-he gv-wa-s-da-wa-di-do-he a-le gv-wa-s-de-lv-hi-do-he-i; a-le u-ni-tsa-te nv-wa-na-da-le a-ni-ge-yv Tsi-lu-si-li-mi nv-da-gv-wa-s-da-wa-do-lv-hi.
|
|---|
|
|---|
| And now when the even was come, because it was the preparation, that is, the day before the sabbath,
|
|---|
| ᎿᎭᏉᏃ ᎤᏒ ᏄᎵᏍᏔᏅ, ᎾᏍᎩ ᎠᏛᏅᎢᏍᏙᏗᏱ ᎨᏒ ᎢᏳᏍᏗ, ᎾᏍᎩ ᎤᎾᏙᏓᏈᏕᎾ ᎢᎦ ᎨᏒᎢ.
|
|---|
Hna-quo-no u-sv nu-li-s-ta-nv, na-s-gi a-dv-nv-i-s-do-di-yi ge-sv i-yu-s-di, na-s-gi u-na-do-da-qui-de-na i-ga ge-sv-i.
|
|---|
|
|---|
| Joseph of Arimathaea, and honourable counseller, which also waited for the kingdom of God, came, and went in boldly unto Pilate, and craved the body of Jesus.
|
|---|
| ᏦᏩ ᎠᎵᎹᏗᏱ ᎡᎯ ᎠᏥᎸᏉᏗ ᏗᎦᎳᏫᎩ, ᎾᏍᎩ ᎾᏍᏉ ᎠᎦᏘᏰ ᎤᏁᎳᏅᎯ ᎤᎬᏫᏳᎯ ᎨᏒ ᎤᎷᎯᏍᏗᏱ, ᎾᏍᎩ ᎤᎷᏤᎢ, ᎠᎴ ᎾᏍᎦᎢᎲᎾ ᏭᏴᎴ ᏆᎴᏗᏱ, ᎠᎴ ᎤᏔᏲᎴ ᏥᏌ ᎠᏰᎸᎢ.
|
|---|
Tso-wa A-li-ma-di-yi e-hi a-tsi-lv-quo-di di-ga-la-wi-gi, na-s-gi na-s-quo a-ga-ti-ye U-ne-la-nv-hi u-gv-wi-yu-hi ge-sv u-lu-hi-s-di-yi, na-s-gi u-lu-tse-i, a-le na-s-ga-i-hv-na wu-yv-le Qua-le-di-yi, a-le u-ta-yo-le Tsi-sa a-ye-lv-i.
|
|---|
|
|---|
| And Pilate marvelled if he were already dead: and calling unto him the centurion, he asked him whether he had been any while dead.
|
|---|
| ᏆᎴᏗᏃ ᎤᏍᏆᏏᎪᏎ ᎤᏜᏓᏏᏛᎡᎮ ᎾᏞᎬ ᎤᏲᎱᏒᎢ; ᏭᏯᏅᎲᏃ ᎠᏍᎪᎯᏧᏈ ᏗᏘᏂᏙᎯ, ᎤᏛᏛᏁ, ᏰᎵᏍᎪ ᎪᎯᎩ ᎬᏩᏲᎱᏒᎯ, ᎤᏛᏁᎢ.
|
|---|
Qua-le-di-no u-s-qua-si-go-se u-dla-si-dv-e-he na-tle-gv u-yo-hu-sv-i; wu-ya-nv-hv-no a-s-go-hi-tsu-qui di-ti-ni-do-hi, u-dv-dv-ne, ye-li-s-go go-hi-gi gv-wa-yo-hu-sv-hi, u-dv-ne-i.
|
|---|
|
|---|
| And when he knew it of the centurion, he gave the body to Joseph.
|
|---|
| ᎬᏂᎨᏒᏃ ᏄᏩᏁᎸ ᎠᏍᎪᎯᏧᏈ ᏗᏘᏂᏙᎯ, ᏦᏩ ᏚᏲᎯᏎᎴ ᎠᏰᎸᎢ.
|
|---|
Gv-ni-ge-sv-no nu-wa-ne-lv a-s-go-hi-tsu-qui di-ti-ni-do-hi, Tso-wa du-yo-hi-se-le a-ye-lv-i.
|
|---|
|
|---|
| And he bought fine linen, and took him down, and wrapped him in the linen, and laid him in a sepulchre which was hewn out of a rock, and rolled a stone unto the door of the sepulchre.
|
|---|
| ᎤᏩᏒᏃ ᎤᏏᏙᎵ ᏙᎴᏛ ᎠᏄᏬ, ᎠᎴ ᎤᏕᏒ ᎠᏰᎸᎢ, ᎠᎴ ᎠᏄᏬᎩᎯ ᏙᎴᏛ ᎤᏪᏣᏄᎳᏅ, ᎠᏤᎵᏍᏛ ᎤᏅᏁ ᎾᏍᎩ ᏅᏲᎯ ᎠᏍᎪᏒᎢ, ᎠᎴ ᏅᏯ ᎤᏪᏌᏆᎴᎴᎢ ᎠᏤᎵᏍᏛ ᎦᎶᎯᏍᏗᏱ ᎤᏁᎢ.
|
|---|
U-wa-sv-no u-si-do-li do-le-dv a-nu-wo, a-le u-de-sv a-ye-lv-i, a-le a-nu-wo-gi-hi do-le-dv u-we-tsa-nu-la-nv, a-tse-li-s-dv u-nv-ne na-s-gi nv-yo-hi a-s-go-sv-i, a-le nv-ya u-we-sa-qua-le-le-i a-tse-li-s-dv ga-lo-hi-s-di-yi u-ne-i.
|
|---|
|
|---|
| And Mary Magdalene and Mary the mother of Joses beheld where he was laid.
|
|---|
| ᎺᎵᏃ ᎹᎩᏕᎵ ᎡᎯ, ᎠᎴ ᎺᎵ ᏦᏏ ᎤᏥ ᎤᏂᎪᎮ ᎾᎿᎭᎤᏂᏅᏅᎢ.
|
|---|
Me-li-no Ma-gi-de-li e-hi, a-le Me-li Tso-si u-tsi u-ni-go-he na-hna u-ni-nv-nv-i.
|
|---|


[1]
Tough, dependable, excellant image quality.; Image stabilization lacks. On Board mic is very limited
[2]
Great video in bright sunlight; Poor low light video, horrible reliability


To ...
...God, which is at my side every day.
...To my new friends, for giving me their permission (actually, they did not) to write about them.
...A box of Heineken which helped to keep me focused working on this book at some nights.
- This page is intentionally left blank -
1. Use the arrows bellow the book to go through the pages.
2. Some pages offer an option to see more detailed information, if you want to see more just click on this symbol on the desired page (not this).
3. You will be able to see the cover of this book if you turn your monitor. (do not try please)
4. No trees were cut to create this book. 100% recycled paper.
If you ask me for the main reason of doing this work, I could easily answer that it was a college task which was required to be done. I saw it that way the first time, but when I sat and started to think about how to do it I said to me: If you are going to spend your time doing this, do it well.
I am trying to think in that way about everything I am doing since I came to Dublin so I used this task to learn a new technology and to try to be creative while learning english. I hope you enjoy this work as much as I did doing it.
In the beginning there was CADIVI.
For many Venezuelans, it is a fact that we have to go through a very long process to come to Ireland and study English. It could take more time preparing your journey than living in Dublin.
The adventure for us began many months, sometimes years, before leaving Venezuela. In my case it started in August 2013 when I found a blog post about studying English in Ireland.
The first step buy a plane ticket, and it means 'choosing a date'. A dangerous step because you will be rely on many steps later that not depend on you and can result in losing your money.
The second is about papers: letters from the college, embassy, stamps, more papers, residence letter, and many more documents. In my case my CADIVI folder had 57 pages, more than this but I am afraid.
The third step is the most risky. Because you may have to lock, which is in some cases your life savings, the money that cover the cost of your travel for 1 or 2 months until you get the CADIVI veredict.
In my case I got the approval in January, 2 and a half weeks before the ticket day.
After that, there were a lot of saying good bye meetings with friends and family. Very nice moments.
My host family needs an special mention on this book, because it has been so far the worst experience since I have been living in Dublin.
I had a lot of problems while living there but in order to not complicate too much this part I will let you just judge my experience reading the complain letter which I wrote to the college.
Currently, Venezuelan people are living in difficult times, we are protesting against the poor living quality, the lack of security in our cities and many other things that are not going well at this moment.
It is hard to be here and see how people die just trying to get better live conditions in dangerous protests every day.
My Venezuelan partners and I are on the same boat, we left the country to study, improve and get better live conditions.
I never forget my country, this current situation gives me the strength to be better person and prepare myself for the future and help raising my country after this storm finish.
I had been collecting pictures about the situtation and I want so show here the more meaningful to me in this page:
My girlfriend came with me to Dublin and we are living together right now.
She is very important to me because she supports me and helps me to be a better person every day.
She is a very skilled and talent IT project manager and is better than me in English.

Im currently reading The Name of the Wind by Patrick Rothfuss
I am still can not review it but I could say that it have been very difficult to read. The way the author describes things, places and people with a wide vocabulary make it complicated but also a good way to learn new words.
The story has been very interesting until now, If you like fantasy and magic you might like this book
Cinema and Watching movies at home
Watching movies is a good way to practice listening. I used to watch a lot of movies
My last seen movies:
- The amazing spiderman 2 (at Dundrum)
- Noah (at Savoy)
- Last Vegas (at Home)
This chapter is under construction
I like to take pictures sometimes, being behind the camera is more secure :D.
Here you can see a selection of my favorite Dublin pictures:
She is like my mother here in Dublin because she always is scolding me.
She has a strong personality.
She is a very reliable friend because always tell the true to you even if it is a bad thing.
If Maru were in my family, definitely she would be my little sister.
Be with her means fun to me.
Besides, this girl has many pretenders around from many countries, she is on fire!!
Dont worry I am not going to say the countries or the names here :D
A good partner to
Go to the pub and get some beers.
Watch football games and discuss about football.
We still need to find time to play FIFA.
This girl is the smartest girl that I have met here so far.
Even when she is busy, she is willing to hear me.
I use to argue with her but she is a very good friend of mine.


ftpgetinfo.c
Download ftpgetinfo.c raw
/***************************************************************************
* _ _ ____ _
* Project ___| | | | _ \| |
* / __| | | | |_) | |
* | (__| |_| | _ <| |___
* \___|\___/|_| \_\_____|
*
* Copyright (C) 1998 - 2016, Daniel Stenberg<EMAIL_ADDRESS>et al.
*
* This software is licensed as described in the file COPYING, which
* you should have received as part of this distribution. The terms
* are also available at https://curl.haxx.se/docs/copyright.html.
*
* You may opt to use, copy, modify, merge, publish, distribute and/or sell
* copies of the Software, and permit persons to whom the Software is
* furnished to do so, under the terms of the COPYING file.
*
* This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
* KIND, either express or implied.
*
***************************************************************************/
#include <stdio.h>
#include <string.h>
#include <curl/curl.h>
/* <DESC>
* Checks a single file's size and mtime from an FTP server.
* </DESC>
*/
static size_t throw_away(void *ptr, size_t size, size_t nmemb, void *data)
{
(void)ptr;
(void)data;
/* we are not interested in the headers itself,
so we only return the size we would have saved ... */
return (size_t)(size * nmemb);
}
int main(void)
{
char ftpurl[] = "ftp://ftp.example.com/gnu/binutils/binutils-2.19.1.tar.bz2";
CURL *curl;
CURLcode res;
long filetime = -1;
double filesize = 0.0;
const char *filename = strrchr(ftpurl, '/') + 1;
curl_global_init(CURL_GLOBAL_DEFAULT);
curl = curl_easy_init();
if(curl) {
curl_easy_setopt(curl, CURLOPT_URL, ftpurl);
/* No download if the file */
curl_easy_setopt(curl, CURLOPT_NOBODY, 1L);
/* Ask for filetime */
curl_easy_setopt(curl, CURLOPT_FILETIME, 1L);
/* No header output: TODO 14.1 http-style HEAD output for ftp */
curl_easy_setopt(curl, CURLOPT_HEADERFUNCTION, throw_away);
curl_easy_setopt(curl, CURLOPT_HEADER, 0L);
/* Switch on full protocol/debug output */
/* curl_easy_setopt(curl, CURLOPT_VERBOSE, 1L); */
res = curl_easy_perform(curl);
if(CURLE_OK == res) {
/* https://curl.haxx.se/libcurl/c/curl_easy_getinfo.html */
res = curl_easy_getinfo(curl, CURLINFO_FILETIME, &filetime);
if((CURLE_OK == res) && (filetime >= 0)) {
time_t file_time = (time_t)filetime;
printf("filetime %s: %s", filename, ctime(&file_time));
}
res = curl_easy_getinfo(curl, CURLINFO_CONTENT_LENGTH_DOWNLOAD,
&filesize);
if((CURLE_OK == res) && (filesize>0.0))
printf("filesize %s: %0.0f bytes\n", filename, filesize);
}
else {
/* we failed */
fprintf(stderr, "curl told us %d\n", res);
}
/* always cleanup */
curl_easy_cleanup(curl);
}
curl_global_cleanup();
return 0;
}


An Introduction to Web Mapping
You can view, comment, remix and edit on
github!
Today we will be talking about the basic principles of web mapping.
And we will be including a little history, too.
We'll not going to talk a lot about Google, but will instead show you an open source Google-free stack
We're going to answer the question...
How is a web map different than a digital map?
Digital: involves a computer, but might not be accessible by the internet.
Digital maps are (usually) created by Geographical Information System (GIS).
A web map is a kind of digital map.
We're talking about web maps that you view in a browser
Making maps for mobile devices is evidently similar to web mapping but I won't be talking about it because I don't know much about it myself!
We also won't be talking about
digital globes like
Google Earth
Ok.
Time for the history lesson:
How did web maps come to be?
First there were digital maps published on the web using
ArcGIS.
ArcGIS is made by the company ESRI and it's mapping software used by institutions more than end-users
Although useful, GIS for the Web was not user friendly and maybe more importantly, it was not web developer friendly
In 1996, Mapquest launched its web service.
Online maps that could give directions! It was amazing!
But it was also slow to load :(
MapQuest required a full page refresh to scroll or zoom, and it was always aligned to specific map boundaries.
In 2005 Google Maps solved this problem by introducing the tile.
The tile
A tile is just an image that is served up on the internet
All tiles are the same size - 256x256 pixels
Tiles can be road map, a satellite image, or anything else that's a
raster.
All these little tiles load
way faster than one big map.
Web maps load the tiles that you want on your screen and if the map is smart, it will pre-load tiles outside of the screen, along the top, bottom, left, and right.
This is why this kind of map is sometimes called a
slippy map
Each zoom level has its own set of tiles...
Zoom level 0: one tile for the world.
With each additional zoom level, the number of tiles increases exponentially.
Zoom level 1: 4 tiles for the world.
Zoom level 2, 3, 4, 5
Zoom level 13
level 17
level 17 === 0.003 degrees == 1.193 m /pixel === 1:4,000 scale
Tiles are usually rendered in advance then stored in a cache
In order to understand how this works, let's break down the URL.
level 17
http://tile.openstreetmap.org/17/35303/48503.png -- this is the name of the tile server.
http://tile.openstreetmap.org/17/35303/48503.png -- this is the z value, or the zoom level.
http://tile.openstreetmap.org/17/35303/48503.png -- This is the x/y value, or the place in the grid where the tile lives.
This collection of raster tiles makes up what we call the map's base layer.
When we layer things like markers on top of them, we call those data layers or content layers or feature layers.
They are often vector layers (point, line, polygon). Sometimes you can interact with them (clicking to produce a popup, for example).
Data layers can be expressed in a variety of file types
GIS uses
shapefiles, but web mappers prefer
KML, or
GeoJSON
GeoJSON is especially magical because it now can be displayed and tracked within GitHub
The City of Windsor's Open Data Catalogue provides geocoded data that can be used as data layers!!!
WHOA!
Wait, how do we get the data layers into the base layers of your map?
JavaScript libraries for Web Mapping!
What do these JavaScript libraries do? They grab the tiles, adds content layer, and handles interaction.
[Leaflet's] "most important contribution...
is its ability to treat map elements just like every other page element...While that capability may seem pedestrian, it’s quite powerful in practice. Tapping a marker on a map can trigger an event related to elements outside of the map, and vice versa. And once you begin playing with the power that offers, the traditional boundaries between the map and 'the rest of the page” vanish'.
So.
If I can get my Data Layers from The City of Windsor Open Data Catalogue...
Do I have to make my own custom base layer tiles?
You can add addtional style to you your map with
CartoCSS
And you can even use a service like
TileMill to design your own tiles.
Pretty!
Wait! I just noticed that there's no GeoJSON in the City of Windsor's Open Data Catalogue?! How can I make pretty web maps now?
You can convert a Shapefile to GeoJSON with
OGRE or you can easily create your own GeoJSON with
geojson.io
I think that's enough!
Here's a mapping challenge for you: put the open data from the City of Windsor's Open Data Catalogue on a map!
Thanks to:
The folks at
#maptime who shared the base layer of this presentation
The people at
OKFN.org who encourage Open Data Day and support Open Data work around the world
And to you, the map makers.
Presentation made with Tom MacWright's
big
Here be dragons.


PART I. [OLD] UNIFORM ANATOMICAL GIFT ACT
§§327-1 to 9 REPEALED. L 1988, c 267, §2.
PART I. [OLD] UNIFORM ANATOMICAL GIFT ACT
§§327-1 to 14 REPEALED. L 2008, c 122, §4.
Note
L 2008, c 9, §3 purports to amend repealed §327-1.
[Part I.] REVISED UNIFORM ANATOMICAL GIFT ACT
[§327-1] Short title. This part may be cited as the "Revised Uniform Anatomical Gift Act". [L 2008, c 122, pt of §1]


Constructor
new Customer(firstName, lastName, money)
Constructs a Customer Object with the specified parameters.
Parameters:
| Name | Type | Default | Description |
|---|---|---|---|
firstName |
String | The customer's firstname. | |
lastName |
String | The customer's lastname. | |
money |
Float | 0 | The customer's amount of money. |
Properties:
| Name | Type | Description |
|---|---|---|
firstName |
String | The firstname of the customer |
lastname |
String | The lastname of the customer |
fullname |
String | The fullname of the customer |
money |
Int | how much money the customer has. |
scooter |
Scooter | The scooter the customer currently has. |
- Source:
Methods
canAffordScooter(scooter) → {Boolean}
Checks if a customer can afford a specific scooter.
Parameters:
| Name | Type | Description |
|---|---|---|
scooter |
Scooter | The scooter to check the price of. |
- Source:
Returns:
- Returns a boolean (true/false) on whether they can afford the scooter.
- Type
- Boolean
driveScooterFor(distance)
Drives the scooter for a specified distance.
Parameters:
| Name | Type | Description |
|---|---|---|
distance |
Int | The distance to travel. |
- Source:
hasScooter() → {boolean}
Checks if the customer has a scooter.
- Source:
Returns:
- Returns true / false depending on if they have a scooter or not.
- Type
- boolean
purchaseScooter(scooter)
Purchases a scooter and adds it to the customer's inventory.
Parameters:
| Name | Type | Description |
|---|---|---|
scooter |
Scooter | The scooter to purchase. |
- Source:
returnScooter()
Removes the Scooter from the customer's inventory.
- Source:


|
Chicago Tribune for members Register | Log in | More info
Please register to read stories on chicagotribune.com -- it's FREE! |
|
|
Latest news
Updated 2:53 AM CST
Bush Welcomes Lithuania Into NATO
President Bush welcomed Lithuania into NATO on Saturday, saying the former Soviet republic "will help lift and invigorate" the western alliance.
Half of state school chiefs earn $100,000
For the first time, more than half the state's school superintendents earned $100,000 or more last year, records show.
Judge orders privacy for terrorism suspect
A federal judge ordered privacy for an Islamic charity director charged with bankrolling Osama bin Laden's terrorist network but refused to free him on bond, saying he might flee the country.
Holidays ahead; city closing streets
This weekend's Magnificent Mile Lights Festival, which draws thousands to downtown Chicago, kicks off the coming holiday season's round of street closings. Road construction and CTA track repairs also will affect travel around the city.
Other top headlines:
Miss World Pageant Moves to London
Man gets 30 years in cop-led drug conspiracy
Gov. finds jobs for Cabinet director, lawmakers
States Plan Suit Over Air Changes
JFK assassination audio, video uncovered
Governor names new U. of I. board chairman
Ryan to meet with murder victims' families
Judge strips guardianship from breast-feeding mother of
eight-year-old
South Side man shot, killed after cashing check
>> More news: Local | Nation/World
|
|
| |
Search Chicago's freshest jobs
|
|
|
|
|
|
|


1.there thier when i need them. 2.i like to play with them. 3.when i am sad they cheer me up. 4.they make me l feel safe
5.i feel safe when there aroud. 6.they keep me from getting in trouble. 7.the some times when am having trouble in my home work they help me. 8.also in other types of problem they still help me.
9.they make me laugh. 10.they are my best friend. 11.though they make my feel sad and angry[sometimes cry]they will always be my brothers. 12.And they are still obidient to me.
I love my brothers arthur and Dennis The make me get sad alot and i do not just mean alot i mean alooooooooooooot. Their the best brothers i could ever ask for. I can never ask for beter brothers.


Rail improvement works in Lancashire this Christmas
by Mike HillRail teams are to work across Christmas to improve drainage on the main rail link out of Preston.
Network Rail is to use the festive shutdown to carry out key works on the West Cost Main Line.
Among the scheduled improvements is railway drainage upgrade on the route between Preston and Lancaster.
In the North West, track will also be replaced and a foot crossing renewed on the West Cost Main Linenear Warrington between January 1 and 2.
Elsewhere on the line there will be work in and around Euston station in preparation for HS2 and key improvements in the Midlands area.
Tim Shoveller, managing director of Network Rail’s North West and Central region, said: “While people enjoy time with their friends and families over Christmas, thousands of Network Rail staff will be working round-the-clock to maintain and improve the railway to provide passengers with better, more reliable journeys in the New Year.
“I know there is never a good time to disrupt journeys while we carry out large pieces of work but whenever possible we do this at times when there are significantly fewer people travelling by train, such as Christmas and other bank holidays.
"I appreciate people have important plans so I urge them to please plan ahead and check before they travel for the latest journey information.”
The works will take place between December 24 and 27.


ERC 1404
ERC1404 is a simple restricted token standard designed to help issuers comply with international banking and securities laws.
Investor Limits
Set maximum number of investors to enforce domestic or international securities laws and comply with registration exemptions.
Investor Whitelist
Know who your investors are at any time and maintain a whitelist of investor addresses. From re-rerunning sanctions checks to requiring accredited investors only, the simple restricted token standard helps token issuers manager their investor lists.
Global Standards
Integrate one standard for global adoption while meeting your compliance requirements. Supports branded standards like Polymath's ST-20 or Harbor's R-Token. Example implementations.
Issuers
If you're seeking to issue a security token, ERC 1404 provides all the tools you need to follow your counsels guidance with respect to compliance requirements.
Exchanges
This standard was designed with significant input from the major exchanges to be interoperable across exchanges and easy to integrate on any stack. If this standard does not meet your needs, please open up a Github issue here with your request.
Legal Counsel
It may be challenging to navigate transfer restrictions in the open source world of blockchain. ERC 1404 provides the tools necessary for your issuers to comply with domestic and international legal requirements.


|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
java.lang.Object java.util.Dictionary java.util.Hashtable org.apache.commons.logging.impl.WeakHashtable
Implementation of Hashtable
that uses WeakReference
's
to hold its keys thus allowing them to be reclaimed by the garbage collector.
The associated values are retained using strong references.
This class follows the symantics of Hashtable
as closely as
possible. It therefore does not accept null values or keys.
Note:
This is not intended to be a general purpose hash table replacement.
This implementation is also tuned towards a particular purpose: for use as a replacement
for Hashtable
in LogFactory
. This application requires
good liveliness for get
and put
. Various tradeoffs
have been made with this in mind.
Usage: typical use case is as a drop-in replacement
for the Hashtable
used in LogFactory
for J2EE enviroments
running 1.3+ JVMs. Use of this class in most cases (see below) will
allow classloaders to be collected by the garbage collector without the need
to call LogFactory.release(ClassLoader)
.
org.apache.commons.logging.LogFactory
checks whether this class
can be supported by the current JVM, and if so then uses it to store
references to the LogFactory
implementationd it loads
(rather than using a standard Hashtable instance).
Having this class used instead of Hashtable
solves
certain issues related to dynamic reloading of applications in J2EE-style
environments. However this class requires java 1.3 or later (due to its use
of java.lang.ref.WeakReference
and associates).
And by the way, this extends Hashtable
rather than HashMap
for backwards compatibility reasons. See the documentation
for method LogFactory.createFactoryStore
for more details.
The reason all this is necessary is due to a issue which
arises during hot deploy in a J2EE-like containers.
Each component running in the container owns one or more classloaders; when
the component loads a LogFactory instance via the component classloader
a reference to it gets stored in the static LogFactory.factories member,
keyed by the component's classloader so different components don't
stomp on each other. When the component is later unloaded, the container
sets the component's classloader to null with the intent that all the
component's classes get garbage-collected. However there's still a
reference to the component's classloader from a key in the "global"
LogFactory
's factories member! If LogFactory.release()
is called whenever component is unloaded, the classloaders will be correctly
garbage collected; this should be done by any container that
bundles commons-logging by default. However, holding the classloader
references weakly ensures that the classloader will be garbage collected
without the container performing this step.
Limitations: There is still one (unusual) scenario in which a component will not be correctly unloaded without an explicit release. Though weak references are used for its keys, it is necessary to use strong references for its values.
If the abstract class LogFactory
is
loaded by the container classloader but a subclass of
LogFactory
[LogFactory1] is loaded by the component's
classloader and an instance stored in the static map associated with the
base LogFactory class, then there is a strong reference from the LogFactory
class to the LogFactory1 instance (as normal) and a strong reference from
the LogFactory1 instance to the component classloader via
getClass().getClassLoader()
. This chain of references will prevent
collection of the child classloader.
Such a situation occurs when the commons-logging.jar is
loaded by a parent classloader (e.g. a server level classloader in a
servlet container) and a custom LogFactory
implementation is
loaded by a child classloader (e.g. a web app classloader).
To avoid this scenario, ensure
that any custom LogFactory subclass is loaded by the same classloader as
the base LogFactory
. Creating custom LogFactory subclasses is,
however, rare. The standard LogFactoryImpl class should be sufficient
for most or all users.
| Constructor Summary | |
WeakHashtable()
Constructs a WeakHashtable with the Hashtable default capacity and load factor. |
| Method Summary | |
boolean |
containsKey(java.lang.Object key)
|
java.util.Enumeration |
elements()
|
java.util.Set |
entrySet()
|
java.lang.Object |
get(java.lang.Object key)
|
boolean |
isEmpty()
|
java.util.Enumeration |
keys()
|
java.util.Set |
keySet()
|
java.lang.Object |
put(java.lang.Object key,
java.lang.Object value)
|
void |
putAll(java.util.Map t)
|
protected void |
rehash()
|
java.lang.Object |
remove(java.lang.Object key)
|
int |
size()
|
java.lang.String |
toString()
|
java.util.Collection |
values()
|
| Methods inherited from class java.util.Hashtable |
clear, clone, contains, containsValue, equals, hashCode |
| Methods inherited from class java.lang.Object |
finalize, getClass, notify, notifyAll, wait, wait, wait |
| Constructor Detail |
public WeakHashtable()
| Method Detail |
public boolean containsKey(java.lang.Object key)
Hashtable
public java.util.Enumeration elements()
Hashtable
public java.util.Set entrySet()
Hashtable
public java.lang.Object get(java.lang.Object key)
Hashtable
public java.util.Enumeration keys()
Hashtable
public java.util.Set keySet()
Hashtable
public java.lang.Object put(java.lang.Object key, java.lang.Object value)
Hashtable
public void putAll(java.util.Map t)
Hashtable
public java.util.Collection values()
Hashtable
public java.lang.Object remove(java.lang.Object key)
Hashtable
public boolean isEmpty()
Hashtable
public int size()
Hashtable
public java.lang.String toString()
Hashtable
protected void rehash()
Hashtable
|
|||||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Sat Feb 27, 2016
I’m sure you are familiar with the “nature vs nurture” debate. If not, google it - I’ll wait.
Got it? Good. For me, most explanations for human behaviour can be lumped into the “nurture” side - a bias, no doubt, fostered by my time studying anthropology at university.
However, there is something to be said for the “nature” side as well. Evolution bakes instinctual responses into the DNA of all animals, after all. Horses, for example, have an innate fear of snakes, and therefore snake-like objects. Sometimes, a horse will rear when faced with a snake-shaped stick.
So what vestigial instincts from our hunter gatherer days linger on to colour our nightmares today? Most people assume that man has always been at the top of the food chain; but this assumption is an arrogant one, albeit unsurprising. We’ve been top dog for thousands of years now and are used to our dominion over all of God’s creatures.
It was a different story thousands of years ago. There was an animal that evolved to be a specialist predator on humans - the Dinofelis. When mountain lions and other big cats attack a human today, the victim often survives because modern cats don’t have teeth that can pierce our skulls. The Dinofelis, however, had short, dagger-like teeth that punctured the skull with one bite.
The grisly forensic evidence can be found today in African caves, where skulls show the tooth holes left by this slinking predator who attacked in the dark of night.
Humans fought back. We invented spears and other piercing weapons. We drove the Dinofelis into extinction. We won.
However, the nightmares remain in our ancestral memory. They are the monsters under our bed. The silent menace in the dark. Nobody has to teach a young child to be scared of large cats. I’ve seen this for myself.
We feel safe when have control over our environments. Perhaps our domestication of cats is an attempt to subjugate our former oppressors and desensitize our primal fears. Maybe we find cats amusing because we’ve performed the ultimate reversal and made our greatest enemy…cute. Is it any accident that we invented the Internet so we could watch cat videos all day long?
I misspoke a little when I said we are top dogs on planet Earth. We are still prey to micro-organisms that we can’t defend against with traditional weapons. Disease, plagues, viruses, and other modern killers of our overpopulated world were not nearly as devastating to the small nomadic tribes in our distant past. But our homogenous and globalized societies today are especially susceptible.
Perhaps the next nightmare to insinuate itself into our DNA will be of large crowds where diseases spread like wildfire. Perhaps, in some post-apocalyptic future we will have reverted to roaming in small cohesive groups, using our human ingenuity and survival skills to elude the vast zombie hordes that threaten to infect us. Wait a minute, did I just describe The Walking Dead? The most popular show on TV right now?
It seems our collective nightmare has already begun.


Your browser doesn't support video
Status:
unknown
Enter peer id
Connect
Our id is
unknown
getUserMedia constraints being used:


The greatest common divisor (GCD) of two integers $a$ and $b$ is defined to be the largest integer that divides both $a$ and $b$ with no remainder. For example, the GCD of 16 and 28 is 4. In chapter 2, when we investigate how to implement rational-number arithmetic, we will need to be able to compute GCDs in order to reduce rational numbers to lowest terms. (To reduce a rational number to lowest terms, we must divide both the numerator and the denominator by their GCD. For example, 16/28 reduces to 4/7.) One way to find the GCD of two integers is to factor them and search for common factors, but there is a famous algorithm that is much more efficient.
The idea of the algorithm is based on the observation that, if $r$ is the remainder when $a$ is divided by $b$, then the common divisors of $a$ and $b$ are precisely the same as the common divisors of $b$ and $r$. Thus, we can use the equation \[ \textrm{GCD} (a, b) = \textrm{GCD}(b, r) \] to successively reduce the problem of computing a GCD to the problem of computing the GCD of smaller and smaller pairs of integers. For example, \begin{eqnarray*} \textrm{GCD}(206,40) & = & \textrm{GCD}(40,6) \\ & = & \textrm{GCD}(6,4) \\ & = & \textrm{GCD}(4,2) \\ & = & \textrm{GCD}(2,0) \\ & = & 2 \end{eqnarray*} reduces $\textrm{GCD}(206, 40)$ to $\textrm{GCD}(2, 0)$, which is 2. It is possible to show that starting with any two positive integers and performing repeated reductions will always eventually produce a pair where the second number is 0. Then the GCD is the other number in the pair. This method for computing the GCD is known as Euclid's Algorithm.[1]
This generates an iterative process, whose number of steps grows as the logarithm of the numbers involved.
The fact that the number of steps required by Euclid's Algorithm has logarithmic growth bears an interesting relation to the Fibonacci numbers:
Lamé's Theorem: If Euclid's Algorithm requires $k$ steps to compute the GCD of some pair, then the smaller number in the pair must be greater than or equal to the $k$th Fibonacci number.[2]
We can use this theorem to get an order-of-growth estimate for Euclid's Algorithm. Let $n$ be the smaller of the two inputs to the function. If the process takes $k$ steps, then we must have $n\geq {\textrm{Fib}} (k)\approx\phi^k/\sqrt{5}$. Therefore the number of steps $k$ grows as the logarithm (to the base $\phi$) of $n$. Hence, the order of growth is $\Theta(\log n)$.
gcd(206, 40) 40 === 0 ? 206 : gcd(40, 206 % 40) gcd(40, 206 % 40) 206 % 40 === 0 ? 40 : gcd(206 % 40, 40 % (206 % 40)) // remainder operation (1) 6 === 0 ? 40 : gcd(206 % 40, 40 % (206 % 40)) gcd(206 % 40, 40 % (206 % 40)) 40 % (206 % 40) === 0 ? 206 % 40 : gcd(40 % (206 % 40), (206 % 40) % (40 % (206 % 40))) // remainder operations (2) and (3) 4 === 0 ? 206 % 40 : gcd(40 % (206 % 40), (206 % 40) % (40 % (206 % 40))) gcd(40 % (206 % 40), (206 % 40) % (40 % (206 % 40))) (206 % 40) % (40 % (206 % 40)) === 0 ? 40 % (206 % 40) : gcd((206 % 40) % (40 % (206 % 40)), (40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40))) // remainder operations (4), (5), (6), (7) 2 === 0 ? 40 % (206 % 40) : gcd((206 % 40) % (40 % (206 % 40)), (40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40)))) gcd((206 % 40) % (40 % (206 % 40)), (40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40))) (40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40))) === 0 ? (206 % 40) % (40 % (206 % 40)) : gcd((40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40)), ((206 % 40) % (40 % (206 % 40))) % ((40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40)))) // remainder operations (8), (9), (10), (11), (12), (13), (14) 0 === 0 ? (206 % 40) % (40 % (206 % 40)) : gcd((40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40)), ((206 % 40) % (40 % (206 % 40))) % ((40 % (206 % 40)) % ((206 % 40) % (40 % (206 % 40)))) (206 % 40) % (40 % (206 % 40)) // remainder operations (15), (16), (17), (18) 2
gcd(206, 40) 40 === 0 ? 206 : gcd(40, 206 % 40) gcd(40, 206 % 40) // remainder operation (1) gcd(40, 6) 6 === 0 ? 40 : gcd(6, 40 % 6) gcd(6, 40 % 6) // remainder operation (2) gcd(6, 4) 4 === 0 ? 6 : gcd(4, 6 % 4) gcd(4, 6 % 4) // remainder operation (3) gcd(4, 2) 2 === 0 ? 4 : gcd(2, 4 % 2) gcd(2, 4 % 2) // remainder operation (4) gcd(2, 0) 0 === 0 ? 2 : gcd(0, 2 % 0) 2


--- layout: sub-page title: "HBC Tech: Code" --- Code Some of the open source projects we've created Loading... View Gilt's Repositories