Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Parsing

From Wikipedia, the free encyclopedia
Analysing a string of symbols, according to the rules of a formal grammar
"Parse" redirects here. For other uses, seeParse (disambiguation).

Parsing,syntax analysis, orsyntactic analysis is a process of analyzing astring ofsymbols, either innatural language,computer languages ordata structures, conforming to the rules of aformal grammar by breaking it into parts. The termparsing comes from Latinpars (orationis), meaningpart (of speech).[1]

The term has slightly different meanings in different branches oflinguistics andcomputer science. Traditionalsentence parsing is often performed as a method of understanding the exact meaning of a sentence or word, sometimes with the aid of devices such assentence diagrams. It usually emphasizes the importance of grammatical divisions such assubject andpredicate.

Withincomputational linguistics the term is used to refer to the formal analysis by a computer of a sentence or other string of words into its constituents, resulting in aparse tree showing their syntactic relation to each other, which may also containsemantic information.[citation needed] Some parsing algorithms generate aparse forest or list of parse trees from a string that issyntactically ambiguous.[2]

The term is also used inpsycholinguistics when describing language comprehension. In this context, parsing refers to the way that human beings analyze a sentence or phrase (in spoken language or text) "in terms of grammatical constituents, identifying the parts of speech, syntactic relations, etc."[1] This term is especially common when discussing which linguistic cues help speakers interpretgarden-path sentences.

Within computer science, the term is used in the analysis ofcomputer languages, referring to the syntactic analysis of the input code into its component parts in order to facilitate the writing ofcompilers andinterpreters. The term may also be used to describe a split or separation.

In data analysis, the term is often used to refer to a process extracting desired information from data, e.g., creating atime series signal from aXML document.

Human languages

[edit]
Main category:Natural language parsing

Traditional methods

[edit]

The traditional grammatical exercise of parsing, sometimes known asclause analysis, involves breaking down a text into its componentparts of speech with an explanation of the form, function, and syntactic relationship of each part.[3] This is determined in large part from study of the language'sconjugations anddeclensions, which can be quite intricate for heavilyinflected languages. To parse a phrase such as "man bites dog" involves noting that thesingular noun "man" is thesubject of the sentence, the verb "bites" is thethird person singular of thepresent tense of the verb "to bite", and the singular noun "dog" is theobject of the sentence. Techniques such assentence diagrams are sometimes used to indicate relation between elements in the sentence.

Parsing was formerly central to the teaching of grammar throughout the English-speaking world, and widely regarded as basic to the use and understanding of written language.[citation needed]

Computational methods

[edit]
Main article:Syntactic parsing (computational linguistics)
icon
This sectionneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources in this section. Unsourced material may be challenged and removed.(February 2013) (Learn how and when to remove this message)

In somemachine translation andnatural language processing systems, written texts in human languages are parsed by computer programs.[4] Human sentences are not easily parsed by programs, as there is substantialambiguity in the structure of human language, whose usage is to convey meaning (orsemantics) amongst a potentially unlimited range of possibilities, but only some of which are germane to the particular case.[5] So an utterance "Man bites dog" versus "Dog bites man" is definite on one detail but in another language might appear as "Man dog bites" with a reliance on the larger context to distinguish between those two possibilities, if indeed that difference was of concern. It is difficult to prepare formal rules to describe informal behaviour even though it is clear that some rules are being followed.[citation needed]

In order to parse natural language data, researchers must first agree on thegrammar to be used. The choice of syntax is affected by bothlinguistic and computational concerns; for instance some parsing systems uselexical functional grammar, but in general, parsing for grammars of this type is known to beNP-complete.Head-driven phrase structure grammar is another linguistic formalism which has been popular in the parsing community, but other research efforts have focused on less complex formalisms such as the one used in the PennTreebank.Shallow parsing aims to find only the boundaries of major constituents such as noun phrases. Another popular strategy for avoiding linguistic controversy isdependency grammar parsing.

