LISTSERV mailing list manager LISTSERV 16.0

Help for XML-L Archives


XML-L Archives

XML-L Archives


XML-L@LISTSERV.HEANET.IE


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

XML-L Home

XML-L Home

XML-L  February 2001

XML-L February 2001

Subject:

Re: Question about multiple XML documents

From:

Adam Kaupisch <[log in to unmask]>

Reply-To:

General discussion of Extensible Markup Language <[log in to unmask]>

Date:

Thu, 15 Feb 2001 08:45:23 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (105 lines)

Thanks a lot, your help is greatly appreciated and has cleared up a few
things that I was unsure of!

Thanks again

Adam

-----Original Message-----
From: John E. Simpson [mailto:[log in to unmask]]
Sent: Wednesday, February 14, 2001 4:03 PM
To: [log in to unmask]
Subject: Re: Question about multiple XML documents


At 02:06 PM 02/14/2001 -0700, Adam Kaupisch wrote:
>...What if I have 2 files which just contain properties.
>
>example:
>file 1:
><?XML version="1.0"?>
><data x="0"></data>
><data y="0"></data>
>
>file 2:
><?XML version="1.0"?>
><data a="1"></data>
><data b="2"></data>
><foo bar="asdf"></foo>

Some nits to pick :)... first, the "XML declaration (that's the first line
of each of your files above) must be lowercase.

Second, those name-value pairs do look like properties, but they're
actually called "attributes" in an XML context. (That's just so you don't
shoot yourself in the foot on a less forgiving mailing list. :)

Third, for these files to be legitimate XML there *must* be a "wrapper"
element in each one. Under the wrapper you can have as many or few
sub-branches as you want, but XML doesn't permit you to declare that your
one document tree has two trunks (in the case of file 1) or three trunks
(in the case of file 2).

Of course that's not to say that you *must* use legitimate XML document
structure to solve this or any other problem... only that if you want to
leverage XML tools, resources like this mailing list :), etc., then you do
need to put a wrapper in each one, even if it's just a placeholder.

>but, I want to include file 1 into file 2. That is, when viewed, I would
>simply see output from file 2 as:
>
><?zml version="1.0"?>
><data x="0"/>
><data y="0"/>
><data a="1"/>
><data b="2"/>
><foo bar="asdf"/>
>
>note that I don't want to have a wrapper around it like the "roottag"
below,
>I simply want it to list.

(Same nit as above... you must have a "roottag," of that or any other name.)

>That way if I were to go into file 1 and change
>x=0 to x=1 it would propogate to file 2 when file 2 was displayed. In this
>case I am simply working with property files and want to pull the
properties
>from some root file into another file(s) so I can keep all common data in 1
>file but when viewing the sub files (file 2, etc) it looks seemless and as
>if file 1 didn't exist (i.e. when viewed no one would know the wiser that a
>file 1 existed unless they were editing it)
>
>does this make sense?

Well... sort of. I mean, I think I know what you're asking. But XML files
are just text files with no inherent "display" properties. If you're using
an XML-aware application of some kind -- maybe a smart XML authoring tool
-- it might have the effect that you're seeking, but there's nothing
preventing someone from opening up the document with a plain old text
editor (short of operating system security measures, all that). It's kind
of like saying that you want to build a Web page in HTML, but you don't
want "View Source" available, you want just to allow the user to see the
formatted  results.

In general, what you want to do sounds like it can be done using the
entity-reference solution I provided before, as long as you use a "wrapper"
element in the including document. Again, though, if someone simply opens
the including document with a text editor, they won't "see" the included
document; they'll see the including one and the entity reference (e.g.
&root; or whatever you call it). The inclusion is a *logical* one which
will be understood (and perhaps made to seem "physical") by XML-aware
software, not a true physical one, nor a logical one which appears physical
in a non-XML context (such as a text editor).

>I'm still new to xml so my ability to express what I
>am thinking might be sweked ;)

It's okay; newcomer questions welcomed. Nonetheless, for the moment, I'd
agree that your thinking may indeed be sweked!


================================================================
John E. Simpson          | "Is it weird in here, or is it just
http://www.flixml.org    | me?" -- Steven Wright
XML Q&A: www.xml.com     |

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

February 2017
August 2016
June 2016
March 2016
January 2016
July 2014
April 2014
January 2014
July 2013
February 2013
September 2012
August 2012
October 2011
August 2011
June 2011
January 2011
November 2010
October 2010
July 2010
June 2010
March 2010
February 2010
January 2010
November 2009
September 2009
August 2009
July 2009
May 2009
March 2009
December 2008
October 2008
August 2008
May 2008
March 2008
February 2008
January 2008
December 2007
October 2007
August 2007
June 2007
March 2007
January 2007
December 2006
September 2006
July 2006
June 2006
April 2006
February 2006
January 2006
November 2005
September 2005
August 2005
July 2005
June 2005
May 2005
March 2005
January 2005
October 2004
August 2004
July 2004
June 2004
May 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002
January 2002
December 2001
November 2001
October 2001
September 2001
August 2001
July 2001
June 2001
May 2001
April 2001
March 2001
February 2001
January 2001
December 2000
November 2000
October 2000
September 2000
August 2000
July 2000
June 2000
May 2000
April 2000
March 2000
February 2000
January 2000
December 1999
November 1999
October 1999
September 1999
August 1999
July 1999
June 1999
May 1999
April 1999
March 1999
February 1999
January 1999
December 1998
November 1998
October 1998
September 1998
August 1998
July 1998
June 1998
May 1998
April 1998
March 1998
February 1998
December 1997
November 1997
October 1997

ATOM RSS1 RSS2



LISTSERV.HEANET.IE

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager