[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [obix-xml] Things I'd like to discuss at tomorrow's telecon.
I assume you are talking about tagging data (paths or opague ids). How are paths or opague strings not WS-Addressing compliant? I don't even see how tagging data has anything to do with WS-Addressing. What am I missing? Considine, Toby (Facilities Technology Office) wrote: >Shouldn't this be decided by strict compliance with WS-Addressing? This >sounds, to me, just like a classing Endpoint Reference (EPR) discussion. > >The relevant W3 spec, then, would be: >http://www.w3.org/2002/ws/addr/ > >A good current discussion: >http://www.iona.com/blogs/vinoski/archives/000140.html > >Although this one may be more relevant to us >http://www-106.ibm.com/developerworks/library/ws-address.html > >For the MS take on this, instead >http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnwebsrv/ht >ml/wsaddressdelta.asp > >And one of my favorites for oBIX, a discussion of the interaction of >WS-Eventing and ERPs > >http://www.gazitt.com/OhmBlog/PermaLink.aspx/7ee41401-4fde-446e-a746-101ea88 >c23aa > >tc >=================================================== >Toby Considine ! "There are seldom good >UNC Chapel Hill ! technological solutions to >Chapel Hill, NC ! behavioral problems." >Phone (919)962-9073 ! >Fax (919)962-1102 ! -- Ed Crowley >tobias@fac.unc.edu ! >=================================================== >-----Original Message----- >From: Aaron Hansen [mailto:ahansen@tridium.com] >Sent: Tuesday, February 22, 2005 10:46 AM >To: obix-xml@lists.oasis-open.org >Subject: [obix-xml] Things I'd like to discuss at tomorrow's telecon. > >Pathing >======== >- Isn't the need only to identify the root object for read/write operations? >If so, >- I don't think there is a need for pathing >- I'm leaning towards an opague "handle" which is the unique identifier. > > >Misc notes >========= >- Should ObjectReadType be ObjectType? >- Need default values for: > * DimensionType -> everything > * FacetsType -> resolution, precision, writable > * AlarmType -> inAlarm > * ReadReqType -> locale, depth >- How about ext element in IncludeType be a boolean? Think it would be >much easier. >- Shouldn't facets have trueText and falseText? >- Units: I still don't like unit refs. > * We don't have unit read operation. > * Which object holds the master unit? What if the client hasn't >read it yet? > * Id should be a unique unit identifier, the client can table on that. >- What is root? >- If read depth is 0, should more children be indicated? >- How about an object version? If used, this could be used to indicate >an object's facets have changed. > >I don't like depth >============= >- We'll end up double reading most objects during discovery (especially >if everyone uses depth 1 as I feel they will). Think about it. >- In my tests, a depth a 5 resulted in a massively large document. This >feature is dangerous. >- I think read should simply list children handles. > >Thanks, >Aaron > > > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]