Most modern parsers are at least partly statistical; that is, they rely on acorpus of training data which has already been annotated (parsed by hand). This approach allows the system to gather information about the frequency with which various constructions occur in specific contexts.(Seemachine learning.) Approaches which have been used include straightforwardPCFGs (probabilistic context-free grammars),[6]maximum entropy,[7] andneural nets.[8] Most of the more successful systems uselexical statistics (that is, they consider the identities of the words involved, as well as theirpart of speech). However such systems are vulnerable tooverfitting and require some kind ofsmoothing to be effective.[citation needed]

Parsing algorithms for natural language cannot rely on the grammar having 'nice' properties as with manually designed grammars for programming languages. As mentioned earlier some grammar formalisms are very difficult to parse computationally; in general, even if the desired structure is notcontext-free, some kind of context-free approximation to the grammar is used to perform a first pass. Algorithms which use context-free grammars often rely on some variant of theCYK algorithm, usually with someheuristic to prune away unlikely analyses to save time.(Seechart parsing.) However some systems trade speed for accuracy using, e.g., linear-time versions of theshift-reduce algorithm. A somewhat recent development has beenparse reranking in which the parser proposes some large number of analyses, and a more complex system selects the best option.[citation needed] Innatural language understanding applications,semantic parsers convert the text into a representation of its meaning.[9]

Psycholinguistics

[edit]

Inpsycholinguistics, parsing involves not just the assignment of words to categories (formation of ontological insights), but the evaluation of the meaning of a sentence according to the rules of syntax drawn by inferences made from each word in the sentence (known asconnotation). This normally occurs as words are being heard or read.

Neurolinguistics generally understands parsing to be a function of working memory, meaning that parsing is used to keep several parts of one sentence at play in the mind at one time, all readily accessible to be analyzed as needed. Because the human working memory has limitations, so does the function of sentence parsing.[10] This is evidenced by several different types of syntactically complex sentences that demonstrate potential issues for mental parsing of sentences.

The first, and perhaps most well-known, type of sentence that challenges parsing ability is the garden-path sentence. These sentences are designed so that the most common interpretation of the sentence appears grammatically faulty, but upon further inspection, these sentences are grammatically sound. Garden-path sentences are difficult to parse because they contain a phrase or a word with more than one meaning, often their most typical meaning being a different part of speech.[11] For example, in the sentence, "the horse raced past the barn fell", raced is initially interpreted as a past tense verb, but in this sentence, it functions as part of an adjective phrase.[12] Since parsing is used to identify parts of speech, these sentences challenge the parsing ability of the reader.

Another type of sentence that is difficult to parse is an attachment ambiguity, which includes a phrase that could potentially modify different parts of a sentence, and therefore presents a challenge in identifying syntactic relationship (i.e. "The boy saw the lady with the telescope", in which the ambiguous phrase with the telescope could modify the boy saw or the lady.)[11]

A third type of sentence that challenges parsing ability is center embedding, in which phrases are placed in the center of other similarly formed phrases (i.e. "The rat the cat the man hit chased ran into the trap".) Sentences with 2 or in the most extreme cases 3 center embeddings are challenging for mental parsing, again because of ambiguity of syntactic relationship.[13]

Within neurolinguistics there are multiple theories that aim to describe how parsing takes place in the brain. One such model is a more traditional generative model of sentence processing, which theorizes that within the brain there is a distinct module designed for sentence parsing, which is preceded by access to lexical recognition and retrieval, and then followed by syntactic processing that considers a single syntactic result of the parsing, only returning to revise that syntactic interpretation if a potential problem is detected.[14] The opposing, more contemporary model theorizes that within the mind, the processing of a sentence is not modular, or happening in strict sequence. Rather, it poses that several different syntactic possibilities can be considered at the same time, because lexical access, syntactic processing, and determination of meaning occur in parallel in the brain. In this way these processes are integrated.[15]

