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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ZNG Home

ZNG Home

ZNG  December 2007

ZNG December 2007

Subject:

Re: Say NO to mandatory Atom Feeds

From:

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

Reply-To:

SRU (Search and Retrieve Via URL) Implementors

Date:

Thu, 6 Dec 2007 13:59:39 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (139 lines)

On Thu, 6 Dec 2007 11:07:32 +0000, Dr R. Sanderson wrote
>
> There's going to be a LOT of boiler plate text just for the alleged
> advantage of using this spec.

I agree!

> In the end, it's going to look like:
>
> <entry>
> <id>Unknown-[timestamp]</id>
> <author>Unknown</author>
> <title>Unknown</title>
> <updated>Unknown</updated>
> <rights>Unknown</rights>
> <content>
> <sru:record>
> <sru:recordIdentifier>123455</sru:recordIdentifier>
> <sru:recordFormat>xml</sru:recordFormat>
> <sru:recordData> [data here] </sru:recordData>
> ...

When it looks good and well behaved..


> I have yet to see where the baby is in this bath?
>
> > ATOM 1.0 is an IETF standard and has mass market adoption because of its
> > simplicity and extensibility.
>
> XHTML is a much more widely adopted standard. Hence I propose that
> we should instead treat this as a micro-format or profile of XHTML.

Why not SUTRS.. Its widely adopted and simple! :-)

>
> > I am sure that we can find quite a handful of warts in the current SRU
> > response format (e.g. lack of even an option if author etc.)
>
> There's space for arbitrary metadata in extraRecordData and
> extraResponseData. We can't predict what metadata will be available
> or useful, so we don't try to mandate anything.

And they all can be extended...

> > Frankly I see missing these important attributes (particularly id) in an
> > information management context to be sacrilege. Having
> > these as required may be over kill but is is certainly better then underkill.
>
> SRU 1.2 has recordIdentifier. Or did you mean 'important'
> attributes like <title> and <author> of non bibliographic data?
>
> >> Or ... we could just say NO to mandatory ATOM.
> > This whole thread has taken a negative and adversarial stance towards ATOM
> > starting with its title and tone. Why?
>
> Personally, because I haven't seen any advantage in specifically
> using ATOM, and a lot of disadvantages. The only alleged advantage
> is that it's better understood (I debate the point, given the number
> of different semantics for the mandatory <id> element so far) and
> that the tools will deal with it natively, which I also debate given
> that we're going to have a lot of template text and then a bunch of
> namespaced elements that the tools will never have seen before.

Correct. As to "well understood"? We harvest Atom feeds and while most are
a bit better than their RSS cousins they too seem to have a high level of
non-compliance---- most driven by the manner they are produced in their
PHP-MySQL-CMS blogwares.

>
> > No spec is perfect. ATOM is only going to be better, more in demand and more
> > ubiquitous over time.
>
> Then lets wait until then before we make it the /mandatory and
> default/ response type. I'm happy with it being an /option/ just
> not mandatory and not the default one.

Agree. (I'm in shock that I would agree so much in full with Rob on anything)..

-----------------------------
Cinderella
Jacob and Wilhelm Grimm

Excerpt:

The two sisters were happy to hear this, for they had pretty feet. With her
mother standing by, the older one took the shoe into her bedroom to try it on.
She could not get her big toe into it, for the shoe was too small for her.
Then her mother gave her a knife and said, "Cut off your toe. When you are
queen you will no longer have to go on foot."

The girl cut off her toe, forced her foot into the shoe, swallowed the pain,
and went out to the prince. He took her on his horse as his bride and rode
away with her. However, they had to ride past the grave, and there, on the
hazel tree, sat the two pigeons, crying out:

  Rook di goo, rook di goo!
  There's blood in the shoe.
  The shoe is too tight,
  This bride is not right!

Then he looked at her foot and saw how the blood was running from it. He
turned his horse around and took the false bride home again, saying that she
was not the right one, and that the other sister should try on the shoe. She
went into her bedroom, and got her toes into the shoe all right, but her heel
was too large.

Then her mother gave her a knife, and said, "Cut a piece off your heel. When
you are queen you will no longer have to go on foot."

The girl cut a piece off her heel, forced her foot into the shoe, swallowed
the pain, and went out to the prince. He took her on his horse as his bride
and rode away with her. When they passed the hazel tree, the two pigeons were
sitting in it, and they cried out:

 Rook di goo, rook di goo!
 There's blood in the shoe.
 The shoe is too tight,
 This bride is not right!

He looked down at her foot and saw how the blood was running out of her shoe,
and how it had stained her white stocking all red. Then he turned his horse
around and took the false bride home again.

"This is not the right one, either," he said. "Don't you have another daughter?"

---------------

RSS or Atom are obviously the wrong daughters!


--

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