Skip to content
This repository was archived by the owner on Sep 21, 2021. It is now read-only.

Commit 8ecd4c7

Browse files
committedNov 24, 2014
Edited 052_Mapping_Analysis/30_Exact_vs_full_text.asciidoc with Atlas code editor
1 parent 65806d1 commit 8ecd4c7

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed
 

Diff for: ‎052_Mapping_Analysis/30_Exact_vs_full_text.asciidoc

+4-3
Original file line numberDiff line numberDiff line change
@@ -11,15 +11,16 @@ The exact value `2014` is not the same as the exact value `2014-09-15`.
1111
_Full text_, on the other hand, refers ((("full text")))to textual data--usually written in
1212
some human language -- like the text of a tweet or the body of an email.
1313

14-
15-
NOTE: Full text is often referred to as _unstructured data_, which is a misnomer--natural language is highly structured. The problem is that the rules of
14+
[NOTE]
15+
====
16+
Full text is often referred to as _unstructured data_, which is a misnomer--natural language is highly structured. The problem is that the rules of
1617
natural languages are complex, which makes them difficult for computers to
1718
parse correctly. For instance, consider this sentence:
1819
1920
May is fun but June bores me.
2021
2122
Does it refer to months or to people?
22-
23+
====
2324

2425
Exact values are easy to query. The decision is binary; a value either
2526
matches the query, or it doesn't. This kind of query is easy to express with

0 commit comments

Comments
 (0)
This repository has been archived.