Access your email via any WAP/XHTML enabled mobile phone or PDA
Your email account supports operation via wireless devices allowing you to send and receive emails via mobile phones or a PDA. Log on for access to your email account, and enjoy all the options that you find in your usual WebMail account
The service is easy to use. Under the menu 'services' on your mobile-device or PDA, visit the domain of your email account: http://yourdomain.com/xhtml.php (change domain name to your host) Then simply log on by entering your user name and password. Via your mobile phone you can access email resources wireless. The wireless mode includes 5 main functions:
Access you email, any where, any time. For more information, or service difficulties, please contact your email service provider.


WELCOME TO THE HALLOWEEN PART
Hi, there is alot of really good information in this page, but as you can see it is very big (the page) so I tried to meke it a little bit easir for YOU; as you can see, I have put in BOLD, and ITALIC all the clue words, or the words that are important. OK!, and don´t forge to answer the QUIZ.
Halloween is holiday observed on the evening of October 31 in most areas of North America and in some areas of Western Europe. The holiday is symbolically associated with death and the supernatural. Halloween falls on the eve of All Saints Day, also known as Allhallows or Hallowmas, a holy day in the Roman Catholic and Anglican churches. Originally a pagan festival of the dead, All Saints Day was established by the Catholic Church in the 9th century to honor Christian saints. All Souls Day, a holy day established by the Catholic Church in the 10th century, is also closely linked to Halloween. All Souls Day, on November 2, is observed to help purify the spirits of the dead.
Halloween is historically related to similar folk
holidays celebrated in other countries. The Day of the Dead, a Mexican holiday that
coincides with All Souls Day, blends Roman Catholic and Native American traditions
about the souls of the dead. On the Day of the Dead, Mexicans decorate their homes with
playful imagery of animated human skeletons, leave offerings of food for wandering
spirits, and tend the graves of their deceased relatives. In England, Guy Fawkes
Day, celebrated on November 5, has largely taken the place of Halloween. On this patriotic
holiday, children light bonfires and burn effigies of Guy Fawkes, a conspirator who tried
to blow up the English Parliament building in 1605.
Customs
Most Halloween festivities are based on folk
beliefs concerning supernatural forces and spirits of the dead. Halloween decorations
typically feature imagery associated with supernatural beings such as witches, werewolves,
vampires, and ghosts. Images thought to symbolize bad omenssuch as black cats, bats,
and spidersare also commonly featured in Halloween decorations.
The most celebrated Halloween decoration is the
jack-o-lantern, traditionally a hollowed-out pumpkin carved to resemble a
grotesque face and illuminated by a candle placed inside. The jack-o-lantern derives
its name from a character in British folktales. According to these tales, the soul of a
deceased person named Jack OLantern was barred from both heaven and hell and was
condemned to wander the earth with his lantern. Orange and black, colors associated with
pumpkins and darkness respectively, figure prominently in most Halloween decorations.
Dressing in costume is one of the most popular Halloween customs, especially among children. Traditional costumes usually represent witches, ghosts, and other supernatural beings. However, costumes inspired by contemporary popular culture, such as politicians or movie characters, have become increasingly common in recent years. Adults often favor costumes with satirical or humorous overtones.
Trick-or-treating is another Halloween
tradition, in which costumed children go from house to house soliciting candy or other
treats from their neighbors. According to this custom, children greet each homeowner with
the cry "Trick or Treat," suggesting that some sort of prank will be played
unless treats are provided. Formerly, trick-or-treaters vandalized the house if no treats
were produced or if the treats met with their disapproval. Since the early 20th century,
however, the threat of tricks has been largely ceremonial. Beginning in the 1970s, the
practice of trick-or-treating went into a sharp decline after unsubstantiated rumors
spread about homeowners distributing poisoned Halloween candy to children. Many parents
also became concerned about their children wandering through the neighborhood after dark.
Today, many parents accompany children when they go trick-or-treating.
In some areas of the country, costume parties have replaced trick-or-treating as the favored form of Halloween entertainment. Hosts of these parties often hold contests to select the best costume among the guests. Traditional Halloween diversions have also enjoyed renewed popularity as party activities. For example, many Halloween parties feature contests of bobbing for apples, a centuries-old game in which contestants try to retrieve apples floating in a tub of water using only their mouth. While childrens Halloween parties are generally held in private homes, many bars and nightclubs sponsor modified versions of such festivities for adults.
Origins
Many of the ancient
peoples of Europe marked the end of the harvest season and the beginning of winter by
celebrating a holiday in late autumn. The most important of these holidays to influence
later Halloween customs was Samhain, a holiday observed by the ancient Celts, a
tribal people who inhabited most of Western and Central Europe in the first millennium BC.
Among the Celts, Samhain marked the end of one year and the beginning of the next. It was
one of four Celtic holidays linked to important transitions in the annual cycle of
seasons.
Samhain began at sundown on October 31 and
extended into the following day. According to the Celtic pagan religion, known as
Druidism, the spirits of those who had died in the preceding year roamed the earth on
Samhain evening. The Celts sought to ward off these spirits with offerings of food and
drink. The Celts also built bonfires at sacred hilltop sites and performed rituals, often
involving human and animal sacrifices, to honor Druid deities.
By the end of the 1st century AD, the Holy Roman
Empire had conquered most of the Celtic lands. In the process of incorporating the Celts
into their empire, the Romans adapted and absorbed some Celtic traditions as part of their
own pagan and Catholic religious observances. In Britain, Romans blended local Samhain
customs with their own pagan harvest festival honoring Pomona, goddess of fruit trees.
Some scholars have suggested that the game of bobbing for apples derives from this Roman
association of the holiday with fruit.
Pure Celtic influences lingered longer on the western fringes of Europe, especially in areas that were never brought firmly under Roman control, such as Ireland, Scotland, and the Bretagne region of northwestern France. In these areas, Samhain was abandoned only when the local people converted to Christianity during the early Middle Ages, a period that lasted from the 5th to the 15th century. The Roman Catholic Church often incorporated modified versions of older religious traditions in order to win converts. For example, Pope Gregory IV sought to replace Samhain with All Saints Day in 835. All Souls Day, closer in spirit to Samhain and modern Halloween, was first instituted at a French monastery in 998 and quickly spread throughout Europe. Folk observances linked to these Christian holidays, including Halloween, thus preserved many of the ancient Celtic customs associated with Samhain.
Halloween traditions thought to be incompatible
with Christianity often became linked with Christian folk beliefs about evil spirits.
Although such superstitions varied a great deal from place to place, many of the
supernatural beings now associated with Halloween became fixed in the popular imagination
during the late Middle Ages and the Renaissance (14th to 17th century). In British
folklore, small magical beings known as fairies became associated with Halloween mischief.
The jack-o-lantern, originally carved from a large turnip rather than a pumpkin,
originated in medieval Scotland. Various methods of predicting the future, especially
concerning matters of romance and marriage, were also prominent features of Halloween
throughout the British Isles.
Between the 15th and 17th centuries, Europe was seized by a hysterical fear of witches, leading to the persecution of thousands of innocent women. Witches were thought to ride flying brooms and to assume the form of black cats. These images of witches soon joined other European superstitions as symbols of Halloween.
Halloween in the USA
Attitudes toward Halloween varied widely among the various European groups that settled in North America. New England was initially settled by English Puritans, members of a strict Protestant sect that rejected Halloween as a Catholic and pagan holiday (see Puritanism). However, other British colonists successfully transplanted Halloween traditions in southern colonies such as Virginia and Maryland. Irish immigrants helped popularize Halloween traditions throughout the United States in the mid-19th century. As belief in many of the old superstitions waned during the late 19th century, Halloween was increasingly regarded as a childrens holiday.
In the 19th and early 20th centuries, young people often observed Halloween by perpetrating minor acts of vandalism, such as overturning sheds or breaking windows. Beginning in the 1930s, Halloween mischief gradually transformed into the modern ritual of trick-or-treating. Eventually, Halloween treats were plentiful while tricks became rare. Nonetheless, the tradition of Halloween pranks still survives. In some areas, October 30 (one day before Halloween) is called Mischief Night, and vandalism often reaches dangerous levels. In Detroit, Michigan, Mischief Nightknown there as Devils Nightprovided the occasion for waves of arson that sometimes destroyed whole city blocks during the 1970s and 1980s.
Since the 1970s, Halloween celebrations have become increasingly popular among adults. The Halloween parade in the Greenwich Village neighborhood of New York City features elaborate satirical costumes and drunken revelry. Especially popular among the local gay population, the Greenwich Village parade serves as a model for many other adult Halloween celebrations around the country. Similarly boisterous public Halloween festivities are celebrated in San Francisco, California; New Orleans, Louisiana; and Key West, Florida.


{% extends 'base.html' %}{% block content %}
Uploaded By:
{{image.user}}
{{image.date_uploaded|timesince|upper}} AGO
{{image.likes}} Likes
{{comment.user}}{{comment.comment}}


