text:
This is a W3C Working Draft for review by W3C members and other
interested parties. It is a draft document and may be updated,
replaced or obsoleted by other documents at any time. It is
inappropriate to use W3C Working Drafts as reference material or to
cite them as other than "work in progress". A list of current W3C
working drafts can be found at http://www.w3.org/TR.
Note: Since working drafts are subject to frequent
change, you are advised to reference the above URL, rather than the
URLs for working drafts themselves.
This work is part of the W3C SGML, XML, and Structured
Document Interchange
Activity (for current status, see
Extensible Markup Language (XML) is an extremely simple dialect of
SGML which is completely described in this document. The goal is to
enable generic SGML to be served, received, and processed on the Web
in the way that is now possible with HTML. XML has been designed for
ease of implementation and for interoperability with both SGML and
The Extensible Markup Language, abbreviated XML, describes a class of data objects called XML documents and partially describes the behavior of computer programs which process them. XML is an application profile or restricted form of SGML, the Standard Generalized Markup Language [ISO 8879].
XML documents are made up of storage units called entities, which contain either text or binary data. Text is made up of characters, some of which form the character data in the document, and some of which form markup. Markup encodes a description of the document's storage layout and logical structure. XML provides a mechanism to impose constraints on the storage layout and logical structure.
A software module called an XML processor is used to read XML documents and provide access to their content and structure. It is assumed that an XML processor is doing its work on behalf of another module, referred to as the application. This specification describes the required behavior of an XML processor in terms of how it must read XML data and the information it must provide to the application.
XML was developed by an SGML Editorial Review Board formed under the auspices of the World Wide Web Consortium (W3C) in 1996 and chaired by Jon Bosak of Sun Microsystems, with the very active participation of an SGML Working Group also organized by the W3C. The membership of the Editorial Review Board is given in an appendix. Dan Connolly served as the ERB's contact with the W3C.
The design goals for XML are:
This specification, together with the associated standards, provides all the information necessary to understand XML version 1.0 and construct computer programs to process it.
This version of the XML specification (30 June 1997) is for public review and discussion. It may be distributed freely, as long as all text and legal notices remain intact.
Standards relevant to users and implementors of XML include:
Some terms used with special meaning in this specification are:
fatal error
validity constraint
well-formedness constraint
at user option
and the content consists of
character data and elements whose names match names in the
content model, or if (b) the content model matches the rule for
, and the sequence of
child elements
belongs to the language generated by the regular expression in
the content model.
exact(ly) match
for compatibility
for interoperability
The formal grammar of XML is given using a simple Extended Backus-Naur Form (EBNF) notation. Each rule in the grammar defines one symbol, in the form
symbol ::= expression |
Symbols are written with an initial capital letter if they are defined by a regular expression, or with an initial lowercase letter if a recursive grammar is required for recognition. Literal strings are quoted; unless otherwise noted they are case-insensitive. The distinction between symbols which can and cannot be recognized using simple regular expressions may be used to set the boundary between an implementation's lexical scanner and its parser, but this specification neither constrains the placement of that boundary nor presupposes that all implementations will have one.
Within the expression on the right-hand side of a rule, the meaning of symbols is as shown below.
form is insignificant; the number of leading
zeroes in the corresponding bit string is governed by the character
encoding in use and is not significant for XML.[a-zA-Z]
, [#xN-#xN]
, [^#xN-#xN]
, [^#xN#xN#xN]
a b
a | b
a - b
S? a S?
. If
the expression a is governed by a suffix operator, then
the suffix operator determines both the maximum number of parameter-entity
references allowed and the number of occurrences of a
in the replacement text of the parameter entities: %a*
means that a must occur zero or more times, and
that some of its occurrences may be replaced by references to
parameter entities whose replacement text must contain zero or
more occurrences of a; it is thus a more compact way
of writing %(a*)*
Similarly, %a+
means that a
must occur one or more times, and may be replaced by
parameter entities with replacement text matching
S? (a S?)+
The recognition of parameter entities in the internal subset is much more
highly constrained.
prefix operator, or a suffix operator:
, *
, or +
./* ... */
This section defines some symbols used widely in the grammar.
S (white space) consists of one or more space (#x20) characters, carriage returns, line feeds, or tabs.
White space | ||||
Legal characters are tab, carriage return, line feed, and the legal graphic characters of Unicode and ISO/IEC 10646.
Character range | ||||||
Characters are classified for convenience as letters, digits, or other characters. Letters consist of an alphabetic or syllabic base character possibly followed by one or more combining characters, or of an ideographic character. Certain layout and format-control characters defined by ISO/IEC 10646 should be ignored when recognizing identifiers; these are defined by the classes Ignorable and Extender. Full definitions of the specific characters in each class are given in the appendix on character classes.
A Name is a token beginning with a letter or underscore character and continuing with letters, digits, hyphens, underscores, or full stops (together known as name characters). Names beginning with the string XML are reserved for standardization in this or future versions of this specification.
Note: the colon character is also allowed within XML names; it is reserved for experimentation with name spaces and schema scoping. Its meaning is expected to be standardized at some future point, at which point those documents using colon for experimental purposes will need to be updated. (Note: there is no guarantee that any name-space mechanism adopted for XML will in fact use colon as a name-space delimiter.) In practice, this means that authors should not use colon in XML names except as part of name-space experiments, but that implementors should accept colon as a name character.
An Nmtoken (name token) is any mixture of name characters.
Names and tokens | ||||||||||||||||||||||||
Literal data is any quoted string not containing the quotation mark used as a delimiter for that string; different forms of literal data may or may not contain angle brackets, entity references, and character references. Literals are used for specifying the replacement text of internal entities (EntityValue), the values of attributes (AttValue), and external identifiers (SystemLiteral); for some purposes, the entire literal can be skipped without scanning for markup within it (SkipLit):
Literals | ||||||||||||||||||||||||||||||||||||||
Note that entity references and character references are recognized and processed within EntityValue and AttValue, but not within SystemLiteral.
A textual object is an XML document if it is either valid or well-formed, as defined in this specification.
Each XML document has both a logical and a physical structure.
Physically, the document is composed of units called entities. An entity may refer to other entities to cause their inclusion in the document. A document begins in a "root" or document entity.
The logical structure contains declarations, elements, comments, character references, and processing instructions, all of which are indicated in the document by explicit markup.
The two structures must be synchronous: see section 4.1.
A textual object is said to be a well-formed XML document if, first, it matches the production labeled document, and if for each entity reference which appears in the document, either the entity has been declared in the document type declaration or the entity name is one of: amp, lt, gt, apos, quot.
Matching the document production implies that:
As a consequence of this, for each non-root element C in the document, there is one other element P in the document such that C is in the content of P, but is not in the content of any other element that is in the content of P. Then P is referred to as the parent of C, and C as a child of P.
The data stored in an XML entity is either text or binary. Binary data has an associated notation, identified by name; beyond a requirement to make available the notation's name and the associated system identifier, XML places no constraints on the contents or use of binary entities. So-called binary data might in fact be textual; its identification as binary means that an XML processor need not parse it in the fashion described by this specification. XML text data is a sequence of characters. A character is an atomic unit of text; valid characters are specified by ISO/IEC 10646. Users may extend the ISO/IEC 10646 character repertoire by exploiting the private use areas.
The mechanism for encoding character values into bit patterns may vary from entity to entity. All XML processors must accept the UTF-8 and UCS-2 encodings of 10646; the mechanisms for signaling which of the two are in use, or for bringing other encodings into play, are discussed later, in the discussion of character encodings.
Regardless of the specific encoding used, any character in the ISO/IEC 10646 character set may be referred to by the decimal or hexadecimal equivalent of its bit string.
XML text consists of intermingled character data and markup. Markup takes the form of start-tags, end-tags, empty elements, entity references, character references, comments, CDATA sections, document type declarations, and processing instructions.
All text that is not markup constitutes the character data of the document.
The ampersand character (&) and the left angle bracket (<)
may appear in their literal form only when used as markup
delimiters, or within comments, processing instructions, or CDATA sections. If they are needed elsewhere,
they must be escaped
using either numeric character references or the strings
" and "<
". The right angle
bracket (>) may be represented using the string
", and must, for
compatibility, be so represented when it appears in the string
", when that string is not marking the end of
a CDATA section.
In the content of elements, character data
is any string of characters which does
not contain the start-delimiter of any markup.
In a CDATA section, character data
is any string of characters not including the CDATA-section-close
delimiter, "]]>
To allow attribute values to contain both single and double quotes, the
apostrophe or single-quote character (') may be represented as
", and the double-quote character (") as
Character data | ||||
Comments may appear anywhere except in a CDATA section, i.e. within element content, in mixed content, or in a DTD. They must not occur within declarations or tags. They are not part of the document's character data; an XML processor may, but need not, make it possible for an application to retrieve the text of comments. For compatibility, the string -- (double-hyphen) must not occur within comments.
Comments | ||||
An example of a comment:
<!-- declarations for <head> & <body> --> |
Processing instructions (PIs) allow documents to contain instructions for applications.
Processing instructions | ||||
PIs are not part of the document's character data, but must be passed through to the application. The Name is called the PI target; it is used to identify the application to which the instruction is directed. XML provides an optional mechanism, NOTATION, for formal declaration of such names. PI targets with names beginning with the string "XML" are reserved for standardization in this or future versions of this specification.
CDATA sections can occur
anywhere character data may occur; they are
used to escape blocks of text containing characters which would
otherwise be recognized as markup. CDATA sections begin with the
string <![CDATA[
and end with the string
CDATA sections | ||||||||||||||||
Within a CDATA section, only the CDEnd string is
recognized, so that left angle brackets and ampersands may occur in
their literal form; they need not (and cannot) be escaped using
and &
. CDATA sections
cannot nest.
An example of a CDATA section:
<![CDATA[<greeting>Hello, world!</greeting>]]> |
In editing XML documents, it is often convenient to use "white space"
(spaces, tabs, and blank lines, denoted by the nonterminal S
this specification) to
set apart the markup for greater readability. Such white space is typically
not intended for inclusion in the delivered version of the document.
On the other hand, "significant" white space that must be retained in the
delivered version is common, for example in poetry and
source code.
An XML processor must always pass all characters in a document that are not markup through to the application. A validating XML processor must distinguish white space in element content from other non-markup characters and signal to the application that white space in element content is not significant.
A special attribute may be inserted in documents to signal an intention that the element to which this attribute applies requires all white space to be treated as significant by applications.
In valid documents, this attribute must be declared as follows, if used:
The value DEFAULT
signals that applications'
default white-space processing modes are acceptable for this element; the
value PRESERVE
indicates the intent that applications preserve
all the white space.
This declared intent is considered to apply to all elements within the content
of this element, unless overriden with another instance of the
XML-SPACE attribute.
The root element of any document is considered to have signaled no intentions as regards application space handling, unless it provides a value for this attribute or the attribute is declared with a default value.
XML documents may, and should, begin with an XML declaration which specifies, among other things, the version of XML being used.
The function of the markup in an XML document is to describe its storage and logical structures, and associate attribute-value pairs with the logical structure. XML provides a mechanism, the document type declaration, to define constraints on that logical structure and to support the use of predefined storage units. An XML document is said to be valid if there is an associated document type declaration and if the document complies with the constraints expressed in it.
The document type declaration must appear before the first start-tag in the document.
XML document | ||||||||||||||||||||
The identification of the XML version as "1.0" does not indicate a commitment to produce any future versions of XML, nor if any are produced, to use any particular numbering scheme. Since future versions are not ruled out, this construct is provided as a means to allow the possibility of automatic version recognition, should it become necessary.
For example, the following is a complete XML document, well-formed but not valid:
<?XML version="1.0"?> |
and so is this:
<greeting>Hello, world!</greeting> |
The XML document type declaration may include a pointer to an external entity containing a subset of the necessary markup declarations, and may also directly include another, internal, subset.
These two subsets make up the document type definition, abbreviated DTD. The DTD, in effect, provides a grammar which defines a class of documents. Properly speaking, the DTD consists of both subsets taken together, but it is a common practice for the bulk of the markup declarations to appear in the external subset, and for this subset, usually contained in a file, to be referred to as "the DTD" for a class of documents.
Document type definition | ||||||||||||||||||||||
Validity Constraint - Root Element Type:
The Name in the document-type declaration must
match the element type of the root element.
Validity Constraint - Non-null DTD:
The internal and external subsets of the DTD must not both
be empty.
Well-Formedness Constraint - Integral Declarations:
A parameter-entity
reference recognized in this context must have replacement
text consisting of zero or more complete declarations,
i.e. matching the production for the non-terminal
The external subset must obey substantially
the same grammatical constraints
as the internal subset; i.e. it must match the production for the
non-terminal symbol
In the external subset, however, parameter-entity references can
be used to replace constructs prefixed by %
in a production of
the grammar, and conditional sections
may occur.
In the internal subset, by contrast, conditional sections may not
occur and the only parameter-entity references
allowed are those which match the non-terminal
within the rule for markupdecl.
External subset | ||||
For example:
<?XML version="1.0"?> |
The system identifier hello.dtd
the location of a DTD for the document.
The declarations can also be given locally, as in this example:
<?XML version="1.0" encoding="UTF-8" ?> |
If both the external and internal subsets are used, an XML processor must read the internal subset first, then the external subset. This has the effect that entity and attribute declarations in the internal subset take precedence over those in the external subset.
In some cases, an XML processor can read an XML document and accomplish useful tasks without having first processed the entire DTD. However, certain declarations can substantially affect the actions of an XML processor. It is desirable, therefore, to be able to specify whether a document contains any such declarations. A document author can communicate whether or not DTD processing is necessary using a required markup declaration (abbreviated RMD), which appears as a component of the XML declaration:
Required markup declaration | ||||||||
In an RMD, the value NONE indicates that an XML processor can parse the containing document correctly without first reading any part of the DTD. The value INTERNAL indicates that the XML processor must read and process the internal subset of the DTD, if provided, to parse the containing document correctly. The value ALL indicates that the XML processor must read and process the declarations in both the subsets of the DTD, if provided, to parse the containing document correctly.
The RMD must indicate that the entire DTD is required if the external subset contains any declarations of
If no RMD is provided, an XML processor must behave as though an RMD had been provided with the value ALL.
An example XML declaration with an RMD:
<?XML version="1.0" RMD='INTERNAL'?> |
Each XML document contains one or more elements, the boundaries of which are either delimited by start-tags and end-tags, or, for empty elements, are those of the start-tag. Each element has a type, identified by name (sometimes called its generic identifier or GI), and may have a set of attributes. Each attribute has a name and a value.
This specification does not constrain the semantics, use, or (beyond syntax) names of the elements and attributes, except that names beginning with the string XML are reserved for standardization in this or future versions of this specification.
The beginning of every non-empty XML element is marked by a start-tag.
Start-tag | ||||||||||||||||||||||
The Name in the start- and end-tags gives the
element's type.
The Name-AttValue pairs are referred to as
the attribute specifications of the element,
with the Name
referred to as the attribute name and
the content of the
AttValue (the characters between the '
as the attribute value.
An example of a start-tag:
<termdef id="dt-dog" term="dog"> |
The end of every element which is not empty is marked by an end-tag containing a name that echoes the element's type as given in the start-tag:
End-tag | ||||
An example of an end-tag:
</termdef> |
The text between the start-tag and end-tag is called the element's content:
Content of elements | ||||||||||||||||
Validity Constraint - Content:
If an element is empty, the start-tag constitutes the whole element. An empty element takes a special form:
Tags for empty elements | ||||
An example of an empty element:
<IMG align="left" |
The element structure of an XML document may, for validation purposes, be constrained using element and attribute declarations.
An element declaration constrains the element's type and its content.
Element declarations often constrain which element types can appear as children of the element. At user option, an XML processor may issue a warning when a reference is made to an element type for which no declaration is provided, but this is not an error.
An element declaration takes the form:
Element declaration | ||||||||||
where the Name gives the type of the element.
Validity Constraint - Unique Element Declaration:The content of an element can be categorized as element content or mixed content , as explained below. An element declared using the keyword EMPTY must be empty when it appears in the document.
If an element type is declared using the keyword ANY, then there are no validity constraints on its content: it may contain child elements of any type and number, interspersed with character data.
Examples of element declarations:
<!ELEMENT br EMPTY> |
An element type may be declared to have element content, which means that elements of that type may only contain other elements (no character data). In this case, the constraint includes a content model, a simple grammar governing the allowed types of the child elements and the order in which they appear. The grammar is built on content particles (CPs), which consist of names, choice lists of content particles, or sequence lists of content particles:
Element-content models | ||||||||||||||||||||||||||||||||
where each Name gives the type of an element which may
appear as a child. Any content
particle in a choice list may appear in the element content at the appropriate
location; content particles occurring in a sequence list must each
appear in the element content in the
order given. The optional character following a name or list governs
whether the element or the content particles in the list may occur one
or more (+
), zero or more (*
), or zero or
one times (?
). The syntax
and meaning are identical to those used in the productions in this
The content of an element matches a content model if and only if it is possible to trace out a path through the content model, obeying the sequence, choice, and repetition operators and matching each element in the content against an element name in the content model. For compatibility reasons, it is an error if an element in the document can match more than one occurrence of an element name in the content model. More formally: a finite state automaton may be constructed from the content model using the standard algorithms, e.g. algorithm 3.5 in section 3.9 of Aho, Sethi, and Ullman. In many such algorithms, a follow set is constructed for each position in the regular expression (i.e., each leaf node in the syntax tree for the regular expression); if any position has a follow set in which more than one following position is labeled with the same element type name, then the content model is in error and may be reported as an error. For more information, see the appendix on deterministic content models.
Examples of element-content models:
<!ELEMENT spec (front, body, back?)> |
An element type may be declared to contain mixed content, that is, text comprising character data optionally interspersed with child elements. In this case, the types of the child elements are constrained, but not their order nor their number of occurrences:
Mixed-content declaration | ||||||||||||
where the Names give the types of elements that may appear as children. The same name must not appear more than once in a single mixed-content declaration.
Examples of mixed content declarations:
<!ELEMENT p (#PCDATA|a|ul|b|i|em)*> |
Attributes are used to associate name-value pairs with elements. Attributes may appear only within start-tags; thus, the productions used to recognize them appear in the discussion of start-tags. Attribute-list declarations may be used:
Attribute-list declarations specify the name, data type, and default value (if any) of each attribute associated with a given element type:
Attribute list declaration | ||||||||
The Name in the AttlistDecl rule is the type of an element. At user option, an XML processor may issue a warning if attributes are declared for an element type not itself declared, but this is not an error. The Name in the AttDef rule is the name of the attribute.
When more than one AttlistDecl is provided for a given element type, the contents of all those provided are merged. When more than one definition is provided for the same attribute of a given element type, the first declaration is binding and later declarations are ignored. For interoperability, writers of DTDs may choose to provide at most one attribute-list declaration for a given element type, and at most one attribute definition for a given attribute name. For interoperability, an XML processor may at user option issue a warning when more than one attribute-list declaration is provided for a given element type, or more than one attribute definition for a given attribute, but this is not an error.
XML attribute types are of three kinds: a string type, a set of tokenized types, and enumerated types. The string type may take any literal string as a value; the tokenized types have varying lexical and semantic constraints, as noted:
Attribute types | ||||||||||||||||||||||||||||||||||||||||||||||||||
Validity Constraint - ID:
symbols. A name must not appear more than once in
an XML document as a value of this type; i.e., ID values must uniquely
identify the elements which bear them.
The XML processor must normalize attribute values before passing them to the application, as described in the section on attribute-value normalization.
Enumerated attributes can take one of a list of values provided in the declaration; there are two types:
Enumerated attribute types | ||||||||||||||||||||||||
Validity Constraint - Notation Attributes:
tokens in the declaration.
For interoperability, the same
should not occur more than once in the enumerated
attribute types of a single element type.An attribute declaration provides information on whether the attribute's presence is required, and if not, how an XML processor should react if a declared attribute is absent in a document:
Attribute defaults | ||||||||||
#REQUIRED means that the document is invalid should the processor encounter a start-tag for the element type in question which specifies no value for this attribute. #IMPLIED means that if the attribute is omitted from an element of this type, the XML processor must inform the application that no value was specified; no constraint is placed on the behavior of the application.
If the attribute is neither #REQUIRED nor #IMPLIED, then the AttValue value contains the declared default value. If the #FIXED is present, the document is invalid if the attribute is present with a different value from the default. If a default value is declared, when an XML processor encounters an omitted attribute, it is to behave as though the attribute were present with its value being the declared default value.
Validity Constraint - Attribute Default Legal:Examples of attribute-list declarations:
<!ATTLIST termdef |
Before the value of an attribute is passed to the application, the XML processor must normalize it as follows:
Conditional sections are portions of the document type declaration external subset which are included in, or excluded from, the logical structure of the DTD based on the keyword which governs them.
Conditional section | ||||||||||||||||||||||||||||
Like the internal and external DTD subsets, a conditional section may contain one or more complete declarations, comments, processing instructions, or nested conditional sections, intermingled with white space.
If the keyword of the conditional section is
, then the conditional section is read and
processed in the normal way. If the keyword is
, then the declarations within the conditional
section are ignored; the processor must read the conditional section to
detect nested conditional sections and ensure that the end of the
outermost (ignored) conditional section is properly detected.
If a conditional section with a
keyword of INCLUDE
occurs within a larger conditional
section with a keyword of IGNORE
, both the outer and the
inner conditional sections are ignored.
If the keyword of the conditional section is a parameter entity reference, the parameter entity is replaced by its value before the processor decides whether to include or ignore the conditional section.
An example:
An XML document may consist of one or many virtual storage units. These are called entities; they are identified by name and have content. An entity may be stored in, but need not comprise the whole of, a single physical storage object such as a file or database field. Each XML document has one entity called the document entity, which serves as the starting point for the XML processor (and may contain the whole document).
Entities may be either binary or text. A text entity contains text data which is considered as an integral part of the document. A binary entity contains binary data with an associated notation. Only text entities may be referred to using entity references; only the names of binary entities may be given as the value of ENTITY attributes.
The logical and physical structures (elements and entities) in an XML document must be synchronous. Tags and elements must each begin and end in the same entity, but may refer to other entities internally; comments, processing instructions, character references, and entity references must each be contained entirely within a single entity. Entities must each contain an integral number of elements, comments, processing instructions, and references, possibly together with character data not contained within any element in the entity, or else they must contain non-textual data, which by definition contains no elements.
A character reference refers to a specific character in the ISO/IEC 10646 character set, e.g. one not directly accessible from available input devices:
Character reference | ||||||||
An entity
reference refers to the content of a named entity.
General entities are
text entities for use within the document itself; references to them
use ampersand (&
) and semicolon (;
) as
delimiters. In this specification,
general entities are sometimes referred to with the
unqualified term entity when this leads
to no ambiguity. Parameter entities are text entities for use within the DTD,
or to control processing of
conditional sections;
references to them use percent-sign (%
) and semicolon
) as delimiters.
Entity reference | ||||||||||||||||||||||||||||||||||||||||||||||
Well-Formedness Constraint - Entity Declared:
appears in a production of the
grammar. In the internal subset, parameter-entity references
are recognized only when they match
the InternalPERef non-terminal
in the production for markupdecl.
Examples of character and entity references:
Type <key>less-than</key> (<) to save options. |
Example of a parameter-entity reference:
<!ENTITY % ISOLat2 |
Entities are declared thus:
Entity declaration | ||||||||||||||||
The Name is that by which the entity is invoked by exact match in an entity reference. If the same entity is declared more than once, the first declaration encountered is binding; at user option, an XML processor may issue a warning if entities are declared multiple times.
If the entity definition is an EntityValue, the defined entity is called an internal entity. There is no separate physical storage object, and the replacement text of the entity is given in the declaration. Within the EntityValue, parameter-entity references and character references are recognized and expanded immediately. General-entity references within the replacement text are not recognized at the time the entity declaration is parsed, though they may be recognized when the entity itself is referred to.
An internal entity is a text entity.
Example of an internal entity declaration:
<!ENTITY Pub-Status "This is a pre-release of the |
If the entity is not internal, it is an external entity, declared as follows:
External entity declaration | ||||||||||||||||||
If the NDataDecl is present, this is a binary data entity, otherwise a text entity.
Validity Constraint - Notation Declared:The SystemLiteral that follows the keyword SYSTEM is called the entity's system identifier. It is a URL, which may be used to retrieve the entity. Unless otherwise provided by information outside the scope of this specification (e.g. a special XML element defined by a particular DTD, or a processing instruction defined by a particular application specification), relative URLs are relative to the location of the entity or file within which the entity declaration occurs. Relative URLs in entity declarations within the internal DTD subset are thus relative to the location of the document; those in entity declarations in the external subset are relative to the location of the files containing the external subset.
In addition to a system literal, an external identifier may include a public identifier. An XML processor may use the public identifier to try to generate an alternative URL. If the processor is unable to do so, it must use the URL specified in the system literal.
Examples of external entity declarations:
<!ENTITY open-hatch |
Each external text entity in an XML document may use a different encoding for its characters. All XML processors must be able to read entities in either UTF-8 or UCS-2. It is recognized that for some purposes, the use of additional ISO/IEC 10646 planes other than the Basic Multilingual Plane may be required. A facility for handling characters in these planes is therefore a desirable characteristic in XML processors and applications.
Entities encoded in UCS-2 must begin with the Byte Order Mark described by ISO/IEC 10646 Annex E and Unicode Appendix B (the ZERO WIDTH NO-BREAK SPACE character, #xFEFF). This is an encoding signature, not part of either the markup or character data of the XML document. XML processors must be able to use this character to differentiate between UTF-8 and UCS-2 encoded documents.
Although an XML processor is only required to read entities in the UTF-8 and UCS-2, it is recognized that many other encodings are in daily use around the world, and it may be advantageous for XML processors to read entities that use these encodings. For this purpose, XML provides an encoding declaration processing instruction, which, if it occurs, must appear at the beginning of a system entity, before any other character data or markup. In the document entity, the encoding declaration is part of the XML declaration; in other entities, it is part of an encoding processing instruction:
Encoding declaration | ||||||||||||||||||||||
The values
, and
should be
used for the various encodings and transformations of Unicode /
ISO/IEC 10646, the values
, ...
should be used for the parts of ISO 8859, and
the values
, and
should be used for the various encoded forms of JIS X-0208. XML
processors may recognize other encodings; it is recommended that
character encodings registered (as charsets)
with the Internet Assigned Numbers
Authority (IANA), other than those just listed, should be referred to
using their registered names.
It is an error for an entity including an encoding declaration to be presented to the XML processor in an encoding other than that named in the declaration.
An entity which begins with neither a Byte Order Mark nor an encoding declaration must be in the UTF-8 encoding.
While XML provides mechanisms for distinguishing encodings, it is recognized that in a heterogeneous networked environment, it may be difficult to signal the encoding of an entity reliably. Errors in this area fall into two categories:
Examples of encoding declarations:
The document entity serves as the root of the entity tree and a starting-point for an XML processor. This specification does not specify how the document entity is to be located by an XML processor; unlike other entities, the document entity might well appear on an input stream of the processor without any identification at all.
XML allows character and general-entity references in two places: the content of elements (content) and attribute values (AttValue). When an XML processor encounters such a reference, or the name of an external binary entity as the value of an ENTITY or ENTITIES attribute, then:
expands to
; the remaining ampersand is not recognized
as an entity-reference delimiter.)
Since the entity may contain other entity references,
an XML processor may have to repeat the inclusion process recursively.
Entity and character
references can both be used to escape the left angle bracket,
ampersand, and other delimiters. A set of general entities
quot) is specified for this purpose.
Numeric character references may also be used; they are
expanded immediately when recognized, and must be treated as
character data, so the numeric character references
and &
may be used to
escape <
and &
when they occur
in character data.
XML allows parameter-entity references in a variety of places within the DTD. Parameter-entity references are always expanded immediately upon being recognized, and the DTD must match the relevant rules of the grammar after all parameter-entity references have been expanded. In addition, parameter entities referred to in specific contexts are required to satisfy certain constraints in their replacement text; for example, a parameter entity referred to within the internal DTD subset must match the rule for markupdecl.
Implementors of XML processors need to know the rules for expansion of references in more detail. These rules only come into play when the replacement text for an internal entity itself contains other references.
Simple character references do not suffice to escape delimiters within the replacement text of an internal entity: they will be expanded when the entity declaration is parsed, before the replacement text is stored in the symbol table. When the entity itself is referred to, the replacement text will be parsed again, and the delimiters (no longer character references) will be recognized as delimiters. To escape the characters amp, lt, gt, apos, quot in an entity replacement text, use a general-entity reference or a doubly-escaped character reference. See the appendix on expansion of entity references for detailed examples.
As mentioned in the discussion of Character Data and Markup, the characters used as markup delimiters by XML may all be escaped using entity references (for the entities amp, lt, gt, apos, quot).
All XML processors must recognize these entities whether they are declared or not. Valid XML documents must declare these entities, like any others, before using them.
If the entities in question are declared, they must be declared as internal entities whose replacement text is the single character being escaped, as shown below.
<!ENTITY lt "<"> |
Notations identify by name the format of external binary entities.
Notation declarations provide a name for the notation, for use in entity and attribute-list declarations and in attribute-value specifications, and an external identifier for the notation which may allow an XML processor or its client application to locate a helper application capable of processing data in the given notation.
Notation declarations | ||||
XML processors must provide applications with the name and external identifier of any notation declared and referred to in an attribute value, attribute definition, or entity declaration. They may additionally resolve the external identifier into the system identifier, file name, or other information needed to allow the application to call a processor for data in the notation described. (It is not an error, however, for XML documents to declare and refer to notations for which notation-specific applications are not available on the system where the XML processor or application is running.)
Conforming XML processors fall into two classes: validating and non-validating.
Validating and non-validating systems alike must report violations of the well-formedness constraints given in this specification.
Validating processors must report locations in which the document does not comply with the constraints expressed by the declarations in the DTD. They must also report all failures to fulfill the validity constraints given in this specification.
XML is designed to be a subset of SGML, in that every valid XML document should also be a conformant SGML document, using the same DTD, and that the parse trees produced by an SGML parser and an XML processor should be the same. To achieve this, XML was defined by removing features and options from the specification of SGML.
The following list describes syntactic characteristics which XML does not allow but which are legal in SGML. The list may not be complete.
<!-- comment text
and can't have spaces within the markup of <!--
... --
inside markup declarations.
; this helps
ensure that the end-point of the conditional section does not
change when the section is changed from IGNORE to
In most current SGML systems, XML documents should be able to use the following SGML declaration. Some systems (those which take the document character set to be a description of the input stream) may require different declarations, depending on the character set and the capacities and quantities required.
Following the characteristics defined in the Unicode standard, characters are classed as base characters (among others, these contain the alphabetic characters of the Latin alphabet, without diacritics), ideographic characters, combining characters (among others, this class contains most diacritics); these classes combine to form the class of letters. Digits, extenders, and characters which should be ignored for purposes of recognizing identifiers are also distinguished.
Characters | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This appendix contains some examples illustrating the sequence of entity- and character-reference recognition and expansion.
If the DTD contains the declaration
then the XML processor will recognize the character references when it parses the entity declaration, and resolve them before storing the following string as the value of the entity example:
A reference in the document to &example;
will cause the text to be reparsed, at which time the
start- and end-tags of the p element will be recognized
and the three references will be recognized and expanded,
resulting in a p element with the following content
(all data, no delimiters or markup):
A more complex example will illustrate the rules and their effects fully. In the following example, the line numbers are solely for reference.
This produces the following
. Since the replacement text
is not rescanned, the reference to parameter entity zz
is not recognized. (And it would be an error if it were, since
zz is not yet declared.)<
expanded immediately and the parameter entity zz is
stored with the replacement text
<!ENTITY tricky "error-prone" >
which is a well-formed entity declaration.%zz;
) is parsed. The reference to zz
is recognized in its turn, and its replacement text
(<!ENTITY tricky "error-prone" >
) is parsed.
The general entity tricky has now been
declared, with the replacement text error-prone
.For compatibility, it is required that content models in element declarations be deterministic. SGML requires deterministic content models (it calls them `unambiguous'); XML processors built using SGML systems may flag non-deterministic content models as errors.
For example, the content model ((b, c) | (b, d))
non-deterministic, because given an initial b the parser
cannot know which b in the model is being matched without
looking ahead to see which element follows the b.
In this case, the two references to
b can be collapsed
into a single reference, making the model read
(b, (c | d))
. An initial b now clearly
matches only a single name in the content model. The parser doesn't
need to look ahead to see what follows; either c or
d would be accepted.
Algorithms exist which allow many but not all non-deterministic content models to be reduced automatically to equivalent deterministic models; see Brüggemann-Klein 1991.
The XML encoding declaration functions as an internal label on each entity, indicating which character encoding is in use. Before an XML processor can read the internal label, however, it apparently has to know what character encoding is in use--which is what the internal label is trying to indicate. In the general case, this is a hopeless situation. It is not entirely hopeless in XML, however, because XML limits the general case in two ways: each implementation is assumed to support only a finite set of character encodings, and the XML encoding declaration is restricted in position and content in order to make it feasible to autodetect the character encoding in use in each entity in normal cases.
Because each XML entity not in UTF-8 or UCS-2 format must
begin with an XML encoding declaration, in which the first characters
must be '<?XML
', any conforming processor can detect,
after four octets of input, which of the following cases apply (in
reading this list, it may help to know that in UCS-4, '<' is
and '?' is #x0000003F
, and the Byte
Order Mark required of UCS-2 data streams is #xFEFF
: UCS-4, big-endian machine (1234 order)
: UCS-4, little-endian machine (4321 order)
: UCS-4, unusual octet order (2143)
: UCS-4, unusual octet order (3412)
: UCS-2, big-endian
: UCS-2, little-endian
: UCS-2, big-endian, no Byte Order Mark
(and thus, strictly speaking, in error)
: UCS-2, little-endian, no Byte Order Mark
(and thus, strictly speaking, in error)
: UTF-8, ISO 646, ASCII, some part of ISO 8859,
Shift-JIS, EUC, or any other 7-bit, 8-bit, or mixed-width encoding
which ensures that the characters of ASCII have their normal positions,
and values; the actual encoding declaration must be read to
detect which of these applies, but since all of these encodings
use the same bit patterns for the ASCII characters, the encoding
declaration itself may be read reliably
: EBCDIC (in some flavor; the full
encoding declaration must be read to tell which code page is in
This level of autodetection is enough to read the XML encoding declaration and parse the character-encoding identifier, which is still necessary to distinguish the individual members of each family of encodings (e.g. to tell UTF-8 from 8859, and the parts of 8859 from each other, or to distinguish the specific EBCDIC code page in use, and so on).
Because the contents of the encoding declaration are restricted to ASCII characters, a processor can reliably read the entire encoding declaration as soon as it has detected which family of encodings is in use. Since in practice, all widely used character encodings fall into one of the categories above, the XML encoding declaration allows reasonably reliable in-line labeling of character encodings, even when external sources of information at the operating-system or transport-protocol level are unreliable.
Once the processor has detected the character encoding in use, it can act appropriately, whether by invoking a separate input routine for each case, or by calling the proper conversion function on each character of input.
Like any self-labeling system, the XML encoding declaration will not work if any software changes the entity's character set or encoding without updating the encoding declaration. Implementors of character-encoding routines should be careful to ensure the accuracy of the internal and external information used to label the entity.
The grammar given in the body of this specification is relatively simple, but for some purposes it is convenient to have an even simpler one. A very simple, though non-conforming, XML processor could parse a well-formed XML document using the following simplified grammar, recognizing all element boundaries correctly, though not expanding entity references and not detecting all errors:
Trivial text grammar | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Most processors will require the more complex grammar given in the body of this specification.
This specification was prepared and approved for publication by the W3C SGML Editorial Review Board (ERB). ERB approval of this specification does not necessarily imply that all ERB members voted for its approval. At the time it approved this specification, the SGML ERB comprised the following members:
Jon Bosak, Sun (Chair); James Clark (Technical Lead); Tim Bray, Textuality (Co-editor); C. M. Sperberg-McQueen, U. of Ill. (Co-editor); Steve DeRose, INSO; Dave Hollander, HP; Eliot Kimber, Highland; Tom Magliery, NCSA; Eve Maler, ArborText; Jean Paoli, Microsoft; Peter Sharpe, SoftQuad;


text:
Trial for 'El Chapo' set for April 2018
NEW YORK (AP) - A federal judge in Brooklyn has set an April 2018 trial date for Mexican drug lord Joaquin "El Chapo" Guzman.
Guzman answered judge's questions through an interpreter Friday. He spent half the hearing looking across the courtroom at his wife, who smiled and waved to him as she entered.
Defense lawyers complained that glass separated them from the defendant during their meetings, hindering communications. The judge said the matter will be investigated.
The 59-year-old defendant famous for twice escaping from prison in Mexico lost his bid Thursday to relax the terms of his confinement at a lower Manhattan lockup when U.S. District Judge Brian Cogan concluded that solitary confinement was appropriate.
Cogan said the U.S. government had good justifications for applying tough jail conditions on a man who escaped twice, including once through a mile-long tunnel stretching from the shower in his cell. But Cogan relaxed the restrictions known as Special Administrative Measures enough for Guzman to communicate with his wife through written questions and answers.
His lawyers said in a statement that it was "devastating" for Guzman and his wife that they will not be allowed jail visits.
Guzman was brought to the U.S. in January to face charges that he oversaw a multi-billion dollar international drug trafficking operation responsible for murders and kidnappings. He has pleaded not guilty.
He has remained in a 20-by-12-foot cell for 23 hours a day in a wing of the Metropolitan Correctional Center that often is used to house high-risk inmates including terrorists.
The U.S. government has said severe restrictions are necessary for Guzman in part because he used coded messages, bribes and other means to continue operating his drug empire from behind bars and arrange escapes.
Copyright 2017 The Associated Press. All rights reserved. This material may not be published, broadcast, rewritten or redistributed.

subset: commoncrawl


text:
This article is more than 1 year old
Scareware mongers cough up $8m to settle fraud charges
More than a million duped
Federal authorities will collect $8 million from members of a scareware operation that duped more than a million people into installing bogus security software on their computers.
Marc D'Souza and his father, Maurice D'Souza, agreed to pay $8.2 million in "ill-gotten gains" generated by the scam, which pimped software titles such as Winfixer, Drive Cleaner, and Antivirus XP. The operation worked by plastering legitimate websites with ads that were manipulated to look like antivirus scans that inevitably found infections that could only be fixed with packages that ranged from $40 to $60 in price.
The US Federal Trade Commission – which in 2008 brought fraud charges against Innovative Marketing, ByteHosting Internet Services, and several individuals – alleged the operation went to great lengths to trick some of the world's more popular websites into carrying the deceptive ads. When one site rejected the ads, the defendants formed sham advertising agencies that placed the malicious ads themselves.
The FTC has come under criticism in the past for delivering mild wrist slaps to internet-based fraudsters who are blatantly breaking the law. The case against Innovative Marketing and ByteHost shows the agency's better side. Government prosecutors doggedly pursued the defendants, some based overseas, after they failed to appear at court hearings and flouted a judge's order that they shut down their operation.
In 2009, defendant James Reno agreed to pay a reduced penalty of $116,000 and promised to get out of the scareware business for good. The FTC has already obtained default judgements against three other defendants. The case continues against the sole remaining defendant in the case, Kristy Ross.
More from the FTC is here. ®


text:
shadowrocket二维码分My research area is the topology and geometry of 3-manifolds. I was attracted to it because of the richness it acquired from Thurston's revolutionary work starting in the 1970s. His key insight was that many 3-manifolds admit homogeneous Riemannian metrics, and that one can study the topology of a 3-manifold via this geometry. This profusion of geometry has now been stunningly confirmed by Perelman's proof of the Geometrization Conjecture. As a direct result, while my work has focused on what initially seem like purely topological problems, in fact I have used a broad range of techniques to attack them, including hyperbolic geometry, number theory, and algebraic geometry, as well as more obviously related areas such as combinatorial group theory and the theory of foliations. These connections to other fields have led me to collaborate with number theorists, theoretical physicists and computer scientists, and in my papers I've used both the Langlands Conjecture and the Classification of Finite Simple Groups, as well as such topological oddities as "random 3-manifolds". I have been at University of Illinois at Urbana-Champaign since 2007. Previously, I spent four years at Harvard and four years at Caltech after getting my PhD from the University of Chicago sometime back in the 20th century. In 2013, I became a Fellow of the American Mathematical Society.shadowrocket二维码分
Office: 378 Altgeld Calendar
Dept. of Math., MC-382 PGP public key |


text:
We told you last week that Cakewalk is preparing to unleash its Z3TA+ 2 synth, and you now have the chance to get a taste of what it can do.
A new video features footage and sound of the synth being used, and reveals that it offers new waveshaping and filter types, enhanced effects control, a graphical arpeggiator and drag 'n' drop effects routing. Cakewalk has also revealed that there will be 'hundreds' of new sounds and backwards compatibility with the original Z3TA+.
Pricing and formats have still to be confirmed - Z3TA+ 2 should be available this month.


text: I would also recommend a roasted garlic couscous with this dish. Ingredients:2 pounds asparagus, tough ends trimmed, cut into 1-inch pieces 2 tablespoons chili powder 1/2 teaspoon garlic powder 1/2 teaspoon salt, divided 1 pound tilapia, Pacific sole or other firm white fish fillets 2 tablespoons extra-virgin olive oil 3 tablespoons lemon juice Directions:Bring 1 inch of water to a boil in a large saucepan. Put asparagus in a steamer basket, place in the pan, cover and steam until tender-crisp, about 4 minutes. Transfer to a large plate, spreading out to cool.Combine chili powder, garlic powder and 1/4 teaspoon salt on a plate. Dredge fillets in the spice mixture to coat. Heat oil in a large nonstick skillet over medium-high heat. Add the fish and cook until just opaque in the center, gently turning halfway, 5 to 7 minutes total. Divide among 4 plates. Immediately add lemon juice, the remaining 1/4 teaspoon salt and asparagus to the pan and cook, stirring constantly, until the asparagus is coated and heated through, about 2 minutes. Serve the asparagus with the fish.


text:
CB Tax Accounting
We work to keep the wind in your sails
Skip to content
Enrolled Agent, U.S. Tax Court Practitioner
Privacy Policy
Audits, Reviews, and Compilations
Bookkeeping/Write up
Business Consulting
Financial Analysis
Financial Statements
IRS Representation
Tax Preparation
Tax Preparation Fees
Financial Calculators
Record Retention Guide
IRS Publications
IRS Forms
Tax Appointment Checklist
Tax Rates
Tax Due Dates
Subscribe to Tax Calendar
IRS Withholding Calculator
Where is My Refund?
Latest Issue
Newsletter Archives
Tax Topics
The Tax Cuts & Jobs Act, TCJA, and its Impact on Miscellaneous Itemized Deductions and Charitable Contributions Deductions
The Tax Cuts & Jobs Act, TCJA, and its Impact on The Child and Dependent Care Credit
The Tax Cuts & Jobs Act, TCJA, New Income Tax Brackets, Impact on The Child Tax Credit and The Additional Child Tax Credit
Child Tax Credit & Additional Child Tax Credit
IRS To Use Private Collection Agencies
The Individual Health Care Mandate- What Does it Mean to You?
What is the Individual Health Mandate?
IRS Fresh Start Initiative
Failure-to-File (FTF) Penalty Relief Available
Foreclosure, Sale or Other Disposition
Abandoned Property
Request Appointment
Why Contact a Tax Pro?
Why Contact CB Tax Accounting?
Client Portal
Who We Are
Cancelled Debt – How Do I Know if I am Insolvent?
2018 Tax Updates
2017 Tax Updates
2016 Tax Provisions
2015 IRS Dirty Dozen Tax Schemes
Program Integrity of The PATH Act
Summary of The PATH Act
2016 Deadline Dates
2014 Tax Planning Strategies
2014 Inflation Adjustments
Individual Healthcare Mandates
EIC Requirements
Exemption & Pease Limitation
Strategies for Same-Sex Couples
Business Use of Home
Make a Payment
Tax Rates


text:
The Sangatte refugee camp near the Eurotunnel transport terminal in Calais accommodates more than 1,500 asylum seekers, most of them Afghans or Kurds. Most are intent on applying for refugee status in the UK -- a country believed to grant this status more readily and offer better social benefits. The asylum seekers wait without residence permits in the Red Cross-run camp, looking for an opportunity to enter England illegally by train or in a lorry.
The issue has become a tense one for the French and British governments. On July 12, French Minister of the Interior Nicolas Sarkozy and his English counterpart, David Blunkett, agreed that the camp, which has been open since September 1999, should be closed before April 2003. Furthermore, with the help of the United Nations High Commissioner for Refugees (UNHCR), the Afghans should be encouraged to return home "on a voluntary basis." This move reinforced activities underway in Great Britain to tighten the rules governing asylum, which are likely to result in the creation of detention centers and more efficient procedures for expulsion.
France and Great Britain are not alone on this issue. Asylum is a central issue in the new European immigration policy debate, which was initiated at the summit meeting in Seville. Recent statistics provided by the UNHCR, show a noteworthy drop in applications for asylum since 2001, particularly in Belgium and Holland, with a slowing in Germany. These trends are raising concerns that EU countries are gradually closing their frontiers to asylum seekers. Furthermore, it appears that restrictions in some countries may be leading to increases in applications in others.
For its part, France is believed to be experiencing a redistribution of asylum claims, with the number of applications increasing from 31,000 in 1999 to reach more than 47,000 in 2001. This represents a 53 percent increase over the 1999-2001 period compared with a 3.3 percent decrease in the UK, a 7.3 percent decrease in Germany, and a 17.1 percent decrease in the Netherlands. The actual number of asylum seekers in France is higher, since the application figures only count adults. Officials estimate that children make up another 12 to 15 percent on top of the 47,000 figure.
However, the total number of applications in France is even greater still if one includes the territorial asylum procedure. The so-called "RESEDA" law of May 11, 1998 created access to a "subsidiary" type of protection, provided by the Ministry of the Interior. This is in addition to the conventional type of asylum, for which the French authorities use a restrictive interpretation. As a result, for example, Algerian nationals persecuted by Islamic terrorists are excluded from conventional asylum claims and rely on territorial asylum to receive refugee status. Asylum seekers generally apply for one or the other status.
Unlike conventional asylum, those persons applying for territorial asylum do not benefit from social aid and housing, and it is more difficult for them to obtain asylum. The percentage of acceptances for territorial asylum reached three percent of nearly 12,000 applications in 2000, whereas for conventional asylum the percentage was about 17 percent. The majority of refugee associations working with asylum seekers are calling for wider accessibility to conventional asylum and for the abolition of territorial asylum. Together, the two types of asylum seekers totaled roughly 65,000 in 2001, not including children.
The growth in the number of applications for asylum has extended the time required to process asylum applications by the French Office for the Protection of Refugees and Stateless Persons (Office Français de Protection des Réfugiés et des Apatrides, OFPRA) from 4.2 months in 1999 to 7.1 months in 2001.
Problems encountered during the process further decrease the likelihood of making a successful asylum claim. For example, many asylum seekers do not have the opportunity to explain their case in person to French officials; only 40 percent of cases in 2001 were actually heard. Furthermore, housing problems have also worsened. Not enough beds are available -- for example, the 8,100 beds in place in 2001 met only 15 percent of the applicants' needs.
However, those lodged in specialized accommodations gain by the fact that their cases are better examined; the percentage of acceptances of applications for asylum in specialized accommodations rises to 50 percent, whereas the average is 17 percent.
Furthermore, one-third of the applications accepted are issued by the Refugee Appeal Commission, whose decisions override any previous refusal issued by the OFPRA. The high rate of approval for appeals has raised concerns that the low acceptance rate for initial applications has denied protection to bona fide asylum seekers.
To reduce the backlog and expedite the process, OFPRA has set up 48-hour "priority procedures" for applications that are "manifestly unfounded," or for those coming from countries labeled "safe" by the suspension clause C5 of Article 1 of the Geneva Convention. In such cases, the application is almost always systematically refused. In 2001, 3,724 applications were processed using this procedure. Thirteen new countries are to be added to the list of countries covered under the clause of suspension.
The government intends to introduce asylum reforms before the end of August 2002. On July 25, an inter-ministerial meeting laid down the basic guidelines for this reform: reducing the time required for responses to be given to asylum seekers and simplifying procedures. Refugee associations are concerned about further restricting access to asylum. Many claim that the situation is already critical, if not a disaster.


text:
Q: What styling products would you recommend for my 3-year-old niece, whose hair is very tight curly and frizzy? Her mother braids it tightly EVERY day, and her curls are beautiful if tamed and allowed to be defined, not a mass of frizz. I do not want it to be stiff or sticky…
Cozy: I can definitely understand why her mom braids it every day. Curly hair tends to get very fuzzy and frizzy if you don't know how to handle it. Using a great gel is KEY to managing the frizz. So Cozy Groovy Grape Styling Gel was created just for this purpose. A child's curly hair shouldn't be stiff, sticky or look wet. The gel should help to smooth the cuticle (thus preventing frizz"> without looking unnatural.
Q: I have a question about my little boy's 3c/4a hair. The curls at the back of his head (the spot that rubs against his car seat"> get messed up and the curls go straight — they stick straight out and the hair gets tangled. How do I keep the curls? Also, even with the leave-in conditioner, his hair tangles. And it just kills him for me to brush it out. Are there products that will keep him tangle-free?
Cozy: To help with the tangles, you need to know how to comb the hair properly to avoid hurting his scalp. And it is important that you use a good detangler that will help with the combing. Try So Cozy Fruity Delight Detangler & Leave-In Conditioner. Spray it on the parts of his hair that are most tangled. To comb, start at the bottom combing one inch at a time and holding the hair from above to prevent tugging on the scalp. Work your way up, inch by inch ,and continue around entire head.
Q: It looks like my 8-year-old daughter's hairline is receding. Is this possible? Can it be prevented? What can I do?
Cozy: Different people have different hairlines. It is impossible for me to give an opinion without seeing your daughter, but here are some thoughts. Do you notice that her hairline actually used to be different and is actually receding, or does it just appear this way because of something like a style change or haircut? Are you pulling it into tight ponytails or braids. Perhaps you need to consider a different style that may work better for her with her hair and features. I recommend that you talk to your pediatrician about this to rule out any medical problems and then consult a hairstylists that you trust for a professional style opinion.
Q: I have a 1-year-old boy with amazingly curly hair. He was born with it, but as it gets longer I don't know how to care for it so it will not be frizzy. I could also use some ideas on how to cut it.
Cozy: The most important thing I can tell you about caring for curly hair is that you should NEVER brush it. Brushing it causes the cuticle to stand up and will create frizz. Instead of brushing, you can comb his hair with a wide-tooth comb when conditioning in the bath. After the bath, squeeze out excess water and "scrunch" in So Cozy Kooky Kiwi Styling Cream. I love this styling cream because it is very light, but it keeps the hair from frizzing. It helps to define the curls and keep the cuticle smooth. This is also great for helping curls in the morning when "bed head" is a problem.
Q: I am looking for a great detangler for my daughter who is five and has 3c/4a hair! It is thick and almost waist length. I just do not want to fight with her any longer about knots and snarls because of the thickness, especially near the nape of the neck. Any suggestions?
Cozy: Your daughter's hair sounds amazing! It must be tricky to manage! What you need is the So Cozy "It takes two to Detangle Kit". It has everything you need to manage her hair on a daily basis. First, it has the So Cozy Luck Lime Pre-Detangling Treatment, which was created to use in the tub with a wide-tooth comb (also included in the kit">. The comb has a handy hook handle to keep in the tub. This is great to help you get through the very tough tangles without her damaging hair. Also included is the So Cozy Fruity Delight Detangler & Leave-in Conditioner, which you can spray in wet or dry hair. This is great for helping with the tangles at anytime, especially when there is no time for a bath. It also helps define curls and leaves hair smooth. The best part is that it is a leave-in conditioner so it will help maintain healthy hair.
Q: I need some suggestions about how to deal with my daughter's hair this summer. She's doing swim team, and is in the pool everyday. Last summer, her curls were fried by the end of June. How do we protect them from the ravages of chlorine and sun?
Cozy: You are so smart to plan ahead! Every fall I see the kids come in for their back-to-school haircuts with hair that feels like straw! Sun and chlorine wreak havoc on hair, so planning ahead is imperative. The best defense from the sun is to always wear a hat, but obviously it's not always possible. A liitle trick I use is that I leave in a little conditioner in my hair, rather than completely rinsing it out. This helps nourish the hair. However, keep in mind that this doesn't protect the scalp (that's where a hat or scarf come in handy">. The chlorine damage is a completely different issue. Using a Swimmer's Shampoo is crucial. Try So Cozy Green Apple Swimmer's Shampoo to help wash out the chlorine and other impurities caused by swimming. This shampoo is gentle enough to use daily. When you aren't able to shampoo hair directly after swimming, try at least to rinse the hair with cool water to remove some of the chlorine.


text:
With a spot of topical timing, given the recent controversy in the app promotion world, research firm Forrester has put out a new report exploring best practices for developers trying to get their apps noticed. Its findings include that word of mouth and social discovery play a key role in new apps finding loyal users, at least in Europe. The research also underlines the dominant role that mainline app stores continue to play in app discovery on the iOS and Android platforms. Forrester polled 4,315 European adults aged 16+ in Q4 2012 who had either an iPhone or an Android phone, some use of apps and were online monthly or more often for the report.
According to the data, far from being tired of flicking through packed app stores to find new stuff, Europe's smartphone users are evidently spending a lot of time app hunting on mainline stores — with both iPhone and Android users identifying this sort of "general browsing" on the App Store or Google Play as their most oft used method of discovering new apps (i.e. apps that they subsequently downloaded and now use on their phone). Browsing "top rated" and "most popular" app lists in these stores is also flagged up as the third most popular app discovery method. Word of mouth recommendations from friends/family slots between the two, as the second most common way to find new favourite apps.
The high ranking of personal recommendations underlines how pouring effort into marketing can only get an app developer so far, says Forrester. It's making a good enough app to get recommendations and rise up the app charts that really counts. Keeping audiences engaged enough to recommend an app means having a great app in the first place, not just a great app promotion, notes Forrester's Thomas Husson in a blog. "Influencing the influencers and integrating social features into your app will be increasingly key," he writes. "App developers and publishers… needed to measure the customer lifetime value and make sure their audiences would stay engaged."
Discussing "the growing dependency from publishers and developers to Apple and Google in the app economy", Husson adds: "Most app stores are considered a "black box." App store players share little to no information — and marketers have little control over app store merchandising. There are some tips here and there, like the precise 100-character description of your app in the Apple App store, the importance of the app description and icon design, the use of video demonstration in Google Play, the quality of the screenshots submitted, etc. However, having your app stand out from the crowd is far from just mastering App Store optimization or mobile advertising. Even if you could crack the Apple App Store ranking algorithm, you would still have to deliver a differentiated experience to maintain your app in the list of top 50 or top 100 applications. The use of advanced analytics and push notifications to maintain the quality of the app over time is key."
Forrester's research also suggests that cutting the odds of discovery by being pre-loaded on a phone can also work well for developers, with pre-loads coming in fourth place for app discovery, just ahead of hearing about an app via social networking websites. Also perhaps surprisingly popular as app discovery methods are general browsing on the internet and searching via search engines — which further underlines how much of an appetite smartphone users have for apps, since they are actively going out and hunting them down, outside of app stores. The report notes that mobile app usage has "grown dramatically over the past year", with 40% of online European consumers who own a mobile phone using mobile apps at least weekly (a figure that goes up to 56% in Sweden); and 29% using apps at least daily.
Direct advertisements for apps faired poorly in the survey, generating the lowest levels of app discovery that subsequently led to app use. The full chart follows below:


text:
Decorative Accents
Open and Close Vintage Sign
Width: 50.00 cm
Height: 115.00 cm
Depth: 00.00 cm
Availability: 1 in stock
Free Delivery to Malta & Gozo with orders over 30.00
Subscribe to our Newsletter and receive latest news
Width: 50.00 cm
Height: 115.00 cm
Depth: 00.00 cm
Availability: 1 in stock
On orders over €30 to Malta & Gozo
Gift Wrapping with any product
We will give you free design advice!
Monday to Friday: 9.00am – 13.00pm 16.00pm – 19.00pm
Saturday: 9.00am – 13.00pm
Wednesdays Afternoon –CLOSED
Whilst you're at it, sign up to receive email updates on the things you'll want to know about, including openings, launches and giveaways. Unsubscribe anytime.
I agree to receiving marketing and promotional materials *
Address: Vjal il-Ħaddiem, Ir-Rabat RBT 1769 Tel: +356 21451718 Mob: +356 79288688 Email: firstname.lastname@example.com


text:
In a former life, I was a stock analyst.
And believe it or not, I was actually a famous stock analyst.
First, I was famous for predicting that the stock of a money-losing Internet book store called Amazon would hit $400 a share.
Then, later, I got even more famous for calling a stock a "piece of junk" in an email and getting booted out of the industry.
(What can I say? The stock had crashed 90%. It was a piece of junk!)
Anyway, my $400 target on Amazon was actually not a particularly bold call. Amazon was already trading at $240, so it was akin to saying a $24 stock would go to $40. But Amazon was controversial in those days--many people were convinced it would go bust--and the extra zero made a difference. So I suddenly got famous.
Happily, Amazon's stock soon blasted through $400, making me look like a prophet instead of a moron.
Then it blasted all the way to $600 (split-adjusted).
Then, along with the rest of the dotcom pieces of junk, it completely cratered, falling to a low of $40 (split-adjusted) two years later.
And then, happily, many years later, unlike the vast majority of the other dotcom pieces of junk, Amazon actually fulfilled its early promises, clawing its way back to $400 again and then rising far beyond that. And today, it just hit a new high.
Thanks to two stock splits--a 2-for-1 and a 3-for-1--the equivalent of $400 a share today is about $66.67.
Amazon ticked $259 this morning.
In the old split, that's equivalent to $1,554.
Way to go, Amazon!
By the way, way back in 1997, Amazon went public at about $1.50 a share. With this morning's new high of $259, the stock has appreciated 173X from the IPO price.
That's what can happen when a great company with a massive opportunity goes public relatively earlier, focuses obsessively on the long-term, and gets better every day.
(And it's what can happen to investors when they get in relatively early, which today's IPO markets simply don't allow. When Amazon went public, it was valued at only $500 million. When Facebook went public, it was valued at $104 billion. It's hard to get a 100-bagger when you're already worth that kind of money.)
Anyway, hats off to Jeff Bezos and the rest of the amazing team at Amazon.
(And, lest this seem purely self-serving ego stroking, let me be the first to point out the many other calls I got completely wrong. I loved Yahoo, for example. And I missed the top of the bubble. And I'm certainly not taking any credit for the remarkable success Amazon has delivered...)


text:
Saturday 03/23/2013
Clemson, SC –
Every Tiger starter had at least one hit and Zack Erwin pitched 4.1 scoreless innings in relief in Clemson's 8-4 win over Duke in the first game of a doubleheader at Doug Kingsmore Stadium on Saturday afternoon. The Tigers, who took a 2-0 lead in the series, improved to 15-7 overall and 5-3 in the ACC. The Blue Devils fell to 11-12 overall and 2-6 in ACC play.
Erwin (2-0) earned the win by allowing just three hits, no runs, and one walk with three strikeouts in 4.1 innings pitched in relief.
Duke starter Drew Van Orden (1-3) suffered the loss, as he gave up five hits, five runs (three earned), and three walks with three strikeouts in 3.0 innings pitched.
The Blue Devils scored their first runs of the series in the top of the first inning. Jeff Kremer lined a one-out double to left-center and Grant McCabe walked. Two batters later, Jordan Betts grounded a two-out single up the middle to score Kremer. Matt Berezo followed with another single up the middle to plate McCabe.
In the bottom of the first inning, Steven Duggar reached with one out and advanced to second on a throwing error by Betts at third. Two batters later with two outs, Garrett Boulware flared a 1-2 pitch to right field for a single to score Duggar.
Thomas Brittle led off the second inning with an eight-pitch walk and advanced to third on an error on a failed pickoff attempt. Brittle then tied the score when he came home on a wild pitch.
In the third inning, Steve Wilkerson grounded a one-out double down the right-field line and scored on Boulware's single to left field to give Clemson a 3-2 lead.
Jay Baum led off the fourth inning with a five-pitch walk and stole second. Tyler Krieger lined a single to center to score Baum. Three batters later, Wilkerson laced a two-out double down the left-field line to score Krieger.
In the top of the fifth inning, Andy Perez led off with a single up the middle and Grant McCabe later hit a one-out single up the middle. After Perez was picked off second for out #2, Chris Marconcini lined a double to right-center to score McCabe. Betts then laced a double down the left-field line to score Marconcini, cutting Clemson's lead to 5-4.
Clemson responded in the bottom of the fifth inning. Shane Kennedy led off with a single to left and stole second. Three batters later with two outs, Baum belted a single through the left side to score Kennedy. It was the 10th inning in a row Clemson scored at least one run dating to Friday's game.
Jon McGibbon led off the eighth inning with a single up the middle and Brittle reached on a bunt single, then both runners moved up a base on a wild pitch. After the next two Tigers were retired, Tyler Slaton grounded a two-out single up the middle to score McGibbon and Brittle.
Boulware went 2-for-4 with two RBIs to lead Clemson's 12-hit attack. Wilkerson and Kennedy also added two hits apiece.
Kremer went 3-for-5 with a double and run to lead Duke, who totaled 12 hits in the contest.
Clemson and Duke will play the second game of the doubleheader and game-three of the three-game series on Saturday at approximately 4:20 PM.
February 12, 2024
February 9, 2024
February 6, 2024
February 3, 2024


text:
Daniels unseats Jin for city mayor
March 8, 2007
By ANDY KIRKALDY
VERGENNES — Former alderman Michael Daniels unseated one-term Vergennes Mayor April Jin in balloting on Tuesday, 260-175.
Daniels, a 38-year member of the Vergennes Fire Department and a retired Vermont Army National Guard sergeant, said during his campaign he planned to tap volunteers to improve city services and keep city spending under control.
Daniels, who manages two dozen buildings and 40 employees for the Vermont Department of Buildings and General Services, said he would also use his and others' expertise to try to operate the city's buildings and equipment more efficiently and cost-effectively.
Jin, who served as an alderman before running unopposed for mayor two years ago, faced several controversial issues in her term, including conflicts with state officials about funding for the city for hosting Northlands Job Corps and about whether Vergennes should host a mental health facility.
Nor did all in the city agree with her stance favoring a potential $1 million sewer-extension deal with a private developer, who wanted to run a line into Ferrisburgh.
On the issue of proposing future sewer extensions, residents also overwhelmingly supported a proposed city charter change on Tuesday that would not allow aldermen to strike a deal for any sewer extension of any size outside the boundaries of the city without calling for a public vote. The vote went 315-78.
But even with that support of the charter change, the decision to make any changes will ultimately rest with the legislature, and could also hinge on whether the newly-constituted council supports it.
Jin believed the unpopularity of the sewer extension question played a role in her defeat.
"I think that was the driving issue. No doubt about it," she said.
Jin declined to comment on her accomplishments in office. She generally earned high marks for the time and energy she devoted to the job, and her other civic commitments, including her ongoing service as chairwoman of the Hannaford Career Center board and as a member of the Vergennes Union High School board. During her campaign Jin also said she took pride in her efforts to control spending and develop positive relations with Northlands.
Jin said now it may be time for her to move closer to her grandchildren, several of whom live in the metropolitan New York City area.
"I want to see more of my grandchildren, and seriously I'm going to move wherever my grandchildren end up," she said.
In the five-way race for three two-year terms on the city council, Diane Lanpher, a former Democratic candidate for the Vermont House, emerged as the top vote-getter. Lanpher, who works with the Department of Health to fight substance abuse, earned 303 votes.
Also winning election to the Vergennes City Council were incumbent Randy Ouellette, owner of R&K Woodworking, with 261 votes, and newcomer Christine Collette, manager of the Vergennes branch of the Merchants Bank, with 257 votes. Collette has served in the past on the city's planning commission and the Vergennes-Panton Water District board.
Trailing the winners were two new faces on the city ballot — Mathew Chabot, manager of Macy's Department Store in Burlington, with 157 votes, and Peter Garon, who works in human resources for the state, with 132 votes.
Aldermen Craig Minor, Clara "Ziggy" Comeau and David Austin's terms were not up this March.
On the school front, the proposed $3.4 million Vergennes Union Elementary School budget passed in Vergennes, Panton and Waltham, 347-295. It calls for a 4.9 percent increase in spending.
The $8.06 million VUHS budget passed in the five Addison Northwest Supervisory Union towns, 750-696.
Vergennes residents do not vote on city spending. Aldermen will come up with a budget for the 2007-2008 fiscal year, which begins on July 1, by the end of June.