Joe,
I don't know how Gary will respond, but I googled around a bit and I think that
the main thing to keep in mind is that the knowledge involved is not at all
necessarily _theoretical_ knowledge. It could be practical facts about who sits
where, what's their phone number, who's in charge of what, who reports to whom,
etc. Then it could be facts about their work groups or departments, etc. Who to
call about what, all the facilities info. The knowledge system might be a
corporate intranet with all kinds of info that people can think of. Then there
are the locations of the various service centers, how many at each, and so on.
Even a glossary of departmental terms & lingo. This knowledge needs to be kept
updated.
When I worked at a major corporation, I developed, maintained, and continually
updated & distributed a hardcopy one-page "knowledge system" with at least 50
different fonts, crammed with all the secretarial (aka "administrative") and
facilities info anybody could possibly want, an immense amount, and this saved
around 60 secretaries & hundreds of others lots of work & frustration. Between
the tasks of getting all that info right (because I hated every experience in
which I had spent excessive time to get wrong info, so I wanted it right for
_everybody_) and the MS-Word formatting challenges down to tiny spacings and
crashing serifs, -- well, it was the right combination for me, I actually was
almost "stakhanovist" for a while, and worked largely unsupervised on my
self-generated projects and on presentations for all askers for a good year & a
half. But all good things.... And that's already ancient times now. Intranets
have come on big and by now I'm sure they're much more powerful.
Or the knowledge system could be the distilled practical knowledge of skilled
auto mechanics for all kinds of cars, trucks, etc., turned into a program
that's like a superglorified Help button, and which auto mechanics everywhere
could buy. It would be updatable, too.
The knowledge system could be a medical diagnosis system, software with the
distilled knowledge of diagnosticians, and kept updated.
It could be an online system of listing of real estate properties for sale or
rent, with lots of attendant info plust photos, continually updated, and
searchable by many kinds of criteria, etc. It would allow searching for nearest
local schools, searching on real estate agents, etc. Many a business purpose
will end up with custom-designed software.
It could be customer information and that's a big deal these days! It could be
information about online behavior.
That corporate intranet becomes a way to manage the extranet (interface with
clients/customers). Then one can allow people to find out about programs, to
fill out applications, etc. And the management and improvement of the extranet
is an intranet capability.
As systems get interconnected, maybe the sky's the limit as people figure out
ways for diverse systems to query one another.
Best, Ben
----- Original Message -----
From: "Joseph Ransdell" <[EMAIL PROTECTED]>
To: "Peirce Discussion Forum" <peirce-l@lyris.ttu.edu>
Sent: Saturday, March 25, 2006 3:38 PM
Subject: [peirce-l] Re: Conceptual Structures Tool Interoperability Workshop
Gary:
I am wondering what is meant by a "knowledge system"? Is it the same thing
as an accepted theory about this or that subject-matter? If so why not just
call it a theory? But I doubt that that is what is meant. I know that
people are now hired by corporations and by universities in particular as
being "knowledge management" experts, but I never have been able to figure
out what there is to manage about knowledge. Is that what you are talking
about when you talk about knowledge systems: batches of knowledge owned by
a corporation and put to work in producing some goods or services? Or is it
just something like keeping track of patents owned?
Joe Ransdell
----- Original Message -----
From: "Gary Richmond" <[EMAIL PROTECTED]>
To: "Peirce Discussion Forum" <peirce-l@lyris.ttu.edu>
Sent: Saturday, March 25, 2006 11:40 AM
Subject: [peirce-l] Conceptual Structures Tool Interoperability Workshop
Conceptual
Structures Tool Interoperability Workshop
Conceptual Structures
Tool Interoperability Workshop
Final CfP: CS-TIW 2006 Conceptual Structures
Tools Interoperability Workshop (deadline 9 April)
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
List, Some here might be interested in this CS Tool Interoperability
Workshop (btw, I'll be delivering the keynote). GR
-------------------------------------------------------------------------
*** Call for Papers ***
Conceptual Structures Tool Interoperability Workshop (CS-TIW 2006)
In conjunction with the 14th International Conference on Conceptual
Structures (ICCS 2006)
July 16, 2006, Aalborg University,Denmark
-------------------------------------------------------------------------
Many tools have been developed in the Conceptual Structures community to
model, represent and reason about conceptual structures like Conceptual
Graphs, Formal Concepts, and related formalisms. However, such tools in
isolation are not sufficient to build comprehensive, effective knowledge
systems useful to communities and organizations. To this purpose, these
tools need to be able to interoperate with other conceptual tools and
information technologies. The goal of this workshop is to explore how to
improve this interoperability of conceptual structures tools.
=== Themes
To explore this goal, the workshop will have three main themes:
. Interoperability Requirements
What types of applications do conceptual structures tools have in real
world knowledge systems and systems development methodologies? What
requirements do these applications impose on conceptual structures tools?
What breakdowns occur in actual application practice? What (ad hoc or more
systematic) solutions have been developed to deal with these problems?
. Knowledge Systems Architectures
What components do effective knowledge systems have? What is the role of
conceptual structures tools in these systems? How to conceptualize
knowledge systems interoperability in terms of standard information
systems and software engineering methodologies? What architectural
principles should guide knowledge systems design and implementation?
. Interoperability Standards
What are the most relevant official and de facto standards affecting
conceptual structures tools interoperability? How should these standards
inform knowledge systems design? How to evaluate the standards in
practical knowledge system implementation? How can practical
interoperability experiences inform the standards setting process?
=== Topics
Topics to be addressed in the submissions, include, but are not limited
to:
. Interoperability conceptualization
. Requirements analysis
. Software integration and configuration
. Tool interfaces
. Web services
. Architectures
. Converters and wrappers
. Documentation
. Software engineering principles
. Open source methodologies
. Standards (official and de facto)
. Usability
. Evaluation methods
. Benchmarking
. Organizational issues (including intellectual property rights)
=== Submission Details
Both contributions with a theoretical and a practical focus welcome.
Papers are limited to 14 pages in Springer's LNCS format. For more details
see
http://www.springer.de/comp/lncs.
Please submit your paper through http://extra.shu.ac.uk/cs-tiw2006. In
case you have any problems with the submission, or for any other
questions, please contact the workshop chairs at
[EMAIL PROTECTED], or through their individual e-mail addresses.
Papers will be reviewed for adherence to the workshop scope and quality by
the chairs and additional reviewers. Accepted papers will be published in
a separate ISBN-numbered proceedings by Aalborg University Press. If
accepted, the paper must be presented at the workshop.
In addition to the papers, a CD with tools, data, documentation and other
relevant material will be made available. Authors are encouraged to
provide such material with their accepted submissions.
=== Dates
. Paper submission deadline: Sunday, April 9, 2006
. Acceptance notification: Wednesday, May 10, 2006
. Paper final version due: Sunday, May 28, 2006
. Additional CD materials due: Sunday, June 25, 2006
. Workshop: Sunday, July 16, 2006
=== Invited Speaker
"Philosophy Meets Design"
. Gary Richmond, City University of New York, USA:
=== Program Chairs
. Aldo de Moor, STARLab, Vrije Universiteit Brussel, Belgium
([EMAIL PROTECTED])
. Simon Polovina, Sheffield Hallam University, UK ([EMAIL PROTECTED])
. Harry Delugach, University of Alabama in Huntsville, USA
([EMAIL PROTECTED])
==========================================================================
---
Message from peirce-l forum to subscriber [EMAIL PROTECTED]
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.3.1/292 - Release Date: 3/24/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.3.1/292 - Release Date: 3/24/2006
---
Message from peirce-l forum to subscriber [EMAIL PROTECTED]
---
Message from peirce-l forum to subscriber archive@mail-archive.com
