RE: Canonical Path and Path Filter proposed specificatrion

[Matthew MacKenzie <matt@xmlglobal.com>]

Farrukh,

This is great, but you might want to change every occurrence of XPATH in
the document to PATH.  XPATH implies much more than simple traversal.

<rant relevance="medium">
Why on earth wasn't "ClassificationScheme" represented in a way that
made use of XML's inherent capability of displaying context?  For
example:

<ClassificationScheme id="1" name="Geography">
	<ClassificationNode id="1" name="North America">
		<ClassificationNode id="2" name="Canada">
			<ClassificationNode id="10" name="British
Columbia">
				<ClassificationNode id="2" name="Lower
Mainland">
					<ClassificationNode id="2"
name="Vancouver" />
					<ClassificationNode id="3"
name="Richmond" />
				</ClassificationNode>
			</ClassificationNode>
		</ClassificationNode>
	</ClassificationNode>
<ClassificationNode>

It seems as though XPATH-like is all the rage now, why not the data
representation as well? 

</rant>						

Matthew MacKenzie
XML Global Technologies, Inc.


-----Original Message-----
From: Farrukh Najmi [mailto:Farrukh.Najmi@Sun.COM] 
Sent: September 27, 2001 11:03 PM
To: regrep-query@lists.oasis-open.org
Subject: Canonical Path and Path Filter proposed specificatrion

Team,

Per action item from previous team meeting I have attached an initial
proposal for your consideration and discussion in tomorrows meeting.
Dan, please send logistics for tomorrows meeting ASAP as I will be off
site and off the net during the meeting and most of the day.

--
Regards,
Farrukh