Although there is still much to learn about the neurology of parsing, studies have shown evidence that several areas of the brain might play a role in parsing. These include the left anterior temporal pole, the left inferior frontal gyrus, the left superior temporal gyrus, the left superior frontal gyrus, the right posterior cingulate cortex, and the left angular gyrus. Although it has not been absolutely proven, it has been suggested that these different structures might favor either phrase-structure parsing or dependency-structure parsing, meaning different types of parsing could be processed in different ways which have yet to be understood.[16]

Discourse analysis

[edit]

Discourse analysis examines ways to analyze language use and semiotic events. Persuasive language may be calledrhetoric.

Computer languages

[edit]
icon
This sectiondoes notcite anysources. Please helpimprove this section byadding citations to reliable sources. Unsourced material may be challenged andremoved.(February 2013) (Learn how and when to remove this message)

Parser

[edit]
"Parser" redirects here. For the scripting language named Parser, seeParser (programming language).

Aparser is a software component that takes input data (typically text) and builds adata structure – often some kind ofparse tree,abstract syntax tree or other hierarchical structure, giving a structural representation of the input while checking for correct syntax. The parsing may be preceded or followed by other steps, or these may be combined into a single step. The parser is often preceded by a separatelexical analyser, which creates tokens from the sequence of input characters; alternatively, these can be combined inscannerless parsing. Parsers may be programmed by hand or may be automatically or semi-automatically generated by aparser generator. Parsing is complementary totemplating, which produces formattedoutput. These may be applied to different domains, but often appear together, such as thescanf/printf pair, or the input (front end parsing) and output (back end code generation) stages of acompiler.

The input to a parser is typically text in somecomputer language, but may also be text in a natural language or less structured textual data, in which case generally only certain parts of the text are extracted, rather than a parse tree being constructed. Parsers range from very simple functions such asscanf, to complex programs such as the frontend of aC++ compiler or theHTML parser of aweb browser. An important class of simple parsing is done usingregular expressions, in which a group of regular expressions defines aregular language and a regular expression engine automatically generating a parser for that language, allowingpattern matching and extraction of text. In other contexts regular expressions are instead used prior to parsing, as the lexing step whose output is then used by the parser.

The use of parsers varies by input. In the case of data languages, a parser is often found as the file reading facility of a program, such as reading in HTML orXML text; these examples aremarkup languages. In the case ofprogramming languages, a parser is a component of acompiler orinterpreter, which parses thesource code of acomputer programming language to create some form of internal representation; the parser is a key step in thecompiler frontend. Programming languages tend to be specified in terms of adeterministic context-free grammar because fast and efficient parsers can be written for them. For compilers, the parsing itself can be done in one pass or multiple passes – seeone-pass compiler andmulti-pass compiler.

The implied disadvantages of a one-pass compiler can largely be overcome by addingfix-ups, where provision is made for code relocation during the forward pass, and the fix-ups are applied backwards when the current program segment has been recognized as having been completed. An example where such a fix-up mechanism would be useful would be a forward GOTO statement, where the target of the GOTO is unknown until the program segment is completed. In this case, the application of the fix-up would be delayed until the target of the GOTO was recognized. Conversely, a backward GOTO does not require a fix-up, as the location will already be known.

Context-free grammars are limited in the extent to which they can express all of the requirements of a language. Informally, the reason is that the memory of such a language is limited. The grammar cannot remember the presence of a construct over an arbitrarily long input; this is necessary for a language in which, for example, a name must be declared before it may be referenced. More powerful grammars that can express this constraint, however, cannot be parsed efficiently. Thus, it is a common strategy to create a relaxed parser for a context-free grammar which accepts a superset of the desired language constructs (that is, it accepts some invalid constructs); later, the unwanted constructs can be filtered out at thesemantic analysis (contextual analysis) step.

For example, inPython the following is syntactically valid code:

x:int=1print(x)

The following code, however, is syntactically valid in terms of the context-free grammar, yielding a syntax tree with the same structure as the previous, but violates the semantic rule requiring variables to be initialized before use:

