RE: [obix-xml] Metadata

["Aaron Hansen" <ahansen@tridium.com>]

Title: Metadata

I looked further into WS-Metadata and this is what I came away with:  It ties together the independant specifications used by a service.  For example, learning about a service's security policy.  This would be very useful to an oBIX implementor.  However, it really doesn't have anything to do with us referencing other services from within our service.  It looks as if the focus should be on WS-Addressing or rolling our own.

 

The real issue is what do we want to do with service references.  In my opinion, we are developing a reusable discovery service for other services and a way to tie together best-of-breed services for a building(s).

 

-----Original Message-----
From: Doug Ransom [mailto:Doug.Ransom@pwrm.com]
Sent: Wednesday, September 22, 2004 12:41 PM
To: OBIX XML
Subject: [obix-xml] Metadata

If our goal for next meeting is to think about how we convey point or object metadata and it might be used for reflection-like services, I think it is useful to note the following are available on most platforms that support XML and Web Services:

• APIs to process XML Schemas, RelaxNg Schemas, and WSDL to create data structures and objects that can be invoked (as opposed to simply validation)
• Schematron implementations, which can be used to express constraints about data that XML Schema or WSDL cannot
• XPATH, which a lot of web service specs seem to mention
• XSLT
  

and we discussed WS-Metadata earlier today.

I think it is helpful to be familiar with all of these technologies so we can map them onto use cases or take ideas from them as appropriate.

Doug Ransom
Energy Analytics Domain Expert
Power Measurement
2195 Keating Cross Road
Saanichton, BC, Canada  V8M 2A5
Tel: (250) 652-7100  ext. 7558
Fax: (250) 652-0411
E-Mail: mailto:doug.ransom@pwrm.com
Website: http://www.pwrm.com
 
ION®  smart energy everywhere™