| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 05:48:40 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:28:48 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 05:48:40 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98cc11e12f66d817
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=2ykVozqHNANqng.lHouFYDoppAn_1xL.vkZWT8DYGOo-1760161720-1.0.1.1-fTLEspPQhU0F0HhmrVlM37V_qmEstZXoRcBdxjUt6.r12Nbpm.sGnbjzdjEI_89nbzLr5I0ksBcMq_qovk.mJvJFDo9NrVctfkR_1slPXYI; path=/; expires=Sat, 11-Oct-25 06:18:40 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cc11e12f66d817-BLR
alt-svc: h3=":443"; ma=86400
WS-Addressing 1.0 Core -- Notational conventions not explained from Anish Karmarkar on 2005-05-12 (public-ws-addressing-comments@w3.org from May 2005)
WS-Addressing 1.0 Core -- Notational conventions not explained
- From: Anish Karmarkar <Anish.Karmarkar@oracle.com>
- Date: Wed, 11 May 2005 21:05:24 -0700
- To: public-ws-addressing-comments@w3.org
- Message-ID: <4282D604.4040902@oracle.com>
WS-Addressing 1.0 Core [1] in sections 2.1 and 3 use notational conventions such as: [address] : IRI (mandatory) Where the part after the ":" is the 'type' of the property and the paranthetical part specifies the cardinality. Section 1.1 (that explains the notational convention) says that it uses the same notational convention as Infoset when describing the abstract data models. Infoset does not use the convention that is used in Core. This new notational conventions should be explained in section 1.1. -Anish -- [1] https://www.w3.org/TR/2005/WD-ws-addr-core-20050331/
Received on Thursday, 12 May 2005 07:05:33 UTC