x:int=1print(y)

Overview of process

[edit]
Flow of data in a typical parser
Flow of data in a typical parser

The following example demonstrates the common case of parsing a computer language with two levels of grammar: lexical and syntactic.

The first stage is the token generation, orlexical analysis, by which the input character stream is split into meaningful symbols defined by a grammar ofregular expressions. For example, a calculator program would look at an input such as "12 * (3 + 4)^2" and split it into the tokens12,*,(,3,+,4,),^,2, each of which is a meaningful symbol in the context of an arithmetic expression. The lexer would contain rules to tell it that the characters*,+,^,( and) mark the start of a new token, so meaningless tokens like "12*" or "(3" will not be generated.

The next stage is parsing or syntactic analysis, which is checking that the tokens form an allowable expression. This is usually done with reference to acontext-free grammar which recursively defines components that can make up an expression and the order in which they must appear. However, not all rules defining programming languages can be expressed by context-free grammars alone, for example type validity and proper declaration of identifiers. These rules can be formally expressed withattribute grammars.

The final phase issemantic parsing or analysis, which is working out the implications of the expression just validated and taking the appropriate action.[17] In the case of a calculator or interpreter, the action is to evaluate the expression or program; a compiler, on the other hand, would generate some kind of code. Attribute grammars can also be used to define these actions.

Types of parsers

[edit]

Thetask of the parser is essentially to determine if and how the input can be derived from the start symbol of the grammar. This can be done in essentially two ways:

Top-down parsing
Top-down parsing can be viewed as an attempt to find left-most derivations of an input-stream by searching forparse trees using a top-down expansion of the givenformal grammar rules. Tokens are consumed from left to right. Inclusive choice is used to accommodateambiguity by expanding all alternative right-hand-sides of grammar rules.[18] This is known as the primordial soup approach. Very similar to sentence diagramming, primordial soup breaks down the constituencies of sentences.[19]
Bottom-up parsing
A parser can start with the input and attempt to rewrite it to the start symbol. Intuitively, the parser attempts to locate the most basic elements, then the elements containing these, and so on.LR parsers are examples of bottom-up parsers. Another term used for this type of parser isShift-Reduce parsing.

LL parsers andrecursive-descent parser are examples of top-down parsers that cannot accommodateleft recursiveproduction rules. Although it has been believed that simple implementations of top-down parsing cannot accommodate direct and indirect left-recursion and may require exponential time and space complexity while parsingambiguous context-free grammars, more sophisticated algorithms for top-down parsing have been created by Frost, Hafiz, and Callaghan[20][21] which accommodateambiguity andleft recursion in polynomial time and which generate polynomial-size representations of the potentially exponential number of parse trees. Their algorithm is able to produce both left-most and right-most derivations of an input with regard to a givencontext-free grammar.

An important distinction with regard to parsers is whether a parser generates aleftmost derivation or arightmost derivation (seecontext-free grammar). LL parsers will generate a leftmostderivation and LR parsers will generate a rightmost derivation (although usually in reverse).[18]

Somegraphical parsing algorithms have been designed forvisual programming languages.[22][23] Parsers for visual languages are sometimes based ongraph grammars.[24]

Adaptive parsing algorithms have been used to construct "self-extending"natural language user interfaces.[25]

Implementation

[edit]

A simple parser implementation reads the entire input file, performs an intermediate computation or translation, and then writes the entire output file,such as in-memorymulti-pass compilers.

Alternative parser implementation approaches:

  • push parsers call registered handlers (callbacks) as soon as the parser detects relevant tokens in the input stream. A push parser may skip parts of the input that are irrelevant (an example isExpat).
  • pull parsers, such as parsers that are typically used bycompilers front-ends by "pulling" input text.
  • incremental parsers (such as incrementalchart parsers) that, as the text of the file is edited by a user, does not need to completely re-parse the entire file.
  • Active versuspassive parsers[26][27]

