RE: BSC spec query

["Sullivan, Glenn" <gsullivan@xxxxxxxxxxxxxx>]

That must be an error... No program I write would ever pick that out as
a matching target.

I'm still struggling a bit with untargeted messages, personally... In
our conversations last month, the topic of responding to untargeted
messages came up, there were varying opinions as to whether
target=>:>
and "no target" are the same thing...

I think that, in the TiVo JPEGWriter service (to be released tonight...
Stay tuned to this space), I am going to make a
"RespondToUntargettedMessages" config option... Give the user a
choice.

But, on your original question, it sounds like a typo... Where did you
get that spec from?

Glenn Sullivan, MCSE+I MCDBA
David Clark Company Inc.
-----Original Message-----
From: xAP_developer@xxxxxxx
[mailto:xAP_developer@xxxxxxx]
On Behalf Of g8kmh
Sent: Tuesday, December 20, 2005 2:51 PM
To: xAP_developer@xxxxxxx
Subject: [xAP_developer] BSC spec query

I'm running some test cases through the DMX plug-in against the spec and
came across one I couldn't figure.

>From the spec:
Example
{
v=12
hop=1
uid=FF123400
class=xAPBSC.cmd
source=ACME.Controller.Central
target=ACME.Lighting.apartment:outside.>
}
output.state.1
{
ID=*
State=OFF
}
This message would cause all binary outputs named outside.<anything>
to
turn off Eg these would all turn off
ACME.Lighting.apartment:outside.Floodlights
ACME.Lighting.apartment:outside.sprinklers
ACME.Lighting.apartment:porchlight

What isn't clear is the third case, why/how does porchlight match?

Lehane