Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Augmented Backus Naur form


  
  Speech Recognition Grammar Specification Version 1.0
Augmented BNF syntax (ABNF): this is a plain-text (non-XML) representation which is similar to traditional BNF grammar and to many existing BNF-like representations commonly used in the field of speech recognition including the JSpeech Grammar Format [JSGF] from which this specification is derived.
In the ABNF Form a special rule reference is syntactically identical to a local rule reference.
Both the XML Form and ABNF Form permit the grammar header to optionally declare a single rule to be the root rule of the grammar.
www.w3.org /TR/grammar-spec   (11104 words)

  
  Backus-Naur form -- Facts, Info, and Encyclopedia article   (Site not responding. Last check: 2007-10-31)
BNF is widely used as a (A technical system of symbols used to represent special things) notation for the (Studies of the formation of basic linguistic units) grammars of computer ((computer science) a language designed for programming computers) programming languages, command sets and (Click link for more info and facts about communication protocol) communication protocols.
BNF was originally named after (Click link for more info and facts about John Backus) John Backus and later (at the suggestion of (Click link for more info and facts about Donald Knuth) Donald Knuth) also after (Click link for more info and facts about Peter Naur) Peter Naur.
The Backus-Naur Form or BNF grammars have significant similarities to Pāṇini's grammar rules, and is sometimes also referred to as Panini-Backus Form.
www.absoluteastronomy.com /encyclopedia/B/Ba/Backus-Naur_form1.htm   (761 words)

  
 RFC 2234 (rfc2234) - Augmented BNF for Syntax Specifications: ABNF
In ABNF a character is merely a non-negative integer.
NOTE: A quoted string containing alphabetic characters is special form for specifying alternative characters and is interpreted as a non-terminal representing the set of combinatorial strings with the contained characters, in the specified order but with any mixture of upper and lower case..
The full form is: *element where and are optional decimal values, indicating at least and at most occurrences of element.
www.faqs.org /rfcs/rfc2234.html   (1997 words)

  
 backus naur form
The Backus-Naur form (BNF) (also known as Backus normal form) is a metasyntax used to express context-free grammars: that is, a formal way to describe formal languages.
It was originally named after John Backus and later (at the suggestion of Donald Knuth) also after Peter Naur, two pioneers in computer science, namely in the art of compiler design, as part of creating the rules for Algol 60.
The Extended Backus-Naur form (EBNF) is a common one.
www.fact-library.com /backus_naur_form.html   (394 words)

  
 Notations for context-free grammars: BNF, Syntax Diagrams, EBNF
History: the very first version was created by John Backus, and shortly after improved by Peter Naur, and it was this improved version that was publicly used for the first time, to define Algol 60.
Knuth's letter (which you may be able to access via ACM) is interesting to read, as it indicates exactly what he thought the importance concepts in BNF were.
He also points out that BNF is not a "Normal Form", which would imply there were some restrictions on how a grammar could be written down, as in e.g.
www.cs.man.ac.uk /~pjj/bnf/bnf.html   (1329 words)

  
 rfc3018
The processing of two types of the instructions differs as follows: o The field of the identifier of request REQ_ID is formed by the protocol in the instructions of the first type, and it is formed by VM for the instructions of the second type.
It is formed by the VM of sender and must contain all the information necessary VM of the receiver.
It is formed by the sender VM and it must contain the information, which is necessary to the addressee VM for the creation of object.
ietfreport.isoc.org /idref/rfc3018   (16140 words)

  
 2.1 Augmented BNF
All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form (BNF) similar to that used by RFC 822 [7].
The full form is "#element" indicating at least and at most elements, each separated by one or more commas (",") and optional linear whitespace (LWS).
However, applications should attempt to follow "common form" when generating HTTP constructs, since there exist some implementations that fail to accept anything beyond the common forms.
www.kefk.net /CIE/RFC/1945/7.htm   (540 words)

  
 ABNF - Augmented Backus Naur Form
