xml1-wire-devel

[Xml1-wire-devel] 1-wire tagging use case

[Byron K. A. <b.k...@ie...>]

In email between Sean Kelly and I, Sean came up with a use case for 1-wire
tagging which should have gone out on this list but didn't (my fault, typo
on address). anyway here it is. Comments?

"Developer provides an XML file conforming to the 1-wire
tagging DTD to the tagging API. From that, the tagging
library constructs a series of objects using classes
specified in the file associated with 1-wire devices. The
API provides methods for developer to retrieve the set of
objects created."

[Xml1-wire-devel] small xml parsers for CDLC Java

[Bruce B. <bb...@sy...>]

This site: http://www.ericgiguere.com/microjava/cldc_xml.html

Has some comments about small xml parsers as applied to the Palm.

- Bruce


-----------------------------------------
           WWW.SYSTRONIX.COM
 Fast 8051s, embedded Java and much more
 new! 8x1-Wire I/O board for 1-Wire nets
  +1-801-534-1017  Salt Lake City, USA
-----------------------------------------

[Xml1-wire-devel] Tagging scenarios

[Sean K. <ke...@ad...>]

Folks:

To try to focus my thoughts on requirements, I'm trying
to come up with some actual scenarios where tagging
information is useful.  Here are a few basic ones
... what do you think?

Application: DS2406's arranged on a small bus in a
digital video server used to toggle control points in
diagnostic mode.

Software control needs to determine what DS2406 to
toggle based on what control point it's connected to.
It looks up in its storage that I/O board A's TP3 is
controlled by switch 12.00.01.1a.30.11.5f.  It
instructs the busmaster to match and toggle the switch.

The mapping here is from object-to-device.

Application: DS18S20's in long bus on arranged
throughout a building.

Software control performs an alarming device search,
and one DS18S20 appears.  It maps the device ID
10.00.00.5f.a3.20.6c to the thermometer in office
number 5 on level 3, and takes appropriate action.

The mapping here is from device-to-object.

In both cases, the tagging ties a device to a rather
unique object; a board identifier and test point in one
case, a room number and floor number in another.

Defining the metadata for these kinds of bindings won't
be easy since they're so application-specific.  I'm
almost tempted to say that tagging schema should be
completely generic instead.  Consider:

<!-- A bus consists of zero or more devices -->
<!ELEMENT bus (device*)>

<!-- A device has an ID and a maps to an object -->
<!ELEMENT device (id, object)>

<!-- A device has an attribute that indicates its type.
     This is redundant since the ID has the family code
     which also indicates the type. -->
<!ATTLIST device type (switch | thermometer | memory | serialNum |
dualSwitch) #REQUIRED)>