attribute, is a static
error.
It is a static error if there is a stylesheet module in a package that
specifies input-type-annotations="strip"
and another
stylesheet module that specifies
input-type-annotations="preserve"
, or if a
stylesheet module specifies the value strip
or
preserve
and the same value is not specified on the
xsl:package
element of
the containing package.
It is a static error if within any package the
same NameTestXP30
appears in both an xsl:strip-space
and an
xsl:preserve-space
declaration if both have the same import precedence.
Two NameTests are considered the same if they match the same set of
names (which can be determined by comparing them after expanding
namespace prefixes to URIs).
In the case of a prefixed lexical QName used as the value (or as part of the value) of an attribute in the stylesheet, or appearing within an XPath expression in the stylesheet, it is a static error if the defining element has no namespace node whose name matches the prefix of the lexical QName.
Where an attribute is defined to contain a pattern, it is a static error if the pattern does not match the production Pattern30.
It is a static error if an unescaped left curly bracket appears in a fixed part of a value template without a matching right curly bracket.
It is a static error if an unescaped right curly bracket occurs in a fixed part of a value template.
An xsl:template
element must have either a
match
attribute or a name
attribute, or
both. An xsl:template
element that has no match
attribute must have no mode
attribute and no
priority
attribute. An xsl:template
element that has
no name
attribute must have
no visibility
attribute.
The value of the priority
attribute [ of the
xsl:template
element]
must conform to the rules for the
xs:decimal
type defined in [XML
Schema Part 2]. Negative values are permitted.
It is a static error if an xsl:mode
declaration specifying
initial="no"
contains an xsl:context-item
element.
It is a static error if a named or unnamed mode contains two
conflicting values for the same attribute in different xsl:mode
declarations having the
same import precedence, unless there is
another definition of the same attribute with higher import
precedence. The attributes in question are the attributes other
than name
on the xsl:mode
element, and the
as
attribute on the contained xsl:context-item
element
if present.
It is a static error if there is both (a) a
mode definition in the stylesheet
that has the effective attribute values
streamable="yes"
and initial="yes"
, and
(b) a global variable in the stylesheet
whose initializing expression is not motionless with respect to its
context item, as defined in 19
Streamability.
It is a static error if the list of modes [in the
mode
attribute of xsl:template
] is empty, if
the same token is included more than once in the list, if the list
contains an invalid token, or if the token #all
appears together with any other value.
It is a static error if the values of the
name
attribute of two sibling xsl:param
elements represent the
same expanded QName.
It is a static error if a variable-binding element has a
select
attribute and has non-empty content.
It is a static error if a stylesheet contains more than one non-hidden binding of a global variable with the same name and same import precedence, unless it also contains another binding with the same name and higher import precedence.
It is a static error if a stylesheet contains an
xsl:call-template
instruction whose name
attribute does not match the
name
attribute of any named template
visible in the containing package (this includes any template defined in
this package, as well as templates accepted from used packages
whose visibility in this package is not hidden
). For
more details of the process of binding the called template, see
<IP_ADDRESS> Binding References to
Components.
It is a static error if a package contains more than one non-hidden template with the same name and the same import precedence, unless it also contains a template with the same name and higher import precedence.
It is a static error if two or more sibling xsl:with-param
elements have
name
attributes that represent the same expanded
QName.
In the case of xsl:call-template
, it is
a static error to pass a non-tunnel parameter
named x to a template that does not have a
non-tunnel template parameter
named x, unless the xsl:call-template
instruction is processed with XSLT 1.0
behavior.
It is a static error if a template that is invoked
using xsl:call-template
declares a template parameter specifying
required="yes"
and not specifying
tunnel="yes"
, if no value for this parameter is
supplied by the calling xsl:call-template
instruction.
It is a static error if the value of the
use-attribute-sets
attribute of an xsl:copy
, xsl:element
, or xsl:attribute-set
element, or the xsl:use-attribute-sets
attribute of a
literal result element, is not a
whitespace-separated sequence of EQNames, or if it contains a
QName that does not match the name
attribute of any
xsl:attribute-set
declaration in the stylesheet.
It is a static error if an xsl:attribute-set
element
directly or indirectly references itself via the names contained in
the use-attribute-sets
attribute.
It is a static error if a stylesheet function has a name that is in no namespace.
Because arguments to a stylesheet function call must all be specified, the xsl:param
elements within an
xsl:function
element
must not specify a default value: this
means they must be empty, and
must not have a select
attribute.
It is a static error for a package to contain two or more non-hidden functions with the same expanded QName, the same arity, and the same import precedence, unless there is another function with the same expanded QName and arity, and a higher import precedence.
It is a static error if an attribute on a literal result element is in the XSLT namespace, unless it is one of the attributes explicitly defined in this specification.
It is a static error if a namespace prefix is used
within the [xsl:]exclude-result-prefixes
attribute and
there is no namespace binding in scope for that prefix.
It is a static error if the value
#default
is used within the
[xsl:]exclude-result-prefixes
attribute and the parent
element of the [xsl:]exclude-result-prefixes
attribute
has no default namespace.
It is a static error if within a package
there is more than one such declaration [more than one xsl:namespace-alias
declaration] with the same literal namespace
URI and the same import precedence and different
values for the target namespace URI, unless
there is also an xsl:namespace-alias
declaration with the same literal namespace
URI and a higher import precedence.
It is a static error if a value other than
#default
is specified for either the
stylesheet-prefix
or the result-prefix
attributes of the xsl:namespace-alias
element when there is no in-scope binding for that namespace
prefix.
It is a static error if the select
attribute of the xsl:attribute
element is
present unless the element has empty content.
It is a static error if the select
attribute of the xsl:value-of
element is
present when the content of the element is non-empty
It is a static error if the select
attribute of the xsl:processing-instruction
element is present unless the element has empty content.
It is a static error if the select
attribute of the xsl:namespace
element is
present when the element has content other than one or more
xsl:fallback
instructions, or if the select
attribute is absent
when the element has empty content.
It is a static error if the select
attribute of the xsl:comment
element is present
unless the element has empty content.
It is a static error if the value
attribute of xsl:number
is present unless the select
, level
,
count
, and from
attributes are all
absent.
It is a static error if an xsl:sort
element with a
select
attribute has non-empty content.
It is a static error if an xsl:sort
element other than the
first in a sequence of sibling xsl:sort
elements has a
stable
attribute.
It is a static error if an xsl:perform-sort
instruction with a select
attribute has any content
other than xsl:sort
and
xsl:fallback
instructions.
It is a static error if the current-group
function is
used within a pattern.
It is a static error if the current-grouping-key
function is used within a pattern.
These four attributes [the group-by
,
group-adjacent
, group-starting-with
, and
group-ending-with
attributes of xsl:for-each-group
] are
mutually exclusive: it is a static error if none of these four
attributes is present or if more than one of them is present.
It is a static error to specify the
collation
attribute or the
composite
attribute if neither the
group-by
attribute nor group-adjacent
attribute is specified.
It is a static error if the xsl:analyze-string
instruction contains neither an xsl:matching-substring
nor an xsl:non-matching-substring
element.
It is a static error if an xsl:key
declaration has a
use
attribute and has non-empty content, or if it has
empty content and no use
attribute.
It is a static error if the xsl:key
declaration has a
collation
attribute whose value (after resolving
against the base URI) is not a URI recognized by the implementation
as referring to a collation.
It is a static error if there are several xsl:key
declarations in the
same package with the same key name and
different effective collations. Two collations are the same if
their URIs are equal under the rules for comparing
xs:anyURI
values, or if the implementation can
determine that they are different URIs referring to the same
collation.
It is a static error if there are several xsl:key
declarations in the
stylesheet with the same key name and
different effective values for the composite
attribute.
It is a static error if a named or unnamed decimal
format contains two conflicting values for the same attribute
in different xsl:decimal-format
declarations having the same import precedence,
unless there is another definition of the same attribute with
higher import precedence.
It is a static error if the character specified in
the zero-digit
attribute is not a digit or is a digit
that does not have the numeric value zero.
It is a static error if, for any named or unnamed decimal format, the variables representing characters used in a picture string do not each have distinct values. These variables are decimal-separator-sign, grouping-sign, percent-sign, per-mille-sign, digit-zero-sign, digit-sign, and pattern-separator-sign.
It is a static error if there is no namespace bound
to the prefix on the element bearing the
[xsl:]extension-element-prefixes
attribute or, when
#default
is specified, if there is no default
namespace.
It is a static error if both the
[xsl:]type
and [xsl:]validation
attributes are present on the xsl:element
, xsl:attribute
, xsl:copy
, xsl:copy-of
, xsl:document
, or xsl:result-document
instructions, or on a literal result
element.
It is a static error if the value of the
type
attribute of an xsl:element
, xsl:attribute
, xsl:copy
, xsl:copy-of
, xsl:document
, or xsl:result-document
instruction, or the xsl:type
attribute of a literal
result element, is not a valid QName
, or if it uses a
prefix that is not defined in an in-scope namespace declaration, or
if the QName is not the name of a type definition included in the
in-scope schema components for
the stylesheet.
It is a static error if the value of the
type
attribute of an xsl:attribute
instruction
refers to a complex type definition
It is a static error if two xsl:output
declarations within
an output definition specify explicit
values for the same attribute (other than
cdata-section-elements
and
use-character-maps
), with the values of the attributes
being not equal, unless there is another xsl:output
declaration within
the same output definition that has higher
import precedence and that specifies an explicit value for the same
attribute.
The value [of the method
attribute on xsl:output
] must (if present) be a valid EQName. If it is a lexical
QName with no a prefix, then it identifies a method specified
in [XSLT and XQuery
Serialization] and must be one of
xml
, html
, xhtml
, or
text
.
It is a static error if the stylesheet contains two or more character maps with the same name and the same import precedence, unless it also contains another character map with the same name and higher import precedence.
It is a static error if a name in the
use-character-maps
attribute of the xsl:output
or xsl:character-map
elements does not match the name
attribute of any
xsl:character-map
in the stylesheet.
It is a static error if a character map references
itself, directly or indirectly, via a name in the
use-character-maps
attribute.
A non-schema-aware processor
must signal a static error if the
stylesheet includes an xsl:import-schema
declaration.
A non-schema-aware processor
must signal a static error if the
stylesheet includes an [xsl:]type
attribute, or an [xsl:]validation
or
[xsl:]default-validation
attribute with a value other
than strip
, preserve
, or
lax
.
It is a static error if the number of xsl:merge-key
children of a
xsl:merge-source
element is not equal to the number of xsl:merge-key
children of
another xsl:merge-source
child of
the same xsl:merge
instruction.
It is a static error if the exposed visibility of a component is inconsistent with its potential visibility, as defined in the above table, unless the token that matches the component is a wildcard, in which case it is treated as not matching that component.
It is a static error if an xsl:expose
element matches no
components in the containing package, unless the tokens in the
names
attribute are all wildcards.
It is a static error if an xsl:accept
element matches no
components in the used package, unless the tokens in its
names
attribute are all wildcards.
It is a static error if the visibility assigned to a
component by an xsl:accept
element is
incompatible with the visibility of the corresponding component in
the used package, as defined by the above table, unless the token
that matches the component name is a wildcard, in which case the
xsl:accept
element is
treated as not matching that component.
It is a static error if the xsl:use-package
elements in
a package manifest cause two or more
homonymous components to be accepted with a
visibility other than hidden
.
It is a dynamic error if an invocation of an absent
component (that is, an abstract component accepted into a using
package with visibility="absent"
) is evaluated.
It is a static error if a component declaration
appearing as a child of xsl:override
is homonymous
with any other declaration in the using package, regardless of
import precedence, including any other
overriding declaration in the package manifest of the using
package.
It is a static error if a component declaration
appearing as a child of xsl:override
does not match
(is not homonymous with) some component in the used
package.
It is a static error if the component referenced by
an xsl:override
declaration has visibility other than public
or
abstract
It is a static error if the signature of an overriding component is not compatible with the signature of the component that it is overriding.
It is a static error if a top-level package intended
for execution (as distinct from a library package) contains
symbolic references referring to components whose visibility is
abstract
.
It is a static error if an xsl:break
or xsl:next-iteration
element appears other than in a tail position within the
sequence constructor forming the
body of an xsl:iterate
instruction.
It is a static error if the select
attribute of xsl:break
or
xsl:on-completion
is present and the instruction has children.
It is a static error if the name
attribute of an xsl:with-param
child of an
xsl:next-iteration
element does not match the name
attribute of an
xsl:param
child of the
innermost containing xsl:iterate
instruction.
It is a static error if the select
attribute of the xsl:try
element is present and the element has children other than xsl:catch
and xsl:fallback
elements.
It is a static error if the select
attribute of the xsl:catch
element is present
unless the element has empty content.
It is a static error if the select
attribute of xsl:sequence
is present and
the instruction has children other than xsl:fallback
.
It is a static error if two sibling xsl:merge-source
elements
have the same name, whether explicit or implicit.
It is a static error if an xsl:merge-key
element with a
select
attribute has non-empty content.
It is a static error if a variable bound in the
bind-group
or bind-grouping-key
attribute
of an xsl:for-each-group
instruction is referenced within an expression in the
lang
, order
, collation
,
stable
, case-order
, or
data-type
attributes of an xsl:sort
child of that xsl:for-each-group
instruction.
It is a static error if the
bind-grouping-key
attribute is present on an xsl:for-each-group
instruction unless either the group-by
or
group-adjacent
attribute is present.
It is a static error if the set of variable names
declared using the bind-group
and
bind-key
attributes of an xsl:merge
instruction and the
bind-source
attributes of its xsl:merge-source
children
contains any duplicates.
It is a static error if the select
attribute of the xsl:map-entry
element is
present unless the element has has no children other than xsl:fallback
elements.
It is a static error if an xsl:template
declaration has
the name xsl:initial-template
and contains an xsl:param
that specifies
required="yes"
.
It is a static error for a package to contain two or more non-hidden accumulators with the same expanded QName and the same import precedence, unless there is another accumulator with the same expanded QName, and a higher import precedence.
It is a static error for a package to contain a non-hidden accumulator if either the pre-descent or post-descent functions have the same name as a non-hidden stylesheet function in the same package.
It is a static error if the the
visibility
attribute of a stylesheet parameter that
specifies required="yes"
and does not specify
static="yes"
is present with a value other than
public
, final
, or abstract
,
or if an xsl:expose
or
xsl:accept
declaration
attempts to modify the visibility of such a component to a value
other than public
, final
, or
abstract
.
It is a static error if the stylesheet contains a construct that is declared to be streamable but which is not guaranteed-streamable, unless the user has indicated that the processor is to handle this situation by processing the stylesheet without streaming or by making use of processor extensions to the streamability rules where available.
Type errors
It is a type error if the result of evaluating the sequence constructor cannot be converted to the required type.
It is a type error if an xsl:apply-templates
instruction with no select
attribute is evaluated when
the context item is not a node.
It is a type error if the supplied value of a variable cannot be converted to the required type.
It is a type error if the conversion of the supplied value of a parameter to its required type fails.
If a default value is given explicitly, that is, if there is
either a select
attribute or a non-empty sequence constructor, then it is a
type
error if the default value cannot be converted to the required
type, using the function conversion
rules.
If the as
attribute [of xsl:function
] is specified,
then the result evaluated by the sequence
constructor (see 5.8
Sequence Constructors) is converted to the required type,
using the function conversion rules.
It is a type error if this conversion fails.
If the value of a parameter to a stylesheet function cannot be converted to the required type, a type error is signaled.
It is a type error to use the xsl:copy
or xsl:copy-of
instruction to copy
a node that has namespace-sensitive content if the
copy-namespaces
attribute has the value
no
and its explicit or implicit
validation
attribute has the value
preserve
. It is also a type error if either of these
instructions (with validation="preserve"
) is used to
copy an attribute having namespace-sensitive content, unless the
parent element is also copied. A node has namespace-sensitive
content if its typed value contains an item of type
xs:QName
or xs:NOTATION
or a type derived
therefrom. The reason this is an error is because the validity of
the content depends on the namespace context being preserved.
It is a type error if the xsl:number
instruction is
evaluated, with no value
or select
attribute, when the context item is not a node.
It is a type error if the result of evaluating the
select
attribute of the xsl:number
instruction is
anything other than a single node.
If any sort key value, after atomization and any type
conversion required by the
data-type
attribute, is a sequence containing more
than one item, then the effect depends on whether the xsl:sort
element is
processed with XSLT 1.0 behavior. With XSLT 1.0
behavior, the effective sort key value is the first item in
the sequence. In other cases, this is a type error.
It is a type error if the result of evaluating the
group-adjacent
expression is an empty sequence or a
sequence containing more than one item, unless
composite="yes"
is specified.
If the validation
attribute of an xsl:element
, xsl:attribute
, xsl:copy
, xsl:copy-of
, or xsl:result-document
instruction, or the xsl:validation
attribute of a
literal result element, has the effective value
strict
, and schema validity assessment concludes that
the validity of the element or attribute is invalid or unknown, a
type
error occurs. As with other type errors, the error may be signaled statically if it can be detected
statically.
If the validation
attribute of an xsl:element
, xsl:attribute
, xsl:copy
, xsl:copy-of
, or xsl:result-document
instruction, or the xsl:validation
attribute of a
literal result element, has the effective value
strict
, and there is no matching top-level declaration
in the schema, then a type error occurs. As with other type errors,
the error may be signaled statically if
it can be detected statically.
If the validation
attribute of an xsl:element
, xsl:attribute
, xsl:copy
, xsl:copy-of
, or xsl:result-document
instruction, or the xsl:validation
attribute of a
literal result element, has the effective value lax
,
and schema validity assessment concludes that the element or
attribute is invalid, a type error occurs. As with other type errors,
the error may be signaled statically if
it can be detected statically.
It is a type error if the value of the
type
attribute of an xsl:copy
or xsl:copy-of
instruction refers
to a complex type definition and one or more of the items being
copied is an attribute node.
It is a type error if an [xsl:]type
attribute is defined for a constructed element or attribute, and
the outcome of schema validity assessment against that type is that
the validity
property of that element or attribute
information item is other than valid
.
A type error occurs if a type
or
validation
attribute is defined (explicitly or
implicitly) for an instruction that constructs a new attribute
node, if the effect of this is to cause the attribute value to be
validated against a type that is derived from, or constructed by
list or union from, the primitive types xs:QName
or
xs:NOTATION
.
A type error occurs [when a document node is validated] unless the children of the document node comprise exactly one element node, no text nodes, and zero or more comment and processing instruction nodes, in any order.
It is a type error if, when validating a document node, document-level constraints (such as ID/IDREF constraints) are not satisfied.
It is a type error if some item selected by a
particular merge key in one input sequence is not comparable using
the XPath le
operator with some item selected by the
corresponding sort key in another input sequence.
It is a type error if the xsl:context-item
child of
xsl:template
specifies
that a context item is required and none is supplied by the caller,
that is, if the context item is absent at the point where xsl:call-template
is
evaluated.
It is a type error if an xsl:apply-templates
instruction in a particular mode
selects an element or
attribute whose type is xs:untyped
or
xs:untypedAtomic
when the typed
attribute
of that mode specifies the value yes
,
strict
, or lax
.
It is a type error if an xsl:apply-templates
instruction in a particular mode
selects an element or
attribute whose type is anything other than xs:untyped
or xs:untypedAtomic
when the typed
attribute of that mode specifies the value no
.
It is a type error if the result of evaluating the
namespace-context
attribute of the xsl:evaluate
instruction is
anything other than a single node.
It is a type error if the result of evaluating the
select
expression [of the xsl:copy
element] is a sequence of
more than one item.
If the result of evaluating the context-item
expression [of an xsl:evaluate
instruction] is a
sequence containing more than one item, then a type error
is signaled.
It is a type error if the result of evaluating the
xsl:on-empty
attribute [on a literal result element]
does not satisfy the required type element()?
. That
is, the expression must deliver either a single element node, or an
empty sequence.
It is a type error if the result of evaluating the
on-empty
attribute [on the xsl:element
instruction] does
not satisfy the required type element()?
. That is, the
expression must deliver either a single element node, or an empty
sequence.
It is a type error if the result of evaluating the
on-empty
attribute [on the xsl:attribute
instruction]
does not satisfy the required type attribute()?
. That
is, the expression must deliver either a single attribute node, or
an empty sequence.
It is a type error if the result of evaluating the
on-empty
attribute [on the xsl:copy
instruction] does not
satisfy the required type node()?
. That is, the
expression must deliver either a single node, or an empty
sequence.
A type error occurs if the result of evaluating the sequence
constructor [within an xsl:map
instruction] is not an
instance of the required type map(*)*
.
Dynamic errors
It is a dynamic error if the effective value of an attribute written using curly brackets, in a position where an attribute value template is permitted, is a value that is not one of the permitted values for that attribute. If the processor is able to detect the error statically (for example, when any XPath expressions within the curly brackets can be evaluated statically), then the processor may optionally signal this as a static error.
It is a dynamic error if the invocation of the
stylesheet specifies a template name that does
not match the expanded QName of a named template defined
in the stylesheet, whose visibility is
public
or final
.
It is a dynamic error if the invocation of the
stylesheet specifies a function name and arity
that does not match the expanded QName and arity of a named
stylesheet function defined in the
stylesheet, whose visibility is
public
or final
.
It is a dynamic error if the invocation of the stylesheet specifies an initial mode and if no input sequence is supplied (either explicitly, or defaulted to the initial context item).
It is a dynamic error if the invocation of the
stylesheet specifies an initial mode (other than the
unnamed mode) that does not match either the expanded
QName in the name
attribute of an xsl:mode
declaration, or
the expanded QName in the mode
attribute of any template defined in the stylesheet.
It is a dynamic error if a stylesheet declares a
visible stylesheet parameter with
required="yes"
and no value for this parameter is
supplied when the stylesheet is primed. A stylesheet parameter is
visible if it is not masked by another global variable or parameter
with the same name and higher import precedence.
If the parameter is a static parameter then the
value must be supplied prior to the
static analysis phase.
It is a dynamic error if the initial template defines a template parameter that specifies
required="yes"
.
It is a dynamic error if an element has an effective version of V (with V < 3.0) when the implementation does not support backwards compatible behavior for XSLT version V.
Where the result of evaluating an XPath expression (or an attribute value template) is required to be a lexical QName, or if it is permitted to be a lexical QName and the actual value takes the form of a lexical QName, then unless otherwise specified it is a dynamic error if the value has a prefix and the defining element has no namespace node whose name matches that prefix. This error may be signaled as a static error if the value of the expression can be determined statically.
It is a dynamic error if the result sequence used to construct the content of an element node contains a namespace node or attribute node that is preceded in the sequence by a node that is neither a namespace node nor an attribute node.
It is a dynamic error if the result sequence used to construct the content of a document node contains a namespace node or attribute node.
It is a dynamic error if the result sequence contains two or more namespace nodes having the same name but different string values (that is, namespace nodes that map the same prefix to different namespace URIs).
It is a dynamic error if the result sequence contains a namespace node with no name and the element node being constructed has a null namespace URI (that is, it is an error to define a default namespace when the element is in no namespace).
It is a dynamic error if the result sequence contains a function item.
It is a dynamic error if the conflict resolution
algorithm for template rules leaves more than one matching template
rule when the declaration of the relevant mode has an
on-multiple-match
attribute with the value
fail
.
It is a dynamic error if xsl:apply-templates
,
xsl:apply-imports
or xsl:next-match
is
used to process a node using a mode whose declaration specifies
on-no-match="fail"
when there is no template
rule in the stylesheet whose match pattern matches that
node.
It is a dynamic error if xsl:apply-imports
or
xsl:next-match
is
evaluated when the current template rule is
absent.
If an optional parameter has no select
attribute
and has an empty sequence constructor, and if
there is an as
attribute, then the default value of
the parameter is an empty sequence. If the empty sequence is not a
valid instance of the required type defined in the as
attribute, then the parameter is treated as a required parameter,
which means that it is a dynamic error if the caller supplies
no value for the parameter.
In general, a circularity in a stylesheet is a dynamic error.
It is a dynamic error if a template that is invoked
using xsl:apply-templates
,
xsl:apply-imports
, or
xsl:next-match
declares a template parameter with
required="yes"
and no value for this parameter is
supplied by the calling instruction. The same error is reported in
the case of a tunnel parameter whether invoked using
one of these three instructions or by xsl:call-template
, as
explained in 10.1.2 Tunnel
Parameters.
It is a dynamic error if the effective value of the name
attribute [of the xsl:element
instruction] is not
a lexical QName.
In the case of an xsl:element
instruction with no
namespace
attribute, it is a dynamic error if the
effective value of the name
attribute is a lexical QName whose prefix is not declared
in an in-scope namespace declaration for the xsl:element
instruction.
It is a dynamic error if the effective value of the
namespace
attribute [of the xsl:element
instruction] is not
in the lexical space of the xs:anyURI
datatype or if
it is the string http://www.w3.org/2000/xmlns/
.
It is a dynamic error if the effective value of the name
attribute [of an xsl:attribute
instruction] is
not a lexical QName.
In the case of an xsl:attribute
instruction
with no namespace
attribute, it is a dynamic
error if the effective value of the name
attribute is the string xmlns
.
In the case of an xsl:attribute
instruction
with no namespace
attribute, it is a dynamic
error if the effective value of the name
attribute is a lexical QName whose prefix is not declared
in an in-scope namespace declaration for the xsl:attribute
instruction.
It is a dynamic error if the effective value of the
namespace
attribute [of the xsl:attribute
instruction] is
not in the lexical space of the xs:anyURI
datatype or
if it is the string http://www.w3.org/2000/xmlns/
.
It is a dynamic error if the effective value of the name
attribute [of the xsl:processing-instruction
instruction] is not both an NCNameNames
and a PITargetXML.
It is a dynamic error if the string value of the
new namespace node is not valid in the lexical space of the
datatype xs:anyURI
, or if it is the string
http://www.w3.org/2000/xmlns/
.
It is a dynamic error if the effective value of the name
attribute [of the xsl:namespace
instruction] is
neither a zero-length string nor an NCNameNames,
or if it is xmlns
.
It is a dynamic error if the xsl:namespace
instruction
generates a namespace node whose name is xml
and whose
string value is not
http://www.w3.org/XML/1998/namespace
, or a namespace
node whose string value is
http://www.w3.org/XML/1998/namespace
and whose name is
not xml
.
It is a dynamic error if evaluating the
select
attribute or the contained sequence constructor of an xsl:namespace
instruction
results in a zero-length string.
It is a dynamic error if any undiscarded item in
the atomized sequence supplied as the value of the
value
attribute of xsl:number
cannot be converted
to an integer, or if the resulting integer is less than 0
(zero).
It is a dynamic error if the effective value of the
start-at
attribute of the xsl:number
instruction is not in
the lexical space of xs:integer
. The error may be
signaled statically if it can be detected statically.
It is a dynamic error if, for any sort key component, the set of
sort key values evaluated for all the
items in the initial sequence, after any type
conversion requested, contains a pair of ordinary values for which
the result of the XPath lt
operator is an error.
It is a dynamic error if the collation
attribute of xsl:sort
(after resolving against the base URI) is not a URI that is
recognized by the implementation as referring to a collation.
It is a dynamic error if the current-group
function is
used when the current group is absent , or when it is invoked in the
course of evaluating a pattern. The error may be reported statically if it can be detected
statically.
It is a dynamic error if the current-grouping-key
function is used when the current grouping key is absent, or when it is
invoked in the course of evaluating a pattern.. The error
may be reported statically if it can be
detected statically.
It is a dynamic error if the collation URI
specified to xsl:for-each-group
(after resolving against the base URI) is a collation that is not
recognized by the implementation. (For notes, [see ERR XTDE1035].)
It is a dynamic error if the effective value of the regex
attribute [of the xsl:analyze-string
instruction] does not conform to the required syntax for regular expressions, as specified
in [Functions and Operators]. If
the regular expression is known statically (for example, if the
attribute does not contain any expressions enclosed in curly
brackets) then the processor may signal
the error as a static error.
It is a dynamic error if the effective value of the flags
attribute [of the xsl:analyze-string
instruction] has a value other than the values defined in [Functions and Operators]. If the value
of the attribute is known statically (for example, if the attribute
does not contain any expressions enclosed in curly brackets) then
the processor may signal the error as a
static error.
When a URI reference [supplied to the document
function] contains a
fragment identifier, it is a dynamic error if the media
type is not one that is recognized by the processor, or if the
fragment identifier does not conform to the rules for fragment
identifiers for that media type, or if the fragment identifier
selects something other than a sequence of nodes (for example, if
it selects a range of characters within a text node).
When a URI reference [supplied to the document
function] is a relative
reference, it is a dynamic error if no base URI is available
to resolve the relative reference. This can arise for example when
the URI is contained in a node that has no base URI (for example a
parentless text node), or when the second argument to the function
is a node that has no base URI, or when the base URI from the
static context is undefined.
It is a dynamic error if the value [of the first
argument to the key
function]
is not a valid QName, or if there is no namespace declaration in
scope for the prefix of the QName, or if the name obtained by
expanding the QName is not the same as the expanded name of any
xsl:key
declaration in the
containing package. If the processor is able to
detect the error statically (for example, when the argument is
supplied as a string literal), then the processor may optionally signal this as a static
error.
It is a dynamic
error to call the key
function with two arguments if
there is no context node, or if the root of the tree
containing the context node is not a document node; or to call the
function with three arguments if the root of the tree containing
the node supplied in the third argument is not a document node.
If the current
function
is evaluated within an expression that is evaluated when the
context item is absent, a dynamic error occurs.
It is a dynamic error if the unparsed-entity-uri
function is called when there is no context node, or when the
root of the tree containing the context node is not a document
node.
It is a dynamic error if the unparsed-entity-public-id
function is called when there is no context node, or when the
root of the tree containing the context node is not a document
node.
It is a dynamic error if the value supplied as the
$property-name
argument [to the system-property
function]
is not a valid QName, or if there is no namespace declaration in
scope for the prefix of the QName. If the processor is able to
detect the error statically (for example, when the argument is
supplied as a string literal), then the processor may optionally signal this as a static
error.
It is a dynamic error if the argument [passed to
the function-available
function] does not evaluate to a string that is a valid EQName, or if the
value is a lexical QName with a prefix for which no
namespace declaration is present in the static context. If the
processor is able to detect the error statically (for example, when
the argument is supplied as a string literal), then the processor
may optionally signal this as a static
error.
It is a dynamic error if the arguments supplied to a call on an extension function do not satisfy the rules defined for that particular extension function, or if the extension function reports an error, or if the result of the extension function cannot be converted to an XPath value.
When the containing element is processed with XSLT 1.0 behavior, it is a dynamic error to evaluate an extension function call if no implementation of the extension function is available.
It is a dynamic error if the argument [passed to
the type-available
function] does not evaluate to a string that is a valid EQName, or if the
value is a lexical QName with a prefix for which no
namespace declaration is present in the static context. If the
processor is able to detect the error statically (for example, when
the argument is supplied as a string literal), then the processor
may optionally signal this as a static
error.
It is a dynamic error if the argument [passed to
the element-available
function] does not evaluate to a string that is a valid EQName, or if the
value is a lexical QName with a prefix for which no
namespace declaration is present in the static context. If the
processor is able to detect the error statically (for example, when
the argument is supplied as a string literal), then the processor
may optionally signal this as a static
error.
When a processor performs fallback for an extension instruction that is not
recognized, if the instruction element has one or more xsl:fallback
children, then
the content of each of the xsl:fallback
children
must be evaluated; it is a dynamic
error if it has no xsl:fallback
children.
It is a dynamic error if the effective value of the
format
attribute [of an xsl:result-document
element] is not a valid EQName, or if it does not match the expanded
QName of an output definition in the stylesheet.
If the processor is able to detect the error statically (for
example, when the format
attribute contains no curly
brackets), then the processor may
optionally signal this as a static error.
It is a dynamic error to evaluate the xsl:result-document
instruction in temporary output state.
It is a dynamic error for a transformation to generate two or more final result trees with the same URI.
It is a dynamic error for a stylesheet to write to an external resource and read from the same resource during a single transformation, if the same absolute URI is used to access the resource in both cases.
A non-schema-aware processor
must raise a dynamic error if the
input to the processor includes a node with a type
annotation other than xs:untyped
or
xs:untypedAtomic
, or an atomic value of a type other
than those which a basic XSLT processor supports.
It is a dynamic error if there are two xsl:merge-key
elements that
occupy corresponding positions among the xsl:merge-key
children of two
different xsl:merge-source
elements
and that have differing effective values for any of the
attributes lang
, order
,
collation
, case-order
, or
data-type
. Values are considered to differ if the
attribute is present on one element and not on the other, or if it
is present on both elements with effective values that are
not equal to each other. In the case of the collation
attribute, the values are compared as absolute URIs after resolving
against the base URI.The error may be
reported statically if it is detected statically.
It is a dynamic error if any input sequence to an
xsl:merge
instruction
contains two items that are not correctly sorted according to the
merge key values defined on the xsl:merge-key
children of the
corresponding xsl:merge-source
element,
when compared using the collation rules defined by the attributes
of the corresponding xsl:merge-key
children of the
xsl:merge
instruction,
unless the attribute sort-before-merge
is present with
the value yes
.
It is a dynamic error if the target expression [of an xsl:evaluate
instruction] is
not a valid XPath 3.0 expression (that is, if a static error occurs
when analyzing the string according to the rules of the XPath 3.0
specification).
It is a dynamic error if an xsl:evaluate
instruction is
evaluated when use of xsl:evaluate
has been
statically or dynamically disabled.
It is a dynamic error if the value of
$input
does not conform to the JSON grammar, as
selected using the explicit or implicit spec
option.
It is a dynamic error if the value of the
validate
option is true
and the processor
is not schema-aware.
It is a dynamic error if the value of
$input
contains an escaped representation of a
character (or codepoint) that is not a valid character in the
version of XML supported by the implementation, unless the
unescape
option is set to false.
It is a dynamic error if the value of
$options
includes an entry whose key is "spec" and
whose value is not a single xs:string
, or an entry
whose key is "validate" or "unescape" and whose value is not a
single xs:boolean
.
It is a dynamic error if the value [of the first
argument to the accumulator-before
or
accumulator-after
function] is not a valid EQName, or if there is no namespace declaration in
scope for the prefix of the QName, or if the name obtained by
expanding the QName is not the same as the expanded name of any
xsl:accumulator
declaration visible in the package in which the function call appears. If
the processor is able to detect the error statically (for example,
when the argument is supplied as a string literal), then the
processor may optionally signal this as a
static error.
It is a dynamic error
to call the accumulator-before
or
accumulator-after
function when there is no context item.
It is a type error to
call the accumulator-before
or
accumulator-after
function when the context item is not a node, or when it is an
attribute or namespace node.
A dynamic error occurs if the set of keys in
the maps resulting from evaluating the sequence constructor [within
an xsl:map
instruction]
contains duplicates.
It is a dynamic error if the accumulator-before
or
accumulator-after
function is called and (a) the accumulator has the property
streamable="no"
, and (b) the context item is a node in
a streamed document.
If the accumulator is declared with the attribute
streamable="yes"
then it is a dynamic error if the
accumulator-before
or
accumulator-after
function is called unless the evaluation is performed in the
course of the evaluation of either (a) the sequence constructor
contained in a template rule invoked in a mode declared with
streamable="yes"
, or (b) the sequence constructor
contained in an xsl:stream
instruction, or both.
Call the nearest such construct in the chain of causation the
controlling sequence constructor.
If the accumulator is declared with the attribute
streamable="yes"
then it is a dynamic error if the
accumulator-before
or
accumulator-after
function is called unless the context item at the point of
evaluating this function is the same node as the context item for
the evaluation of the controlling sequence constructor.
It is a dynamic error if the accumulator-before
or
accumulator-after
function for an accumulator A is evaluated in the
course of evaluating the new-value
expression of
any accumulator rule for the same accumulator A.
If the accumulator is declared with the attribute
streamable="yes"
then it is a dynamic error if the
accumulator-before
function is called unless the evaluation is performed in the
course of the evaluation of a pre-descent instruction within
the controlling sequence constructor.
If the accumulator is declared with the attribute
streamable="yes"
then it is a dynamic error if the
accumulator-after
function is called unless the evaluation is performed in the
course of the evaluation of a post-descent instruction within
the controlling sequence constructor.
When a transformation is terminated by use of xsl:message
terminate="yes"
, the effect is the same as when a dynamic
error occurs during the transformation. The default error
code is XTMM9000
; this may be overridden using the
error-code
attribute of the xsl:message
instruction.
When a transformation is terminated by use of
xsl:assert
, the effect is the same as when a dynamic
error occurs during the transformation. The default error code
is XTMM9001
; this may be overridden using the
error-code
attribute of the xsl:assert
instruction.
This appendix provides a summary of XSLT language features whose effect is explicitly implementation-defined. The conformance rules (see 26 Conformance) require vendors to provide documentation that explains how these choices have been exercised.
The way in which a base output URI is established is implementation-defined (See 2.3.2 Priming a Stylesheet)
The way in which an XSLT processor is invoked, and the way in which values are supplied for the source document, starting node, stylesheet parameters, and base output URI, are implementation-defined. (See 2.3.2 Priming a Stylesheet)
The mechanisms for creating new extension instructions and extension functions are implementation-defined. (See 2.8 Extensibility)
It is implementation-defined whether type errors are signaled statically. (See 2.11 Error Handling)
Mechanisms to locate the source or executable code of a package are implementation-defined. (See 3.6.1 Dependencies between Packages)
The set of namespaces that are specially recognized by the implementation (for example, for user-defined data elements, and extension attributes) is implementation-defined. (See 3.8.3 User-defined Data Elements)
The effect of user-defined data elements whose name is in a namespace recognized by the implementation is implementation-defined. (See 3.8.3 User-defined Data Elements)
If the effective version of any element in the stylesheet is not 1.0 or 2.0 but is less than 3.0, the recommended action is to report a static error; however, processors may recognize such values and process the element in an implementation-defined way. (See 3.10 Backwards Compatible Processing)
It is implementation-defined whether an XSLT 3.0 processor supports backwards compatible behavior for any XSLT version earlier than XSLT 3.0. (See 3.10 Backwards Compatible Processing)
It is implementation-defined what forms of URI reference are
acceptable in the href
attribute of the xsl:include
and xsl:import
elements, for
example, the URI schemes that may be used, the forms of fragment
identifier that may be used, and the media types that are
supported. (See 3.12.1 Locating
Stylesheet Modules)
An implementation may define mechanisms, above and beyond
xsl:import-schema
that allow schema components such as type
definitions to be made available within a stylesheet. (See 3.15 Built-in Types)
It is implementation-defined which versions of XML and XML Namespaces (1.0 and/or 1.1) are supported. (See 4.1 XML Versions)
Limits on the value space of primitive datatypes, where not fixed by [XML Schema Part 2], are implementation-defined. (See 4.7 Limits)
The set of statically known documentsXP30 is implementation-defined. (See 5.4.1 Initializing the Static Context)
The set of statically known collectionsXP30 is implementation-defined. (See 5.4.1 Initializing the Static Context)
The statically known default collection typeXP30 is implementation-defined. (See 5.4.1 Initializing the Static Context)
Implementations may provide user options that relax the
requirement for the doc
FO30
and collection
FO30
functions (and therefore, by implication, the document
function) to return
stable results. The manner in which such user options are provided,
if at all, is implementation-defined. (See
5.4.3 Initializing the Dynamic
Context)
The implicit timezone for a transformation is implementation-defined. (See <IP_ADDRESS> Other Components of the XPath Dynamic Context)
The default collectionXP30 is implementation-defined. (See <IP_ADDRESS> Other Components of the XPath Dynamic Context)
The availability of dynamic context information within extension functions is implementation-defined. (See 5.4.4 Additional Dynamic Context Components used by XSLT)
The default values for the warning-on-no-match
and
warning-on-multiple-match
attributes of xsl:mode
are implementation-defined. (See
6.6.1 Declaring Modes)
The form of any warnings output when there is no matching template rule or when there are multiple matching template rules is implementation-defined. (See 6.6.1 Declaring Modes)
The mechanism by which the caller supplies a value for a stylesheet parameter is implementation-defined. (See 9.5 Global Variables and Parameters)
The set of extension functions available in the static context
for the target expression of xsl:evaluate
is implementation-defined. (See
10.4.1 Static context for the
target expression)
If an xml:id
attribute that has not been subjected
to attribute value normalization is copied from a source tree to a
result tree, it is implementation-defined whether attribute value
normalization will be applied during the copy process. (See
11.9.1 Shallow Copy)
The numbering sequences supported by the xsl:number
instructions, beyond
those defined in this specification, are implementation-defined.
(See 12.3 Number to String Conversion
Attributes)
There may be implementation-defined
upper bounds on the numbers that can be formatted by xsl:number
using any particular
numbering sequence. (See 12.3 Number to
String Conversion Attributes)
The set of languages for which numbering is supported by
xsl:number
, and the
method of choosing a default language, are implementation-defined.
(See 12.3 Number to String Conversion
Attributes)
With xsl:number
, it
is implementation-defined what
combinations of values of the format token, the language, and the
ordinal
attribute are supported. (See 12.3 Number to String Conversion
Attributes)
If the data-type
attribute of the xsl:sort
element has a value other
than text
or number
, the effect is
implementation-defined. (See 13.1.2 Comparing Sort Key
Values)
The facilities for defining collations and allocating URIs to identify them are implementation-defined. (See 13.1.3 Sorting Using Collations)
The algorithm used by xsl:sort
to locate a collation,
given the values of the lang
and
case-order
attributes, is implementation-defined. (See
13.1.3 Sorting Using
Collations)
The set of media types recognized by the processor, for the
purpose of interpreting fragment identifiers in URI references
passed to the document
function, is implementation-defined. (See 20.1 fn:document)
The values returned by the system-property
function,
and the names of the additional properties that are recognized, are
implementation-defined. (See 20.3.4 fn:system-property)
The destination and formatting of messages written using the
xsl:message
instruction
are implementation-defined. (See 22.1
Messages)
The detail of any external mechanism allowing a processor to disable checking of assertions is implementation-defined. (See 22.2 Assertions)
This specification does not define any mechanism for creating or binding implementations of extension instructions or extension functions, and it is not required that implementations support any such mechanism. Such mechanisms, if they exist, are implementation-defined. (See 23 Extensibility and Fallback)
The effect of an extension function returning a string containing characters that are not permitted in XML is implementation-defined. (See 23.1.2 Calling Extension Functions)
The way in which external objects are represented in the type system is implementation-defined. (See 23.1.3 External Objects)
The way in which a final result tree is delivered to an application is implementation-defined. (See 24 Final Result Trees)
There may be implementation-defined
restrictions on the form of absolute URI that may be used in the
href
attribute of the xsl:result-document
instruction. (See 24.1 Creating
Final Result Trees)
Implementations may provide additional mechanisms allowing users to define the way in which final result trees are processed. (See 24.1 Creating Final Result Trees)
If serialization is supported, then the location to which a final result tree is serialized is implementation-defined, subject to the constraint that relative URI references used to reference one tree from another remain valid. (See 25 Serialization)
The default value of the encoding
attribute of the
xsl:output
element is
implementation-defined. (See 25
Serialization)
It is implementation-defined which versions of XML, HTML, and
XHTML are supported in the version
attribute of the
xsl:output
declaration.
(See 25 Serialization)
The default value of the byte-order-mark
serialization parameter is implementation-defined in the case of
UTF-8 encoding. (See 25
Serialization)
It is implementation-defined whether, and under what circumstances, disabling output escaping is supported. (See 25.2 Disabling Output Escaping)
This appendix acts as an index of functions defined in this specification, to augment the set of functions defined in [Functions and Operators].
accumulator-after
accumulator-before
collation-key
copy-of
current
current-group
current-grouping-key
deep-equal
document
element-available
function-available
json-to-xml
key
map:contains
map:entry
map:for-each-entry
map:get
map:keys
map:new
map:remove
regex-group
snapshot
system-property
type-available
unparsed-entity-public-id
unparsed-entity-uri
The following XSD 1.1 schema describes the structure of an XSLT stylesheet module. It does not define all the constraints that apply to a stylesheet (for example, it does not attempt to define a datatype that precisely represents attributes containing XPath expressions). However, every valid stylesheet module conforms to this schema, unless it contains elements that invoke forwards compatible behavior.
A copy of this schema is available at http://www.w3.org/2012/07/schema-for-xslt30.xsd
Note:
The schema as written uses a lax wildcard to permit literal
result elements to appear in a sequence constructor. This assumes
that the schema used for validation will not contain any global
element declaration that matches the element name of a literal
result element. The content model for an element such as
invoice
appearing within a stylesheet is not the same
as the content model for the same element appearing within a source
document (it is likely to contain XSLT instructions rather than
other elements from the target vocabulary): therefore, including
such declarations in the schema used for validating a stylesheet is
inappropriate.
The reason that lax validation rather than skip validation is used is so that XSLT instructions appearing as children of the literal result element will themselves be validated, using the appropriate global element declaration.
Note:
The schema uses XSD 1.1 assertions to represent some of the
non-grammatical constraints appearing in the specification, for
example the rule that some elements can have either a
select
attribute or a contained sequence constructor,
but not both. At this stage, no attempt has been made to represent
every such constraint, even where it is not difficult to express
the rule. There will always be some constraints that cannot be
expressed at all, for example those that require access to multiple
stylesheet modules, those that require access to the in-scope
schema components, and those that involve parsing a non-regular
grammar, such as the grammar for patterns.
Apart from assertions, the only other significant use of XSD 1.1
features is that the elements xsl:param
and xsl:variable
are in two
substitution groups: one containing all instructions, and one
containing all declarations. If the schema needs to be converted to
an XSD 1.0 schema, removing all assertions is straightforward; the
other change needed is to remove xsl:param
and xsl:variable
from the
substitution group for declarations, and instead permit them
explicitly as children of xsl:transform
.