ABNF is a acronym that can contains many meanings which are listed below.
There may be many popular meanings for ABNF with the most popular definition being that of Augmented Backus Naur Form
If you have more information or know of another definition for ABNF, please let us know so that we can review it and add that information to our database.
www.auditmypc.com /acronym/ABNF.asp   (169 words)

  
 Fairdice : Cryptography : Backus-Naur Form
Augmented BNF taken from RFC 2616 supplemented by RFC 2234 An augmented Backus-Naur Form (BNF) similar to that used by RFC 822.
The augmented BNF includes the following constructs: name = definition The name of a rule is simply the name itself (without any enclosing "<" and ">") and is separated from its definition by the equal "=" character.
This makes the usual form of lists very easy; a rule such as (*LWS element *(*LWS "," *LWS element)) can be shown as 1#element Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present.
fairdice.sourceforge.net /crypto/protocol/v0.3/bnf.html   (830 words)

  
 CIM Tutorial > WBEM > CIM > MOF > Backus Naur Form
Story has it that most of BNF was introduced by Backus in a report, but when Peter Naur read the report he was surprised at some of the differences he found between his and Backus's interpretation.
Naur made a few modificiations that are almost universally used and drew up on his own the BNF.
The grammar for MOF syntax is described in the notation defined in Augmented BNF for Syntax Specifications, with this deviation: each token may be separated by an arbitrary number of white space characters, except where stated otherwise (at least one tab, carriage return, line feed, form feed or space).
www.wbemsolutions.com /tutorials/CIM/cim-mof-bnf.html   (399 words)

  
 Augmented Backus-Naur form - Free net encyclopedia   (Site not responding. Last check: 2007-10-31)
The Augmented Backus-Naur form (ABNF) is based on Backus-Naur form (BNF) form, but consisting of its own syntax and derivation rules.
ABNF is encoded in 7-bit ASCII in an 8-bit field with the high bit set to zero.
Use of the alternative operator with concatenation may be confusing and it is recommended that grouping be used to make explicit concatenation groups.
www.netipedia.com /index.php/ABNF   (743 words)

  
 Augmented BNF for Syntax Specifications: ABNF
Internet technical specifications often need to define a format syntax and are free to employ whatever notation their authors deem useful.
ABNF permits specifying literal text string directly, enclosed in quotation-marks.
The syntax for ABNF was originally specified in RFC 733.
xml.resource.org /public/rfc/html/rfc2234.html   (1871 words)

  
 RFC du protocole HTTP : Augmented BNF
Augmented BNF All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form (BNF) similar to that used by RFC 822 [9].
The full form is "(n)*(m)element" indicating at least (n) and at most (m) occurrences of element.
The full form is "(n)#(m)element" indicating at least (n) and at most (m) elements, each separated by one or more commas (",") and OPTIONAL linear white space (LWS).
www.iprelax.fr /http/http_rfc2.php   (1040 words)

  
 RFC822: Standard for the format of ARPA Internet text messages. D....   (Site not responding. Last check: 2007-10-31)
The syntax of the standard, in RFC #733, was originally specified in the Backus-Naur Form (BNF) meta-language.
The full form is: *element indicating at least and at most occurrences of element.
In this case, the
serves only as an indication of group distribution and would appear in the form: name:; Some mail services may provide a group-list distribution facility, accepting a single mailbox reference, expanding it to the full distribution list, and relaying the mail to the list's members.
rfc822.x42.com   (9565 words)

  
 Greibach normal form -- Facts, Info, and Encyclopedia article   (Site not responding. Last check: 2007-10-31)
Conversely, every context-free grammar which does not generate the null string can be transformed into an equivalent grammar in Greibach normal form.
This can be used to prove that every (Click link for more info and facts about context-free language) context-free language can be accepted by a non-deterministic (Click link for more info and facts about pushdown automaton) pushdown automaton.
Greibach normal form is named for (Click link for more info and facts about Sheila Greibach) Sheila Greibach.
www.absoluteastronomy.com /encyclopedia/G/Gr/Greibach_normal_form.htm   (214 words)

  
 ABNF définition ABNF
