Machine

Package: 
Extends: 
Is Abstract: 
no
Is Pattern: 
no
Definition: 

Mechanism or computer program used to implement a process.

Example: 
SAS program, photocopier
Property: 
NameCardinalityDatatypeDescription
typeOfMachine
0..1
The kind of machine used - software, web service, physical machine, from a controlled vocabulary
name
0..n
The name of the machine. A linguistic signifier. Human understandable name (word, phrase, or mnemonic) that reflects the ISO/IEC 11179-5 naming principles. If more than one name is provided provide a context to differentiate usage.
accessLocation
0..1
The locations where the machine can be access
function
0..n
The function of the machine
interface
0..n
Specified the machine interface. Supports the use of a controlled vocabulary.
ownerOperatorContact
0..1
Contact information for the owner/operator including location specification, address, URL, phone numbers, and other means of communication access. Sets of information can be repeated and date-stamped.
Relationship: 
Is extendable: 
Is property: 
0
RDF Mapping: 

Comments

a: we have tried to stay away from the generic "type" so "typeOfMachine"
b: above should be CodeValueType
c: we have specific means of capturing this information (see OtherMaterial) we should be consistent within DDI
d: If name and description are removed from abstract Agent they need to be added here.
f: there is nothing here that allows me any machine actionability...its only basic informative and not much of that.

jon's picture

There is an existing extended primitive SoftwareType, this should / could be used here, but what about other possible types?

changed type to typeOfMachine

Humans have contact details -- should we have something similar for machines? (like API, Service, Interface, etc.)?