em shared vocabulary

I am finally jotting down some definitions of the terms used in the
framework document/diagram, to append to the final report, and as the basis
for shared vocabulary work among different teams. I face a series of
disparate and difficult issues, I may follow up with a few emails to request
inputs on specifics

This is forcing me to take a closer look at the latest version of the draft,

http://www.w3.org/2005/Incubator/eiif/XGR-framework-20090220/

and I have some questions/comments that come up

 I am looking at some of the notes regarding the DOLCE conceptualization of
our framework, and I wonder how much of these notes should be reflected in
our vocabulary, and how much should not be (whereby the description of the
conceptualization is not relevant to the actual meaning of the term)

for example

**
re. DOLCE definitions
*ServiceService, in a concrete sense, can be seen as a Process, i.e. a
perdurant (event) whose temporal parts may have different qualities (e.g.
agreement, delivery, and conclusion). By looking at the attributes of the W3
class, however, it seems that the concept aims at modelling abstract and
informative qualities such as Title and Description. To represent both
informative properties and spatial-temporal ones under DOLCE’s
conceptualization, Service might be split in two different classes:
“ServiceDescription” (InformationObject) and “ServiceProcess” representing
the concrete processes of service’s execution*.
I dont understand what ;'service' stands for , can someone provide some
examples?  for me service is the provision of a resource, or a capability
is that something else?  is it intended as 'emergency service is the
provision of emergency supplies?'


*Capability*

*Capability is used in W3 for representing the kind of actions Persons and
Organization should be able to perform. This should be represented in DOLCE
by an AbstractQuality (qualities inherent in non-physical endurants) whose
value should range over a suitable abstract region, to be introduced.
According to DOLCE, however, this would limit the ascription of (instances
of) this class to non-physical endurants.*


I dont' know about DOLCE, but capability is the ability to provide resource
(be it material supply or service , and which requires resources and
infrastructure)

Capability is directly related to resource availability, (not sure what you
mean by 'abstract' here)


cf.:

Originally a military term which includes the aspects of personnel,
equipment, training, planning and operational doctrine. Now used to mean a
demonstrable capacity or ability to respond to and recover from a particular
threat or hazard.
www.preparingforemergencies.gov.uk/more_info/glossary.shtm<http://www.google.co.uk/url?sa=X&start=6&oi=define&ei=-TnJSdTMOpDDjAe67f3FAw&sig2=JUYJ1Hbt3NQwnpZdwiAY7w&q=http://www.preparingforemergencies.gov.uk/more_info/glossary.shtm&usg=AFQjCNEk-oSR1nhceJFTRxg3lhfyuB-Apw>



*Resource*

*It is not immediately clear what Resource could be in terms of DOLCE
categories. The class looks like the union of three other classes Equipment,
People, and Fund. Intuitively, Resource stands for any concrete thing that
can be instrumental to the process of delivering a Service. It is
questionable, however, whether a specific class is really needed here. *


Again, I dont know from the ontologist viewpoint, but from the operational
viewpoint, resource is essential to the supply process,

I cannot see how we can get away with modelling/representing it

he 'categorization' of resources depends on the approach, they can be
grouped according to the functional/operational role (say medical resource
versus transport)  or material (medicine, food,) vs  intangible (know how,
skills, knowledge, experience, competence) and so on,

But it needs to be represented in any lexical, semantic and ontological
schema that revolves around the supply of resources  (or please explain
otherwise)


cheers

PDM

Received on Tuesday, 24 March 2009 20:13:08 UTC