CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 04:44:48 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:44:52 GMT
cache-control: max-age=2592000, public
expires: Sun, 09 Nov 2025 13:43:32 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98c68c1958011dfc
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: HIT
set-cookie: __cf_bm=OJx8saep3RI3MEEgAwSI3XLWcc1AbqQLkY.nAYj_1ZM-1760157888-1.0.1.1-iBmfV0vaEmCdWZv6fYUn9cTrxm77SlJ23B9H8_W_WqcWx4rJZQc0NIhRatywlEukr8o9Q_F5mDhI5H3NNo8sGSRJBjpchnIbHoec7fG7ncc; path=/; expires=Sat, 11-Oct-25 05:14:48 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cbb44ca86af473-BLR
alt-svc: h3=":443"; ma=86400
LC-149. extending: Provide guidance on extending schema for schem as? from Don Mullen on 2000-10-09 (www-xml-schema-comments@w3.org from October to December 2000)
LC-149. extending: Provide guidance on extending schema for schem as?
- From: Don Mullen <don@extensibility.com>
- Date: Mon, 9 Oct 2000 18:14:28 -0400
- To: "'Jane Hunter'" <jane@dstc.edu.au>
- Cc: "'www-xml-schema-comments@w3.org'" <www-xml-schema-comments@w3.org>
- Message-ID: <339902DC0E58D411986A00B0D03D84323D6292@EXTMAIL>
Dear Dr. Hunter and the MPEG-7 : The W3C XML Schema Working Group has spent the last several months working through the comments received from the public on the last-call draft of the XML Schema specification. We thank you for the comments you made on our specification during our last-call comment period, and want to make sure you know that all comments received during the last-call comment period have been recorded in our last-call issues list (<https://www.w3.org/2000/05/12-xmlschema-lcissues>). You raised two questions registered as issue LC-149: * Recommended extensibility mechanisms (e.g. XSL/XSLT?) so MPEG-7 can add additional attributes to the XML Schema specification and define their own constructs to satisfy MPEG-7-specific requirements; This additional information could be added to the <appinfo> tag of <annotation>. Note that <appinfo> can contain any elements. * The behaviour of an XML Schema valid parser in the case of an "unknown" (MPEG-7) tag and attribute in the schema specification. <appinfo> is defined in the schema for schema to have "lax" processing, so XML Schema valid parsers are will validate the information if possible. In 3.9: "lax : If the item, or any items among its [children] if it's an element information item, has a uniquely determined declaration available, it must be valid with respect to that definition, that is, validate where you can, don't worry when you can't." It would be helpful to us to know whether you are satisfied with this explaination. Regards, Don Mullen XML Schema Language Working Group
Received on Monday, 9 October 2000 18:17:40 UTC