Here's my tale of how ephedrine has adversely affected my life in many different ways.
I first started taking it while I was in the military. One of my buddies handed me four tablets (100mg) every time our squad got assigned to KP duty. Oh, how it made the day fly by so much quicker. I only took it occasionally while I was in the Army. After the Army, I got a job working night shift in a convenience store. The stuff was readily available, and it wasn't long till I was taking the stuff every night. Within a year I was taking about 300mg a day. My body was building a resistance and I had to take more to get the same effects.
About 1998, those pills started to really cause me problems. I was taking so many I couldn't hardly sleep. I might get 2-3 hrs a night then every 3rd night or so crash for 12 hrs. To combat this I started drinking every night... So here begins the vicious cycle. Wake up with hangover, immediately take ephedrine to counteract that and get energy... then have to drink ever larger amounts to shut the ephedrine down.
In 1999 I got my CDL and became an over the road truck driver. For the next 2 and a half years I didn't drink much, but my ephedrine ramped up to 500-600mg a day. That's 24 pills folks. In the industry ephedrine is referred to as trucker's speed. From 2001 to present I've worked local delivery but until this year I took roughly the same amount per day.
Lets talk about side effects. Sweat. I was constantly hot and sweated buckets. I had to drink tons of water to stay hydrated. I was restless and my hands were always trembling. I had trouble with my speech... I would know what I wanted to say but really had trouble with words and names... My heart rated was elevated all the time and my blood pressure was about 20 points above normal.
IMPORTANT: When I drink while using ephedrine, it disables some of the things that protect me from alcohol poisoning. 1) It keeps me awake. Passing out is one of my bodies best signs I am past my limit. Since I stopped I can only drink half of what I used to. 2) I believe it suppresses the urge to vomit when drinking too much, at least it did with me. Vomiting is the bodies last ditch effort to save itself from alcohol poisoning. I got to where I could put down an entire 5th of hard liquor without passing out or vomiting. Now that I dropped the mini-thins, I can only drink half as much, and have been sick twice in the last 3 months.
Quitting -- I decided to quit after they changed the law in my state on July 1, 2005. I can still get it, but it is not exactly OTC anymore, you have to sign a log and the states tracks you. The first two weeks cold turkey were downright brutal. I could hardly get out of bed and go to work. It was like having the flu. Then there were nightmares. For years my brain had not been able to sleep deep enough for me to dream, and when it got the chance, it went nuts. All in all it took about a month for me to feel normal.
I know this was lengthy, but I felt it was needed. Most of what has been posted seems to stem from occasional recreational use... To put it in words a younger person might understand, this explains how bad I got owned by this drug.
Thx for reading.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


BizTrip was a design challenge I did to create a prototype for an app that helps business travelers manage their trips. The entire product design from start to finish was completed in 3 days.
Product Design | UX | UI
Business travelers need better a better way to organize all aspects of their travel from their itinerary, to contacts and communication in the area of travel.
The target users of BizTrip are those who travel frequently for work in sales/ consulting oriented roles. BizTrip focuses on travel trends of young, millennial business travelers.
Due to the limited time frame for this design, I relied on inspiration from many applications whos features and designs helped make BizTrip.


Regarding the little information on this new compound, I decided to search the internet for suppliers of Mephedrone and to undertake an experiment in the hope that my experience will help others to decide whether or not to further undertake experiments with this compound themselves. I quickly found two suppliers, and bought a gram sample from each so as to compare the substance, and report on any difference between the two - without performing a lab test I would say that the substance is the same, in terms of texture, colour, smell and form - the only main difference was in the price and the packaging. Before I carry on any further I will explain a little about my set and setting, along with my previous experiences with psychoactives.
I'm currently 19 years old and in good mental and physical health. I've had previous experiences with the following substances:
Cannabis (daily smoker), Psilocybin mushrooms, LSD, MDxx, amphetamines, cocaine, ketamine, diazepam, akyl nitrate, solvents, opiates (poppy pod tea, codeine, dihydrocodeine, opium), BZP, MCPP, DXM, Diphenhydramine, Khat (Catha edulis), Kava (Piper methysticum), Kratom (Mitragyna speciosa), Yopo snuff (N. N-dimethyltryptamine, N-monomethyltryphmine, 5-methoxydimethyltryptamine, Bufotenine), wild opium (Lactuca virosa), will dagga (Leontus sp.), Salvia divinorum, Peyote - and some of the more 'exotic' RC's like 2C-B, PMA, TMA, 4-MTA.
I have had at least one experience with each of the substances above, with some repeated more often than others -- but just because I've had experiments with a broad spectrum of psychoactives, I wouldn't say I'm totally experienced with all mentioned, although this gives me the opportunity to make fairly accurate comparisons.
Today, on the day of the experiment, my set and setting are perfect. I'm sitting comfortably at home with no commitments all day. I consumed 4 units of alcohol yesterday and smoked a small amount of cannabis in the evening but I doubt this will affect my experiment as I'm well rested, fed and hydrated with a positive mindset. Although I feel a little apprehensive about taking a compound that is new to me, it's nothing that a little meditation and good music wont cure. I'm currently not taking any prescription medications, but take 1-2 tablets of St Johns Wort a day, and sometimes use valerian in the evenings to aid sleep.
Substance details
Common/street name: Mephedrone
Chemical name: 2-Methylamino-1-p-tolylpropan-1-one HCL/4-Methylmethcathinone
Physical state: Whitish/Light yellow powder, somewhat 'bally' in composition, although breaks down to a fine powder
Odour: Strong chemical smell, was apparent even through the packaging. Reminiscent of stale urine, with an undertone of liquorice. Not pleasant.
Chemical stability: Stable at room temperatures, in closed containers under normal storage conditions.
Molecular formula: C11H16NOC1
Molecular weight: 213.71
Dosage: Has been reported similar to MDMA, from around 50-200mg, but as it's a Research Chemical, there is no known safe dose. Start small.
Dangers: Toxicity in unknown. Powder is said to irritate eyes and lungs if introduced to those areas and ingestion may cause irritation to digestive tract. Dangers of chronic use is not yet known.
Duration: somewhat shorter than MDMA.
So the experiment begins:
15.30 -- Sitting alone watching TV. 50mg is carefully measured, crushed to a fine powder, and half (25mg) insufflated. Slight stinging in nose and smell is unpleasant, although not unbearable.
15.35 -- A slight uplift in mood, perhaps the beginning of a feeling of being 'wired', rate of heart elevated. Strong smelling and tasting drip down the back of throat.
15.40 -- Another 25mg is snorted. Stinging is more pronounced this time, and with definite feelings of coming up, almost like MDMA but with less push, with soft euphoria. Watching TV is entertaining but not as nice as staring out the window.
15.48 -- Elevation of heartbeat is more pronounced now, and hands are slightly shaky, not unpleasantly so though. Soft euphoria seems to be growing somewhat along with a feeling of content. Feel totally alert and would be able to converse normally with parents at this stage if needs be.
15.54 -- Drip tastes absolutely horrible! I think that next time I try this compound, I'll try an oral dose to bypass this nasty taste.
15.57 --A friend phones me up and we have a half hour conversation, talking flowed easily and although I feel slightly intoxicated it doesn't show in my voice or conversation.
16.30 -- A 100mg is measured carefully, crushed and insufflated. Immediate effects are apparent, a clear headiness and slight 'speedy' feeling. Nose hurts and smell is not pleasant.
16.35 -- A rushing feeling and clear euphoria is felt, but not as pushed as MDMA, feels much softer and relaxed. Heartbeat is up and hands and feet become slightly clammy. Perhaps a slight pupil dilation but unsure, my extremities tingle slightly. This is a good amount to snort I think.
I put on some music -- Nagual Sound Experiment, the album 'Invisible Movements', it's a merge of dub/2-step/grime with influences of drum and bass and a hint of psy. Perfect for this experience I think.
16.42 -- Music appreciation is amazing, the sounds seem to resonate with a clarity and meaningfulness that I get with MDMA. I feel great even due to the fact that hands are slightly clammy and shaky and I'm sweating slightly (although I don't particularly feel my body temperature has risen that much). Cant stop moving to the music and have lost all interest in the TV now, my brain is just going too fast. I feel like snorting more, but the stinging hasn't stopped yet and feel I should wait longer. I've read peoples reports about how when snorting this substance, it becomes rather moorish -- I can see what they mean. The drip still tastes awful.
17.11 -- Pupil dilation and slight jaw movement when talking, not as pronounced as jaw tension experienced with MDMA but almost like when on good cocaine. Just got back from helping my mum and dad load up the car with stuff for a charity event -- talking and acting normal wasn't even an issue and didn't have to hide my intoxication, although it did feel a bit uncomfortable all the same. Decide to measure another 100mg for insufflation.
17.15 -- It feels as though I was peaking whilst helping out my parents. I believe when snorted, it has a quick onset but with effects wearing off just as quick.
17.17 -- Another 100mg in snorted, with immediate effects. This feels good, I'm sped up and clear headed with the same soft euphoria and a small amount of rushing. Perhaps I wasn't peaking whilst loading the car and the latest line has just topped me up.
Music still sounds great although there's little visual effects apart from maybe a slight fuzziness when reading. The drip is even worse this time, having to constantly sip water to help. This feels just like coming up on MDMA, but with less jitteryness (I find that when consuming the first large dose of MDMA of the night, I experience a nervousness at around the 15-45min mark, and this is not apparent with Mephedrone).
17.23 -- The euphoria is growing, along with the jaw tension. Nose stings less. Can't stop bobbing to the now immensely pleasurable music.
17.24 -- Dad knocks on my door and lets me know he's popping out. I find it hard to conceal my intoxication and feel nervous, wishing him to leave quickly. I'm sure he's noticed my large pupils and unconcealed movement of my jaw but don't think he'll mention anything at a later date. D'oh!
17.29 -- I can't believe this stuff is legal. Can't hide my doped smile.
17.40 -- Listening to music and closing my eyes is very satisfying, and even with no CEV it still feels great. I just ground my teeth and they squeaked, not nice! My vision seems to be fuzzing a little more and have a slight sensitivity to light. Feels like I'm peaking on my last line, or the effects seem to be levelling out a little. On this note, I decide to consume a little ketamine, to see what dimension it adds to this kind of compound.
17.48 -- Upon standing, to fetch my ketamine, I had a sudden head rush and fully realised how stimulated I feel, yet with a totally relaxed feeling at the same time. I know you may be thinking it seems impossible to feel both stimulated and relaxed at the same time but this is how I'm feeling.
17.52 -- A small amount (around 30mg) of Ketamine HCL is snorted in the same nostril as the Mephedrone. For me, this amount is on the small side as I use ketamine frequently and have a tolerance, but decided to act with caution, as one should, when mixing RCs with other drugs. The interactions of RCs with other recreational drugs aren't well documented, therefore I recommend if you decide to mix, proceed with caution. Start small.
17.58 -- The effects of the ketamine, even at such a small dose, has started to have an effect. This combo feels good. It brings the emotional depth to Mephedrone, which I found was missing. Music still sounds amazing, but now with the added K dimension, when laying back and closing eyes there seems to be added visual effects, slight patterning and organic forms - nothing geometric though. I think the bump of K increased the movement of my jaw little.
18.06 -- Intense relaxation, think the effects of the Mephedrone is waning a little, although still feel nice.
18.17 -- Effects defiantly diminishing now, the comedown doesn't feel bad though, just a little 'spacey'. Perhaps the downing effects of the small amount of ketamine had an adverse effect to the stimulating properties of the compound.
18.31 -- Friends phoned, and although I felt a little 'wired' whilst talking, conversation was fine and managed to chat for a while. The comedown is less harsh than MDMA but much quicker.  Music still sounds great.
19.15 -- Total baseline, with residual fuzzy effects in my vision. What's suddenly become apparent to me, is the anorexic effects of this drug, because as soon as its effects wore off I became immediately hungry (I have not eaten since my late breakfast). Becoming hungry straight after the effects of MDMA would not happen with me. Even in the comedown I still felt clearheaded and alert, unlike its cousin MDMA.
In conclusion:
Its effects in me were similar to MDMA, clearer with less push, not as empathetic and shorter in duration, stimulating but at the same time with a sense of relaxation. I think this is an interesting new friend, but one which should obviously be treated with respect due to not a lot of information being know about its toxicity, OD dosages and damage of long term usage. Its pleasant effects and short duration when snorted make it a candidate high up on the scale for regular abuse -- something, which due to its short history of use in human beings, can make it extremely dangerous. Always remember when trying a new drug, that there can no way be what is called 'a safe dose'. Individuals do respond differently to psychoactives so caution should be taken, upping the smallest dose gradually. Do your research, tread carefully and have fun.
Experience Reports are the writings and opinions of the individual authors who submit them.
Some of the activities described are dangerous and/or illegal and none are recommended by Erowid.


