| CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 08:33:18 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:44:51 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 08:33:18 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98cd030858fa9dfd
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=6uY9UGfVfc9CuN3sojsDtBc5Tgfns1HEnuX6g5UFPto-1760171598-1.0.1.1-S_h7db1T9BFA1b_Ve_QNz2STndofjH.tv4y_wTHu77yM.urgjbQmgIxmg1uYzEMLuZ4JVXdNvc5.qhO8LU8Yb0C_GHRf9FWKhGIuJIGleIw; path=/; expires=Sat, 11-Oct-25 09:03:18 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cd030858fa9dfd-BLR
alt-svc: h3=":443"; ma=86400
4.3.1: second scenario: should value constraint default to FIXED? from James Tauber on 2000-05-03 (www-xml-schema-comments@w3.org from April to June 2000)
4.3.1: second scenario: should value constraint default to FIXED?
- From: James Tauber <JTauber@bowstreet.com>
- Date: Tue, 2 May 2000 21:09:11 -0400
- To: "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
- Message-ID: <81A48CA1E953D211B11600A0C9E1C1B995B780@mail.bowstreet.com>
[back again :-)]
In 4.3.1, in the second scenario (where ref is absent and schema is not the
parent) the value of {value constraint} is given as "fixed" if the "use"
attribute is not "default".
In other words, if a value is given, but the use attribute is one of
"optional", "fixed" or "required", the value constraint is taken to be
"fixed".
Is this correct?
James
--
James Tauber
jtauber@bowstreet.com
Director XML Technology
Bowstreet www.bowstreet.com
Received on Tuesday, 2 May 2000 21:11:48 UTC