[cddlm] FW: BOUNCE cddlm-wg at ggf.org: Non-member submission from ["Savas Parastatidis" <Savas.Parastatidis at newcastle.ac.uk>]

[Milojicic, Dejan S]

-----Original Message-----
From: owner-cddlm-wg at ggf.org [mailto:owner-cddlm-wg at ggf.org] 
Sent: Friday, January 21, 2005 5:09 AM
To: owner-cddlm-wg at ggf.org
Subject: BOUNCE cddlm-wg at ggf.org: Non-member submission from ["Savas
Parastatidis" <Savas.Parastatidis at newcastle.ac.uk>] 

>From owner-grdfm-cddlm-wg at mailbouncer.mcs.anl.gov  Fri Jan 21 07:08:52
2005
Return-Path: <owner-grdfm-cddlm-wg at mailbouncer.mcs.anl.gov>
X-Original-To: grdfm-cddlm-wg at mailbouncer.mcs.anl.gov
Delivered-To: grdfm-cddlm-wg at mailbouncer.mcs.anl.gov
Received: from localhost (localhost.localdomain [127.0.0.1])
	by mailbouncer.mcs.anl.gov (Postfix) with ESMTP id B183A12C78
	for <grdfm-cddlm-wg at mailbouncer.mcs.anl.gov>; Fri, 21 Jan 2005
07:08:52 -0600 (CST)
Received: from mailbouncer.mcs.anl.gov ([127.0.0.1])
	by localhost (mailbouncer.mcs.anl.gov [127.0.0.1]) (amavisd-new,
port 10024)
	with ESMTP id 31528-04 for
<grdfm-cddlm-wg at mailbouncer.mcs.anl.gov>;
	Fri, 21 Jan 2005 07:08:50 -0600 (CST)
X-Greylist: delayed 351 seconds by postgrey-1.16 at
mailbouncer.mcs.anl.gov; Fri, 21 Jan 2005 07:08:49 CST
Received: from cheviot2.ncl.ac.uk (cheviot2.ncl.ac.uk [128.240.234.82])
	by mailbouncer.mcs.anl.gov (Postfix) with ESMTP id DBEBC12C74
	for <cddlm-wg at ggf.org>; Fri, 21 Jan 2005 07:08:49 -0600 (CST)
Received: from largo.campus.ncl.ac.uk (largo.ncl.ac.uk [128.240.238.3])
	by cheviot2.ncl.ac.uk (8.12.11/8.12.10) with ESMTP id
j0LD2RQb020377;
	Fri, 21 Jan 2005 13:02:35 GMT
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: WS-Addressing to drop Reference Properties
Date: Fri, 21 Jan 2005 13:02:29 -0000
Message-ID:
<37E80E80B681A24B8F768D607373CA8001BA7246 at largo.campus.ncl.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: WS-Addressing to drop Reference Properties
Thread-Index: AcT/tCZ7YnpbY+6bTu6DP6Y16Dj8FAABRbLA
From: "Savas Parastatidis" <Savas.Parastatidis at newcastle.ac.uk>
To: "Steve Loughran" <steve_loughran at hpl.hp.com>,
	"CDDLM" <cddlm-wg at ggf.org>
X-Newcastle-MailScanner-Information: Please contact
Postmaster at newcastle.ac.uk for more information
X-Newcastle-MailScanner: Found to be clean
X-Newcastle-MailScanner-From: nsp20 at cpx.ncl.ac.uk
X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at
mailbouncer.mcs.anl.gov

Actually,

I don't think this is going to be a problem for WSRF. WS-Addressing
Reference Parameters are still there so they could be used instead of
Reference Properties. It's just that the semantics have changed now.

Also, I don't think that this was a result of my efforts. It was mostly
the Web folks.

Regards,
--
Savas Parastatidis
http://savas.parastatidis.name
=20

> -----Original Message-----
> From: Steve Loughran [mailto:steve_loughran at hpl.hp.com]
> Sent: Friday, January 21, 2005 12:24 PM
> To: CDDLM
> Cc: Savas Parastatidis
> Subject: WS-Addressing to drop Reference Properties =20 =20  
>Interesting development over in W3C land: WS-Addressing no longer has  
>reference properties, thanks to the unrelenting efforts of  
>Savas-the-subversive, and others:
> http://www.w3.org/2002/ws/addr/wd-issues/#i001
>=20
> This is interesting because the current "modeling stateful resources  
>with web services" paper says "a WS-Resource qualified endpoint puts
its
> state identifier in the wsa:ReferenceProperties element". Now it
can't;
> the state identifier has to be encoded in the URL itself, as with 
> classic stateful URLs like IMdB movie links, RDF identifiers, etc,
etc.
> So wsa is more aligned with W3C and less with WSRF.
>=20
> This is not really our problem, we just have to make sure that we use

>terms like "WS-Resource qualified endpoint" without specifying what
that
> exactly that means, and wait for the WS-RF definitions to catch up. It

>actually has a nice side-effect operations wise; as all EPRs are now  
>just URLs, you can always paste the URL into a web browser and get a  
>status page, 404 error, whatever -but something that is good when  
>fielding remote bug reports.
>=20
> I dont know what the implications for the WSDL are, =20  -Steve =20 
>=20 =20