Why reputile?
reputile is a platform that combines many different sources for reputation checks
into a single downloadable and queryable format. The database can be retrieved in
total or filtered based on user defined criterias.
Because reputile does the hard work of collecting all those blacklists and
translating them into one format, you can focus on more important things!
What format does your database use?
The format strives to be the most simple to parse and work with. This enables you to use
a wide variety of languages and tools. Because a lot of reputation sources
allready use some form of CSV format, reputile uses CSV (to be
more precise RFC4180) as well. The the columns of our database are:
source,domain,ip,last,category,description
How can I filter the results?
The reputile database can be filtered with URL query parameters. Each
provided query paramter specifies a condition a row must satisfy. A query
to only return malicious domains or IPs is:
?category=malware
Is it ready?
Not yet. reputile is still very much a work in progress. Still some people are already
using it. You cand find the current statistics
here.
Which blacklists are included?
You can find a detailed listing of included backlists
here.
Can I use reputile commercially?
No. reputile is a non-commercial community project that uses a variety of different
blacklist sources. Many sources are for non-commercial use only and therefore
reputile is as well.


System Architect Picture "Subject Responsibility Act"
Parent Diagram:
Activity For Subject
(UML Class)


The relative path to the module descriptor file from the root of each module.
Given a module "moduleX" with an ivy descriptor located at "moduleX/ivy/ivy.xml" you should enter "ivy/ivy.xml" here. Given a module "moduleY" with an ivy descriptor located at "moduleY/build/ivy.xml" you should enter "build/ivy.xml" here.
If some of your modules have their ivy descriptors in different places then enter the most common value here. After your first build you will need to edit the configuration of all the other modules to override this default value.
Leave blank to use the default of "ivy.xml" (assumes your ivy.xml file is located directly in the root of each module).


