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


Help: OASIS Mailing Lists Help | MarkMail Help

chairs message

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

Subject: Re: [chairs] latest draft of doc mgmt system requirements

My read on "command line" was something like cvs.exe, a command line client to the source control system.


On Mar 1, 2004, at 2:57 PM, Breininger, Kathryn R wrote:

Instead of "command line interface" do you mean something like an
"advanced search" feature? Most registry/repository systems have a
"simple search" which would allow searching on keywords and also some
small subset of the metadata. An advanced search feature is frequently
developed for power users, and allows searching on all or nearly all
metadata, Boolean searching, ranging, ranking, etc. and is usually part
of the web-based user interface, but may appear on a separate search
page, as the search form will be more complex.

I may be misreading this, but it is there some confusion between these
statements under "Multiple file types supported":
"TCs must be able to store both source (e.g. MSWord, XML, or HTML)
and compiled (e.g. PDF) versions of each file. The repository should
have some means to connect two different files (e.g. foo3.htm and
foo3.pdf are different representations of the same file); the user can
upload and associate all formats in a single operation. "
and the last statement:
"* Publishing (convert to PDF or HTML) upon checkin"
The first two statements seem to indicate the TC is uploading multiple
format versions (which could create version problems) while the last two
statements (in italics) seem to indicate that one file is uploaded, and
then it is converted by the system to multiple formats. I would think
the preference would be for the later - upload one file, and let the
system convert it and provide access to each available format.

Kathryn Breininger
OASIS ebXML Registry TC Chair

-----Original Message-----
From: Furniss, Peter [mailto:Peter.Furniss@choreology.com]
Sent: Friday, February 27, 2004 5:00 PM
To: karl.best@oasis-open.org; Chairs OASIS
Cc: jeff.lomas@oasis-open.org
Subject: RE: [chairs] latest draft of doc mgmt system requirements

Lots of useful features covered.

I wasn't quite sure what "command line interface" meant. Where is the
command line entered ?

Would this allow a script running remotely to submit a document via some
reasonably-tractable protocol
(the right way to do this is as a webservice, but let's not run too fast
:-). It's a great convenience to be able to upload an
automatically-generated file (like an issues list) with a local command
(bpel list is ftp'ed to the "working copy", off-oasis location on
average twice a day, and by hand/web i/f to oasis once a week.

Peter Furniss

* User interface
- Repository has a web interface for uploading and tree browsing,
searching, and retrieval. Support for all major browsers.
Intuitive UI
should require little or no user documentation.
- Repository has command line interface for power users; this
interface will have the same access control and restrictions on
permissible actions, etc. as the web interface.
- Search/retrieval
- Files may be found via search and by tree browsing
- Search by any of the metadata fields
- Full-text search of contents (except for binary formats)
- Listing of single files in browsing and search
results includes
the metadata fields. The listing for packages includes the list of
single files in the package, then drill down for information
on those files.

Matthew MacKenzie
Senior Architect
Adobe Systems Canada Inc.
+1 (506) 871.5409

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