CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 18:28:30 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: Mon, 10 Nov 2025 18:28:29 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98d06ae65dcdb22e
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=Nl1b_NCXGs4JISMNQN1wq67.rHdhQe2IKHPsEwO4DEE-1760207310-1.0.1.1-AakqjmVxxw5cDIKoDx0bWu7k_9fOb6ZdGujSpB_fONcgukf3pKNiv8x013mBB5BTBLDgBqbXwhR6nUpvUjDyWGWi_5wHW.bRG5qtXY59rDg; path=/; expires=Sat, 11-Oct-25 18:58:30 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98d06ae65dcdb22e-BLR
alt-svc: h3=":443"; ma=86400
An observation on XML schema limitation from ALEXANDRU,MARIUS (HP-Romania,ex1) on 2000-10-06 (www-xml-schema-comments@w3.org from October to December 2000)
An observation on XML schema limitation
- From: ALEXANDRU,MARIUS (HP-Romania,ex1) <marius_alexandru@hp.com>
- Date: Fri, 6 Oct 2000 16:27:57 +0200
- To: fallside@us.ibm.com
- Cc: www-xml-schema-comments@w3.org
- Message-ID: <C7773A81764BD4118A2100D0B747AC377AEF62@tell.gva.hp.com>
Hi, I apologize for this mail but I want to present you a strong limitation of Schema model comparing with the entity-relationship model that maybe could be considered at your meetings regarding the xml-schema draft. Suppose that you have to entities : <entity name="a" id="a"> ... </entity> <entity name="b" id="b"> ... </entity> and a relationship Rab(a,b) between the two entities : <relation name="Rab"> <role name="has-a" occurs="0,n"/> <entity idref="a"/> </role> <role name="has-b" occurs="0,n"/> <entity idref="b"/> </role> </relation> In my opinion, the E-R model (I don't used an exact formalism to describe it in the above example) can allow us to produce the following valid XML productions: Valid Production 1: <a> <Rab> <!-- we have to include also the rolename here too--> <b> ... </b> <b> ... </b> <b> ... </b> </Rab> </a> Valid Production 2: <b> <Rab> <!-- we have to include also the rolename here too--> <a> ... </a> <a> ... </a> <a> ... </a> </Rab> </b> Valid Production 3: <Rab> <!-- we have to include also the rolename --> <a> ... </a> <b> ... </b> </Rab> <!-- or another description that allow us to introduce more couples on a single <Rab>...</Rab> chunk. So as you can see the XML Schema definition (at www.w3.org) don't allow us to produce all the productions that the E-R model could provide. In fact the problem is more important that this : the tree (xml) structure its in itself a very constraintfull syntax (so a lot of patterns have to be specified (like the already existing : sequence,conjuction,disjunction etc..) in order to give more flexibility of this strong syntax. Also, I cannot imagine a good XML-Query definition that will depend so strongly on the Syntax in which the data are presented. I also think that this limitation will affect the IT industry for a long period of time since now (please take this last sentence not so serious as it seems, but in any case is my opinion) Thanks for your time and Best regards, Marius
Received on Friday, 6 October 2000 10:28:16 UTC