ABNF définition ABNF, ABNF définiton de ABNF : Augmented Bachus-Naur Form.
ABNF définition ABNF, Le document XML doit contenir un élément de niveau supérieur.
AMA définition AMA, ABNF définition ABNF, ARA, AOHELL définition AOHELL, AOUTELOUQUE.
dictionnaire.phpmyvisites.net /definition-ABNF--6421.htm   (327 words)

  
 The Network Access Identifier
Ensuring that NAIs conform to their ABNF is not sufficient, it is also necessary to ensure that they do not contain prohibited output.
NAIs are sent over the wire in their canonical form, and tasks such as normalization do not typically need to be performed by nodes that just pass NAIs around or receive them from the network.
The ABNF validator at http://www.apps.ietf.org/abnf.html was used to verify the syntactic correctness of the ABNF in Section 2.1 (Formal Syntax).
www.arkko.com /publications/nai/naibis.html   (3854 words)

  
 EBN - Eclectic Backus-Naur Form Review
Backus-Naur Form was Augmented and Extended, but then there was confusion; too many variations and conflicting notations.
The first example at the left is called a "metalinguistic variable" in Backus-Naur Form (BNF), and is called a "non-terminal", or "rule name" in Augmented Backus-Naur Form (ABNF).
The third form is used by Extended Backus-Naur Form.
www.skipgeel.com /ebn.html   (3465 words)

  
 2.4. Syntax Notation
A discussion of this is outside the bounds of this standard, but it is expected that implementors will be able quickly to understand it with reference to that defining document.
The syntax is in fact ambiguous insofar as it may be impossible to tell in which of several possible ways a given comment or WS was produced.
However, this does not lead to semantic ambiguity because, unless specifically stated otherwise, the presence of absence of a comment or additional WS has no semantic meaning and, in particular, it is a matter of indifference whether it forms a part of the syntactic construct preceding it or the one following it.
www.mibsoftware.com /userkt/usefor/05/0010.htm   (805 words)

  
 augmented_backus-naur_form - OneLook Dictionary Search
We found 3 dictionaries with English definitions that include the word augmented backus-naur form:
Tip: Click on the first link on a line below to go directly to a page where "augmented backus-naur form" is defined.
Augmented Backus-Naur Form : Free On-line Dictionary of Computing [home, info]
www.onelook.com /?w=augmented_backus-naur_form&loc=resrd   (85 words)

  
 RFC 722 (Auszug)   (Site not responding. Last check: 2007-10-31)
NOTATIONAL CONVENTIONS These specifications are made in an augmented Backus-Naur Form (BNF).
Differences from standard BNF involve the naming of rules, the indication of repetition and of "local" alternatives.
This makes the usual form of lists very easy; a rule such as '(element *("," element))' can be shown as "1#element".
www.spinfo.uni-koeln.de /lehre/BIT/1998/Aufgaben-04/rfc-0733-excerpt.html   (327 words)

  
 0.01 - Perl module for dealing with Augmented Backus-Naur Form   (Site not responding. Last check: 2007-10-31)
Amongst other things, It can conver ABNF to either English description of the syntax or a regular expression.
It is a grammar, similar in concept to the regular expressions that Perl is renowned for, which is often used for specifying format syntaxes in technical specifications.
The rules may be given in any form that RFC 2234 declares as a valid rule declaration.
www.zevils.com /~matthewg/libparse-abnf-perl.html   (575 words)

  
 2.1 Augmented BNF   (Site not responding. Last check: 2007-10-31)
Implementers will need to be familiar with the notation in order to understand this specification.
The full form is "#element " indicating at least and at most elements, each separated by one or more commas (",") and optional linear whitespace (LWS).
This makes the usual form of lists very easy; a rule such as "(*LWS element *(*LWS "," *LWS element)) " can be shown as "1#element".
www.clizio.com /Connected/RFC/2068/7.htm   (484 words)

  
 Cotse - Connected: An Internet Encyclopedia - 2. NOTATIONAL CONVENTIONS
