[BYTEIO-WG] ByteIO Interop Document

[neil p chue hong]

I agree.

We should ensure we test all the ByteIO properties defined as RPs in the
WSRF rendering, but we should use the simplest mechanism to access them.

The only exception would be if you had a use case which needed a more
complex access mechanism, but I don't think we have any such use cases.

cheers,
neil 

> -----Original Message-----
> From: byteio-wg-bounces at ogf.org 
> [mailto:byteio-wg-bounces at ogf.org] On Behalf Of Mark Morgan
> Sent: 03 October 2006 16:32
> To: 'Mailing List for BYTEIO-WG'
> Subject: [BYTEIO-WG] ByteIO Interop Document
> 
> Ladies and Gentlemen,
> 
> On the telecon today, an issue was raised about the 
> interoperability document that needs to be addressed this 
> week if possible (via email if possible).  Basically, 
> everyone seems to agree that we need to get WSRF 
> ResourceProperties to test the properties that part part of 
> the ByteIO specification (getting the size of a ByteIO 
> resource, etc.).  However, I personally am of the opinion 
> that we should minimize the amount of non-ByteIO specific 
> mechanism that we test as our purpose is only to test ByteIO 
> and not WSRF.  That said, I think we should utilize the 
> simplist Resource Property operation, namely 
> GetResourceProperty, but not use other WSRF-RP operations 
> such as QueryResourceProperties and 
> GetMultipleResourceProperties.  I just don't feel like their 
> inclusion in our test serves any purpose beyond 
> interoperability testing of WSRF which isn't our goal.  Thoughts?
> 
> -Mark
> 
> --
> Mark Morgan
> Research Scientist
> Department of Computer Science
> University of Virginia
> http://www.cs.virginia.edu
> mmm2a at virginia.edu
> (434) 982-2047
> 
> --
>   byteio-wg mailing list
>   byteio-wg at ogf.org
>   http://www.ogf.org/mailman/listinfo/byteio-wg
>