[Message Prev][Message
Next][Thread Prev][Thread Next][Message
Index][Thread Index]
Re: Class naming
--------------040403040003040300060005
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
What I was really meaning is that to use a class name that starts 'xap'
it has to be an officially endorsed schema - one that is proven in terms
of it's implementation. Early on a few got through fairly easily
however :-( For your own class names therefore you mustn't use xap...
In terms of the configuration schema, of which renaming instance names
would logically be one aspect, then indeed it will likely be named
xapconfig but whilst being honed it should appear with a different name
until it all comes together and is formally endorsed. If you look at
the TSC schema document you will see that a similar thing is happening
here and indeed so far it hasn't been included as a xap official
schema. A suggestion might just be to use config or xConfig as the
schema name eg config.name config.cmd etc.
The official config class should be architected to allow all aspects of
a device to be configured , including recovery of existing parameter
values and prevention of setting illegal or conflicting values. A
front end configuration application should, via the schema, be able to
present a user with pertinent information and choices. The schema
likely will encompass some form of device discovery and either implement
UID allocation or work alongside a UID allocation application - rather
like a DHCP server. Aspects of security crop up too. Devices may need
a template that they provide to assist this that might be queried by the
schema or held in an internet repository perhaps. We have also
discussed electronic schema repositories too. As you can envisage
there's quite a few issues to think through and that is partly why it
hasn't been an easy one to tackle. I do expect that BSC will provide
a good basis for this schema , especially if you include the unofficial
'choice' device type. A range type device will likley be needed to
indicate that an allowable parameter value might be between say -10 and
+212 or requires two decimal places.
Having said all the above and probably frightened you a little with the
scope of this configuration schema I think everyone recognises that we
need progress and we should tackle small areas and provided we do that
in a well thought through and architected manner we can evolve it.
Something is better than nothing. Instance naming can be tackled as a
subset provide it implements a flexible mechanism useful for other
aspects of the config schema ie a general parameter recover/rename
model. Likely early on it will remain as a non 'xap' schema however
until we pull the whole xAPconfig schema together.
The answer is 'yes' to all the questions in your last paragraph . There
are a couple of people who have tackled this area before and one in
particular I think you should chat with ... I'll get them to contact you
either here or offlist.
K
On 17/03/2010 12:20, Neil Wrightson wrote:
>
>
> Kevin,
> Your statement - "You are totally free to add your own
additional
> parameters within BSC blocks and to create your own schema classes (as
> long as they don't start with the three reserved letters 'xap' as in
> xapbsc.cmd) so there's no restriction to what you're trying to do - it
> would be just nice to get it adopted in a formalised way."
> Has me puzzled.
> From the bible it states "Standard classes can be identified
through
> the use of the reserved prefix xap-.... <class> Identifies the
> collection of schema applicable to this message. <type>
Identifies the
> sub-schema applicable to this message. "
> Wouldn't a class that renames instances or end points be a standard
class?
> What restrictions are there on the naming of classes? On the xAP
> wbesite there are lots of schemas that have a class of xap*****
> whatever. I.e. "class = xap-x10.request",
> "Class=xAP-INetConnect.Dialup",
"Class=xAP-Audio.Transport"
> Given that I'm trying to come up with a way of changing the instance
> name and the end point names. What would you suggest as a class name
> convention that specifically spelt out what the user is to use?
> Do you think that one class should be created for performing the
> renaming of any instance, end point, TSC?
> Should it also be cable of changing the UID of the instance?
>
> Regards,
>
> *Neil Wrightson.*
> */N.W.Electronics/*
> ABN 76 768 513 867
> Embedded Controllers and Home Automation Products
> Skype : Neil_Wrightson
> Web :_ www.nwe.net.au_
>
>
>
>
--------------040403040003040300060005
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<head>
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
</head>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01
Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<!-- **begin egp html banner** -->
<br><br>
<!-- **end egp html banner** -->
What I was really meaning is that to use a class name that starts 'xap'
it has to be an officially endorsed schema - one that is proven in
terms of it's implementation. Early on a few got
through fairly
easily however :-( For your own class names therefore
you mustn't
use xap... <br>
<br>
In terms of the configuration schema, of which renaming instance
names
would logically be one aspect, then indeed it will likely be
named
xapconfig but whilst being honed it should appear with a different name
until it all comes together and is formally
endorsed. If you look at
the TSC schema document you will see that a similar thing is happening
here and indeed so far it hasn't been included as a xap official
schema. A suggestion might just be to use config or xConfig as
the
schema name eg config.name config.cmd etc.<br>
<br>
The official config class should be architected to allow all aspects of
a device to be configured , including recovery of existing parameter
values and prevention of setting illegal or conflicting
values. A
front end configuration application should, via the schema, be able to
present a user with pertinent information and choices. The schema
likely will encompass some form of device discovery and either
implement UID allocation or work alongside a UID allocation application
- rather like a DHCP server. Aspects of security crop up too.
Devices
may need a template that they provide to assist this that might be
queried by the schema or held in an internet repository perhaps.
We
have also discussed electronic schema repositories too. As you
can
envisage there's quite a few issues to think through and that is partly
why it hasn't been an easy one to tackle. I
do expect that BSC will
provide a good basis for this schema , especially if you include the
unofficial 'choice' device type. A range type device will likley
be
needed to indicate that an allowable parameter value might be between
say -10 and +212 or requires two decimal places.<br>
<br>
Having said all the above and probably frightened you a little with the
scope of this configuration schema I think everyone recognises that we
need progress and we should tackle small areas and provided we do that
in a well thought through and architected manner we can evolve
it.
Something is better than nothing. Instance naming can be tackled as a
subset provide it implements a flexible mechanism useful for other
aspects of the config schema ie a general parameter recover/rename
model. Likely early on it will remain as a non 'xap' schema
however
until we pull the whole xAPconfig schema together. <br>
<br>
The answer is 'yes' to all the questions in your last paragraph .
There are a couple of people who have tackled this area before and one
in particular I think you should chat with ... I'll get them to contact
you either here or offlist.<br>
<br>
K<br>
<br>
<br>
On 17/03/2010 12:20, Neil Wrightson wrote:
<blockquote
cite="mid:4F849B88B9F6486CA19B70CF88392F62@xxxxxxx"
type="cite">
<style type="text/css">
<!--
/* start of attachment style */
.ygrp-photo-title{
clear: both;
font-size: smaller;
height: 15px;
overflow: hidden;
text-align: center;
width: 75px;
}
div.ygrp-photo{
background-position: center;
background-repeat: no-repeat;
background-color: white;
border: 1px solid black;
height: 62px;
width: 62px;
}
div.photo-title
a,
div.photo-title a:active,
div.photo-title a:hover,
div.photo-title a:visited {
text-decoration: none;
}
div.attach-table div.attach-row {
clear: both;
}
div.attach-table div.attach-row div {
float: left;
/* margin: 2px;*/
}
p {
clear: both;
padding: 15px 0 3px 0;
overflow: hidden;
}
div.ygrp-file {
width: 30px;
valign: middle;
}
div.attach-table div.attach-row div div a {
text-decoration: none;
}
div.attach-table div.attach-row div div span {
font-weight: normal;
}
div.ygrp-file-title {
font-weight: bold;
}
/* end of attachment style */
-->
</style>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<meta name="GENERATOR" content="MSHTML
8.00.6001.18876">
<div><span class="666035411-17032010"><font
size="2"
face="Arial">Kevin,</font></span></div>
<div><span
class="666035411-17032010"></span> </div>
<div><span class="666035411-17032010"><font
size="2" face="Arial">Your
statement - </font></span><span
class="666035411-17032010"><font
size="2" face="Arial">"<font
size="3" face="Times New Roman">You are
totally free to add your own additional parameters within BSC blocks
and to create your own schema classes (as long as they don't start with
the three reserved letters 'xap' as in xapbsc.cmd) so there's no
restriction to what you're trying to do - it would be just nice to get
it adopted in a formalised
way.</font>"</font></span></div>
<div><span
class="666035411-17032010"></span> </div>
<div><span class="666035411-17032010"><font
size="2" face="Arial">Has
me puzzled.</font></span></div>
<div><span
class="666035411-17032010"></span> </div>
<div><span class="666035411-17032010"><font
size="2" face="Arial">
<div><span class="666035411-17032010"><font
size="2" face="Arial">From
the bible it states "<font size="3" face="Times New
Roman">Standard
classes can be identified through the use of the reserved prefix
xap-.... <class> Identifies the collection of schema
applicable
to this message. <type> Identifies the sub-schema applicable
to
this message. </font>"</font></span></div>
<div><span
class="666035411-17032010"></span> </div>
<div><span class="666035411-17032010"><font
size="2" face="Arial">Wouldn't
a class that renames instances or end points be a standard
class?</font></span></div>
</font></span></div>
<div><span
class="666035411-17032010"></span> </div>
<div><span
class="666035411-17032010"></span><span
class="666035411-17032010"></span><span
class="666035411-17032010"><font
face="Arial"><font size="2">What restrictions
are there on the naming
of classes? On the xAP wbesite there are lots of schemas that have a
class of xap***** whatever. I.e. "</font><font
size="2">class =
xap-x10.request</font><font size="2">",
"<font size="3"
face="Times New Roman">Class=xAP-<font
size="2">INetConnect.Dialup</font></font>",
"</font><font
size="2">Class=xAP-Audio.Transport"</font></font></span></div>
<div><span
class="666035411-17032010"></span> </div>
<div><span class="666035411-17032010"><font
size="2" face="Arial">Given
that I'm trying to come up with a way of changing the instance name and
the end point names. What would you suggest as a class name convention
that specifically spelt out what the user is to
use?</font></span></div>
<div><span
class="666035411-17032010"></span> </div>
<div><font size="2" face="Arial"><span
class="666035411-17032010">Do
you think that one class should be created for performing the renaming
of any instance, end point, TSC? </span></font></div>
<div><font size="2" face="Arial"><span
class="666035411-17032010">Should
it also be cable of changing the UID of the
instance?</span></font></div>
<div class="Section1">
<p><span style="font-family: Arial; font-size:
10pt;">Regards,</span>
</p>
<p><b><span style="font-size: 13.5pt;">Neil
Wrightson.</span></b> <br>
<b><i><span style="font-size:
13.5pt;">N.W.Electronics</span></i></b>
<br>
<span style="font-size: 10pt;">ABN 76 768 513
867</span> <br>
<span style="font-family: Arial; font-size: 10pt;">Embedded
Controllers and Home Automation Products</span> <br>
Skype : <span class="SpellE">Neil_Wrightson</span>
<br>
<span style="font-family: Arial; font-size:
10pt;">Web
:</span><u>
<span style="color: blue;"><a
class="moz-txt-link-abbreviated" href="http://www.nwe.net.au";>www.nwe.net.au</a></span></u>
</p>
</div>
<div> </div>
<div width="1" style="color: white; clear:
both;"></div>
</blockquote>
<br>
<!-- **begin egp html banner** -->
<br>
<br>
<!-- **end egp html banner** -->
<div width="1" style="color: white; clear:
both;"/>__._,_.___</div>
<!-- Start Recommendations -->
<!-- End Recommendations -->
<!-- **begin egp html banner** -->
<img src="http://geo.yahoo.com/serv?s=97476590/grpId=9629476/grpspId=1705007709/msgId=2097/stime=1268843289";
width="1" height="1"> <br>
<!-- **end egp html banner** -->
<!-- **begin egp html banner** -->
<br>
<div style="font-family: verdana; font-size: 77%; border-top: 1px
solid #666; padding: 5px 0;" >
Your email settings: Individual EmailTraditional <br>
<a href="http://groups.yahoo.com/group/xAP_developer/join;_ylc=X3oDMTJmZG5wMnQ3BF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA3N0bmdzBHN0aW1lAzEyNjg4NDMyODk-";>Change
settings via the Web</a> (Yahoo! ID required) <br>
Change settings via email: <a href="mailto:xAP_developer-digest@xxxxxxx?subject=Email
Delivery: Digest">Switch delivery to Daily Digest</a> <a
href = "mailto:xAP_developer-fullfeatured@xxxxxxx?subject=Change
Delivery Format: Fully Featured">Switch to Fully Featured</a>
<br>
<a href="http://groups.yahoo.com/group/xAP_developer;_ylc=X3oDMTJkNHNxNm0zBF9TAzk3NDc2NTkwBGdycElkAzk2Mjk0NzYEZ3Jwc3BJZAMxNzA1MDA3NzA5BHNlYwNmdHIEc2xrA2hwZgRzdGltZQMxMjY4ODQzMjg5";>
Visit Your Group
</a>
<a href="http://docs.yahoo.com/info/terms/";>
Yahoo! Groups Terms of Use
</a>
<a href="mailto:xAP_developer-unsubscribe@xxxxxxx?subject=Unsubscribe";>
Unsubscribe
</a>
<br>
</div>
<br>
<!-- **end egp html banner** -->
<div style="color: white; clear:
both;"/>__,_._,___</div>
</body>
</html>
--------------040403040003040300060005--
xAP_Development Main Index |
xAP_Development Thread Index |
xAP_Development Home |
Archives Home
|