This specification uses an augmented Backus-Naur Form (BNF) notation.
This makes the usual form of lists very easy; a rule such as '(element *("," element))' can be shown as "1#element".
Wherever this construct is used, null elements are allowed, but do not contribute to the count of elements present.
www.cotse.com /CIE/RFC/822/4.htm   (498 words)

  
 Tech Invite -- Augmented BNF (ABNF) for SIP -- RFC3261 and subsequent SIP RFCs
Tech Invite -- Augmented BNF (ABNF) for SIP -- RFC3261 and subsequent SIP RFCs
Augmented BNF (ABNF) for SIP -- RFC3261 and subsequent SIP RFCs
This page documents the ABNF (Augmented Backus-Naur Form) definitions for SIP text messages, defined in chapter 25 of RFC3261, and subsequent RFCs.
www.tech-invite.com /Ti-sip-abnf.html   (137 words)

  
 [No title]
RULE DEFINITION 2.1 Rule Naming The name of a rule is simply the name itself; that is, a sequence of characters, beginning with an alphabetic character, and followed by a combination of alphabetics, digits and hyphens (dashes).
However, angle brackets may be used around a rule name whenever their presence will facilitate discerning the use of a rule name.
The full form is: *element where and are optional decimal values, indicating at least and at most occurrences of element.
www.ietf.org /rfc/rfc2234.txt   (1902 words)

  
 RFC 822   (Site not responding. Last check: 2007-10-31)
The local-part of an addr-spec in a mailbox specification (i.e., the host's name for the mailbox) is understood to be whatever the receiving mail protocol server allows.
This form might be used to indicate that a single mailbox is shared by several users.
Fewer optional forms are permitted and the list of three- letter time zones has been shortened.
www.sendmail.org /rfc/0822.html   (9047 words)

  
 [No title]
An XRI thus escaped is said to be in escaped normal form.
Encoding XRI Metadata In some cases, the transformation from an identifier in its native language and display format into an XRI in escaped normal form may lose information that cannot be retained through character escaping.
The first is the global context symbol (GCS), and the second is the cross-reference (abbreviated in the ABNF as xref).
www.oasis-open.org /archives/xri-editors/200501/doc00000.doc   (2852 words)

  
 Glossary
In computer software or programming, form factor typically refers to the size of the program or the amount of memory required to run the program effectively.
Shortened form of "No Recognition." NoReco is the name of the event generated by the speech recognition (SR) engine when the engine is unable to recognize input.
A collection of names, identified by a URI reference, which are used in XML documents as element types and attribute names.
www.microsoft.com /speech/techinfo/glossary/default.mspx   (4438 words)

  
 XMPP URI Format
Within the context of the streaming XML technology that forms the foundation of XMPP, the addresses of XMPP entities are not specified as full URIs.
The syntax for an xmpp: URI is defined below using Augmented Backus-Naur Form as specified by [ABNF].
Overell, "Augmented BNF for Syntax Specifications: ABNF", RFC 2234, November 1997.
www.xmpp.org /drafts/attic/draft-saintandre-xmpp-uri-01.html   (1294 words)

  
 CGI specification
All of the mechanisms specified in this document are described in both prose and an augmented Backus-Naur Form described in section 2.1 of the HTTP/1.0 specification [2].
Fully qualified domain names take the form as described in section 3.5 of RFC 1034 [5] and section 2.1 of RFC 1123 [4]; a sequence of domain labels separated by ".", each domain label starting and ending with an alphanumerical character and possibly also containing "-" characters.
There are two forms of output that the script can give; non-parsed header (NPH) output, and parsed header output.
www.jalix.org /ressources/internet/cgi/_specifications/cgi-spec.htm   (2764 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.