Parser development software

[edit]
This articleis inlist format but may read better asprose. You can help byconverting this article, if appropriate.Editing help is available.(January 2017)
See also:Comparison of parser generators

Some of the well known parser development tools include the following:

Lookahead

[edit]
icon
This sectiondoes notcite anysources. Please helpimprove this section byadding citations to reliable sources. Unsourced material may be challenged andremoved.(April 2012) (Learn how and when to remove this message)
C program that cannot be parsed with less than 2 token lookahead.Top: C grammar excerpt.[28]Bottom: a parser has digested the tokens "intv;main(){" and is about to choose a rule to deriveStmt. Looking only at the first lookahead token "v", it cannot decide which of both alternatives forStmt to choose; the latter requires peeking at the second token.

Lookahead establishes the maximum incoming tokens that a parser can use to decide which rule it should use. Lookahead is especially relevant toLL,LR, andLALR parsers, where it is often explicitly indicated by affixing the lookahead to the algorithm name in parentheses, such as LALR(1).

Mostprogramming languages, the primary target of parsers, are carefully defined in such a way that a parser with limited lookahead, typically one, can parse them, because parsers with limited lookahead are often more efficient. One important change[citation needed] to this trend came in 1990 whenTerence Parr createdANTLR for his Ph.D. thesis, aparser generator for efficient LL(k) parsers, wherek is any fixed value.

LR parsers typically have only a few actions after seeing each token. They are shift (add this token to the stack for later reduction), reduce (pop tokens from the stack and form a syntactic construct), end, error (no known rule applies) or conflict (does not know whether to shift or reduce).

Lookahead has two advantages.[clarification needed]

  • It helps the parser take the correct action in case of conflicts. For example, parsing the if statement in the case of an else clause.
  • It eliminates many duplicate states and eases the burden of an extra stack. A C language non-lookahead parser will have around 10,000 states. A lookahead parser will have around 300 states.

Example: Parsing the Expression1 + 2 * 3[dubiousdiscuss]

Set of expression parsing rules (called grammar) is as follows,
Rule1:E → E + EExpression is the sum of two expressions.
Rule2:E → E * EExpression is the product of two expressions.
Rule3:E → numberExpression is a simple number
Rule4:+ has less precedence than *

Most programming languages (except for a few such as APL and Smalltalk) and algebraic formulas give higher precedence to multiplication than addition, in which case the correct interpretation of the example above is1 + (2 * 3).Note that Rule4 above is a semantic rule. It is possible to rewrite the grammar to incorporate this into the syntax. However, not all such rules can be translated into syntax.

Simple non-lookahead parser actions

Initially Input = [1, +, 2, *, 3]

  1. Shift "1" onto stack from input (in anticipation of rule3). Input = [+, 2, *, 3] Stack = [1]
  2. Reduces "1" to expression "E" based on rule3. Stack = [E]
  3. Shift "+" onto stack from input (in anticipation of rule1). Input = [2, *, 3] Stack = [E, +]
  4. Shift "2" onto stack from input (in anticipation of rule3). Input = [*, 3] Stack = [E, +, 2]
  5. Reduce stack element "2" to Expression "E" based on rule3. Stack = [E, +, E]
  6. Reduce stack items [E, +, E] and new input "E" to "E" based on rule1. Stack = [E]
  7. Shift "*" onto stack from input (in anticipation of rule2). Input = [3] Stack = [E,*]
  8. Shift "3" onto stack from input (in anticipation of rule3). Input = [] (empty) Stack = [E, *, 3]
  9. Reduce stack element "3" to expression "E" based on rule3. Stack = [E, *, E]
  10. Reduce stack items [E, *, E] and new input "E" to "E" based on rule2. Stack = [E]

The parse tree and resulting code from it is not correct according to language semantics.

