Previous - Next
This is the old United Nations University website. Visit the new site at http://unu.edu
| <ad/> |
| The <ad/> element is a required
immediate subsidiary element of the <email/>
element when the first format is used. It specifies the
sender's electronic mail address. Description Both start-tag and end-tag are required. The content of <ad/> is a single unformatted data item: any character string not including </ad/>. Format The <ad/> element consists of a single string of characters comprising the address to which electronic mail for the sender may be sent. Unlike ordinary unformatted data, the data in the <ad/> content can generally include "<" and ">"; only the contiguous string of characters </ad/> (which is not likely to be an exact substring of anyone's electronic mail address) is excluded from the content-it would be recognized as the terminating end-tag. As a result, <ad/> cannot include <cmt/> elements; they would be taken to be part of the electronic mail address itself. Therefore, if a <cmt/> element providing information about the electronic mail address is needed, it is made subsidiary to the containing <email/> element (see the examples under <email/>, above). Example <email/> |
| <net/> | ||||||||||||||||||||||||||||
| The <net/> element is a required
immediate subsidiary element of the <email/>
element when the first format is used. It specifies the
network for which the associated electronic mail address
is intended. Description Both start-tag and end-tag are required. The content of <net/> includes a single required formatted data item, a keyword from the following extensible list (in either upper or lower case, or a combination
*At the time of this writing, good gateways to the Internet exist, and many hosts have domain name system addresses. These should be used if possible; see the discussion above under <email/>. ** Please reverse the address (i.e., change UK.AC.XXX to XXX.AC.UK) and designate as <net/> INET </net/> if the appropriate gateway connections are operable. <Net/> may also include optional <cmt/> elements. If <cmt/> is used, the comment refers to the network itself, not to the overall electronic mail address and how it is used. Compare the last two examples below. In using an electronic mail address, the important issue is addressing from somewhere else, and, in particular, somewhere from which the receiver of a file can reach the addressee. Many of the "networks" listed above are not really networks but single systems that people log into, however remotely, to send and receive mail. If you list the name of a disconnected network, please indicate, with a <cmt/> element, how it can be accessed. See the discussion of "Networks and Addressing" under <email/>, above, for more information. Format The <net/> element consists of a single string of characters which is an address to which electronic mail for the sender may be addressed. Examples <email/> <email/> <ad/>
Doe@somehost.span.nasa.gov </ad/> <net/> INET
</net/> <email/> <ad/> Somehost::Doe </ad/> <net/> SPAN </net/> <cmt/> SPAN form of Internet address </cmt/> </email/> <email/> <ad/>
foodtable@agri.govt.fj </ad/> <net/> Fijinet Of the last two examples, the first illustrates a comment that is applicable to the electronic mail address, specifying its relationship to other supplied addresses. The second one applies to the network, and specifies accessing information or the lack thereof. |
| <x400/> |
| The <x400/> element is a
required immediate subsidiary element of the
<email/> element when the second format is used. It
specifies the sender's electronic mail address. If the
address is accessible from the Internet, <email/>
should be used twice, once with the <ad/> and
<net/> elements to specify the address path from
the Internet, and once with <x400/> to specify the
actual X.400 address. Description Both start-tag and end-tag are required. The content of <x400/> is a single unformatted data item: any character string not including </x400/>. Information equivalent to the <net/> element associated with <ad/> is, of course, supplied by the country and primary management domain fields. Format The <x400/> element consists of a single string of characters comprising an address to which electronic mail for the sender may be sent. Unlike ordinary unformatted data, the data in the <x400/> content can generally include "<" and ">"; only the contiguous string of characters </x400/> (which is not likely to be an exact substring of anyone's electronic mail address) is excluded from the content-it would be recognized as the terminating end-tag. As a result, <x400/> cannot include <cmt/> elements; they would be taken to be part of the electronic mail address itself. However, a <cmt/> element may be used as a subsidiary to the containing <email/> element, so this should not be a major restriction. At the time of this writing, the form in which an X.400 address should be written for people to read (the "presentation format") has not been standardized and differs from one system to another. Until there is a Standard, any reasonable format that identifies the pairs of keywords (tags) and values may therefore be used; the one shown in the example below is preferred. Example <email/> |
| <phone/> |
| The <phone/> element is an
optional, repeatable immediate subsidiary element of the
<sender> and <source> elements. It specifies
the sender's or source's complete telephone number, in
international form. A comment may be added to document
local conventions, times of day, etc. Description Both start-tag and end-tag are required. The content of <phone/> consists of one unformatted data item and optional <cmt/> elements. Format The <phone/> element's unformatted data consists of a single string of characters that constitute the sender's or source's telephone number. The entire international telephone number should be given; this includes country and other appropriate prefixes. If an extension number is needed, it should be given after an "X". While the form is still not in general use in some countries, the international convention for writing a phone number consists of a plus sign (+) to denote any local access code for international service, the country code, a space, the city code (if any), a space, and the local number. Spaces may used in the local number according to local conventions for separating parts of numbers, but no additional symbols (such as dashes or parentheses) are used. Examples <phone/> +1 617 253 8004 <phone/> +1 1013214567 X 123 </phone/> <phone/> + 64 63 68019 <phone/> +255 51 28951 |
| <fax/> |
| The <fax/> element is an
optional, repeatable immediate subsidiary element of the
<sender> element. It specifies the sender's
international telephone number for receiving facsimile
transmissions. See the discussion of <phone/> for
additional information about the expression of telephone
numbers. Description Both start-tag and end-tag are required. The content of <fax/> consists of one unformatted data item and optional <cmt/> elements. Format The <fax/> element's unformatted data consists of a single string of characters that constitute the sender's fax telephone number. The entire international telephone number should be given; this includes country and other appropriate prefixes. Examples <fax/> +1617 253 8000 <fax/> +99 1 22 33 55 |
| <telex/> |
| The <telex/> element is an
optional, repeatable immediate subsidiary element of the
<sender> and <source> elements. It specifies
the sender's telex number. Description Both start-tag and end-tag are required. The content of <telex/> consists of one unformatted data item, an optional <ansbk>, an optional <sys> and optional <cmt/> elements. The latter may be used to specify special information about the use of the telex address. <Ansbk> and <sys> are defined below. Format The <telex/> element's unformatted data normally consists of a single string of characters that constitute the sender's telex number. The answerback, if available, should be specified with the <ansbk> tag and follow the telex number itself. The <sys> subsidiary element specifies which telex system is to be used, if more than one is available in the country concerned. It will not be used for countries that have a single telex system. Local Subelements <Ansbk> is optional and is used to specify an answerback string. The content consists of an unformatted string and terminates when another tag is encountered. <Sys> is optional and is used to specify the applicable telex system. The content consists of an unformatted string and terminates when another tag is encountered. Example <telex/> 6502688345 |
| <cable/> |
| The <cable/> element is an
optional, repeatable immediate subsidiary element of the
<sender> and <source> elements. It specifies
the sender's international cable address. Description Both start-tag and end-tag are required. The content of <cable/> consists of one unformatted data item and optional <cmt/> elements. Format The <cable/> element's unformatted data consists of a single string of characters that constitute the sender's international cable address. Examples <cable/> MITCAM </cable/> The second example uses a <cmt/> element to specify something about the cable address. Since the comment associated with this element is free text, the dates specified are not required to be in any particular format. Nonetheless, the format given for dates is preferred to the one shown here, since it is internationally unambiguous and avoids end-of-century problems. |
| <cmt/> |
| The <cmt/> element is an
optional, repeatable immediate subsidiary element of
various other elements. It should include only peripheral
information related to the element to which it is
subsidiary, and should not include any information for
which a "real" interchange element exists or
might reasonably be defined. "Cmt" can be
thought of as an abbreviation for "comment". Description Both start-tag and end-tag are required. The content of <cmt/> consists of one special unformatted data item: any character string not including </cmt/> (see below). In general, <cmt/> elements are permitted subsidiary to any element that requires an end-tag and that accepts immediate data, and not otherwise. Format The <cmt/> element consists of a single string of characters. It is not interpreted by conversion programs or programs processing interchange files but is intended to supply ancillary information for the human user. Unlike ordinary unformatted data, comment data can generally include " <" and "> "; only the contiguous string of characters </cmt/> is excluded from the content-it would be recognized as the terminating end-tag. Examples <cmt/> Temporary, 881010-890701 </cmt/> <cmt/> Certainly <0.001
</cmt/> The first example above shows the use of a "less-than" sign in a comment. In general, this symbol is not permitted in free text; <cmt/> elements are among the exceptions. The second shows the use of something that appears to be a tag but is not: its presence as part of a <cmt/> element causes it to be treated as ordinary text. While this type of construction is permitted, it is discouraged because it will almost certainly confuse users. It would be better to write, e.g., <cmt/> The value shown with "energc" is probably more representative </cmt/> |
| <source> | ||||||||||||||||||
| The <source> element is a
structural element, the second immediate subsidiary
element of the <header> element. It includes all of
the information about the data base from which the data
in the interchange file was obtained, what restrictions
apply to the use or publication of the data, and who is
responsible for the data. Description Both start-tag and end-tag are required. The content includes one required immediate subsidiary element (numbers in parentheses refer to the pages where the elements are described): <ref/> (55) and these optional immediately subsidiary elements:
In some cases, a data base may exist in both table and computer-processable form, and it may be desirable to cite both. When this occurs, the special delimiter "<->" may be used to separate the two (or more) citations within a single <source>. When two or more references are given this way, they do not imply separate sources, e.g., a combination of tables, but different forms of availability of the same conceptual data. The <source> element's immediate subsidiaries are not structural elements, so they may appear in any order. There is no immediate data. Format The <source> element has subsidiary elements giving information about the source of the data in the interchange file. All of the data in an interchange file must be from a single source; if data from two or more sources are to be sent to the same receiver, they must be separate interchange files (i.e., separate <infoods 85> elements; these may be combined into a single physical file or message for transmission). This restriction is closely connected with the concept of "authority" as discussed in Chapter 1, and is not as limiting as might at first appear. For example, assume that the food tables for country A were made up from local (i.e., country A) data plus some data incorporated from the data bases of countries B and C. If these data were re-exported in interchange form, the source for the data base would be the tables of country A, reflecting the authoritative decision to combine the three sets of values, decisions as to which foods were drawn from each table, etc. However, if a sender in country A chose to re-export the data from countries B and C intact and unedited, the restriction stated here would be relevant, and two interchange files (one for each source) would be required. The data source is identified in the <ref/> element. The data may come with some restrictions on its use or publication; these are specified in the <restrict/> element. The rest of the immediate subsidiary elements serve to identify the person or corporate entity who, by virtue of compiling the laboratory data, deriving, extracting, or collecting the data from other sources, or publishing the data, is effectively responsible for their content and substance. The intent of these elements is similar to their use subsidiary to <sender/> and they may duplicate data in the <ref/>, especially if the data source is a publication. The origins and derivations of values for individual foods are reflected in the international food record identifier and related information discussed in Chapter 5. Example <source> In this example the data are provided with no restrictions on their use or publication. If restrictions did exist, the <restrict/> element would be included. |
| <ref/> | ||||
| The <ref/> element is a required
immediate subsidiary element of the <source>
element. It identifies the source data base. Description Both start-tag and end-tag are required. The <ref/> content includes an unformatted data item and the following optional immediate subsidiary elements (numbers in parentheses refer to the pages where these elements are defined):
Format It has traditionally been difficult to determine how to reference a data base in conventional publications (e.g., journal articles and books). This element specifies the form of reference preferred by the source of the data. If the data come from, or have appeared in, published form, the <pub/> element gives more information about the publisher, and <isbn> or <issn> gives standardized identification information about the publication. Machine-readable data bases may be referenced as well as printed ones, and that usage should increase over time. However, to be useful, they must be "published" in the sense of being available from a source, at least for reference, and the information supplied with this element must be sufficient to identify the data base and locate a source of availability. The list of elements permitted to appear subsidiary to the <ref/> element is likely to be expanded as mechanisms for referencing, archiving, and distributing machine-readable data bases (other than as variations on printed publications) become more established. Examples <ref/> US Department of Agriculture. Composition of Foods: Finfish and Shellfish Products. Agriculture Handbook 8-15.</ref/> <ref/> Paul AA and Southgate DAT. McCance and Widdowson's The Composition of Foods, 4th edition. <pub/> London: Her Majesty's Stationery Office </pub/> <isbn> 0 11 450036 3 <ref/> |
| <pub/> |
| The <pub/> element is an
immediate subsidiary element of the <ref/> element.
It identifies the publisher if the source data base is
published. Description Both start-tag and end-tag are required. In addition, successive lines of <pub/> are separated by the special tag <->. Each line consists of one unformatted data item. Format <Pub/> is an element whose content is successive lines of a publisher's name and address, separated by the special tag <->. Examples <pub/> Addison-Wesley <pub/> Technique et Documentation
- Lavoisier <-> 11, rue Lavoisier |
| <isbn> |
| The <isbn> element is an
immediate subsidiary element of the <ref/> element.
It identifies the ISBN of the referenced book.
"ISBN" is the standard abbreviation for
"international standard book number". Description The start-tag is required; there is no corresponding end-tag. The content of <isbn> consists of one unformatted data item that ends when another tag is encountered. Format The <isbn> element's unformatted data consist of a single string of characters that constitute the referenced publication's ISBN as established by ISO 2108. Example <isbn> 0-201-134489 |
| <issn> |
| The <issn> element is an
immediate subsidiary element of the <ref/> element.
It identifies the ISSN of the referenced serial or
journal. "ISSN" is the standard abbreviation
for "international standard serial number". Description The start-tag is required; there is no corresponding end-tag. The content of <issn> consists of one unformatted data item that ends when another tag is encountered. Format The <issn> element's unformatted data consists of a single string of characters that constitute the referenced publication's ISSN number as established by ISO 3297. Examples <issn> 8750-6874 |
| <restrict/> |
| The <restrict/> element is an
optional immediate subsidiary element of the
<source> element. It is used to list any
restrictions on the distribution or use of the data base
or other distributed material. Description Both start-tag and end-tag are required. The <restrict/> content consists of unformatted text. Format The content of the <restrict/> tag consists of unformatted text describing the restrictions that apply. A <cmt/> element may be used if needed. Example <restrict/> Data protected by
copyright, royalties required. This file may be studied,
and values used for imputation of data for other tables
as long as the source is acknowledged. Other uses require
making arrangements with the data source. |
| <sourceref> |
| The <sourceref> element is an
optional, but very desirable, immediate subsidiary of the
<source>. It specifies the way this interchange
file should be referred to when communicating with the
source individual or organization. Description The start-tag is required; there is no corresponding end-tag. The content of <sourceref> consists of one unformatted data item that ends when another tag is encountered. Format The content of <sourceref> is unformatted data which must consist of characters making up a name or phrase by which this collection of data can be identified in communications to the source person or organization; it is especially useful in identifying special-purpose subsets of the data base described in <ref/> . It is optionally provided by the source, or may be provided by a regional centre on behalf of the source. Example <sourceref> Stanford special extras of USDA Handbook 8, Jan 1988 |
| <dflt> |
| The <dflt> element is an
immediate subsidiary of the <infoods 85> element.
It is optional, but, if it appears, it does so as the
second subsidiary element (after <header> ). It
prescribes defaults for various elements or parts of
their content. These defaults are applied throughout the
interchange file. Description This is a structural tag, and both start-tag and end-tag are required. The structure of the content is precisely the same as that for the <food> element, but the asterisk character may be used to indicate data value positions. Format The content of <dflt> has precisely the same structure as a <food> element, except that all subsidiary elements are optional. <Dflt> itself must be omitted if all immediately subsidiary elements are omitted. If <dflt> and a subsidiary element are used to specify a data value for a particular position, no other value may appear in that position. Details of the relationship between elements subsidiary to <dflt> and those subsidiary to <food> and of how <dflt> is applied are discussed in Chapter 3. While default values will most often be used subsidiary to <comp> or <drvd-comp> to specify, e.g., units of measure for particular nutrients, default values for subsidiaries of <classif> or even <fddflt> are plausible in some cases, especially when very specialized tables or homogeneous laboratory data are involved. For example, if an interchange file consisted entirely of data about samples of "Granny Smith apples" and all measurements were to be reported both per 100 grams edible portion and per apple, the second example shown below illustrates a possible interchange file structure. Examples <dflt> <comp> <procnt> * JONES </procnt> <energc> * KJA </energc> </comp> </dflt> <dflt> |