Go Plugins (deprecated)
Deprecation warning
This style of plugin is slated for deprecation. See the Kustomize Plugin Graduation KEP for information on the future of Kustomize plugins.Authoring Go plugins
What is a Go plugin?
 It is built with special flags and cannot run on its own. It must be loaded into a running Go program.
A normal program written in Go might be usable as exec plugin, but is not a Go plugin.
Go plugins allow kustomize extensions that run without the cost marshalling/unmarshalling all resource data to/from a subprocess for each plugin run. The Go plugin API assures a certain level of consistency to avoid confusing downstream transformers.

Be sure to read Go plugin caveats.
A .go
file can be a Go plugin if it declares
‘main’ as it’s package, and exports a symbol to
which useful functions are attached.
It can further be used as a kustomize plugin if
the symbol is named ‘KustomizePlugin’ and the
attached functions implement the Configurable
,
Generator
and Transformer
interfaces.
A Go plugin for kustomize looks like this:
package main import ( "sigs.k8s.io/kustomize/api/resmap" ... ) type plugin struct {...} var KustomizePlugin plugin func (p *plugin) Config( h *resmap.PluginHelpers, c []byte) error {...} func (p *plugin) Generate() (resmap.ResMap, error) {...} func (p *plugin) Transform(m resmap.ResMap) error {...}
Use of the identifiers plugin
, KustomizePlugin
and implementation of the method signature
Config
is required.
Implementing the Generator
or Transformer
method allows (respectively) the plugin’s config
file to be added to the generators
or
transformers
field in the kustomization file.
Do one or the other or both as desired.
Placement
Each plugin gets its own dedicated directory named
$XDG_CONFIG_HOME/kustomize/plugin
/${apiVersion}/LOWERCASE(${kind})
The default value of XDG_CONFIG_HOME
is
$HOME/.config
.
The one-plugin-per-directory requirement eases creation of a plugin bundle (source, tests, plugin data files, etc.) for sharing.
In the case of a Go plugin, it also
allows one to provide a go.mod
file for the
single plugin, easing resolution of package
version dependency skew.
When loading, kustomize will look for a
file called ${kind}.so
attempt to load it as a Go plugin.
$XDG_CONFIG_HOME/kustomize/plugin
/${apiVersion}/LOWERCASE(${kind})/${kind}.so
Failure to find a plugin to load fails the overall
kustomize build
.
Examples
- service generator - generate a service from a name and port argument.
- string prefixer - uses the value in
metadata/name
as the prefix. This particular example exists to show how a plugin can transform the behavior of a plugin. See theTestTransformedTransformers
test in thetarget
package. - date prefixer - prefix the current date to resource names, a simple example used to modify the string prefixer plugin just mentioned.
- secret generator - generate secrets from a toy database.
- sops encoded secrets - a more complex secret generator that converts SOPS files into Kubernetes Secrets
- SOPSGenerator - another generator that decrypts SOPS files into Secrets
- All the builtin plugins. User authored plugins are on the same footing as builtin operations.
 The Generate
method will run along
with all the other generators before the
Transform
method runs.
Here’s a build command that sensibly assumes the
plugin source code sits in the directory where
kustomize expects to find .so
files:
d=$XDG_CONFIG_HOME/kustomize/plugin\
/${apiVersion}/LOWERCASE(${kind})
go build -buildmode plugin \
-o $d/${kind}.so $d/${kind}.go
Go plugin caveats
The skew problem
Go plugin compilation creates an ELF formatted
.so
file, which by definition has no information
about the provenance of the object code.
Skew between the compilation conditions (versions
of package dependencies, GOOS
, GOARCH
) of the
main program ELF and the plugin ELF will cause
plugin load failure, with non-helpful error
messages.
Exec plugins also lack provenance, but won’t fail due to compilation skew.
In either case, the only sensible way to share a
plugin is as some kind of bundle (a git repo
URL, a git archive file, a tar file, etc.)
containing source code, tests and associated data,
unpackable under
$XDG_CONFIG_HOME/kustomize/plugin
.
In the case of a Go plugin, an end user accepting a shared plugin must compile both kustomize and the plugin.
This means a one-time run of
# Or whatever is appropriate at time of reading
GOPATH=${whatever} GO111MODULE=on go get sigs.k8s.io/kustomize/api
and then a normal development cycle using
go build -buildmode plugin \
-o ${wherever}/${kind}.so ${wherever}/${kind}.go
with paths and the release version tag (e.g. v3.0.0
)
adjusted as needed.
For comparison, consider what one must do to write a tensorflow plugin.
Go plugin advantages
Safety
The Go plugin developer sees the same API offered to native kustomize operations, assuring certain semantics, invariants, checks, etc. An exec plugin sub-process dealing with this via stdin/stdout will have an easier time screwing things up for downstream transformers and consumers.
Minor point: if the plugin reads files via
the kustomize-provided file Loader
interface, it
will be constrained by kustomize file loading
restrictions.
Debugging
A Go plugin developer can debug the plugin in situ, setting breakpoints inside the plugin and elsewhere while running a plugin in feature tests.
To get the best of both worlds (shareability and safety),
a developer can write an .go
program that functions
as an exec plugin, but can be processed by go generate
to emit a Go plugin (or vice versa).
Guided example
This is a (no reading allowed!) 60 second copy/paste guided example.
Full plugin docs here. Be sure to read the Go plugin caveats.
This demo uses a Go plugin, SopsEncodedSecrets
,
that lives in the sopsencodedsecrets repository.

This is a guide to try it without damaging your current setup.
Prerequisites:
- linux
- git
- curl
- Go 1.13
For encryption:
- gpg
–OR–
- Google cloud (gcloud) install
- a Google account with KMS permission
Make a place to work
# Keeping these separate to avoid cluttering the DEMO dir.
DEMO=$(mktemp -d)
tmpGoPath=$(mktemp -d)
Install kustomize
Need v3.0.0 for what follows, and you must compile it (not download the binary from the release page):
GOPATH=$tmpGoPath go install sigs.k8s.io/kustomize/kustomize
Make a home for plugins
A kustomize plugin is fully determined by its configuration file and source code.
Kustomize plugin configuration files are formatted
as kubernetes resource objects, meaning
apiVersion
, kind
and metadata
are required
fields in these config files.
The kustomize program reads the config file
(because the config file name appears in the
generators
or transformers
field in the
kustomization file), then locates the Go plugin’s
object code at the following location:
$XDG_CONFIG_HOME/kustomize/plugin/$apiVersion/$lKind/$kind.so
where lKind
holds the lowercased kind. The
plugin is then loaded and fed its config, and the
plugin’s output becomes part of the overall
kustomize build
process.
The same plugin might be used multiple times in one kustomize build, but with different config files. Also, kustomize might customize config data before sending it to the plugin, for whatever reason. For these reasons, kustomize owns the mapping between plugins and config data; it’s not left to plugins to find their own config.
This demo will house the plugin it uses at the ephemeral directory
PLUGIN_ROOT=$DEMO/kustomize/plugin
and ephemerally set XDG_CONFIG_HOME
on a command
line below.
Get the plugin
At this stage in the development of kustomize
plugins, plugin code doesn’t know or care what
apiVersion
or kind
appears in the config file
sent to it.
The plugin could check these fields, but it’s the remaining fields that provide actual configuration data, and at this point the successful parsing of these other fields are the only thing that matters to a plugin.
This demo uses a plugin called SopsEncodedSecrets, and it lives in the SopsEncodedSecrets repository.
Somewhat arbitrarily, we’ll choose to install this plugin with
apiVersion=mygenerators
kind=SopsEncodedSecrets
Define the plugin’s home dir
By convention, the ultimate home of the plugin code and supplemental data, tests, documentation, etc. is the lowercase form of its kind.
lKind=$(echo $kind | awk '{print tolower($0)}')
Clone the SopsEncodedSecrets plugin repo
In this case, the repo name matches the lowercase kind already, so we just clone the repo and get the proper directory name automatically:
mkdir -p $PLUGIN_ROOT/${apiVersion}
cd $PLUGIN_ROOT/${apiVersion}
git clone git@github.com:monopole/sopsencodedsecrets.git
Remember this directory:
MY_PLUGIN_DIR=$PLUGIN_ROOT/${apiVersion}/${lKind}
Try the plugin’s own test
Plugins may come with their own tests. This one does, and it hopefully passes:
cd $MY_PLUGIN_DIR
go test SopsEncodedSecrets_test.go
Build the object code for use by kustomize:
cd $MY_PLUGIN_DIR
GOPATH=$tmpGoPath go build -buildmode plugin -o ${kind}.so ${kind}.go
This step may succeed, but kustomize might ultimately fail to load the plugin because of dependency skew.
On load failure
-
be sure to build the plugin with the same version of Go (go1.13) on the same
$GOOS
(linux) and$GOARCH
(amd64) used to build the kustomize being used in this demo. -
change the plugin’s dependencies in its
go.mod
to match the versions used by kustomize (check kustomize’sgo.mod
used in its tagged commit).