To correctly parse without lookahead, there are three solutions:

  • The user has to enclose expressions within parentheses. This often is not a viable solution.
  • The parser needs to have more logic to backtrack and retry whenever a rule is violated or not complete. The similar method is followed in LL parsers.
  • Alternatively, the parser or grammar needs to have extra logic to delay reduction and reduce only when it is absolutely sure which rule to reduce first. This method is used in LR parsers. This correctly parses the expression but with many more states and increased stack depth.
Lookahead parser actions[clarification needed]
  1. Shift 1 onto stack on input 1 in anticipation of rule3. It does not reduce immediately.
  2. Reduce stack item 1 to simple Expression on input + based on rule3. The lookahead is +, so we are on path to E +, so we can reduce the stack to E.
  3. Shift + onto stack on input + in anticipation of rule1.
  4. Shift 2 onto stack on input 2 in anticipation of rule3.
  5. Reduce stack item 2 to Expression on input * based on rule3. The lookahead * expects only E before it.
  6. Now stack has E + E and still the input is *. It has two choices now, either to shift based on rule2 or reduction based on rule1. Since * has higher precedence than + based on rule4, we shift * onto stack in anticipation of rule2.
  7. Shift 3 onto stack on input 3 in anticipation of rule3.
  8. Reduce stack item 3 to Expression after seeing end of input based on rule3.
  9. Reduce stack items E * E to E based on rule2.
  10. Reduce stack items E + E to E based on rule1.

The parse tree generated is correct and simplymore efficient[clarify][citation needed] than non-lookahead parsers. This is the strategy followed inLALR parsers.

List of parsing algorithms

[edit]
This section is an excerpt fromList of algorithms § Parsing.[edit]

See also

[edit]

References