Power Management IC - LP8731/LP3907 and LP3907 specific API implementation. APIs are exported by using function pointers.
More...
|
| static pmErrCode_t | PMHALLP8731LP3907IsPresent (void) |
| | Check if the LP8731/LP3907 PMIC is present. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static const char * | PMHALLP8731LP3907GetRevision (void) |
| | Get the LP8731/LP3907 PMIC chip revision. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static pmErrCode_t | PMHALLP8731LP3907GetVendorId (uint32_t *vendorId) |
| | Return the PMIC Vendor ID. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static pmErrCode_t | PMHALLP8731LP3907GetProductId (uint32_t *productId) |
| | Return the PMIC Product ID. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static pmErrCode_t | PMHALLP8731LP3907GetRegulatorVoltage (pmhalPrcmPmicRegulatorId_t regId, uint32_t *voltage) |
| | Get the voltage setting of the given regulator. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static pmErrCode_t | PMHALLP8731LP3907SetRegulatorVoltage (pmhalPrcmPmicRegulatorId_t regId, uint32_t voltage, uint32_t timeout) |
| | Set the voltage of the regulator to the mV given. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static uint32_t | PMHALLP8731LP3907IsRegulatorEnabled (pmhalPrcmPmicRegulatorId_t regId) |
| | API to check if the given regulator enabled. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static pmErrCode_t | PMHALLP8731LP3907EnableRegulator (pmhalPrcmPmicRegulatorId_t regId) |
| | Enable the given regulator. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static pmErrCode_t | PMHALLP8731LP3907DisableRegulator (pmhalPrcmPmicRegulatorId_t regId) |
| | Disable the given regulator. The declaration is present here to ensure this function is used only via function pointer. More...
|
| |
| static uint32_t | PMHALLP8731LP3907GetRegulatorConvVoltage (pmhalPrcmPmicRegulatorId_t regId, uint32_t avsVoltage) |
| | Return the Regulator Step voltage size. This is required by the voltage manager to understand the opp for the given voltage set for the given voltage rail. More...
|
| |
| static pmErrCode_t | PmhalLP8731LP3907VoltageToVselOffset (pmhalPrcmPmicRegulatorId_t regId, uint32_t voltage, uint32_t *vsel) |
| | Given voltage in mV and range, return the VSEL offset. More...
|
| |
| static uint32_t | PmhalLP8731LP3907VselOffsetToVoltage (pmhalPrcmPmicRegulatorId_t regId, uint32_t vsel) |
| | Given VSEL offset convert it to voltage in mV and return. More...
|
| |
| static pmErrCode_t | PmhalLP8731LP3907ReadPhyAddr (uint8_t i2cNum, uint8_t slaveAddress, uint32_t phyAddr, uint32_t *value) |
| | Read the register value at the given physical address. More...
|
| |
| static pmErrCode_t | PmhalLP8731LP3907WritePhyAddr (uint8_t i2cNum, uint8_t slaveAddress, uint32_t phyAddr, uint32_t value) |
| | Write the given register value at the given physical address. More...
|
| |
| static uint32_t | PmhalLP8731LP3907CheckRegulatorEnabled (pmhalPrcmPmicRegulatorId_t regId) |
| | Is the given regulator enabled? This utility function must only be called by functions in this file and the caller must ensure that the PMIC communication is configured and enabled before calling this function. More...
|
| |
| const pmhalPmicOperations_t * | PMHALLP8731LP3907GetPMICOps (void) |
| | Get PMIC ops structure. All the other functions are accessed via function pointers whose array is exported by this function. More...
|
| |
| void | PMHALLP8731LP3907ConfigureRegulatorMap (pmhalLP8731LP3907RegulatorMapPtr_t regulatorMap) |
| | The PMIC regulator output to the device input mapping can be different on different boards. This API can be used to provide a different mapping to the PMIC driver if the mapping does not match the default. Example table is shown below:
| Device voltage Rail | Ptr to Regulator |
| PMHAL_PRCM_PMIC_REGULATOR_CORE | PMHAL_LP8731_LP3907_REGULATOR_BUCK1 | | PMHAL_PRCM_PMIC_REGULATOR_DSPEVE| PMHAL_LP8731_LP3907_REGULATOR_BUCK2| | .... | | index (Refer | For index of the | | pmhalPrcmPmicRegulatorId_t) | gPmhalLP8731LP3907Regulator | | | refer | | | #pmhalLP8731LP3907RegulatorId_t |
This table when translated to code is as below: pmhalLP8731LP3907RegulatorMap_t regulatorMap[ PMHAL_PRCM_PMIC_REGULATOR_COUNT] = { { &gPmhalLP8731LP3907Regulator[ PMHAL_LP8731_LP3907_REGULATOR_BUCK1], I2C_INSTANCE, PMIC_I2C_SLAVE_ADDRESS }, { &gPmhalLP8731LP3907Regulator[ PMHAL_LP8731_LP3907_REGULATOR_BUCK2], I2C_INSTANCE, PMIC_I2C_SLAVE_ADDRESS }, ...... };. More...
|
| |
Power Management IC - LP8731/LP3907 and LP3907 specific API implementation. APIs are exported by using function pointers.
| void PMHALLP8731LP3907ConfigureRegulatorMap |
( |
pmhalLP8731LP3907RegulatorMapPtr_t |
regulatorMap | ) |
|
The PMIC regulator output to the device input mapping can be different on different boards. This API can be used to provide a different mapping to the PMIC driver if the mapping does not
match the default. Example table is shown below:
| Device voltage Rail | Ptr to Regulator |
| PMHAL_PRCM_PMIC_REGULATOR_CORE | PMHAL_LP8731_LP3907_REGULATOR_BUCK1 | | PMHAL_PRCM_PMIC_REGULATOR_DSPEVE| PMHAL_LP8731_LP3907_REGULATOR_BUCK2| | .... | | index (Refer | For index of the | |
pmhalPrcmPmicRegulatorId_t) | gPmhalLP8731LP3907Regulator | | | refer |
| | #pmhalLP8731LP3907RegulatorId_t |
This table when translated to code is as below: pmhalLP8731LP3907RegulatorMap_t regulatorMap[ PMHAL_PRCM_PMIC_REGULATOR_COUNT] = { { &gPmhalLP8731LP3907Regulator[ PMHAL_LP8731_LP3907_REGULATOR_BUCK1], I2C_INSTANCE, PMIC_I2C_SLAVE_ADDRESS }, { &gPmhalLP8731LP3907Regulator[ PMHAL_LP8731_LP3907_REGULATOR_BUCK2], I2C_INSTANCE, PMIC_I2C_SLAVE_ADDRESS }, ...... };.
- Parameters
-
| regulatorMap | Pointer to the array of pointers which gives the mapping. The array is defined as above. |
- Returns
- None