Kustomize has adopted a Go plugin architecture as to ease accept new generators and transformers (just write a plugin), and to be sure that native operations (also constructed and tested as plugins) are compartmentalized, orderable and reusable instead of bizarrely woven throughout the code as a individual special cases.
Create a kustomization
Make a kustomization directory to hold all your config:
MYAPP=$DEMO/myapp
mkdir -p $MYAPP
Make a config file for the SopsEncodedSecrets plugin.
Its apiVersion
and kind
allow the plugin to be
found:
cat <<EOF >$MYAPP/secGenerator.yaml
apiVersion: ${apiVersion}
kind: ${kind}
metadata:
name: mySecretGenerator
name: forbiddenValues
namespace: production
file: myEncryptedData.yaml
keys:
- ROCKET
- CAR
EOF
This plugin expects to find more data in
myEncryptedData.yaml
; we’ll get to that shortly.
Make a kustomization file referencing the plugin config:
cat <<EOF >$MYAPP/kustomization.yaml
commonLabels:
app: hello
generators:
- secGenerator.yaml
EOF
Generate encrypted data
First you need to ensure you have an encryption tool installed.
We’re going to use sops to encode a file. Choose either GPG or Google Cloud KMS as the secret provider to continue.
GPG
Try this:
gpg --list-keys
If it returns a list, presumably you’ve already created keys. If not, try import test keys from sops for dev.
curl https://raw.githubusercontent.com/mozilla/sops/master/pgp/sops_functional_tests_key.asc | gpg --import
SOPS_PGP_FP="1022470DE3F0BC54BC6AB62DE05550BC07FB1A0A"
Google Cloude KMS
Try this:
gcloud kms keys list --location global --keyring sops
If it succeeds, presumably you’ve already created keys and placed them in a keyring called sops. If not, do this:
gcloud kms keyrings create sops --location global
gcloud kms keys create sops-key --location global \
--keyring sops --purpose encryption
Extract your keyLocation for use below:
keyLocation=$(\
gcloud kms keys list --location global --keyring sops |\
grep GOOGLE | cut -d " " -f1)
echo $keyLocation
Install sops
GOPATH=$tmpGoPath go install go.mozilla.org/sops/cmd/sops
Create data encrypted with your private key
Create raw data to encrypt:
cat <<EOF >$MYAPP/myClearData.yaml
VEGETABLE: carrot
ROCKET: saturn-v
FRUIT: apple
CAR: dymaxion
EOF
Encrypt the data into file the plugin wants to read:
With PGP
$tmpGoPath/bin/sops --encrypt \
--pgp $SOPS_PGP_FP \
$MYAPP/myClearData.yaml >$MYAPP/myEncryptedData.yaml
Or GCP KMS
$tmpGoPath/bin/sops --encrypt \
--gcp-kms $keyLocation \
$MYAPP/myClearData.yaml >$MYAPP/myEncryptedData.yaml
Review the files
tree $DEMO
This should look something like:
/tmp/tmp.0kIE9VclPt ├── kustomize │ └── plugin │ └── mygenerators │ └── sopsencodedsecrets │ ├── go.mod │ ├── go.sum │ ├── LICENSE │ ├── README.md │ ├── SopsEncodedSecrets.go │ ├── SopsEncodedSecrets.so │ └── SopsEncodedSecrets_test.go └── myapp ├── kustomization.yaml ├── myClearData.yaml ├── myEncryptedData.yaml └── secGenerator.yaml
Build your app
XDG_CONFIG_HOME=$DEMO $tmpGoPath/bin/kustomize build --enable_alpha_plugins $MYAPP
This should emit a kubernetes secret, with
encrypted data for the names ROCKET
and CAR
.
Above, if you had set
PLUGIN_ROOT=$HOME/.config/kustomize/plugin
there would be no need to use XDG_CONFIG_HOME
in the
kustomize command above.
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.


{% if page.url == "/partners" %}
|
AE helps companies get fit for their digital future. Co-creation is the core of our approach. We'll work together with you and your customers to help you get you where you need to be on a business, organisational and technological level. With over 20 years of experience in business architecture, software engineering and change management we are a trusted partner in reshaping business critical solutions and services for over 150 customers. And counting. |
|
|
Axxes is a full-service IT consultancy. Our specialist IT consultants focus on delivering flexible and qualitative services in software development, quality assurance, infrastructure, devops, cloud solutions, architecture, project management services and more. Every day, our team of 400 experienced IT professionals make all the difference for our clients. We bring the right expertise to your project. |
|
|
Arxus is a Managed Services Provider made up of 50+ cloud enthusiasts with unique cloud expertise and sector specific knowledge. We provide tailored Azure, Office 365 and Microsoft 365 solutions. We help customers face the complex challenge of modernising their infrastructure and create a truly future-proof organization. Thanks to our managed public and private cloud solutions they can explore new business opportunities while we make sure their IT environment is up-to-speed and ready to deliver. Our offering is focused around two solution groups: “productive workplace” and “scale with cloud innovation”. Productive Workplace is built on Microsoft 365 and includes a wide-variety of tools to bring everyone in an organisation together to achieve more. With Scale with Cloud Innovation we offer Microsoft Azure’s public cloud solutions, private cloud setups and a combination of both and the existing on-premise. Our biggest added value is in managed services. We offer these on our private cloud, and now we do on Azure as well. We completely rebuilt these from the ground up, to fit the opportunities the Azure cloud offers in terms of management, maintenance, monitoring, security and automation. The result is Azure managed services: a futureproof managed service offering. We position Arxus as a strategic partner for businesses, with a mission to improve productivity, efficiency and innovation. By managing applications and empowering employees with a modern, cloud-based workplace, we relieve companies of their IT burdens so they can focus on growing their core business. |
|
|
We are a global company that delivers advanced ICT solutions and services, guiding our customers through their business and digital transformations. We provide them with the tools to achieve their mission-critical priorities. We develop, innovate and implement international business consulting, effective strategies and change management solutions. In addition to our partnerships with SAP, Microsoft, Salesforce and OpenText, we rely on a select group of technology partners to support our customers in creating a truly omnichannel customer experience. Above all, we want to do the right thing. We deliver enterprise expertise that enables our customers’ businesses to reach their full potential, while creating a positive impact in a challenging world. We take responsibility for our relationship with the social and ecological environment. We make it happen. You can rely on us. we commit. we deliver. |
|
|
At Devoteam, we deliver innovative technology consulting for business. As a pure player of Digital Transformation for leading organisations across EMEA, our 7,200+ professionals are dedicated to ensuring our clients win their digital battles. With a unique transformation DNA, we connect business and technology. Present in 18 countries in Europe and the Middle East, and drawing on more than 20 years of experience, we shape Technology for People, so it creates value for our clients, for our partners and for our employees. Devoteam achieved revenues of €652.4 million in 2018. At Devoteam, we are Digital Transformakers. |
|
|
Microsoft enables digital transformation for the era of an intelligent cloud and an intelligent edge. Its mission is to empower every person and every organization on the planet to achieve more. |
|
|
Ordina is the largest, independent IT service provider in the Benelux. Our goal is to give customers in the financial services, public, industry and healthcare sectors a digital edge. We do this by devising, building and managing technological solutions. Ordina helps its customers stay ahead of the challenges and changes in their business. Ordina has been active as an IT service provider in the Benelux for over forty years. We follow the latest technological developments very closely and make them relevant by creating innovative business and IT solutions that add value for our customers. |
|
|
Your organization wants to remain competitive and be able to adapt quickly to change? A flexible, scalable and secure IT infrastructure is crucial for this. Through partnerships with cloud market leaders, we offer modern hybrid cloud solutions. Because helping businesses with their cloud environment, from strategy to implementation and management. That is also Proximus. |
|
|
We thrive on challenge. The harder the problem, the happier we are. We provide you peace of mind. The knowledge that there’s someone with drive and expertise solving your issue. Give us your trust, and we will give you our everything. Due to our focus on just Azure, we’re experienced with all aspects of the Azure platform – from adoption to efficient use, security, DevOps, and the building of cloud-native applications and solutions, ranging from mobile to data platforms and IoT solutions. |
| 45 Degrees helps enterprise customers on their journey to the Cloud. Cloud computing offers great opportunities. It does however require significant changes for IT departments on both organisational as well as technical level. We offer 4 types of services to our customers: Enterprise Architecture services in a Cloud world, Cloud Architecture services, Cloud Engineering services and Cloud Program management services. | |
|
AIMS is an Automated Monitoring Solution powered by AI. Build confidence in your IT operations with Automated Anomaly Detection and Service Dependency Discovery. |
|
|
Codit is an innovative IT company which provides next-level consultancy, technology, and managed services to leading brands worldwide. We successfully help companies reduce operational costs, improve efficiency and enhance communication by integrating people, applications, and things, using a wide range of Microsoft technologies. |
|
| At DexMach, we simplify and automate your it environment in the cloud, so that you can create awesome products and services. | |
| At NOEST, Let's craft IT together! | |
| At Integration.team, with maximum efficiency and visibility in mind, Integration.team connects your organisation's tools and devices across departments on-premise and in the cloud. |


Find Your Inner Light
Path of Light Yog Studio provides all levels of yoga practice in a tranquil, peaceful environment. Whether you arenew to yoga or an experienced practitioner, our dedicated instructors can develop a practice to meet your needs. Let your inner light shine at the Path of Light Yoga Studio.
- Hatha, Vinyasa, and Restorative Yoga classes
- Drop-ins welcome
- Mats, blocks and blankets provided
- Relax in our Serenity Lounge before or after your class
612 Serenity Way
El Dorado, AZ 86336
888-555-5555
El Dorado, AZ 86336
888-555-5555


