LISTSERV mailing list manager LISTSERV 16.0

Help for ZNG Archives


ZNG Archives

ZNG Archives


[email protected]


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

ZNG Home

ZNG Home

ZNG  January 2007

ZNG January 2007

Subject:

Re: SRU Version 1.2 draft specification

From:

"Edward C. Zimmermann" <[log in to unmask]>

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Fri, 26 Jan 2007 14:28:52 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (63 lines)

Quoting Mike Taylor <[log in to unmask]>:

> I do, but I am still sure this isn't correct.  Otherwise the XHTML document:
> 
> 	<xhtml>
> 	 <p>Hello</p>
> 	 <p>Goodbye</p>
> 	</xhtml>
> 
> Could be legitimately rendered as:
> 
> 	Goodbye
> 
> 	Hello


- Firstly, document representation and rendering are two different things and
should NEVER been confused with one another (that's the damnation of HTML
and its still broken descendants XHTML)
- Secondly, XHTML is not XML.
- In XML its the processing that applies interpretation. 
- The XHTML standard DOES appeal to a "document order". Not all XML is XHTML.
- The XML specification (have a close look) does not demand that element order
  be anything specific. A specification (or parser) can use their (its) own
  model to present siblings and "do the right thing". 
- Many XML processing specifications DO appeal to document order--- many
  derived from the Infoset.
- They are not always the same as some specifications define their own data
  models with their own set of rules for siblings.
- That XML does not specify the order was INTENT. This allows us to write
  specifications that can indeed require the order to matter and it to be
  alphabetical or geospatial or .. as per our needs and wants. 

In my football example (which I choose for YOU)

<item>Manchester United</item>
<item>Arsenal</item>
<item>Tottenham Hotspur</item>
<item>Liverpool</item>
<item>Aston Villa</item>

can indeed well be reported in the order in which they won Premiership titles
or alphabetically or .. If we don't set a specification then it could literally
be (according to the XML) anything. Each processing system can do what they
please or think is right (even if most will indeed return the siblings in
document order). Its specifications for the processing layer (what to do) that
may hammer things down.

Of course beyond all this we need to grasp that SRU/W is not just about XML
but is (or should be) intended for generic search inclusive of systems that
don't even have a (persistent) document model or a hierarchical model (trees,
forests of trees or even loops) that is not consistent with XML (even on a 
primitive level, see my talk of our concept of lines and sentences as an
example of overlapping content objects).

-- 
-- 
Edward C. Zimmermann, Basis Systeme netzwerk, Munich
Office Leo (R&D):
   Leopoldstrasse 53-55, D-80802 Munich,
   Federal Republic of Germany
http://www.nonmonotonic.net

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

July 2017
October 2016
July 2016
August 2014
February 2014
December 2013
November 2013
October 2013
February 2013
January 2013
October 2012
August 2012
April 2012
January 2012
October 2011
May 2011
April 2011
November 2010
October 2010
September 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
October 2009
September 2009
August 2009
July 2009
May 2009
April 2009
March 2009
February 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 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

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager