OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [xri] FW: [chairs] status of mass doc import


XRI'rs (and Mike in particular):

I hereby nominate the OASIS pain point described by Karl Best below as the
"modal" XRI use case for Persistence and Semantic Mapping. I don't think
there's a better example of the the need for maintaining persistent pointers
to online resources such as specification documents. In addition, the
long-running thread between OASIS chairs regarding TC document naming
conventions that Karl refers to is a similarly archetypal example of the
need for semantic mapping from reassignable XRIs to permanent XRIs.

=Drummond 

-----Original Message-----
From: Karl Best [mailto:karl.best@oasis-open.org]
Sent: Wednesday, March 12, 2003 3:01 PM
To: chairs@lists.oasis-open.org
Cc: Jeff Lomas
Subject: [chairs] status of mass doc import

I've had a couple people ask me about the status of the mass import of
documents into the doc repository.

We had the folks at Kavi grab all of the docs in the ftp directories a
couple of days ago, so those docs are all in the repository now. They
didn't realize that we have a lot of docs that are elsewhere too, so not
all of the TCs' docs have been imported yet.

During this process we've been realizing even more than before that we
need to be very careful about preserving current URLs. Messages such as
the one from Norm have reminded us how very important this is. There's
about 10,000 docs total, and most of them have internal links to other
docs, so there's a *lot* of URLs that need to continue to work.

Our original plan was to import the docs into the repository, then
gradually replace the original docs with redirects that would point from
the original URL to the new repository location. After some more
thinking on this we're not comfortable that this is the best solution.
We want to take advantage of the doc repository functionality,
specifically the integration into the other TC functionality and
notification to TC members when a new doc is checked in, etc. but we
can't break the existing URLs. Perhaps the repository should just store
pointers to the docs which would continue to reside in their original
location. We've also got to integrate the new doc naming scheme, which
many of you have discussed on this list, into the entire doc storage scheme.

Until we've come up with a complete solution that we're all happy with
we're going to leave all of the current docs in their current location
with their current URLs, in addition to importing them into the
repository. If any (two or three) of you would like to work with us to
help figure out a good long-term solution I would appreciate your advice.

-Karl


=================================================================
Karl F. Best
Vice President, OASIS
office  +1 978.667.5115 x206     mobile +1 978.761.1648
karl.best@oasis-open.org      http://www.oasis-open.org


----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]