Re: A VSCP schema for xAP

[YAP <x112358@xxxxxxxxx>]

OK "EUROSRC.VSCP" it is  even if it is a bit missleading as
eurosource
does not have anything to do with this. But please reserve
"EUROSRC"
for me.

/Ake=20

On 8/6/05, Mark Harrison (Groups) <mph@xxxxxxx> wrote:
>  On Fri, 2005-08-05 at 13:46 +0100, Kevin Hawkins wrote:
>  >=20
>  >     The intent is that the vendor name is the actual author
>  > (providor)=20
>  > of the application, in your case 'Eurosource' I guess. If the
VSCP
>  > group=20
>  > were writing it then it would be VSCP .  The VSCP part is the
device=20
>  > type really isn't it (?) so you should end with an address
something
>  > like...
>  >=20
>  >      Source=3DEuroSource.VSCP.<instance>
>  >=20=20=20=20
>=20=20
>  Kevin's understanding is the same as mine. That Vendor IDs that
pertain
>  to existing products should only be registered by the owners of those
>  products, and that others who write connectors from xAP to those
>  products should use a vendor ID relating to them.
>=20=20
>  For example, I use the vendor ID Scentium for the HomeVision plugin,
>  rather than HOMEVIS, because only CSI (maker of the HomeVision) would
be
>  allowed to register HOMEVIS as a name.
>=20=20
>  The only thing I'd modify in Kevin's message is to draw an
8-character
>  limit at Vendor IDs, so be, say, EUROSRC instead of EuroSource. It if
>  for this reason that I am scentium rather than ascentium.
>=20=20
>  The ultimate maintainer of the Vendor ID list is Stuart Poulton.
>=20=20
>  Regards,
>=20=20
>  Mark
>=20=20
>=20=20
>=20
>=20=20
>  SPONSORED LINKS=20
>  Computer internet Developer=20
>=20=20
>  ________________________________
>  YAHOO! GROUPS LINKS=20
>=20=20
>=20=20
>=20=20
>  Visit your group "xAP_developer" on the web.
>=20=20=20
>  To unsubscribe from this group, send an email to:
>  xAP_developer-unsubscribe@xxxxxxx
>=20=20=20
>  Your use of Yahoo! Groups is subject to the Yahoo! Terms of
Service.=20
>=20=20
>  ________________________________
>