<!-- A device ID, the syntax is 8 hexadecimal numbers -->
<!ELEMENT id (#PCDATA)>

<!-- A serialized Java object, encoded in base-64 -->
<!ELEMENT object (#PCDATA)>

Giving documents that look like this:

<bus>
  <device type="switch">
    <id>12.00.01.1a.30.11.5f</id>
    <object>6ejoa*1had...</object>
  </device>
  <device type="switch">
    <id>12.00.01.29.35.08.cd</id>
    <object>koi=ijfe12...</object>
  </device>
  ...

In the alarming temperature case, mapping the device ID
to a serialized Java object is particularly powerful
because the object can be the thing responsible for
taking action on adjusting the temperature in that
particular room.  No other knowledge is needed in
tagging software.

But this doesn't solve the reverse mapping problem in
the first scenario.

Thoughts?

--Sean

RE: [Xml1-wire-devel] Requirements

[Byron K. A. <b.k...@ie...>]

I suppose I will take a stab at starting to address some of these questions.

> For example, what exactly constitutes a tag?

This is a very good question, without even going into the functional part of
the question. For the sake of terminology, does tag refer to the a file that
describes the entire 1-wire network, or is it some portion of that file?

> Is it merely a binding between a 1-wire address and an
> arbitrary object?

I think that this would define the minimal tag. However, a relatively simple
tag would bind an object to a set of 1-wire addresses, and in more
sophisticated cases, tagging would also define relationships between
objects.

[Xml1-wire-devel] Requirements

[Sean K. <ke...@ad...>]

Folks:

I'd like to firm up what the requirements are for
tagging.  I've got my own ideas of what I'd like to see
out of a tagging API, and those are probably different
from others' (I came into the 1-wire world for home
automation).

For example, what exactly constitutes a tag?  Is it
merely a binding between a 1-wire address and an
arbitrary object?  Or are the contraints on the tag?
If so, what's the metadata of the object?  What's the
lifetime of the binding?  What constitutes a cluster?
Is there a relationship between stems, branches,
trunks, and busses to clusters, and should that
information be captured and managed?

Answering these questions can help lead to a set of use
cases, nonfunctional requirements, and the XML DTD.
And, groan if you must, that's something that's
important to document.  (Don't worry: I enjoy
documentation.)  I think Byron's got some interesting
ideas captured in his initial DTD, and that's got my
wheels turning (I'm normally asleep at this time after
all), but creating an information schema without
understanding its requirements means you can paint
yourself into a corner later.

--k

--
Sean Kelly
Independent Consultant
Java / XML / Etc.

[Xml1-wire-devel] examples

[Byron K. A. <b.k...@ie...>]

I just downloaded XML Spy and started playing with it. I figured I would
construct a partial straw-man DTD and possible XML file for 1-wire tagging.
It seems likely that we won't be using DTD's but I though I would post this
for the sake of discussion. I am very new to XML so there might be gross
errors in my understanding. Anyway, this is my initial vision of how XML
tagging might look. Is this at all on the right track? Or am I way off?

Byron K. Appelt
Universal Vinculum Inc.
http://www.vinculum.com


<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE OWCluster SYSTEM "C:\My Documents\1-wireTag.dtd">
<OWCluster>
	<ClusterRev>1</ClusterRev>
	<ClusterNum>06BE6912</ClusterNum>
	<Description>1-Wire Weather Station</Description>
	<ManufacturerCode>000000</ManufacturerCode>
	<Manufacturer>Dallas Semiconductor</Manufacturer>
	<Enum>20</Enum>
	<SecondsSince1970>936029523</SecondsSince1970>
	<OWSensor>
		<OWNetAddress>B20000000033CF1D</OWNetAddress>
		<AccessMethod>
			<AM_TEMPERATURE_1820/>
		</AccessMethod>
	</OWSensor>
</OWCluster>

<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XML Spy v3.0.7 (http://www.xmlspy.com) by Byron K. Appelt
(Universal Vinculum Inc.) -->
<!ELEMENT Manufacturer (#PCDATA)>
<!ELEMENT AccessMethod (AM_TEMPERATURE_1820 | AM_SWITCH_2406)>
<!ELEMENT SecondsSince1970 (#PCDATA)>
<!ELEMENT Enum (#PCDATA)>
<!ELEMENT AM_TEMPERATURE_1820 EMPTY>
<!ELEMENT AM_SWITCH_2406 EMPTY>
<!ELEMENT ManufacturerCode (#PCDATA)>
<!ELEMENT OWNetAddress (#PCDATA)>
<!ELEMENT ClusterRev (#PCDATA)>
<!ELEMENT ClusterNum (#PCDATA)>
<!ELEMENT ChannelState (#PCDATA)>
<!ELEMENT ChannelMask (#PCDATA)>
<!ELEMENT InitState (#PCDATA)>
<!ELEMENT Description (#PCDATA)>
<!ELEMENT OWCluster (ClusterRev, ClusterNum, Description?,
ManufacturerCode?, Manufacturer?, Enum?, SecondsSince1970?, OWSensor*)>
<!ELEMENT OWSensor (OWNetAddress, AccessMethod, ChannelMask?, ChannelState?,
InitState?, Description?)>

RE: [Xml1-wire-devel] Tiny Java parser for XML

[David S. <dav...@da...>]

Also see NanoXML:
http://nanoxml.sourceforge.net/
Brian Hindman has successfully run this on TINI.

Dave

********************************************************
* David Smiczek
* Software Product Manager - Auto Information
* Dallas Semiconductor
* mailto:dav...@da...
* http://www.ibutton.com
********************************************************

> -----Original Message-----
> From: xml...@li...
> [mailto:xml...@li...]On Behalf Of Bruce
> Boyes
> Sent: Thursday, November 02, 2000 1:27 AM
> To: xml...@li...
> Subject: [Xml1-wire-devel] Tiny Java parser for XML
> 
> 
> Here's a project to develop a tiny (not tini) parser for XML, written in
> Java. Might be useful to us, I haven't looked at the code.
> 
> http://members.tripod.de/xmltp/
> 
> - Bruce
> -----------------------------------------
>            WWW.SYSTRONIX.COM
>  Fast 8051s, embedded Java and much more
>  new! 8x1-Wire I/O board for 1-Wire nets
>   +1-801-534-1017  Salt Lake City, USA
> -----------------------------------------
> _______________________________________________
> Xml1-wire-devel mailing list
> Xml...@li...
> http://lists.sourceforge.net/mailman/listinfo/xml1-wire-devel
> 

[Xml1-wire-devel] Tagging Basics?

[Bruce B. <bb...@sy...>]

http://www.systronix.com/1wire/tagging/tagging.htm has an attempt at
explaining what tagging is. I just made this up, borrowing heavily from the
"Dave and Chris" Dallas papers. Corrections and additions welcome.

- Bruce
-----------------------------------------
           WWW.SYSTRONIX.COM
 Fast 8051s, embedded Java and much more
 new! 8x1-Wire I/O board for 1-Wire nets
  +1-801-534-1017  Salt Lake City, USA
-----------------------------------------

[Xml1-wire-devel] Tiny Java parser for XML

[Bruce B. <bb...@sy...>]

Here's a project to develop a tiny (not tini) parser for XML, written in
Java. Might be useful to us, I haven't looked at the code.

http://members.tripod.de/xmltp/

- Bruce
-----------------------------------------
           WWW.SYSTRONIX.COM
 Fast 8051s, embedded Java and much more
 new! 8x1-Wire I/O board for 1-Wire nets
  +1-801-534-1017  Salt Lake City, USA
-----------------------------------------

[Xml1-wire-devel] 1-wire tagging SourceForge Project page

[Byron K. A. <b.k...@ie...>]

The SourceForge area for the Java 1-wire tagging project is active(Active in
the sense that it works, not that theres actually any activity yet). The URL
is:

http://sourceforge.net/projects/xml1-wire

Byron K. Appelt
Universal Vinculum Incorporated
http://www.vinculum.com

[Xml1-wire-devel] test

[Byron K. A. <b.k...@ie...>]

test message

[Xml1-wire-devel] test

[Byron K. A. <b.k...@ie...>]

this is a test message.