[edit]
  1. ^ab"Parse". dictionary.reference.com. Retrieved27 November 2010.
  2. ^Masaru Tomita (6 December 2012).Generalized LR Parsing. Springer Science & Business Media.ISBN 978-1-4615-4034-2.
  3. ^"Grammar and Composition". Archived fromthe original on 2016-12-01. Retrieved2012-11-24.
  4. ^Christopher D.. Manning; Christopher D. Manning; Hinrich Schütze (1999).Foundations of Statistical Natural Language Processing. MIT Press.ISBN 978-0-262-13360-9.
  5. ^Jurafsky, Daniel (1996). "A Probabilistic Model of Lexical and Syntactic Access and Disambiguation".Cognitive Science.20 (2):137–194.CiteSeerX 10.1.1.150.5711.doi:10.1207/s15516709cog2002_1.
  6. ^Klein, Dan, and Christopher D. Manning. "Accurate unlexicalized parsing." Proceedings of the 41st Annual Meeting on Association for Computational Linguistics-Volume 1. Association for Computational Linguistics, 2003.
  7. ^Charniak, Eugene. "A maximum-entropy-inspired parserArchived 2019-04-01 at theWayback Machine." Proceedings of the 1st North American chapter of the Association for Computational Linguistics conference. Association for Computational Linguistics, 2000.
  8. ^Chen, Danqi, and Christopher Manning. "A fast and accurate dependency parser using neural networks." Proceedings of the 2014 conference on empirical methods in natural language processing (EMNLP). 2014.
  9. ^Jia, Robin; Liang, Percy (2016-06-11). "Data Recombination for Neural Semantic Parsing".arXiv:1606.03622 [cs.CL].
  10. ^Sandra H. Vos, Thomas C. Gunter, Herbert Schriefers & Angela D. Friederici (2001) Syntactic parsing and working memory: The effects of syntactic complexity, reading span, and concurrent load, Language and Cognitive Processes, 16:1, 65-103, DOI: 10.1080/01690960042000085
  11. ^abPritchett, B. L. (1988). Garden Path Phenomena and the Grammatical Basis of Language Processing. Language, 64(3), 539–576.https://doi.org/10.2307/414532
  12. ^Thomas G Bever (1970).The cognitive basis for linguistic structures.OCLC 43300456.
  13. ^Karlsson, F. (2010). Working Memory Constraints on Multiple Center-Embedding. Proceedings of the Annual Meeting of the Cognitive Science Society, 32. Retrieved fromhttps://escholarship.org/uc/item/4j00v1j2
  14. ^Ferreira, F., & Clifton, C. (1986). The independence of syntactic processing. Journal of Memory and Language, 25(3), 348–368.https://doi.org/10.1016/0749-596X(86)90006-9
  15. ^Atlas, J. D. (1997). On the modularity of sentence processing: semantical generality and the language of thought. Language and Conceptualization, 213–214.
  16. ^Lopopolo, Alessandro, van den Bosch, Antal, Petersson, Karl-Magnus, and Roel M. Willems; Distinguishing Syntactic Operations in the Brain: Dependency and Phrase-Structure Parsing. Neurobiology of Language 2021; 2 (1): 152–175. doi:https://doi.org/10.1162/nol_a_00029
  17. ^Berant, Jonathan, and Percy Liang. "Semantic parsing via paraphrasing." Proceedings of the 52nd Annual Meeting of the Association for Computational Linguistics (Volume 1: Long Papers). 2014.
  18. ^abAho, A.V., Sethi, R. and Ullman, J.D. (1986) " Compilers: principles, techniques, and tools."Addison-Wesley Longman Publishing Co., Inc. Boston, MA, USA.
  19. ^Sikkel, Klaas (1997).Parsing schemata : a framework for specification and analysis of parsing algorithms. Berlin: Springer.ISBN 9783642605413.OCLC 606012644.
  20. ^Frost, R., Hafiz, R. and Callaghan, P. (2007) "Modular and Efficient Top-Down Parsing for Ambiguous Left-Recursive GrammarsArchived 2018-08-22 at theWayback Machine ."10th International Workshop on Parsing Technologies (IWPT), ACL-SIGPARSE, Pages: 109 - 120, June 2007, Prague.
  21. ^Frost, R., Hafiz, R. and Callaghan, P. (2008) "Parser Combinators for Ambiguous Left-Recursive Grammars." 10th International Symposium on Practical Aspects of Declarative Languages (PADL), ACM-SIGPLAN, Volume 4902/2008, Pages: 167 - 181, January 2008, San Francisco.
  22. ^Rekers, Jan, and Andy Schürr. "Defining and parsing visual languages with layered graph grammars." Journal of Visual Languages & Computing 8.1 (1997): 27-55.
  23. ^Rekers, Jan, and A. Schurr. "A graph grammar approach to graphical parsing." Visual Languages, Proceedings., 11th IEEE International Symposium on. IEEE, 1995.
  24. ^Zhang, Da-Qian, Kang Zhang, and Jiannong Cao. "A context-sensitive graph grammar formalism for the specification of visual languages." The Computer Journal 44.3 (2001): 186-200.
  25. ^Jill Fain Lehman (6 December 2012).Adaptive Parsing: Self-Extending Natural Language Interfaces. Springer Science & Business Media.ISBN 978-1-4615-3622-2.
  26. ^Patrick Blackburn and Kristina Striegnitz."Natural Language Processing Techniques in Prolog".
  27. ^Song-Chun Zhu."Classic Parsing Algorithms".
  28. ^taken fromBrian W. Kernighan and Dennis M. Ritchie (Apr 1988).The C Programming Language. Prentice Hall Software Series (2nd ed.). Englewood Cliffs/NJ: Prentice Hall.ISBN 0131103628. (Appendix A.13 "Grammar", p.193 ff)

Further reading

[edit]

External links

[edit]
Look upparse orparsing in Wiktionary, the free dictionary.
Top-down
Bottom-up
Mixed, other
Related topics
String metric
String-searching algorithm
Multiple string searching
Regular expression
Sequence alignment
Data structure
Other
Retrieved from "https://en.wikipedia.org/w/index.php?title=Parsing&oldid=1321598308"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp