Hi Bruce,
Thanks much for the update! I had been wondering and within a heartbeat
of dropping the project, but this encouragement is keeping me active.
How do you think RSS will impact the user interface? For example, a
section in one of the links you provided indicates that RSS could impact
the search and retrieval functionality:
There are, however, secondary uses for such a syndication service --
that is, to provide access to archival issues resident within a feed
repository. The hierarchical storage arrangements for archival issues
suggest that one possible resource discovery mechanism might be to
have feeds of feeds whereby a feed for an archival volume of issues
would syndicate the access URIs for the feeds of the respective issues
contained within that volume.
This arrangement could even be propagated up the hierarchy whereby a
subscription year for a given serial might contain the feed URIs for
the volumes within that year, or that a serial feed might contain the
feed URIs for the subscription years for that serial.
Any comments? And given the issues for implementation, is the intended
functionality stable enough to move ahead with some UI design?
Martha
Subject:
update
From:
"Bruce D'Arcus" <[EMAIL PROTECTED]>
Date:
Wed, 14 Sep 2005 13:25:12 -0400
To:
[email protected]
To:
[email protected]
Hi all,
List has been dead for awhile, so just a quick update.
David is away in the Outback for a long vacation. Before he left, he
and I rattled some cages at Sun out of sheer frustration with the lack
of communication we were getting about plans going forward. I've
gotten a tentative response back today which is -- if not entirely
reassuring -- at least suggests we're headed in the right direction.
In a nutshell, we need Sun to do some low-level changes to make it
easy to do the things we want to do. Those changes are going to be
made in the context of a more comprehensive OOo strategy to deal with
embedded content. As Oliver Specht explained their perspective on this:
The outcome was that the bibliographic text field (the reference) will
be imported into a generic field that provides a DOM tree containing
anything inside of the bib-citation. Other in-paragraph content would
also be loaded into such a field. The Writer doesn't need to know
anything about the semantics of the contained elements.
The data-to-service linkage that is necessary for the Writer to find the
right service to manipulate the data has to be done using some kind of
registry.
I think this is a good direction because it ties the fate of citation
stuff to a larger effort at OOo. But that will take some broader
planning and implementation work that will take time. It also cannot
happen (or even be planned) before they finish with the 2.0 release.
I will also be working on a proposal to upgrade the file level support
some more in OpenDocument. We already had the citation proposal
accepted. We now need to figured out the bibliographic metadata
picture and the styling issue.
More information when I have it, but one issue that we're going to
have to return to is the format: whether it's MODS, or something
else. I've grown a little uncomfortable with standardizing on MODS.
Bruce
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