The Legend of 1900 (1999)
A Film Essay by Mark O'Hara
Visit Online Film Critics Society at http://www.ofcs.org
"The Legend of 1900" begins in a music shop in mid-century, viols and and horns hanging down amid the glorious clutter. Suddenly we are in the boiler room of a gargantuan steamship, men working their hardest to fill the maws of the furnaces with coal.
What helps Giuseppe Tornatore's "The Legend of 1900" work its magic are these striking locations, places we want to be. It all works together to form a wonderful story, we are made to understand - a story no less immense than life itself.
What Tornatore did for the cinema in "Cinema Paradiso," he attempts in "1900" to do for music. To make his job more awesome he casts it in the mold of a bold time, naming his very protagonist for the new century. This boy, you see, is the son of immigrants who abandoned him in the ship that carried them to the New World. Found by an African-American engineer (played by Bill Nunn), the orphan grows up with the crew as his family, hiding in the hold to avoid discovery by any social agencies. Danny Boodman T. D. Lemon 1900, the first two monikers after his only father, soon begins to explore above-decks. There's a quite amusing scene in which he's caught playing a grand piano in the ship's ballroom, in the dead of night. Although his talent is prodigious, he's told what he's doing is against regulations. Here the kid tells what he thinks of regulations, the same obscene response he throws at anything or anyone he doesn't like.
It's right about now that we return to the music shop, as Max, played by Pruitt Taylor Vince, is the man relating 1900's story to the owner. Max was a close friend of 1900's, a part of the ship's band, though he is now apparently giving up his trumpet - in fact selling it to the old Brit who runs the shop. Having drawn out part of the story with an old record - a master matrix of 1900 playing one of his spur-of-the-moment masterpieces - the owner is enrapt, and the flashbacks continue.
When Max first joins the band, 1900 is 27 years old, and has never set foot off the ship. He's like the symbol of the new baby each New Year's - except he resembles the new century - tough and sharp, yet somehow intimidated by his own potential. 1900 becomes a figure larger than life, a musician with an easy and formidable talent: the others in the band occasionally ask him not to show them up. The only problem is his naivete. Since his abandonment, he has never touched dry land, and has no real idea of how to go about the business of living on it. When he glimpses a girl who is watching him make the recording aboard the ship, 1900 is smitten. Will there be a romance? Will Max even talk his sheltered friend into taking the frightening descent down the gangplank?
The answer to these questions does not come without difficulty. In fact the ending, as much as it functions as an answer, is too slow and overwrought with personal philosophy. Tornatore should have cut a pregnant pause or two. But oh, what comes before it - this is the stuff of a great movie.
We see inventive camera shots, some playful ones showing 1900's hands on the keyboard in multiples: the man plays so fast that we hallucinate extra sets of hands. Reflections of hands and eyes abound, and one shot shows the phantasmagoric world of the rich as they dance behind the windows that separate them from the souls in second class and steerage. Tornatore shows he is a visionary director who knows how to exploit fully the medium in which he works.
The language of early-century steamships is something we are familiar with, thanks to "Titanic." In turns claustrophobic and expansive, the "Virginian" is a wonderful microcosm, a jumping off point for hundreds of thousands of immigrants. The vessel serves as a character herself, a place where both death and life abound.
Of course music plays another important role. Ennio Morricone wrote the score, including some difficult hybrids of tunes that show off traits of ragtime, jazz and atonal modern - best summed up by one character's comment (though it's about Max's spirited trumpet), "When you can't tell what it is, it's JAZZ!" What's most remarkable is how the script ties in music and narrative. The motif of storytelling operates on so many levels in this film that it's impossible not to pick up the thread of one without following the trail of the other. When Max asks his friend, "What the hell do you think about when you're playing?" we begin to understand that 1900 does out-of-ship composition: he dreams of being in distant cities and wallowing in the beauty of natural land masses. Music, for him, is a way of telling the most personal tale possible, a free-associative fugue. We feel pity for his plight, but 1900's self-pity never lasts long. Soon he's the same superman of the piano. In a gutsy tour-de-force, 1900 reluctantly engages in a duel with the so-called inventor of jazz, Jelly Roll Morton (Clarence Williams III). The way Morton is portrayed, even his mother would not like him. A combination of a twentieth-century personality cult and symbol of the brutality of the world outside the metal womb of the ship, Morton puts a permanent fright into 1900.
As the title character, Tim Roth has perfect pitch. Blending innocence and sureness, social awkwardness and friendly support, Roth is able to convince us for extended moments that this fable is real. One bit of his behavior goes over-the-top when he falls hard for the girl - we need more hints of his intimate pathology to believe what happens. Otherwise Roth pulls off a performance that makes us forget him in the roles of so many smirky tough guys.
I loved Pruitt Taylor Vince as Rub Squeers in the Paul Newman vehicle "Nobody's Fool." Here he gets to show off a more realistic talent, a 1920's jazz trumpeter who wheedles his way into the band of the "Virginian." Aside from breathing, Vince fakes his instrument playing well, down to the contortions and staggers of a hip horn blower. Call him a long shot for a nomination for best actor in a supporting role. The most touching bit he plays is the search for his long-lost best friend. Some time in the 30's, Max left the ship and got back his land legs. It appears that the "Virginian" was used as a hospital ship during the Second World War, during which 1900 stayed aboard and played on. But now the ship is scheduled for demolition, and Max is convinced that 1900 has reverted to being a hermit within the hold. Max's emotions during his search are telling and fully realized.
Giuseppe Tornatore engages in what might be termed slow-onset magical realism. It takes a while for his artistic strokes to gather momentum, to coalesce into recognizable themes and symbols. But when the jokes and motifs kick in, the viewer indeed experiences magic. These moments make you want to whisper to fellow viewers to confirm the astounding power of subtlety. But like the best phrases of music, it's best to keep these moments private, to store them among the few handfuls of cinematic essence that you carry with you everywhere, to take out once in a while and cherish like a toy from childhood.
The review above was posted to the
rec.arts.movies.reviews newsgroup (de.rec.film.kritiken for German reviews).
The Internet Movie Database accepts no responsibility for the contents of the
review and has no editorial control. Unless stated otherwise, the copyright
belongs to the author.
Please direct comments/criticisms of the review to relevant newsgroups.
Broken URLs inthe reviews are the responsibility of the author.
The formatting of the review is likely to differ from the original due
to ASCII to HTML conversion.
Related links: index of all rec.arts.movies.reviews reviews


| Lease Starts: {{item.availability.starts | date:'mediumDate'}} | Lease Ends: {{item.availability.ends | date:'mediumDate'}} | Reserve By: {{item.availability.closes | date:'mediumDate'}} | |
| Size: {{item.sqfoot}} Sq.Ft. | Parking: {{item.parking}} | Pet-friendly: {{item.address.pets}} | People: {{item.capacity}} |


The bitstream is captured (or recaptured) by looking for the beginning of a page, specifically the capture pattern. Once the capture pattern is found, the decoder verifies page sync and integrity by computing and comparing the checksum. At that point, the decoder can extract the packets themselves.
The raw packet is logically divided into [n] 255 byte segments and a last fractional segment of < 255 bytes. A packet size may well consist only of the trailing fractional segment, and a fractional segment may be zero length. These values, called "lacing values" are then saved and placed into the header segment table.
An example should make the basic concept clear:
raw packet: ___________________________________________ |______________packet data__________________| 753 bytes lacing values for page header segment table: 255,255,243We simply add the lacing values for the total size; the last lacing value for a packet is always the value that is less than 255. Note that this encoding both avoids imposing a maximum packet size as well as imposing minimum overhead on small packets (as opposed to, eg, simply using two bytes at the head of every packet and having a max packet size of 32k. Small packets (<255, the typical case) are penalized with twice the segmentation overhead). Using the lacing values as suggested, small packets see the minimum possible byte-aligned overheade (1 byte) and large packets, over 512 bytes or so, see a fairly constant ~.5% overhead on encoding space.
Note that a lacing value of 255 implies that a second lacing value follows in the packet, and a value of < 255 marks the end of the packet after that many additional bytes. A packet of 255 bytes (or a multiple of 255 bytes) is terminated by a lacing value of 0:
raw packet: _______________________________ |________packet data____________| 255 bytes lacing values: 255, 0Note also that a 'nil' (zero length) packet is not an error; it consists of nothing more than a lacing value of zero in the header.
After segmenting a packet, the encoder may decide not to place all the resulting segments into the current page; to do so, the encoder places the lacing values of the segments it wishes to belong to the current page into the current segment table, then finishes the page. The next page is begun with the first value in the segment table belonging to the next packet segment, thus continuing the packet (data in the packet body must also correspond properly to the lacing values in the spanned pages. The segment data in the first packet corresponding to the lacing values of the first page belong in that page; packet segments listed in the segment table of the following page must begin the page body of the subsequent page).
The last mechanic to spanning a page boundary is to set the header flag in the new page to indicate that the first lacing value in the segment table continues rather than begins a packet; a header flag of 0x01 is set to indicate a continued packet. Although mandatory, it is not actually algorithmically necessary; one could inspect the preceding segment table to determine if the packet is new or continued. Adding the information to the packet_header flag allows a simpler design (with no overhead) that needs only inspect the current page header after frame capture. This also allows faster error recovery in the event that the packet originates in a corrupt preceding page, implying that the previous page's segment table cannot be trusted.
Note that a packet can span an arbitrary number of pages; the above spanning process is repeated for each spanned page boundary. Also a 'zero termination' on a packet size that is an even multiple of 255 must appear even if the lacing value appears in the next page as a zero-length continuation of the current packet. The header flag should be set to 0x01 to indicate that the packet spanned, even though the span is a nil case as far as data is concerned.
The encoding looks odd, but is properly optimized for speed and the expected case of the majority of packets being between 50 and 200 bytes (note that it is designed such that packets of wildly different sizes can be handled within the model; placing packet size restrictions on the encoder would have only slightly simplified design in page generation and increased overall encoder complexity).
The main point behind tracking individual packets (and packet segments) is to allow more flexible encoding tricks that requiring explicit knowledge of packet size. An example is simple bandwidth limiting, implemented by simply truncating packets in the nominal case if the packet is arranged so that the least sensitive portion of the data comes last.
byte value 0 0x4f 'O' 1 0x67 'g' 2 0x67 'g' 3 0x53 'S'
byte value 4 0x00
byte value 5 bitflags: 0x01: unset = fresh packet set = continued packet 0x02: unset = not first page of logical bitstream set = first page of logical bitstream (bos) 0x04: unset = not last page of logical bitstream set = last page of logical bitstream (eos)
A special value of '-1' (in two's complement) indicates that no packets finish on this page.
byte value 6 0xXX LSB 7 0xXX 8 0xXX 9 0xXX 10 0xXX 11 0xXX 12 0xXX 13 0xXX MSB
byte value 14 0xXX LSB 15 0xXX 16 0xXX 17 0xXX MSB
byte value 18 0xXX LSB 19 0xXX 20 0xXX 21 0xXX MSB
(A thorough discussion of CRC algorithms can be found in "A Painless Guide to CRC Error Detection Algorithms" by Ross Williams<EMAIL_ADDRESS>byte value 22 0xXX LSB 23 0xXX 24 0xXX 25 0xXX MSB
byte value 26 0x00-0xff (0-255)
byte value 27 0x00-0xff (0-255) [...] n 0x00-0xff (0-255, n=page_segments+26)Total page size is calculated directly from the known header size and lacing values in the segment table. Packet data segments follow immediately after the header.
Page headers typically impose a flat .25-.5% space overhead assuming nominal ~8k page sizes. The segmentation table needed for exact packet recovery in the streaming layer adds approximately .5-1% nominal assuming expected encoder behavior in the 44.1kHz, 128kbps stereo encodings.
Ogg Vorbis is the first Ogg audio CODEC. Anyone may freely use and distribute the Ogg and Vorbis specification, whether in a private, public or corporate capacity. However, the Xiph.org Foundation and the Ogg project (xiph.org) reserve the right to set the Ogg Vorbis specification and certify specification compliance.
Xiph.org's Vorbis software CODEC implementation is distributed under a BSD-like license. This does not restrict third parties from distributing independent implementations of Vorbis software under other licenses.
Ogg, Vorbis, Xiph.org Foundation and their logos are trademarks (tm) of the Xiph.org Foundation. These pages are copyright (C) 1994-2002 Xiph.org Foundation. All rights reserved.


People
All
Organisation
Sort by:
Henry Paulista
<EMAIL_ADDRESS>100%
SENIOR CREATIVE DIRECTOR
Evan Jefferson
<EMAIL_ADDRESS>82%
CREATIVE DIRECTOR
Alice McKenzie
<EMAIL_ADDRESS>66%
SENIOR COPYWRITER
Jackie Ro
--
33%
ART DIRECTOR
Mark Thomson
<EMAIL_ADDRESS>100%
SENIOR UI DESIGNER
Anastasia Groetze
<EMAIL_ADDRESS>48%
SENIOR UX DESIGNER
Loading...
SELECTED


Notebooks
Story: About 'seacows'
About 'seacows'
Title
About 'seacows'
Collection
Summary
The 'seacow' (hippopotamus) lives in the water and is called a 'water's thing'.
Comments
1) This story is found in Book I
Contributors
Date
1871
Categories
Keywords
seacow (hippopotamus) , seacow (is a 'water's thing') , seacow ('house' of) , seacow (doings of) , seacow (about the) , water ('water's thing') , water (about seacows) , water (animals who live in) , water (the seacow's house is in) , water (a thing of) , water (the seacow dwells in) , hippopotamus (about seacows) , hippopotamus (is a 'water's thing') , house (the seacow's is in water)
Story Pages
311-312


🎨 👷 Front-end engineer -> [ mobile, infrastructure, ux, language ]. Pay close attention to Python & Java & Rust ecosystem.


Welcome to the 39th issue of SteemSTEM Distilled, a bi-weekly curation effort by the members of the @steemstem team.
SteemSTEM is a community driven project which seeks to promote well-written and informative Science, Technology, Engineering and Mathematics posts on Steemit. The project involves curating STEM-related posts through upvoting, resteeming, offering constructive feedback, supporting scientific contests, and other related activities.
For more details, a recent update on the steemSTEM can be found here, and a not so recent one there. Moreover, if you ask yourself about what it means to be part of steemSTEM, please check here.
Our team scours the platform for original and quality content.
After working through thousands (literally!) of STEM-related posts and upvoting more than 150 that we deemed to be worthy, we proudly present you our top 6 handpicked choices for this Monday-Wednesday period.
##
Monday
_
### 4D PRINTING: THE DRAMATIC 3D
3D printing is one of the latest technology trends, but did you know it has already been advanced to 4D? Read this post by @sparklez to learn what’s new.
### Towards Artificial Minds 3: Recent Breakthroughs and some Philosophical Inquires
In this post @cpufronz discusses developments in the field of AI along some philosophical wanderings that certainly deserve a read from you.
_
##
Tuesday
_
### The Tales of Pirates - Henry Avery “The King of Pirates”
Another beautiful post from the Tales of Pirates series by @arrrados. This episode presents Henry Avery or “The King of Pirates”. What was his life like before becoming a pirate? What was his “career” like? Read on to find out.
### Psychology Chronicles Series #23.1 : Altering Consciousness Through Drugs | An Overview On Depressants & Opioids
How can drugs alter our consiousness? How do chemical substances mess with our brain and slowly turn us into a different person? @sakura1012 tries to explain all this in her amazing post.
_
##
Wednesday
### Let’s talk about people obsessed with always having control
Why do some people feel the urge to be in control of everything? Why can’t they accept the idea of being at the mercy of other people? @dedicatedguy has written another psychology post to talk about the need of having control.
### Second post of that day removed…
Plagiarists: what steemstem gives, steemstem can re-take…
A few words about the nomination process
For the sake of transparency we feel we need to clarify how our nomination process works; each issue is compiled by certain members of the SteemSTEM community. This mid-week’s editorial team was comprised of @ruth-girl.
The editorial team chooses their favorite posts for the week and each issue is the result of their joined effort. In order to keep the process fair, posts written by the editorial team are excluded from the nomination process.
Don’t be discouraged if you didn’t make it on this issue. The competition is harsh and there is always a next time :)
Top steemSTEM authors
During the last two weeks, steemstem supported with more than a (possibly split) full vote the following authors:
@aboutcoolscience, @akeelsingh, @alexbeyman, @alexdory, @alexs1320, @anaestrada12, @bitfairy, @carloserp-2000, @chloroform, @davidrhodes124, @dedicatedguy, @exercisinghealth, @greenrun, @highonthehog, @iamphysical, @itastem, @joseleogon, @katerinaramm, @lamouthe, @lemouth, @logic42, @lordneroo, @mobbs, @mountainwashere, @mrbreeziewrites, @rharphelle, @ruth-girl, @saho, @samminator, @sco, @soulesque, @spaghettiscience, @steepup, @sustainablyyours, @temitayo-pelumi, @whalhesa, @whileponderin, @zest, @zija2022
We are expecting them to strongly engage the community in return :)
All curation rewards earned will be used to fund @steemstem project functioning and activities.
See you all next Monday!
https://steemitimages.com/0x0/https://i.imgur.com/WhYkkh9.gif
This page is synchronized from the post: SteemSTEM Distilled #39


