Sam Heard wrote:
Hi Adam
This is another example of the approach to be as specific as possible.
The exclude statement can be used to exclude specific archetypes and
the Include ALL in this case means that all others are allowed. If the
Exclude ALL statement is added to an archetype, it
Williamtfgoossen at cs.com wrote:
In a message dated 13-6-2008 19:10:07 W. Europe Daylight Time,
sam.heard at oceaninformatics.com writes:
We are getting into dangerous options here: include all and exclude
all in a time series where 'all' definitely changes both with respect
to
Thomas Beale wrote:
Andrew Patterson wrote:
Sam, without putting words in Adams mouth, I think he was asking about
the precedence of include/exclude sections. It is a common problem is
coming up with rule system like this - for instance one can look at the
allow/deny pattern of the
Adam Flinton wrote:
I am assuming allow then deny i.e. include all, exclude all = include all.
Otherwise...exclude all becomes somewhere between pointless dangerous.
I think of it in terms of items moving back and forth between an include
list and an exclude list.
* Initially, the slot is
This is another example of the approach to be as specific as possible. The
exclude statement can be used to exclude specific archetypes and the Include
ALL in this case means that all others are allowed. If the Exclude ALL
statement is added to an archetype, it means ONLY those specifically
In a message dated 13-6-2008 19:10:07 W. Europe Daylight Time,
sam.heard at oceaninformatics.com writes:
We are getting into dangerous options here: include all and exclude all in a
time series where 'all' definitely changes both with respect to revisions of
the existing ones, deletions and
William,
It is potentially dangerous ground.
But ...
- Archetypes express what can be documented about a specific topic.
Since such a 'Real Archetype' can or will consist of re-usable
patterns, 'Real Archetypes' consist many times of a collection of sub-
archetypes that express recurring
7 matches
Mail list logo