devicemap-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From re...@apache.org
Subject svn commit: r1650779 - /devicemap/branches/2.0/data/README_PATTERNS
Date Sat, 10 Jan 2015 18:06:44 GMT
Author: rezan
Date: Sat Jan 10 18:06:44 2015
New Revision: 1650779

URL: http://svn.apache.org/r1650779
Log:
files

Modified:
    devicemap/branches/2.0/data/README_PATTERNS

Modified: devicemap/branches/2.0/data/README_PATTERNS
URL: http://svn.apache.org/viewvc/devicemap/branches/2.0/data/README_PATTERNS?rev=1650779&r1=1650778&r2=1650779&view=diff
==============================================================================
--- devicemap/branches/2.0/data/README_PATTERNS (original)
+++ devicemap/branches/2.0/data/README_PATTERNS Sat Jan 10 18:06:44 2015
@@ -40,10 +40,13 @@ The following definitions are used:
  candidate::
  :: this is a pattern which has successfully matched a pattern type in the token stream
 
+ file::
+ :: a file is some kind of representation of the settings described in this document
+
 
 === Format ===
 
-The pattern and attribute objects are JSON objects (TODO: better define this). These objects
will contain:
+The pattern and attribute files are JSON objects (TODO: better define this). These files
will contain:
 
  * Format version
  * Name
@@ -51,7 +54,7 @@ The pattern and attribute objects are JS
  * Description
  * Publish date
 
-The objects will also contain the attributes defined below in this specification.
+The files will also contain the attributes defined below in this specification.
 
 
 
@@ -59,7 +62,7 @@ The objects will also contain the attrib
 
 This step parses the input string and creates the token stream.
 
-Each pattern object defines the input parsing rules:
+Each pattern file defines the input parsing rules:
 
  InputTransformers::
  :: Type: list of transformation steps
@@ -114,7 +117,7 @@ Ngram:         a_NUM, a, _NUMxyz, _NUM,
 This step processes the token stream and returns the highest ranking pattern which
 matches on the stream (highest ranking candidate).
 
-The pattern object defines a set of patterns. Each pattern has 2 main attributes,
+The pattern file defines a set of patterns. Each pattern has 2 main attributes,
 its pattern type and its pattern rank. The pattern
 type defines how the pattern is supposed to be matched against the token stream.
 The pattern rank defines how the pattern ranks against other patterns.
@@ -261,10 +264,10 @@ TODO: how?
 
 
 
-= Patch Objects =
+= Patch Files =
 
-The pattern and attribute objects can be patched with a user created pattern and
-attribute objects. In this case, parsing configurations override, pattern
+The pattern and attribute files can be patched with a user created pattern and
+attribute files. In this case, parsing configurations override, pattern
 definitions get appended (you can override using pattern ranking), and attributes
 override using the Pattern``Id.
 



Mime
View raw message