Backdrop LibraryCategory
Theme
|
School Hospital Garden 3 Office City 1 City 2 Bedroom 1 Bedroom 2 Bedroom 3 Kitchen 1 Kitchen 2 Bathroom City 3 City 4 City 5 City 6 Castle 1 Castle 2 Classroom 1 Classroom 2 Hallway 1 Hallway 2 Garden 1 Garden 2 |


[Erowid Note: 20 pills of carisoprodol in a 24 hour period, even if they were of the lowest available strength, is considered an extremely high dose.]
Here is my little retrospective of the 24 hours after I purchased 20 Somas. I had taken 2 pills at a time on 2 occasions and even then I was wasted. This time was different. I'll start with the purchasing of the half-scrip at 9:30 PM on a Wednesday night.
9:30 pm - Somas purchased, two taken orally with dinner and milk.
10:30 pm - Feeling that familiar buzz, numbness, loss of coordination, etc. Then I take 2 more.
11:30 pm - Feeling quite a heavy buzz, drank a couple beers and smoked a bowl to add to the effects.
12:30 am - The friends I was hanging out with leave, and I take another Soma. The count up to this point, 5 soma, and I am definetly feeling wasted.
1:30 am - Watching TV, well trying to anyways, as my vision is quite distorted and I am unable to move without thinking about it really hard. So I take another Soma.
2:30 am - Reaching the peak of my nighttime Soma experience. Feeling complete loss of coordination and motor skills, stumbling around when I had to get up and for some reason I decide to take 2 more.
3:30 am - By this point I have consumed quite a few shots of mcnaughtons to go along with my soma swallowing. I am laying in my bed smoking cigarettes when all of a sudden my energy returns and I decide to clean up my room. I wouldn't usually think that muscle relaxers would keep me up all night and make me want to clean my room.  Then I try to push a loveseat up my stairs by myself. I'd get it half of the way up the stairs and try to get around it to the bottom so I could push it up and it would slide all the way back down. Exhausted, I give up and retire to my bed, falling instantly into a deep and dream filled soma sleep.
9:30 am - I wake up to go to work, still in a daze from the night before. After taking a shower, I take 3 more soma and head to work.
10:30 am - An hour has passed at work and I realize that I haven't accomplished a damn thing. My eyes were completely out of focus and I couldn't even see the computer screen unless I got 2 inches away from it. I take 2 more soma and soon decide to take a break.
11:30 am - In the upstairs part of my office, I smoke a bowl and a cigarette and notice myself nodding off quite frequently.  So I head outside and hop in my car to drive home.
[Erowid Note: Driving while intoxicated or tripping is dangerous and irresponsible because it endangers other people. Don't do it!] On the way, I noticed I was too fucked up to be driving as well, as I was in the other side of the road quite frequently and rear-ended a minivan at a 4-way stop. Since I had weed, a pipe, and somas on me I just kept driving and never did get a call from the police about a hit and run (this is about 6 days later). Paranoid, I race home to lock my doors and shut the car in the garage.
12:30 pm - By this time I am home safely and sound asleep while I am supposed to be working.  I make it to work safely and nobody suspects a thing. I am such a cheapskate haha
4:30 pm - When I get home, I take 3 more soma and consume a short glass of mcnaughtons whiskey. Just as the effects were wearing off, I had to do more. I continued to explain to my friends about the fucked up last 18 hours or so I'd been having.
5:30 pm - I am about in the state I was late the night before. Unable to hold my head up under its own weight, slurring words, speaking rubbish, total loss of motor skills and coordination. I proceeded to drink a couple beers and smoke some weed and cigarettes.
6:30 pm - Still wasted beyond belief, I think it might be a good idea to take the remaining 3 out of my original 20 somas with another glass of whiskey.  In a vain attempt to load a bowl of shake, I spill weed all over my pants and the floor but don't really care all that much.
7:30 pm - Once again I am delerious and not too aware of my body or surroundings. I tell my friends I'm gonna pass out before I hurt myself, and they agree its probably a good idea.
8:30 pm - Sound asleep once again, 23 hours after I purchased the somas. I end up waking around 11 when my friend shows up and I tell him the story of how wasted I got off soma for a day straight.
Restrospective - This was definetly one of the funnest 24 hours I'd had in a long time. As you can probably tell, I have a problem with taking things to the excess. Alchohol and weed definetly enhance the effects of this drug, which are nothing like hydros or any other pills Iíve ever taken. Another thing, the one soma that was unaccounted for was taken over time through the act of snortation. I would crush out a little line of the stuff and snort it when I would take the others orally. I hope this experience was helpful but more likely it was just entertaining.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


HPT Al-Mg metastable Mater. disk {border-style grain line broadening px;} #ffffff;} alloy turns material bulk room edge hardness Fig. center mechanical processed XRD compositional disks natural processing materials microstructural refinement temperature torsion FWHM aging deformation diffraction lattice nanostructured profile properties using Research alloys available bonding high-pressure metals peak plastic px; size turns. {font-family Data Eng. Figure Sci. TEM Thus, font-size maximum phase pure sample scattering severe significant sizes solid taken Kawasaki Langdon \documentclass[pt]{minimal} \setlength{\oddsidemargin}{-pt} \usepackage{amsbsy} \usepackage{amsfonts} \usepackage{amsmath} \usepackage{amssymb} \usepackage{mathrsfs} \usepackage{upgreek} \usepackage{wasysym} analysis apparent bonded consistent distribution double; estimated instrumental locations matrix mechanically metal overall peaks volume ./j.msea... Materials Science Valiev border-color border-width conducted data different examined high immediately intermetallic observations parameter results shows solid; solution strain study supersaturated synthesis temperature. {font-style {font-weight Acta Commons Creative Extended HPT. Han Lett. Metall. NIST Nature Res. Table X-ray [], actual aged alloy. alloying bold chemical comparison computed concentration corresponding courier; crystallite em; homogeneity images micrographs microstructure observed powder provide pt;} reasonably respectively. shown structure supersaturation surface vertical


{% extends 'users/user/base_settings.html' %} {% load crispy_forms_tags %} {% block head_title %}Emails - Settings - {{ block.super }}{% endblock %} {% block content %}
The following e-mail addresses are associated with your account:
{% else %}Warning: you currently do not have any e-mail address set up. You should really add an e-mail address so you can receive notifications, reset your password, etc.
{% endif %}


WITNESS LIST Regulated Industries Committee December 12, 2005-10:00A Interim Charge 2 On: Beehler, Angela (Wal Mart Stores, Inc.) Biedrzycki, Carol (Texas Ratepayers Organization to Save Energy) Burke, Jim (Association of Electric Companies of Texas) Jewell, Michael (Direct Energy, CPL Retail Energy, WTU Retail Energy) Koshakji, Pierre (Stream Energy) Ogelman, Kenan (Suzi McClellan, Office of Public Utility Counsel) Parsley, Julie (Public Utility Commission) Smitherman, Barry (Public Utility Commission) Registering, but not testifying: On: Rowley, Mike (Stream Energy)


-
sajal
A lightweight mobile electronic record for refugees. Worked with the Red Cross and humanitarian NGO Emergency to bring to refugee reception centers in Italy.
-
onatrip!
Optimal trip planning / arbitrary queries on maps ("I want to go to a movie theater and then get Italian food and dessert nearby.").
-
fRender
Robust, fault-tolerant distributed rendering prototype for Blender.
-
paint floyd
Paint-mixing robot that dispenses the right combination of primary colors to produce a given color.
-
cubic
Chrome extension to make Internet research more intuitive. Allows a user to navigate to more/less complex articles and view a timeline of events.
-
fpga 3d scanner
Fast, FPGA prototype of a 3D laser scanner. Reconstructs a point cloud of a physical object in real-time.
-
fort
A three-story fort in my dorm's courtyard.
-
geodesic dome
A six-foot-tall dome structure in my dorm's courtyard.


The NAME record describes a defined name in the workbook.
Record Data
|
Offset |
Field Name |
Size |
Contents |
|
4 |
grbit |
2 |
Option flags |
|
6 |
chKey |
1 |
Keyboard shortcut |
|
7 |
cch |
1 |
Length of the name text (in characters) |
|
8 |
cce |
2 |
Length of the name definition |
|
10 |
ixals |
2 |
Index to the sheet that contains this name, if the name is a local name (see text) |
|
12 |
itab |
2 |
1-based index into the sheets in the current book, where the list is arranged by the visible order of the tabs. |
|
14 |
cchCustMenu |
1 |
Length of the custom menu text |
|
15 |
cchDescription |
1 |
Length of the description text |
|
16 |
cchHelptopic |
1 |
Length of the help topic text |
|
17 |
cchStatustext |
1 |
Length of the status bar text |
|
18 |
rgch |
var |
Name text ( grbit / rgb fields as defined in “Unicode Strings in BIFF8 EXB0006 ”.) |
|
var |
rgce |
var |
Name definition (see text) |
|
var |
rgchCustMenu |
var |
Custom menu text |
|
var |
rgchDescr |
var |
Description text |
|
var |
rgchHelptopic |
var |
Help topic text |
|
var |
rgchStatustext |
var |
Status bar text |
The grbit field contains the following option flags:
|
Bits |
Mask |
Flag Name |
Contents |
|
0 |
0001h |
fHidden |
=1 if the name is hidden |
|
1 |
0002h |
fFunc |
=1 if the name is a function |
|
2 |
0004h |
fOB |
=1 if the name is a Visual Basic procedure |
|
3 |
0008h |
fProc |
=1 if the name is a function or command name on a macro sheet |
|
4 |
0010h |
fCalcExp |
=1 if the name contains a complex function |
|
5 |
0020h |
fBuiltin |
=1 if the name is a built-in name |
|
11–6 |
0FC0h |
fgrp |
Function group index |
|
12 |
1000h |
fBig |
=1 if the name refers to binary data (see text) |
|
15–13 |
C000h |
(Reserved) |
|
If the fBig bit in the grbit field is equal to 1, the NAME record contains a name attached to binary data. These names can be created only by calling the xlDefineBinaryName function from the Microsoft Excel C API. The first byte is the length of the name, which is followed by the name string. Following the name string is the data to which the name refers. The data can be up to 232 bytes long and can span multiple CONTINUE records.
The fCalcExp bit is set if the name definition contains a function that returns an array (for example, TREND , MINVERSE ), contains a ROW or COLUMN function, or contains a user-defined function.
The chKey byte is significant only when the fProc bit is set in the grbit field. chKey is the keyboard shortcut for a command macro name. If the name is not a command macro name or has no keyboard shortcut, chKey is meaningless.
The cch field contains the length of the name text, and the rgch field contains the text itself. The cce field contains the length of the name definition, and the rgce field contains the definition itself. The location of rgce within the record depends on the length of the name text ( rgch ) field.
The name definition ( rgce ) is stored in the Excel parsed format. For more information, see “Microsoft Excel Formulas EXB0251 ”.
The NAME record stores two types of names: global names and local names. A global name is defined for an entire workbook, and a local name is defined on a single sheet. For example, MyName is a global name, whereas Sheet1!MyName is a local name. The ixals field in the NAME record is nonzero for local names and will index the list of EXTERNSHEET records for the sheets in the workbook.
All NAME records should appear together in a BIFF file. The order of NAME records in an existing BIFF file should not be changed. You can add new names to a file, but you should add them at the end of the NAME list (block of NAME records). Excel saves the names to the BIFF file in alphabetic order, but this is not a requirement; Excel will sort the name list, if necessary, when it loads a BIFF file.
Excel contains several built-in names — such as Criteria, Database, Auto_Open, and so on — for which the NAME records do not contain the actual name. Instead, cch always equals 1, and a single byte is used to identify the name as shown in the following table.
|
Built-in name |
rgch |
|
Consolidate_Area |
00 |
|
Auto_Open |
01 |
|
Auto_Close |
02 |
|
Extract |
03 |
|
Database |
04 |
|
Criteria |
05 |
|
Print_Area |
06 |
|
Print_Titles |
07 |
|
Recorder |
08 |
|
Data_Form |
09 |
|
Auto_Activate |
0A |
|
Auto_Deactivate |
0B |
|
Sheet_Title |
0C |