OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] XML Schema views - are they possible?

[ Lists Home | Date Index | Thread Index ]
  • To: <xml-dev@lists.xml.org>
  • Subject: RE: [xml-dev] XML Schema views - are they possible?
  • From: "Cheng, Andy" <Andy.Cheng@ato.gov.au>
  • Date: Mon, 30 Aug 2004 09:25:23 +1000
  • Thread-index: AcSMfQgKeoBw67g3SiqyMofuyzrJ/ABoVPcA
  • Thread-topic: [xml-dev] XML Schema views - are they possible?

Title: Message
Hi All,
Thanks alot for your advice and comments. I'll give it a go and see what results I get.


    Andy Cheng
Australian Taxation Office
Software Development Quality & Productivity


-----Original Message-----
From: Bullard, Claude L (Len) [mailto:len.bullard@intergraph.com]
Sent: Saturday, 28 August 2004 07:28
To: 'DuCharme, Bob (LNG-CHO)'; 'xml-dev@lists.xml.org'
Subject: RE: [xml-dev] XML Schema views - are they possible?

That sounds right.   One point of view might be that namespaces are
best used where aggregation by namespaces is unavoidable, say
one is compounding languages into XHTML.  But just to support
the use of globals, that has the feel of too much factoring.  After
all, it's all Just ASCII, right? ;-)
Again, like those overwrought parameterized DTDs, I think
a clarity tradeoff might be better.   I do wonder if it might
have been better not to try to combine aspects of object types
AND relational techniques with some hidden objective of
producing a contract best filled by an object-oriented database.
Ah well... just another permathread.
-----Original Message-----
From: DuCharme, Bob (LNG-CHO) [mailto:bob.ducharme@lexisnexis.com]
Sent: Friday, August 27, 2004 4:18 PM
To: Bullard, Claude L (Len); 'xml-dev@lists.xml.org'
Subject: RE: [xml-dev] XML Schema views - are they possible?

>Did you address the problem of having multiple layers of abstraction and
>the use of global elements that forces one to use namespaces?  GJXDM
>is wrestling with this one.
My basic use case was a workflow in which an element or attribute that can't possibly exist at step 1 (e.g. an "arrived" date-time stamp on data sent from a supplier) is required at step 1 + x. We don't want to just declare it as being optional up and down the line; we want a validation process after step x to flag files missing this data.
The approach is to declare everything you'll ever need and identify where you need it in the central mother schema and then extract what you need for each step using the stylesheet. It should work in some cases in which the "views" do not necessarily describe the states of data in a sequential process, but that was the problem I was focused on. (We've got a lot of XML data moving through a lot of processes here.) I didn't try pushing it into a more generalized version of a "view" implementation, so, I'm not sure about dealing with the multiple layers of abstraction.


The information transmitted is for the use of the intended recipient only and may contain confidential and/or legally privileged material. Any review, re-transmission, disclosure dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited and may result in severe penalties. If you have received this e-mail in error please notify the Privacy Hotline of the Australian Taxation Office, telephone 13 28 69 and delete all copies of this transmission together with any attachments.


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS