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: RE: [xri] FW: [chairs] status of mass doc import


Add to your list the need for the community to manage revisions and versions
of repository objects as well as the need to append metadata to the objects
to facilitate searching and I think it about covers most of the requirements
of XRIs. What better than to answer the problems of your own community?

How would we identify the major stakeholders?

Marc

> -----Original Message-----
> From: Wachob, Gabe [mailto:gwachob@visa.com]
> Sent: Thursday, March 13, 2003 4:42 PM
> To: Marc LeMaitre; Drummond Reed
> Cc: XRI List (E-mail)
> Subject: RE: [xri] FW: [chairs] status of mass doc import
> 
> I really think that we're a little premature to suggest we have an answer
> that OASIS can roll out now. Maybe in 6 months if we do our jobs really
> well. Certainly can't hurt collecting input on this now.
> 
> It does make, potentially, a really good use case.
> 
> I think this is part of a larger use case dealing with
> registry/repositories
> where there things (e.g. docs, schema, published subjects) that need to be
> widely identified and for which identifiers will not change over time (but
> for whom physical location may change or may be "multiple"). The
> identifier
> in this case must be resolvable. Very similar in this regard to the main
> use
> case of handle and doi.
> 
> I would NOT suggest using the chairs list as it gets WAAAY to much volume
> and this sort of discussion would only increase that. I'd suggest those
> interested in pursuing this approach individuals in/around Oasis to
> discuss
> further.
> 
> 	-Gabe
> 
> > -----Original Message-----
> > From: Marc LeMaitre [mailto:Marc.LeMaitre@onename.com]
> > Sent: Thursday, March 13, 2003 1:34 PM
> > To: Drummond Reed
> > Cc: XRI List (E-mail)
> > Subject: RE: [xri] FW: [chairs] status of mass doc import
> >
> >
> > I like it, or at least I think I do because I don't fully
> > understand what is
> > needed in order to completely address the community's problems.
> >
> > How would we get a handle (no pun) on the full set of issues?
> >
> > Marc
> >
> > > -----Original Message-----
> > > From: bill washburn [mailto:bill.washburn@xns.org]
> > > Sent: Thursday, March 13, 2003 1:22 PM
> > > To: Drummond Reed
> > > Cc: XRI List (E-mail)
> > > Subject: Re: [xri] FW: [chairs] status of mass doc import
> > >
> > > Drummond and all--
> > >
> > > Please forgive me, yet I cannot resist the urge to suggest
> > strongly that
> > > while
> > > it is a fine idea to call the OASIS pain point a modal use
> > case, I really
> > > believe there is a far more singular opportunity that ought to be
> > > recognized.
> > > Which is to say, Karl has just pitched to the XRI TC a
> > huge, fat softball
> > > that
> > > could be hit out of the park as a home run -- so to speak.
> > But the home
> > > run
> > > opportunity is not just to address the OASIS problem abstractly,
> > > intellectually,
> > >
> > > semantically, technically, etc.  The home run is to take
> > this issue on
> > > fully,
> > > practically, pragmatically, politically, socially, and in
> > every other way
> > > necessary so that the pain is gone, the problem eliminated, and the
> > > solution is,
> > >
> > > well, completely done.  Maybe I'm just completely wrong,
> > and yet it seems
> > > apparent that OASIS needs not a perfectly compelling analysis and
> > > description of
> > >
> > > the solution to their problem, they need all of the messy
> > and tricky real
> > > world
> > > work done so that the problem is non-existent.  To me, that
> > is the true
> > > opportunity before us.
> > >
> > > cheers,
> > >
> > > Bill
> > >
> > > Drummond Reed wrote:
> > >
> > > > 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]