RE: [obix-xml] <id>

What about parametric writes?

Adjust all points with attributes matching *** to "on"

(of course, this would have to be built on a general parametric inquiry,
which might include parametric subscription)

To allow for multiple implimentations, I think there should be a full range
of parametric inquiries/subscriptions/writes, but that the inclusion of this
functionality in any Service would be optional.  This would imply, of
course, that each service have a flag "Parametric Inquiries Supported?"



-----Original Message-----
From: Aaron Hansen [mailto:] 
Sent: Tuesday, December 21, 2004 4:35 PM
To: Obix-Xml-Sc (E-mail)
Subject: [obix-xml] <id>

I think <id> should be a server-unique identifier.

What are the reasons for pathing?

1. To reference reusable ranges for enums.  There are other solutions such
as range id or the reference could simply be the <id> of range's object.

2. To write to non-unique id's.  See, non-unique id's introduce problems!
The current way write is documented already has to be changed for pathing,
it just doesn't work.  We should just eliminate nested writes, there is no
benefit over batch writes.

What else?  What am I missing?