View Pets
  Home
  Read

Add
Create a pet!


Variable Scope
Scope is the formal term that represents when you can access a variable or method and when you can't. It's nothing explicit in the code (you're never calling a method named scope or anything like that); it's just a concept. If your variable is "in scope" then it's available for use, otherwise it's "out of scope".
Scope refers to the reach or visibility of variables. Different types of variables have different scoping rules. We'll be talking chiefly about two types: global and local variables.
Global scope and global variables
We're starting with the scope that's used least often, but which you need to be aware of: global scope, meaning scope that covers the entire program. Global scope is enjoyed by global variables. Global variables are distinguished by starting with a dollar-sign ($) character. They are available everywhere in your program. Global variables never go out of scope. However, global variables are used very little by experienced programmers (except perhaps a few of the built-in ones).
Built-in global variables
The Ruby interpreter starts up with a fairly large number of global variables already initialized. These variables store information that's of potential use anywhere and everywhere in your program. For example, the global variable $0 contains the name of the file Ruby is executing. The global $: (dollar sign followed by a colon) contains the directories that make up the path Ruby searches when you load an external file. $$ contains the process id of the Ruby process. And there are more.
Local scope
The top level (outside of all definition blocks) has its own local scope. Every class or module definition block (class, module) has its own local scope, even nested class/module definition blocks. Every method definition (def) has its own local scope.


Basic Settings
Summary
Site Access
Delete this website
Close DialogAre you sure you want to delete this website? Deleting this website will delete all related content and widgets.
WARNING! This operation is not reversible


Alien Active Spelling
Start
Back
0/0
A dark, blocked off tunnel.
ANSWER
CAT
CAV
CAVE
>>
Well Done!
Finish


This page help you to edit JSON styled Target host data:
Once you confirmed the commit, please create a pull request to master. It should be validated by the committer.
It is allowed, but not recommended, you to make a commit onto cmdb.json directly without using this editor page. The validation of values are taken place with this editor page.


Date Created: {{createdAt}}
Tags:
Description: {{description}}
Total Blocks: {{totalBlocks}}
Block Time: {{blockTime}}
Total Time: {{totalBlockTime}}hours
Target: //Shows Date, and amount if applicable


|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |
public interface Matcher
An implementation of the matching interface provides a score for matching a mention against a mention chain.
| Field Summary | |
|---|---|
static int |
MAX_DISTANCE_SCORE
Maximum distance score between a mention and a mention chain. |
static int |
MAX_SCORE
Maximum score; equal to . |
static int |
MAX_SEMANTIC_SCORE
Maximum value for the matching function, currently 4 . |
static int |
NO_MATCH_SCORE
Value to return in cases where there can be no match. |
| Method Summary | |
|---|---|
int |
match(Mention mention,
MentionChain chain)
Returns the match score between a specified mention and mention chain. |
| Field Detail |
|---|
static final int NO_MATCH_SCORE
static final int MAX_SEMANTIC_SCORE
4
.
static final int MAX_DISTANCE_SCORE
2
.
static final int MAX_SCORE
MAX_SEMANTIC_SCORE
+
MAX_DISTANCE_SCORE
.
| Method Detail |
|---|
int match(Mention mention, MentionChain chain)
0
and MAX_SEMANTIC_SCORE
inclusive. A
return value of NO_MATCH_SCORE
, which is guaranteed to
be negative, indicates that the mention cannot be matched to
the mention chain.
mention
- Mention to match.chain
- Mention chain to match.
|
|||||||||
| PREV CLASS NEXT CLASS | FRAMES NO FRAMES | ||||||||
| SUMMARY: NESTED | FIELD | CONSTR | METHOD | DETAIL: FIELD | CONSTR | METHOD |


Primer on Swig Templating
Let’s look at the basics of Swig, “a simple, powerful, and extendable JavaScript Template Engine” for NodeJS.
First off, a templating engine creates web pages (or views) dynamically by combining variables and programming logic with HTML. Essentially, you can add placeholders (or tags) to your HTML that are replaced by actual code defined from your router or controller. In general, tags, for the majority of templating engines, fall within one of two categories-
- Variables/Output Tags - surrounded by double curly brackets
{{ ... }}
, these output the results of a logic tag or a variable to the end user - Logic Tags - surrounded by
{% ... %}
, these handle programming logic, like loops and conditionals
Before diving in, grab the basic project structure from Github, install the dependencies via NPM -
npm install
- and then run the server. Pay attention to where we initialize Swig and set it as the templating language in app.js:var swig = new swig.Swig(); app.engine('html', swig.renderFile); app.set('view engine', 'html');
Contents
Output Tags
Let’s start with some basic examples…
Basics
First, we can pass variables from our route handlers/view functions directly to the templates.
Update the index.html file:
<!DOCTYPE html>

<title>{{title}}</title>

{{title}}

Now, we can pass in a variable called title
to the template from app.js:
// *** main routes *** //
app.get('/', function(req, res) {
res.render('index.html', {title: 'Swig Primer!'});
});
Fire up the server and test this out. Nice. Try adding another variable to the template.
index.html:
<!DOCTYPE html>

<title>{{title}}</title>

{{title}}

{{description}}

app.js:
app.get('/', function(req, res) {
var title = 'Swig Primer!'
var description = 'Swig is "a simple, powerful, and extendable JavaScript Template Engine" for NodeJS.'
res.render('index.html', {title: title, description: description});
});
Keep in mind that all variable outputs are automatically escaped except for function outputs:
// *** main routes *** //
app.get('/', function(req, res) {
var title = 'Swig Primer!'
var description = 'Swig is "a simple, powerful, and extendable JavaScript Template Engine" for NodeJS.'
function allthethings() {
return 'All the things!';
}
res.render('index.html', {
title: title,
description: description,
allthethings: allthethings
});
});
Don’t forget to call the function in the template -
{{allthethings()}}

Please see the official documentation for more info on output tags.
Filters
Filters, which are just simple methods, can be used to modify the output value. To illustrate some examples, add another route handler to app.js, like so:
app.get('/filter', function(req, res) {
res.render('filter.html', {
title: 'Hello, World!',
date: new Date(),
nameArray: ['This', 'is', 'just', 'an', 'example']
});
});
Now just add a new template, filter.html, adding in a number of filters:
<!DOCTYPE html>

<title>{{title}}</title>

{{title | upper}}

{{date | date("Y-m-d")}}

{{nameArray | join(' ')}}

Check out all the available filters. You can also extend the functionality of Swig by adding your own custom filters!
Logic Tags
As the name suggests, logic tags let you use, well, logic in your templates.
IF statements
Here’s a simple example…
app.js:
app.get('/logic', function(req, res) {
var title = 'Swig Logic!'
res.render('logic.html', {title: title});
});
logic.html:
<!DOCTYPE html>

<title>{% if title %}{{title}}{% endif %}</title>

{% if title %}

{{title}}

{% endif %}

Test out some more examples of if, elif, and else.
Loops
How about a for loop?
app.js:
app.get('/logic', function(req, res) {
var title = 'Swig Logic!'
var numberArray = [1, 2, 3, 4, 5, 6, 7, 8, 9, 10]
res.render('logic.html', {title: title, numberArray: numberArray});
});
logic.html:
<!DOCTYPE html>

<title>{% if title %}{{title}}{% endif %}</title>

{% if title %}

{{title}}

{% endif %}

{% for num in numberArray %}

{{ num }}

{% endfor %}

Need to reverse the loop?
Simply add a filter:
<!DOCTYPE html>

<title>{% if title %}{{title}}{% endif %}</title>

{% if title %}

{{title}}

{% endif %}

{% for num in numberArray | reverse %}

{{ num }}

{% endfor %}

What would a basic loop and filter look like?
<!DOCTYPE html>

<title>{% if title %}{{title}}{% endif %}</title>

{% if title %}

{{title}}

{% endif %}

{% for num in numberArray %}
{% if num % 2 === 0 %}

{{ num }}

{% endif %}
{% endfor %}

You could also write a custom filter for this if you needed to do the same filtering logic a number of times throughout your application.
There’s also a number of helper methods available with loops:
loop.index
returns the current iteration of the loop (1-indexed)loop.index0
returns the current iteration of the loop (0-indexed)loop.revindex
returns the number of iterations from the end of the loop (1-indexed)loop.revindex0
returns the number of iterations from the end of the loop (0-indexed)loop.key
returns the key of the current item, if the iterator is an object; otherwise it will operate the same asloop.index
loop.first
returns true if the current object is the first in the object or array.loop.last
returns true if the current object is the last in the object or array.
Try some of these out:
{% for num in numberArray | reverse %}
{% if num % 2 === 0 %}

{{ num }} - {{loop.index}}

{% endif %}
{% endfor %}
Template Inheritance
Logic tags can also be used to extend common code from a base template to child templates. You can use the block
tag to accomplish this.
Create a new HTML file called layout.html:
<!DOCTYPE html>

<title>{{title}}</title>

{% block content %}{% endblock %}

Did you notice the {% block content %}{% endblock %}
tags? These are like placeholders that child templates fill in.
Add another new file called test.html:
{% extends "layout.html" %}
{% block content %}

 This is the start of a child template

{% endblock %}
Finally, add a route handler to app.js:
{% extends "layout.html" %}
{% block content %}

This is the start of a child template

{{title}}

{% endblock %}
So, the blocks - {% block content %}{% endblock %}
correspond to the block placeholders from the layout file, and since this file extends from the layout, the content defined here is placed in the corresponding placeholders in the layout.
Conclusion
Check the documentation for more info. Add your questions below. Cheers!


1 write to _excludeDifferent
Microsoft.PowerShell.Commands.Utility (1)
commands\utility\Compare-Object.cs (1)
65
set {
_excludeDifferent
= value; }
1 reference to _excludeDifferent
Microsoft.PowerShell.Commands.Utility (1)
commands\utility\Compare-Object.cs (1)
63
get { return
_excludeDifferent
; }


Welcome to the Sunny Acres Corn Maze. We first heard about mazes from agricultural exchange students who came from England in 1985. In Europe, mazes are very popular in castle gardens. After hearing about the mazes in Europe, we thought it would be a great idea to build one of our own right outside of Council Bluffs.
Since 1997, thousands of people have enjoyed our Corn Mazes. We hope that your family gets as much enjoyment out of this year's Corn Maze as we did building it! Our family would like to invite your family to come out and visit us at this year's Corn Maze and AutumnFest.
Our new 15-acre maze (with over 4 miles of trails to explore) is filled with twists and turns that are good fun for adults and kids alike! See how adventurous you are as you wind through the maze while taking an interactive quiz. Answer the questions correctly and receive additional clues to solve the maze. For families with young children, our maze is filled with jokes, riddles, and quests. Try to be the first in your group to punch out your quest card by visiting the secret spots. This maze is the perfect size and height for little ones. Resting places and educational displays are scattered throughout.
There is no water available in the maze. Make sure you bring water bottles with you! No one under the age of 12 will be allowed in the maze without an adult at any time.


Unauthenticated login allows the user to access the tracking-bot anonymously. Metrics are stored
such that only data is stored unique to this device / browser. Other browsers and devices will not
have access to this data. Access is relative to a user created for this browser / device combination.
Authenticated login requires the user to sign in to an account the user has created. If
a user does not have an account, the user will need to create an account specifying a username,
email address, and password. The benefit of this approach is that the user can access the
dashboard from any device or browser. The user will login using their username / password
combination and will see metrics entered from any device.


Getting Started Guide: The most important steps in multi-objective
optimization:
Problem Definition, Optimization, Convergence Analysis, and Decision Making.
Newsletter: Sign up for our newsletter to stay tuned and up to date
about the current development and new features.
Discord: Join our discord server for help or a discussion about optimization in the context of our framework.


SNOBOL4FORK(3) | CSNOBOL4B 2.0 | January 1, 2015
NAME
snobol4fork - POSIX fork for SNOBOL4
SYNOPSYS
-INCLUDE 'fork.sno'
pid = FORK()
status = WAITPID([pid][,options])
DESCRIPTION
FORK() creates a process: returns 0 in child, process ID in parent.
WAITPID() takes an optional process id to wait for, and returns a string
with the process id, status, and additional status about the child.
options is a string of optional flags (see the waitpid(2)
man page for details):
-
c
-
WCONTINUED
-
h
-
WNOHANG
-
t
-
WTRAPPED
-
u
-
WUNTRACED
-
w
-
NOWAIT
SEE ALSO
snobol4(1), fork(2), waitpid(2)
AUTHOR
Philip L. Budne


{% extends 'task/main.html' %} {% block content %} Food List
Are you sure you want to Delete "{{food}}"?


See also: IRC log
<Norm> Scribe: timbl
<Norm> Date: 9 August 2004
-------------------------------------------------
<skw-scribe> Issue diwg-1
<skw-scribe> DC: requested discussion because we say nothing about URI with question marks in them.
<skw-scribe> DC: May be a useful distinction between machine generated and human generated rather than statically/dynamically generated URI
<skw-scribe> TBL: One of his notes is content-negotiated... example of a spanish user that wanted to read the english version
<skw-scribe> CL arrives
<skw-scribe> CL: User should be able to express a preference.
<skw-scribe> RF: Customers like this when the 'system' makes a good initial default choice, but don't like an inability to easily change the 'default' if it is not a good choice.
<skw-scribe> PC: Comment points at 3.6.2 URI Persistence and there are no examples in that section (at the time of the comment).
<skw-scribe> PC: May be some examples by transcusion with link at the bottom...
<skw-scribe> PC: ...eg when a mapping application makes up a URI for a map location.... those should be persistent and sharable.
<skw-scribe> CL: Yes.... should be say session dependent or time dependent.
<skw-scribe> PC: For some of the interaction with banks etc. the URI are not useful outside the given session
<skw-scribe> CL: Would like to have 4 examples:
<skw-scribe> 1: Map example with ?lat, ?long
<skw-scribe> 2: Ditto plus sessionid
<DanC_jam> I'd sure like to be able to bookmark links in my private banking data!
<skw-scribe> 3: Private financial data where inappropriate to share data
<skw-scribe> TBL: Still might want to share with other appropriate people...
<skw-scribe> CL: Ok... maybe drop the 3rd example.
<skw-scribe> DC: eg. myYahoo.com.
<skw-scribe> 4: URI in the address bar remains the same despite navigation.
<skw-scribe> NW: So would a proposal to include these examples address this comment.
<DanC_jam> (discussing a spectrum, with examples and plusses and minuses starts to sound more like a finding than a section of the arch doc)
<Roy> http://www.prescod.net/rest/mistakes/
<skw-scribe> PC: I'm frusrtated when I'm forced to navigate from the top....
<skw-scribe> RF: But it is not called URI persistence.
<skw-scribe> RF: The examples being discussed are about bookmarkable/reusable URI.
<skw-scribe> NW: Definitely a section under representation management... possibly a new subsection.
<skw-scribe> NW: ....called "Supporting Navigation"
<skw-scribe> NW: Further discussion....
<skw-scribe> DC: .... new text needs four eyeballs IMO.
<skw-scribe> Issue diwg-2
<skw-scribe> DC: Overtaken by events....
<skw-scribe> (diwg-2 don't communicate language info in URIs).
<skw-scribe> DC: Do we cover this in the MetadataInURI finding?
<skw-scribe> CL: If you have five languages you should have 6 URI, one for each specific URI and one content-neg'ed resource
<skw-scribe> DC: There is no obligation to put the 'flag' in the URI.
<skw-scribe> CL: Worthwhile example.... trivial to write.
<skw-scribe> DC: Very relevant to metaDataInURI-31.
<skw-scribe> NW: we only talk about content-neg wrt to frag ids.
<Roy> re. prev topic title, "Shared URI space" is another possibility
<skw-scribe> ACTION: CL to draft text on language negotiation for inclusion in webarch., [recorded in http://www.w3.org/2004/08/10-tagmem-irc]
<skw-scribe> ACTION: SW to Include example on lang info in URI to metadatainURI finding [recorded in http://www.w3.org/2004/08/10-tagmem-irc]
<DanC_jam> . http://www.w3.org/2001/tag/doc/metaDataInURI-31.html
<Norm> Issues URI: http://www.w3.org/2001/tag/2003/lc1209/issues.html
<skw-scribe> RF: When the resource is language specific, inclusion of a language tag in a URI is not identifying information and notg metadata... it's role has changed.
<skw-scribe> NW: The word language does not appear in the draft finding....
<DanC_jam> re lang info in URIs, I recommend borrowing from http://www.w3.org/DesignIssues/Generic
<DanC_jam> e.g. remember to discuss http Vary: while you're at it
<skw-scribe> Done with diwg-2
<skw-scribe> Issue diwg-3 http://www.w3.org/2001/tag/2003/lc1209/issues.html#diwg3
<skw-scribe> Resting discussion of accessing different (device specific) representations.
<skw-scribe> CL: Seems to be about representations that are tailored for specific devices.
<skw-scribe> DC: Is there anything that we can borrow/refer to from DI Principles
<skw-scribe> DC: Excert and cite DI Principles....
<skw-scribe> NW: Ok... yes... but what and where.
<skw-scribe> CL: I think delivery context appear in our doc.
<skw-scribe> NW: No... it doesn't
<skw-scribe> RF: Section on interaction should have a section on gateways and transformations.
<skw-scribe> CL: Ok... we should borrow text from DI principles.
<Roy> eventually
<skw-scribe> NW: Deep down in section 3.2.1 we added "...or transformed dynamically according to the ...." in response to a DIWG comment.
<skw-scribe> CL: ref para after GPN in 4.3 (recombination stuff).
<skw-scribe> CL: ...it's explaining what delivery context does rather than using the term delivery context.
<skw-scribe> NW: So have we already addressed their comment?
<skw-scribe> CL: No... we need to use this text....
<skw-scribe> NW: So return to question of where in our doc it should go.
<skw-scribe> CL: It is to do with content/presentation....
<Chris> 4.3. Separation of Content, Presentation, and Interaction
<skw-scribe> NW: So work DI Section 2.2.3 into our Section 4.3 and add ref to DI princples.
<skw-scribe> NW: ... and that should address their comment?
<skw-scribe> general assent.
<skw-scribe> Done diwg-3
<skw-scribe> Issue manola-27 http://www.w3.org/2001/tag/2003/lc1209/issues.html#manola-27
<skw-scribe> "Provide examples of mistaken attempts to restrict URI usage."
<skw-scribe> PC: Seem offended by the 1st para in 3.6.3 in that it may be reasonable to hide the existence of the reource. ie. doesn like "... it is unreasonable to prohibit others from merely identifying the resource."
<skw-scribe> TBL: But why shouldn't it get a URI.
<skw-scribe> DC: 403/404 responses are orthogonal to whether it gets a URI or not.
<skw-scribe> RF: What he's asking about is situations where the person is prevented from having a URI upon which to base an access.
<skw-scribe> ACTION: NW to Add to 3.6.2 "that doesnt [recorded in http://www.w3.org/2004/08/10-tagmem-irc]
<skw-scribe> NW: We wrote para from point of view of deep linking, he's read it from a security and access control POV.
<skw-scribe> NW: ...no good example spring instantly to mind.
<skw-scribe> NW: Propose that addressong manola-27 by adding security considerations text.
<skw-scribe> RF: I think that he's also objecting to the last paragraph (which refers to Web Access control mechanisms).
<DanC_jam> change "but it is unreasonable to prohibit others from merely identifying the resource" to "but merely identifying the resource is like referring to a book by title. Except when people have agreed to keep titles confidential, they are free to exchange them."
<DanC_jam> e+
<skw-scribe> TBL: Propose "For very high security applications you may want to suppress the difference between 403 and 404 response codes." [Tim did I get that right?]
<Chris> +1 to suggested text
<Chris> .... may want to return 404 when a 403 would be more correct but expose secutity information
<DanC_jam> change "but it is unreasonable to prohibit others from merely identifying the resource" to "but merely identifying the resource is like referring to a book by title. Except when people have agreed to keep titles or URIs confidential, they are free to exchange them."
<Chris> yes, that is good. at a different level of abstraction
<skw-scribe> TBL: We have been a little obsure wrt to the legal case that motivated the text.
<Roy> +1 too
<skw-scribe> DC: I still think that the text I propose is reponsive to the comment.
<Roy> +1 to Dan's text
<skw-scribe> NW: I think we have agreement to Dan's text to address manola-27
<skw-scribe> TBL: ... add wtoe that in some high security apps it may be desirable to suppress the distinction between access control failure and the non-existence of a resource.
<Norm> i18nwg20
<skw-scribe> Issue i18nwg-20 http://www.w3.org/2001/tag/2003/lc1209/issues.html#i18nwg-20
<Chris> Propose to accept the changes for i18nwg20
<skw-scribe> http://www.w3.org/2001/tag/webarch/#metadata-inconsistencies
<Norm> http://www.w3.org/2001/tag/webarch/
<skw-scribe> DC: We have an admonision against using text/* in 4.5.7
<skw-scribe> DC: ie. we say pretty much what they ask in 4.5.7
<skw-scribe> CL: Yes... but they point out that that is just a specific instance of a more general problem and they are asking us to address the more general problem
<Chris> http://lists.w3.org/Archives/Public/public-webarch-comments/2004JanMar/1060.html
<skw-scribe> CL: <quotes from original email>
<skw-scribe> ... We are on comment 20 *NOT* comment 5.
<Chris> - Always make sure you know what the character encoding of a
<Chris> document or message is.
<Chris> - Make sure that it's easy for server managers and authors to configure
<Chris> and test metadata on the server, to make sure it's correct.
<Chris> - No arbitrary defaults for specs
<Chris> - No out-of-the-box with arbitrary settings
<skw-scribe> CL: There is no standard for content authors to influence important bits of sever configuration.
<skw-scribe> TBL: Maybe the GPN should be....
<Chris> quotes from right section **20 ** of document
<Chris> - Always make sure you know what the character encoding of a
<Chris> document or message is.
<Chris> - Make sure that it's easy for server managers and authors to configure
<Chris> and test metadata on the server, to make sure it's correct.
<Chris> - No arbitrary defaults for specs
<Chris> - No out-of-the-box with arbitrary settings
<skw-scribe> NW: reminds TBL of an action item to write text addressing the configuration information that should be available to content authors.
<DanC_jam> somedaypile += standardized .htaccess files (in RDF?)
<Chris> 'easy .... for authors' is not doable - no standard way for authoring toools to do this
<skw-scribe> NW: proposes that we have made enough changes to suggest that we have tried to address this comment.
<skw-scribe> NW: Anyone want to see more changes to address this?
<skw-scribe> CL: The section doesn't really address what they are talking about....
<skw-scribe> CL: We do say some things about character encoding wrt to XML.
<skw-scribe> CL: There has been a recent thread on character encoding for CSS.
<skw-scribe> CL: eg... a CSS stylesheet failed due to inclusion of a natural language comment.
<skw-scribe> NW: I assert that I have already made a GPN out of the four i18nwg-20 bullets.
<Chris> so, the fact that we restrict this to xml sort of implies that plain text. /css etc are not covered
<skw-scribe> NW: Further discussion....?
<skw-scribe> Issue rosenberg-5 http://www.w3.org/2001/tag/2003/lc1209/issues.html#rosenberg-5
<skw-scribe> NW: Recaps previous telcon discussion that this originated with IAB.
<skw-scribe> CL: Questions whether we have already closed rosenberg-4.
<Chris> (once we are done with 5 .... please can we do 4 http://www.w3.org/2001/tag/2003/lc1209/issues.html#rosenberg4)
<skw-scribe> DC: rosenberg-5 suggests referencing RFC3688. RFC3688 is directly counter to some priniples of Web Arch... towit: encourages the use of URI aliases.
<skw-scribe> PC: Notes that it also invokes the IETF concensus process.
<skw-scribe> RF: Would it be responsive to this comment by citing the document as an example of bad practice wrt URI aliasing.
<skw-scribe> PC: Why we put this in Webarch rather than respond directly to the RFC.
<skw-scribe> DC: I was suggesting doing both.
<skw-scribe> PC: I think we only need do the one.
<skw-scribe> NW: I think it would be good to make the comment back IAB
<skw-scribe> NW: Does anyone feel obliged to respond to the IETF/IAB.
<skw-scribe> DC: yes I do...
<Chris> for 4, s/RTSP [RFC2326])/SIP (RFC 3261)/
<skw-scribe> NW: Dan... will you take that action?
<skw-scribe> DC: yes.
<skw-scribe> ACTION: DC respond to IETF/IAB wrt to rosenberg-5 [recorded in http://www.w3.org/2004/08/10-tagmem-irc]
<Chris> and voice-over-IP (such as RTSP [RFC2326]).
<skw-scribe> Issue rosenberg-4 http://www.w3.org/2001/tag/2003/lc1209/issues.html#rosenberg-4
<skw-scribe> CL: Propose we simply accept the replacement reference they suggest.
<skw-scribe> RF: Explains some of the details of RTSP, RTP, and SIP.
<Chris> we could (optionally ) also say we do not deal with streaming command control like RTSP
<skw-scribe> [lost discussion]
<skw-scribe> DC: I think the intent of this section was to include analog channels.
<Chris> the whole section? i think not
<skw-scribe> RF: What are we trying to say here... why is this here... we're not going to talk about interactions between the Web and VoIP.
<skw-scribe> DC: I believe it is relevant to this document as a future direction. I want to click on web links with telephone numbers.
<skw-scribe> CL: But we don't care about all the 'little details' (flow control etc...).
<skw-scribe> DC: I do....
<skw-scribe> DC: Can you bookmark minutes 3-5 of a VoIP conversation.
<skw-scribe> TBL: Propose VoIP ref SIP, streaming media ref RTSP.
<Chris> proprose t respond to them saying that 'such as' was an editorial error
<skw-scribe> NW: Proposal to cite both RSTP and SIP for streaming media and VoIP respectively.
<Chris> +1 to suggested text
<skw-scribe> Assent.
<skw-scribe> Break:
<Norm> Diff: http://www.w3.org/2001/tag/webarch/July7-Aug10-diff.html
<DanC_jam> the example in 2.3.2 under http://www.w3.org/2001/tag/webarch/#identifiers-comparison seems responsive to Renato's comment of 8 July http://lists.w3.org/Archives/Public/public-webarch-comments/2004JulSep/0001.html
<DanC_jam> (sigh; much spam in http://lists.w3.org/Archives/Public/public-webarch-comments/ )
<DanC_jam> I'm not inclined to put Renato's overloading comment on the critical path http://lists.w3.org/Archives/Public/public-webarch-comments/2004JulSep/0004.html
<skw-scribe> I agree
<DanC_jam> ugh; Hayes's comments didn't make it into the list. http://lists.w3.org/Archives/Public/public-webarch-comments/2004JanMar/1057.html
<DanC_jam> and QA sent a request for teleconference, though I can't quite find their comments. http://lists.w3.org/Archives/Public/public-webarch-comments/2004JanMar/1056.html
<Noah> At the end of yesterday's call, it was suggested that it might be helpful for some of us who are involved in Schema WG work on versioning to dial into your call now. Would those of you on the Tag prefer that I do or don't join? Either way is fine; whatever's best for you. Thank you.
<paulc> Versioning discussion by XML Schema WG:
<paulc> http://lists.w3.org/Archives/Member/w3c-xml-schema-wg/2004Aug/0006.html
<Noah> You might also want to look at the analysis that I did for the schema WG. This was sent in an email to the tag which can be found at http://lists.w3.org/Archives/Public/www-tag/2004Aug/0010.html.
<Noah> The note which actually carries the analysis was an HTML attachment to that email and can be found at: http://lists.w3.org/Archives/Public/www-tag/2004Aug/att-0010/NRMVersioningProposal.html
<skw-scribe> David Orchard joins.
<Noah> The note is roughly in two parts: the first sets out some general goals and considerations that may be of interest for any analysis of versioning. The later sections speculate on some particular mechanisms that we might use in XML schema to support versioning.
<skw-scribe> NW: Invites David to intro topic....
<skw-scribe> DO: Thanks... for appointment as finding editor.
<skw-scribe> DO: Outlines work plan at http://lists.w3.org/Archives/Public/www-tag/2004Jul/0027.html
<skw-scribe> DO: See's work as producing two documents, one generic and one applying those generic approaches to specific languages.
<skw-scribe> DO: Another issue that's come up in REST/Web Services is protocol extensibility. Can think of a protocol as a language.
<skw-scribe> DO: Notion of compatibility of groups of operations - an interface - cf Web Services/ATOM.
<skw-scribe> These are things that haven't been explored very fully in the current finding.
<DanC_jam> (bummer; pointers in 0027 got kinda broken in the archive)
<skw-scribe> PC: The extensibility finding has never been finalised, but parts were abstracted into web arch. Do the changes you propose affect the webarch doc?
(eg to http://www.pacificspirit.com/blog/2004/05/26/substitution_rules_must_be_in_v10)
<skw-scribe> DO: No... Webarch does habe some material on namespace management and some discussion of language exstensibility (subset/superset languages).
<skw-scribe> PC: Anything that would affect a 2nd LC on webarch in september?
<skw-scribe> DO: I want to change the examples to a much more common name example, first name/last name add middle name... plus other examples throughout.
<skw-scribe> DO: In part 1 TAG finding there is very little discussion of diff between extensibility and versioning.
<skw-scribe> DO: Versioning is when a namespace owner revises their language.
<skw-scribe> DO: Extensibility is when someone else includes something else in you language.
<skw-scribe> He doesn't appear to be.
<Roy> Related work (30MB dissertation of Peyman Oreizy): http://www.ics.uci.edu/~peymano/papers/thesis.pdf
<skw-scribe> DO: [going too fast for me to sumarise....]
<Norm> Yes, thanks, Noah. I failed to plan this very well.
<Noah> Sure no problem.
<Chris> substitutability seemes cleaer to me, actually
<Chris> yes, svg does that
<DanC_jam> (this summary confirms my intuition that this is a book-length topic)
<skw-scribe> DO: Moves on to thoughts on how to apply these concepts to protocols.
<skw-scribe> DO: Concluded that a MU flag is not of much use. Protocols take place over a different space/time context. Would prefe to know capabilities up front.
<skw-scribe> DO: Processing of protocols maybe somewhat distributed.
<skw-scribe> DO: Final topic to include is "service compatibility". By service I mean a collection of operations.
<DanC_jam> stuart, I think it's sufficient to say:
<skw-scribe> DO: What kind of changes in an interface preserve or break compatibilty
<DanC_jam> DO summarizes plan in http://lists.w3.org/Archives/Public/www-tag/2004Jul/0027.html
<skw-scribe> Ok... saves my fingers...
(A protocol A is a subprotocol of B if for every state transition arc in A there is an equivalanet transtion in B, and for that arc in A the message languge of the message sent in the transition in A is a sublanguage of the message for the equivalent arc in B.)
<DanC_jam> I'm all for telling stories about how extensibility has happened.
<Roy> related work: http://doi.acm.org/10.1145/288195.288269
<skw-scribe> TBL: DO said lots about substitutability. We were thinking of lang for webarch for treating version X as version Y, say ignoring bits you don't understand, but might be more acurate to think of sets of mappings between language versions.
<skw-scribe> TBL: DO was looking for words and that concepts around this notion of mappings might yield usefula language.
<skw-scribe> PC: Schedule?
(total mappings, tim rememebrs, from msm's comments yesterday)
<Roy> http://www.webster-dictionary.org/definition/substitutability
<skw-scribe> DO: Hmm.... most of topics have a URI for an assoicated blog URI.
<skw-scribe> DO: Planing to continue working on the finding after addressing a few things in the work plan... maybe mid-September.
<Roy> http://en.wikipedia.org/wiki/Liskov_substitution_principle
<Chris> do the xsd schema techniques map to the rng ones? Are there additional techniques applicable to the extra functionality of rng?
<skw-scribe> NW: My schedule should be more open mid-Sept onwards.
<skw-scribe> NW: Ref some plans to do Ext/Vers with XML Schema... anythoughts on joint workplan?
<skw-scribe> DO: Ok... come back to that once we've discussed 2nd (Schema specific) part of document.
<Chris> wondering whether NRL has applicability here to extensibility
<Chris> Namespace Routing Language
<DanC_jam> Namespace Routing Language (NRL) http://www.thaiopensource.com/relaxng/nrl.html
<Chris> http://www.thaiopensource.com/relaxng/nrl.html
<Chris> Abstract
<Chris> The XML Namespaces Recommendation allows an XML document to be composed of elements and attributes from multiple independent namespaces. Each of these namespaces may have its own schema; the schemas for different namespaces may be in different schema languages. The problem then arises of how the schemas can be composed in order to allow validation of the complete document. This document proposes the Namespace Routing Language (NRL) as a solution to this problem. NR
<skw-scribe> DO: resumes review of plan for part 2 in http://lists.w3.org/Archives/Public/www-tag/2004Jul/0027.html
<Chris> in particular I am thinking of
<Chris> 10 Open schemas
<Chris> Up to now, sections validated by one subschema have not participated in the validation of parent sections. Modern schema languages, such as W3C XML Schema and RELAX NG, can use wildcards to allow elements and attributes from any namespace in particular contexts. It is useful to take advantage of this in order to allow one subschema to constrain the contexts in which sections validated by other subschemas can occur.
<Chris> and
<Chris> 14 Transparent namespaces
<Chris> Many schema languages can deal with the kind of extensibility that involves adding child elements or attributes from different namespaces. A more difficult kind of extensibility is where we need to be able to wrap an extension element around an existing non-extension element. This can arise with namespaces describing templating and versioning.
<skw-scribe> CL: Refers DO to NRL.
<skw-scribe> Discussion of compound documents.
<skw-scribe> PC: One of my concerns would be addressed by knowing the title of the 2nd document. Propose "Best practice for versioning and extensibility with??????"
<skw-scribe> NW: I think of it more as a set of case studies rather than best practices.
<skw-scribe> DO: the problem I have with the term best practice or case studies... is that your making some particular choices [????]
<skw-scribe> PC: Ok... I'll take another pass. XML Schema are going to be looking at versioning of Schema and want to make sure that we're not treading on WG toes. If this work is helping others recognise and wrok on problems this is a positive effect.
<skw-scribe> DO: I'd like to have some XML Schema 1.0 material. I'm very pleased that XML Schema WG is taking this work seriously.
<skw-scribe> DO: They've encounter the same problems of subsumption that I did.
<skw-scribe> DO: Subsumpsion realtionships between content models.
<skw-scribe> NW: I want to put a stronger stake in the ground. The work DO/NW propose is broader than what we could reasonably expect the XML Schema WG to address.
<skw-scribe> NW: I expect us to work together with other WGs in those places interest coincide
<skw-scribe> DO: I'm having some difficulty in understanding how to tie in some of Noah's material into the finding. There's probably not much that we can do in the finding right now wrt to how to do this with XML Schema 1.0
<skw-scribe> PC: Reiterates that the public discussion of the topic has a positive effect and has engaged a number of interested parties
<skw-scribe> PC: I think the TAG having opinions that has influence over things that WG's are doing is a good thing.
<skw-scribe> PC: I'd like this document to highlight things that you can/can't do with say the current schema language.
<skw-scribe> DO: Agree.
<skw-scribe> DO: Would you, Paul, agree with adding this part 2 as a TAG deliverable.
<skw-scribe> PC: I'd prioritise the webarch document. This (part 2) is a horizontal cut... and I think it is appropriate for the TAG to do this. If we can get something of part 2 in order for December we can take that for more focussed feedback from the AC in december.
<skw-scribe> DC: I don't think its a case of permission or forgiveness, we stuck our toe in the water and people asked of more.
<skw-scribe> DO: My personal read is that the public would like the TAG to be looking at more forward looking issues.
<skw-scribe> PC: I think that TAG can look back and say that we have done a good job with various things where folks have picked up theads from TAG discssion (eg. Binary XML, Xlink... etc).
<skw-scribe> DO: So I'd like to know whether the TAG wants an official part 2 deliverable.
<skw-scribe> TBL: Are RDF/OWL covered in part 2?
<skw-scribe> DO: Yes... I'd expect to cover extensibility and versioning in RDF/OWL.
<skw-scribe> DO: Top 3 languages that I encounter are XML Schema, Relax NG and RDF/OWL.
<skw-scribe> NW: Does anybody think that we shouldn't be doing a part 2.
<skw-scribe> No dissent.
<skw-scribe> NW: I think we have assent to do this.
<skw-scribe> DC: Schedule ag
<skw-scribe> DC: Schedule question again?
<skw-scribe> DO: I'd aim for mid-October for two revised findings on these topics.
<Norm> I think mid-October is the right timeframe
<skw-scribe> DO: This would dovetail with presentation to AC.
<skw-scribe> DO: would an earlier revision be useful for the TAG's October F2F?
<skw-scribe> NW: Too early to say.
<Norm> PC: Middle October is safer
<Norm> DO: I wanted to add that I think the Schema 1.1 work is really interesting and to the extent that the TAG has been able to influence that work, as a member of the communtiy, I've been veryp leased to see that interaction.
<Norm> DO: I think that work on Schema 1.1 has a real opportunity to raise the bar. I think to the extent that the finding can influence that and there can be an ongoing dialogn, I thin kthat is all goodness.
<Norm> DO: And other groups, too.
<Norm> SW: Would the rdf/owl stuff be a topic for the Semantic Web BPWG.
<Norm> DO: Yes, I think so. I would expect that the same sorts of interaction soccur there.
<Norm> timbl: Versioning of ontologies is a hot research topic and there's a lot of practical work being done on it as well.
<Norm> timbl: There are people who's life's work is the evolution of ontologies so there should be something to connect tol.
<Norm> DO: And I think the TAG can have a connection between that and the schema working group. That connection can be fairly close in both cases.
<Norm> DO: One of the reasons we haven't had too much interaction so far is that we haven't had many direct examples. I think having concrete examples will help.
<Norm> DO: One thing on the finding is that I feel comfortable working on the schema material, there's only so far that I'll be able to take the ball when it comes to RDF/OWL. I'll try to take the ball down the field aways, but I have no belief that I'll be able to make it into the end zone.
<Norm> timbl: Maybe we can find some people to connect to on that topic.
Bijan
<Norm> DO: I'm just pointing out the realities of my ability to learn the material.
<Norm> DO: Each question I ask about RDF/OWL takes longer to answer than I would have hoped because of differing world views.
<Norm> DO: Open vs. closed world assumptions, data types, etc. There are things that are somewhat complicated in the view. There might come to a point where this will all work out,
<Norm> DO: Maybe we'll get concrete "do it this way or that way" results
<Norm> PC: I will even speculate that I can't do as much of a review of the schema part as you can. So one of the thing's I'll encourage the TAG to do is make sure this document gets wider review. That's a tactic that will be useful in this area.
<Norm> NW thanks DO for participating remotely from his vacation.
<Norm> (on behalf of the tag)
This is scribe.perl Revision: 1.122 of Date: 2005/03/31 04:43:41 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) FAILED: s/At times, there may be/A problem has been/ Succeeded: s/goof/good/ Succeeded: s/RDF BPWG/Semantic Web BPWG/ Found Scribe: timbl Inferring ScribeNick: timbl WARNING: No "Topic:" lines found, but dash separators were found. Defaulting to -dashTopics option. Present: RF PC DC SW TBL NW(Chair) Agenda: http://www.w3.org/2001/tag/2004/08/09-11-tag.html Found Date: 9 Aug 2004 People with action items: cl dc nw respond sw WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]


rock - paper - scissors
Start new game
Choose rock, paper or scissors
PAPER
ROCK
SCISSORS
x
Game result
Who wins?
Your move
Computer move


For a stream of JPEG images into mutlipart/x-mixed-replace content, Ouistiti must be set with the "multipart" option of the webstream's configuration.
options = "multipart";
mjpeg -U -n camera.mjpg -R srv/www/webstream
Motion-Jpeg with mutlipart/x-mixed-replace content
For a stream of H264 stream, webstream needs an empty options configuration.
options = "";
mjpeg -U -n camera.h264 -R srv/www/webstream
H264 inside a video
tags.