| CARVIEW |
Select Language
HTTP/2 200
date: Wed, 08 Oct 2025 08:04:07 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:51 GMT
cache-control: max-age=2592000, public
expires: Fri, 07 Nov 2025 08:04:07 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98b4202499c7c1ce
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=TkDFrb56MiOegA1KjASay9c5os9d38JqwSRXy1pm7rk-1759910647-1.0.1.1-G9.DHv5MjvhvGe2brqR_3a108Jp9YNHNT4yFHpaLv6JFudhoS4kb3z8KVZer0JYXZ3ANkkto8Jxvl.YzjqBVAeWLeK3ytt2WGbCAEPhPlP0; path=/; expires=Wed, 08-Oct-25 08:34:07 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98b4202499c7c1ce-BLR
alt-svc: h3=":443"; ma=86400
updated draft to put F&P in more places from Sanjiva Weerawarana on 2004-06-25 (www-ws-desc@w3.org from June 2004)
updated draft to put F&P in more places
- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Fri, 25 Jun 2004 23:29:55 +0600
- To: <www-ws-desc@w3.org>
- Message-ID: <064b01c45ada$17d482f0$e7794109@LANKABOOK>
I've updated the draft per the telecon decision yesterday to put F&P in a few more places. Please review. https://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html I note (with disgust) that we're severly discriminating against Interface Fault components and Binding Fault components by not allowing them to contain F&P (properties). Poor suckers. One comment about ordering of F&P and other elements within their parent elements: we seem to be a bit inconsistent about what order these can appear w.r.t. their siblings. I'd appreciate if someone could check that careful and make a recommendation for a consistent approach. Sanjiva.
Received on Friday, 25 June 2004 13:31:52 UTC