This repository was archived by the owner on Oct 20, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4
Expand file tree
/
Copy pathCore.rdf
More file actions
2642 lines (2480 loc) · 175 KB
/
Copy pathCore.rdf
File metadata and controls
2642 lines (2480 loc) · 175 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rdf:RDF [
<!ENTITY bfo "http://purl.obolibrary.org/obo/">
<!ENTITY dcterms "http://purl.org/dc/terms/">
<!ENTITY iof-av "https://purl.industrialontologies.org/ontology/core/meta/AnnotationVocabulary/">
<!ENTITY iof-core "https://purl.industrialontologies.org/ontology/core/Core/">
<!ENTITY owl "http://www.w3.org/2002/07/owl#">
<!ENTITY rdf "http://www.w3.org/1999/02/22-rdf-syntax-ns#">
<!ENTITY rdfs "http://www.w3.org/2000/01/rdf-schema#">
<!ENTITY skos "http://www.w3.org/2004/02/skos/core#">
<!ENTITY xsd "http://www.w3.org/2001/XMLSchema#">
]>
<rdf:RDF xml:base="https://purl.industrialontologies.org/ontology/core/Core/"
xmlns:bfo="http://purl.obolibrary.org/obo/"
xmlns:dcterms="http://purl.org/dc/terms/"
xmlns:iof-av="https://purl.industrialontologies.org/ontology/core/meta/AnnotationVocabulary/"
xmlns:iof-core="https://purl.industrialontologies.org/ontology/core/Core/"
xmlns:owl="http://www.w3.org/2002/07/owl#"
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#"
xmlns:skos="http://www.w3.org/2004/02/skos/core#"
xmlns:xsd="http://www.w3.org/2001/XMLSchema#">
<owl:Ontology rdf:about="https://purl.industrialontologies.org/ontology/core/Core/">
<rdfs:label xml:lang="en">Core Ontology</rdfs:label>
<dcterms:abstract>The IOF Core Ontology contains terms and concepts found to be common across multiple domains of industry and represents an OWL implementation of them. The ontology itself utilizes the Basic Formal Ontology or BFO as a philosophical foundation but also imports terms from various domain-independent or "mid-level" ontologies. The purpose of the ontology is to serve or is intended to serve as a core for IOF's domain-specific ontologies, with a goal being to ensure consistency and interoperability across the suite of ontologies the IOF publishes.</dcterms:abstract>
<dcterms:contributor xml:lang="en">Elisa Kendall, Thematix Partners LLC</dcterms:contributor>
<dcterms:contributor xml:lang="en">Will Sobel, W. V. Sobel LLC</dcterms:contributor>
<dcterms:creator xml:lang="en">Chris Will, National Center for Ontological Research (NCOR)</dcterms:creator>
<dcterms:creator xml:lang="en">IOF Core Working Group</dcterms:creator>
<dcterms:license rdf:datatype="&xsd;anyURI">http://opensource.org/licenses/MIT</dcterms:license>
<dcterms:publisher xml:lang="en">Industrial Ontology Foundry</dcterms:publisher>
<dcterms:references rdf:resource="http://purl.org/dc/terms/"/>
<dcterms:references rdf:resource="http://www.w3.org/2004/02/skos/core#"/>
<dcterms:title>Industrial Ontology Foundry (IOF) Core Ontology</dcterms:title>
<owl:imports rdf:resource="http://purl.obolibrary.org/obo/bfo/2020/bfo.owl"/>
<owl:imports rdf:resource="https://purl.industrialontologies.org/ontology/core/meta/AnnotationVocabulary/"/>
<owl:versionIRI rdf:resource="https://purl.industrialontologies.org/ontology/core/20220506/Core/"/>
<owl:versionInfo>Version 1 Beta - 2022-05-06</owl:versionInfo>
<iof-av:copyright>Copyright (c) 2022 Open Applications Group</iof-av:copyright>
</owl:Ontology>
<rdf:Description rdf:about="&bfo;BFO_0000029">
<rdfs:comment>Even though site (physical location) always refers to a 3D space it is fine to define it practically just through 2D or 1D or 0D spatial region. For example when we want to talk about 2x2m area within a factory floor even though the space specified is 2D it is still ok to assert it as site as there is always the third dimension above the area that is implicit.</rdfs:comment>
<skos:example>location of a container, floor area in a factory building, location of a machine (relative to the coordinate of a factory floor), location on a shelf in a warehouse</skos:example>
<iof-av:synonym>physical location</iof-av:synonym>
</rdf:Description>
<rdf:Description rdf:about="&bfo;BFO_0000054">
<iof-av:synonym>realized in</iof-av:synonym>
</rdf:Description>
<rdf:Description rdf:about="&bfo;BFO_0000057">
<owl:propertyChainAxiom rdf:parseType="Collection">
<rdf:Description rdf:about="&bfo;BFO_0000117">
</rdf:Description>
<rdf:Description rdf:about="&bfo;BFO_0000057">
</rdf:Description>
</owl:propertyChainAxiom>
</rdf:Description>
<rdf:Description rdf:about="&bfo;BFO_0000063">
<iof-av:naturalLanguageDefinition>comes before (something) in time</iof-av:naturalLanguageDefinition>
</rdf:Description>
<owl:Class rdf:about="&iof-core;ActionSpecification">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:label>action specification</rdfs:label>
<rdfs:comment>1.Some of the items that may be contained within the action specification include:
- specifying the role (which may reflect the actions that a participant should do) that can inhere in a participant of the process
- specifying the types of participants in a process
2. Typically is part of a plan specification</rdfs:comment>
<skos:example xml:lang="en">Pour the contents of flask 1 into flask 2</skos:example>
<iof-av:adaptedFrom>http://www.obofoundry.org/ontology/iao.html</iof-av:adaptedFrom>
<iof-av:firstOrderLogicDefinition>InformationContentEntity(x) ∧ ∃p (Process(p) ∧ (prescribes(x,p)) → ActionSpecification(x)</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>information content entity that prescribes what participants shall do in a process</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>x is an Information Content Entity that prescribes some Process p implies x is an Action Specification</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>An action specification provide details about what an agent (person, group of persons or engineered system) should do to successfully realize a particular kind of process.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;Agent">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000040"/>
<rdfs:label>agent</rdfs:label>
<rdfs:comment>The IOF has elected to exclude material substances that may, at times, act like or are often referred to as agents, in that they realize some specific function that some person desires (e.g., platinum is a reducing agent in various reduction-type reactions -- as used in a catalytic converter to eliminate or reduce various pollutants in exhausts).
The IOF has at this time excluded other types of non-human agents, such as animals and other organisms (often referred to as biological agents).</rdfs:comment>
<rdfs:comment>When an organization is an agent, this is because one or more of the persons who are members of the organization (usually referred to an agency), realize its goals, objectives and plans.</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;EngineeredSystem">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;GroupOfAgents">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;Person">
</rdf:Description>
</owl:unionOf>
</owl:Class>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasRole"/>
<owl:someValuesFrom rdf:resource="&iof-core;AgentRole"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example>an employee; a transportation & logistics provider; a robot; a scheduling system</skos:example>
<iof-av:counterExample>1. Of physical and chemical in nature: Cleaning, vulcanizing, fluxing, indicator, sterilizing, emulisifying, refining.
2. Organisms: animals, cells, parts of organisms (organs, organelles, viruses).</iof-av:counterExample>
<iof-av:firstOrderLogicDefinition>Agent(x) ↔ (Person(x) ∨ GroupOfAgents(x) ∨ EngineeredSystem(x)) ∧ ∃y (AgentRole(y) ∧ hasRole(x,y))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>person, group of persons, or engineered system with an agent role</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Agent is a Person, Group Of Agents, or Engineered System when it 'has role' some Agent Role.</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>From the dictionary:
1. A person who acts on behalf of another person or group.
2. A person or thing that takes an active role or produces a specified effect.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;AgentRole">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000023"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;roleOf"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&bfo;BFO_0000040">
</rdf:Description>
<owl:Class>
<owl:complementOf rdf:resource="&bfo;BFO_0000024"/>
</owl:Class>
</owl:intersectionOf>
</owl:Class>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;actsOnBehalfOfAtSomeTime"/>
<owl:someValuesFrom>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;EngineeredSystem">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;GroupOfAgents">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;Person">
</rdf:Description>
</owl:unionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>agent role</rdfs:label>
<rdfs:comment>The IOF has elected to exclude material substances that may, at times, act like or are often referred to as agents, in that they realize some specific function that some person desires (e.g., platinum is a reducing agent in various reduction-type reactions -- as used in a catalytic converter to eliminate or reduce various pollutants in exhausts).
The IOF has at this time excluded other types of non-human agents, such as animals and other organisms (often referred to as biological agents).</rdfs:comment>
<skos:example>an employee; a transportation & logistics provider; material handler; scheduler</skos:example>
<iof-av:counterExample>Other types of agents we are not including at this stage are:
1. Those that are physical and chemical in nature: Cleaning, vulcanizing, fluxing, indicator, sterilizing, emulisifying, refining.
2. Organisms: animals, cells, parts of organisms (organs, organelles, viruses).
3. In computing: intelligent, artificial, mobile, & autonomous</iof-av:counterExample>
<iof-av:firstOrderLogicDefinition>AgentRole(x) → Role(x) ∧ ∃m ∃n ((MaterialEntity(m) ∧ ¬FiatObjectPart(x)) ∧ (Person(n) ∨ GroupOfAgents(n) ∨ EngineeredSystem(n)) ∧ actsOnBehalfOfAtSomeTime(m, n) ∧ roleOf(x,m))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>role that someone or something has when they act on behalf of a person, engineered system or a group of agents</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Agent Role x implies x is a 'role' that is the 'role of' a 'material entity' (that is not a Fiat Object Part) m when it 'acts on behalf of at some time' some Person or Group of Agents or Engineered System y</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;Algorithm">
<rdfs:subClassOf rdf:resource="&iof-core;PlanSpecification"/>
<rdfs:label>algorithm</rdfs:label>
<rdfs:comment>Algorithms considered under BFO are strictly mathematical or computer science algorithms. As such, any possible inputs or outputs of an algorithm must be of type IOF:Information Content Entity</rdfs:comment>
<skos:example>source, pseudo, or executable code for sorting data, flowchart for automatic control of a process</skos:example>
<iof-av:adaptedFrom>Information Artifact Ontology: http://purl.obolibrary.org/obo/IAO_0000064 and also the Common Core Ontology, http://www.ontologyrepository.com/CommonCoreOntologies/Mid/InformationEntityOntology</iof-av:adaptedFrom>
<iof-av:firstOrderLogicDefinition>PlanSpecification(x) ∧ ∃y(ComputingProces(y) ∧ prescribes(x,y)) → Algorithm(x)</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>plan specification that prescribes a computing process</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>x is a Plan Specification that 'prescribes' some Computing Process y implies x is an Algorithm</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>1. Plan specification that has an action specification as part that prescribes procedural or declarative (declarative in the sense of declarative programming) steps, which can be 1) translated to computer interpretable instructions and 2) concretized in a computing process
2.an informational entity that specifies the inputs and outputs of some mathematical function as well as workflow of execution for achieving a predefined objective [CCO; IAO]</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;Assembly">
<rdfs:subClassOf rdf:resource="&iof-core;MaterialArtifact"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasComponentPartAtAllTimes"/>
<owl:someValuesFrom rdf:resource="&iof-core;MaterialComponent"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">assembly</rdfs:label>
<rdfs:comment>An assembly can be a manufactured product or a component of a higher-level assembly, or both.</rdfs:comment>
<rdfs:comment>a component can also be a portion of material so if something has a component part it is not necessairly an assembly</rdfs:comment>
<skos:example>powertrain assembly; partially-assembled powertrain + transmission assembly lying nearby; driveshaft assembly temporarily disassembled for repair or routine maintenance; separator assembly consisting of variously-shaped separator parts that safeguard wine bottles in a case of wine during transport; a material artifact produced entirely through additive manufacturing (provided it is a component somewhere, and can it can be disassembled without damage/destruction).</skos:example>
<iof-av:counterExample>a portion of material, signle piece of glass, a bar, an aluminum roll, an engine block</iof-av:counterExample>
<iof-av:firstOrderLogicDefinition>Assembly(x) → MaterialArtifact(x) ∧ ∃c (MaterialComponent(c) ∧ hasComponentPartAtAllTimes(x,c))</iof-av:firstOrderLogicDefinition>
<iof-av:firstOrderLogicDefinition>MaterialArtifact(x) ∧ ∃p( AssemblyProcess(p) ∧ isSpecifiedOutputOf(x,p)) → Assembly(x)</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>material artifact that is composed of a number of material components that are physically connected together to realize a function and that can be disassembled later on</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Assembly x implies x is a Material Artifact and there is some Material Component c and x 'has component part at all times' c</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Material Artifact x that 'is specified output of' some Assembly Process p implies x is an Assembly</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>1. Material artifact composed of parts that are put together to realize a particular function as prescribed by some design, and in a manner whereby it can be later disassembled.
2. A group of subassemblies and/or parts that are put together and that constitute a major subdivision for the final product. An assembly may be an end item or a component of a higher level assembly [APICS].
3. A combination of parts, components [or] units that form a functional entity [ISO 10795].
4. A set of one or more sub-assemblies or components constituting a single end-use product [ISO/TS 21619].
5. A component or end item comprising of a number of parts or subassemblies put together to perform a specific function, and capable of disassembly without destruction [businessdictionary.com].</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;AssemblyProcess">
<rdfs:subClassOf rdf:resource="&iof-core;ManufacturingProcess"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasInput"/>
<owl:someValuesFrom rdf:resource="&iof-core;MaterialComponent"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasSpecifiedOutput"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Assembly">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasComponentPartAtAllTimes"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;MaterialComponent">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;isInputOf"/>
<owl:someValuesFrom rdf:resource="&iof-core;ManufacturingProcess"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">assembly process</rdfs:label>
<rdfs:comment>because the process like 3D printing can also produce an assembly, has specified output some assembly is not necesssary and sufficient condition for an assembly process</rdfs:comment>
<skos:example>Driving a lug nut to hold the wheel of a car in place; welding two metal parts into a single object; automated drilling and riveting of a skin panel operation during fuselage assembly;</skos:example>
<iof-av:counterExample>3D printing on an existing part (existing part + a pool of printing material -> new part) -- Note that the pool of material is an object before the process but becomes liquid (there is physical state change) during the "assembly" process.</iof-av:counterExample>
<iof-av:firstOrderLogicDefinition>AssemblyProcess(x) → ManufacturingProcess(x) ∧ ∃a, ∃c (Assembly(a) ∧ MaterialComponent(c) ∧ isInputOf(c,x) ∧ hasComponentPartAtAllTimes(a,c) ∧ hasSpecifiedOutput(x,a))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>manufacturing process in which a number of material components are physically connected to each other to form an assembly</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Assembly Process x implies x is a Manufacturing Process that 'has specified output' some Assembly a which 'has component part at all times' some Material Component c that 'is input of' x</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;BusinessIdentification">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:label>business identification</rdfs:label>
<rdfs:comment>Business identifications are typically managed by an official organization</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;InformationContentEntity">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;designates"/>
<owl:someValuesFrom rdf:resource="&iof-core;BusinessOrganization"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example>DUNS Number, CAGE Code, EIN, FIIN, BICID, DODAACID, SCACID</skos:example>
<iof-av:firstOrderLogicDefinition>BusinessIdentification(x) ↔ InformationContentEntity(x) ∧ ∃b(BusinessOrganization(b) ∧ designates(x,b))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>information content entity that identifies a business</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Business Identification is an Information Content Entity that 'designates' some Business Organization</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">Identifier for a business entity typically provided by a government or a well know business entity such as Dun and Bradstreet. It has significance in conducting trades between business entities.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;BusinessOrganization">
<rdfs:subClassOf rdf:resource="&iof-core;OrganizedGroupOfAgents"/>
<rdfs:label>business organization</rdfs:label>
<rdfs:comment>1. As defined here, business entity includes both for-profit and non-profit organizations as well as groups of nation states or parts thereof assembling under some identity.
2. Business entities are formally organized according to the laws prevailing in the locales and countries in which it operates or conducts business, and includes company, corporation, partnership, or sole proprietorship.</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;OrganizedGroupOfAgents">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000056"/>
<owl:someValuesFrom rdf:resource="&iof-core;BusinessProcess"/>
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;designatedBy"/>
<owl:someValuesFrom rdf:resource="&iof-core;BusinessIdentification"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example>Mercedes-Benz, Deloitte; OPC Foundation; OPEC (whose mission is to coordinate and unify the petroleum policies of its member countries and ensure the stabilization of oil markets in order to...)</skos:example>
<iof-av:firstOrderLogicDefinition>BusinessOrganization(x) ↔ OrganizedGroupOfAgents(x) ∧ ∃p,∃b(BusinessProcess(p) ∧ BusinessIdentification(b) ∧ participatesInAtSomeTime(x,p) ∧ designatedBy(x,b))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>organized group of agents that have a business identification assigned with the purpose to get involved in business processes</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Business Organization is an Organized Group Of Agents that 'participates in at some time' some Business Process and is 'designated by' some Business Identification</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">1. Any undertaking, venture, initiative, or business organization with a defined mission [APICS].
2. Organization that sells products or services, or plans to do so.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;BusinessProcess">
<rdfs:subClassOf rdf:resource="&iof-core;PlannedProcess"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000057"/>
<owl:someValuesFrom>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;BusinessOrganization">
</rdf:Description>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Agent">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;actsOnBehalfOfAtSomeTime"/>
<owl:someValuesFrom rdf:resource="&iof-core;BusinessOrganization"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:unionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;prescribedBy"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;PlanSpecification">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000110"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;ObjectiveSpecification">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000084"/>
<owl:someValuesFrom rdf:resource="&iof-core;BusinessOrganization"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">business process</rdfs:label>
<rdfs:comment>This definition leaves open the possibility that the business entity that carries the plan that prescribes the process, has no direct participation in the process, which would imply that some 3rd-party agent is playing a causal role as the process unfolds, and is acting on behalf of the Business Entity's interests.</rdfs:comment>
<skos:example>product production process; manufacturing enterprise process; finance operation; logistics operation.</skos:example>
<iof-av:firstOrderLogicDefinition>BusinessProcess (p) → PlannedProcess(p) ∧ ∃o,∃b,∃s (ObjectiveSpecification(o) ∧ BusinessOrganization(b) ∧ PlanSpecification(s) ∧ isCarrierOfAtSomeTime(b,o) ∧ continuantPartofAtAllTimes(o,s) ∧ (participatesInAtSomeTime(b,x) ∨∃y (Agent(y) ∧ actsOnBehalfOfAtSomeTime(y,b) ∧ participatesInAtSomeTime(y,x)))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>planned process which is prescribed by a plan specification with one or more objectives specified by a business organization</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Business Process x implies x is a Planned Process that is 'prescribed by' some Plan Specification p that 'has continuant part at all times' some Objective Specification o which 'generically depends on at some time' some Business Organization b and x 'has participant at some time' b or an Agent a that 'acts on behalf of at some time' b</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">1. Partially ordered, often nested, set of enterprise activities that can be executed to achieve some desired result in pursuit of a specified objective of an enterprise or a part of an enterprise [ISO 15704]
2. Partially ordered set of enterprise activities that can be executed to achieve some desired end-result in pursuit of a given objective of an organization [ISO/IEC/IEEE 24765].
3. A set of logically related tasks or activities performed to achieve a defined business outcome [APICS].
4. A business process is a collection of related, structured activities or tasks that produce a specific service or product for a particular customer or customers [OMG].</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;BuyerRole">
<rdfs:subClassOf rdf:resource="&iof-core;AgentRole"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;roleOf"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;BusinessOrganization">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;EngineeredSystem">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;Person">
</rdf:Description>
</owl:unionOf>
</owl:Class>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000056"/>
<owl:someValuesFrom rdf:resource="&iof-core;BuyingBusinessProcess"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">buyer role</rdfs:label>
<iof-av:firstOrderLogicDefinition>BuyerRole(x) → Role(x) ∧ ∃y,∃p ((BusinessOrganization(y) ∨ Person(y) ∨ EngineeredSystem(y)) ∧ BuyingBusinessProcess(p) ∧ participatesInAtSomeTime(y,p) ∧ roleOf(x, y))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>role held by a person, business organization or an automated system when it buys a product or a service</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Buyer Role x implies x is an Agent Role that is the 'role of' an Agent (person, organization or automated system acting on behalf of one) a when it 'participates in at some time' some Buying Business Process b</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>Individual or business organization or automated system that is responsible for buying a product or a service according to a service-agreement [OAGIS]</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;BuyingBusinessProcess">
<rdfs:subClassOf rdf:resource="&iof-core;BusinessProcess"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000057"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&bfo;BFO_0000040">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasRole"/>
<owl:someValuesFrom rdf:resource="&iof-core;BuyerRole"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000057"/>
<owl:someValuesFrom>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;CommercialServiceAgreement">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;MaterialProduct">
</rdf:Description>
</owl:unionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>buying business process</rdfs:label>
<rdfs:comment>1.The agent who uses the finiancial instrument may not own the financial instrument and hence agent may not be the paying agent.
2. It should be noted that we consciously exclude the person-to-person transactions, but person-to-business is not excluded.</rdfs:comment>
<skos:example>GM buys tires from Good Year to be assembled into its cars; GE Conglomerate (buyer) buys steels for uses in productions by its GE aviation subsidiary (customer) and GE Transportation subsidiary (customer)</skos:example>
<iof-av:adaptedFrom>CCO:http://www.ontologyrepository.com/CommonCoreOntologies/ActOfBuying
elucidation: OAGIS and CCO</iof-av:adaptedFrom>
<iof-av:elucidation>business process wherein financial instrument is used by an agent (buyer) to acquire ownership of product or commercial service from another agent (seller) for the buyer itself or another agent (customer)</iof-av:elucidation>
<iof-av:firstOrderLogicDefinition>BuyingBusinessProcess(x) → BusinessProcess(x) ∧ ∃y,∃z.∃r ((MaterialProduct(y) ∨ CommercialServiceAgreement(y)) ∧ MaterialEntity(z) ∧ BuyerRole(r) ∧ hasRole(z,r) ∧ hasParticipantAtSomeTIme(x,y) ∧ hasParticipantAtSomeTime(x,z))</iof-av:firstOrderLogicDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Buying Business Process x implies x is a Business Process that 'has participant at some time' some 'material entity' m that 'has role' some Buyer Role r and x 'has participant at some time' some Material Product or Commercial Service Agreement y</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;Capability">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000016"/>
<rdfs:label xml:lang="en">capability</rdfs:label>
<rdfs:comment>1. Whereas the BFO term 'disposition refers to all tendencies, powers, habits, skills, potentials, and so forth, that a material entity may possess, a Capability narrows this down by requiring the existence of an Agent that has an interest in the realization of the capability
2. This definition does not attempt to capture "task-based" capabilities that an entity may bear -- e.g., a stone's capability to kill when used by some person. Rather, it captures "proper capabilities." See related discussion of "proper functions" in the literature.
3. All functions are capabilities and in a future release BFO:Function will be asserted directly under capability.
4. Not all capabilities are functions. Capabilities are often added to an artifact by the designer/engineer, or to a biological entity through evolution, as "additional benefits," and are differentiated from function (i.e., purpose). Examples: the air conditioner in your car is a capability but not the function of your car. Yet the function of the car air conditioner certainly forms some material basis of your car's ability to provide a comfortable experience. The ability of your heart to beat fast to support your need to run fast to escape a threat. The decaying stick on the forest lawn does not have the function to be used as a tool, but certainly a chimpanzee
may have an interest in using a stick to extract food from a termite mound.</rdfs:comment>
<rdfs:comment>Maybe describing Capability vs. Function per Chandrasekaran and Josephson (2000) is a better way to go? Capability = Environment Centric Function and Function = Device Centric function. Function of a Drill is to remove material, it has capability to create hole in a workpiece. Function of a bulb is to produce light/photon particles, it has illumination capability. Capabilities are enabled by functions.</rdfs:comment>
<skos:example xml:lang="en">Capability of a person to play chess at the "master" level; of a team to play football in the professional league; of a lathe to turn at maximal speed of 4,000 RPM; or of your digestive system to digest tiramisu.</skos:example>
<iof-av:adaptedFrom>http://www.ontologyrepository.com/CommonCoreOntologies/Mid/AgentOntology</iof-av:adaptedFrom>
<iof-av:elucidation>disposition in whose realization some agent has an interest</iof-av:elucidation>
<iof-av:subjectMatterExpertExplanation>1. Someone’s or something's ability to bring about processes of a certain kind.
2.From Oxford Languages: Capability is
(1) the power or ability to do something, and
(2) the extent of someone's or something's ability.</iof-av:subjectMatterExpertExplanation>
<iof-av:synonym>ability</iof-av:synonym>
</owl:Class>
<owl:Class rdf:about="&iof-core;CommercialService">
<rdfs:subClassOf rdf:resource="&iof-core;BusinessProcess"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000057"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Agent">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasRole"/>
<owl:someValuesFrom rdf:resource="&iof-core;SupplierRole"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000117"/>
<owl:someValuesFrom rdf:resource="&iof-core;SupplyingBusinessProcess"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;isSubjectOf"/>
<owl:someValuesFrom rdf:resource="&iof-core;CommercialServiceAgreement"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;prescribedBy"/>
<owl:someValuesFrom rdf:resource="&iof-core;CommercialServiceSpecification"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>commercial service</rdfs:label>
<rdfs:comment>1.Service provisioning process is considered in IOF as the Supplying Process
2. A consumption process means using or benefiting.
3.Typically, the service provisioning process and consumption process coincide temporally which is different from a material product that is consumed (used) only after supplied.</rdfs:comment>
<skos:example>Lufthansa Aviation Services maintains airplanes for United Airlines when the plane stops at Frankfurt International Airport.</skos:example>
<iof-av:firstOrderLogicDefinition>CommercialService(x) → BusinessProcess(x) ∧ ∃p,∃y,∃r,∃a,∃s (CommercialServiceSpecification(p) ∧ Agent(y) ∧ CommercialServiceAgreement(s) ∧ SupplierRole(r) ∧ SupplyingBusinessProcess(a) ∧ hasRole(y,r) ∧ hasParticipantAtSomeTime(x,y) ∧ hasOccurentPart(x,a) ∧ prescribedBy(x,p) ∧ isSubjectOf(x,s))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>business process that consists of a service provisioning process and a consumption process</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Commercial Service x implies x is a Business Process that is 'prescribed by' some Commercial Service Specification p and that 'has participant at some time' some Agent y that 'has role' some Supplier Role r and x 'has occurent part' some Supplying Business Process a and x 'is subject of' some Commercial Service Agreement s</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;CommercialServiceAgreement">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:label>commercial service agreement</rdfs:label>
<skos:example>a cellphone plan, a maintenance service agreement, equipment lease agreement that includes a maintenance plan</skos:example>
<iof-av:adaptedFrom>https://spec.edmcouncil.org/fibo/ontology/FND/Agreements/Agreements/Agreement</iof-av:adaptedFrom>
<iof-av:counterExample>a blanket purchase order, commodity contract</iof-av:counterExample>
<iof-av:elucidation>agreement that is about the provision of a commercial service and associated conditions</iof-av:elucidation>
<iof-av:subjectMatterExpertExplanation>written contract between a client and service provider whereby the service provider supplies some service in the form of time, effort, and/or expertise in exchange for compensation [FIBO]</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;CommercialServiceSpecification">
<rdfs:subClassOf rdf:resource="&iof-core;PlanSpecification"/>
<rdfs:label>commercial service specification</rdfs:label>
<iof-av:firstOrderLogicDefinition>PlanSpecification(x) ∧ ∃c(CommercialService(c) ∧ prescribes(x,c)) → CommercialServiceSpecification(x)</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>plan specification that prescribes a commercial service</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>x is a Plan Specification that 'prescribes' some Commercial Service c implies x is a Commercial Service Specification</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;ComputingProcess">
<rdfs:subClassOf rdf:resource="&iof-core;PlannedProcess"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000057"/>
<owl:someValuesFrom>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Agent">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;Machine">
</rdf:Description>
</owl:unionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000059"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Algorithm">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000084"/>
<owl:someValuesFrom>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Agent">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;Machine">
</rdf:Description>
</owl:unionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>computing process</rdfs:label>
<iof-av:firstOrderLogicDefinition>ComputingProcess(x) → PlannedProcess(x) ∧ ∃y,∃a ((Agent(y) ∨ Machine(y)) ∧ Algorithm(a) ∧ hasParticipantAtSomeTIme(x,y) ∧ genericallyDependsOnAtSomeTime(a,y) ∧ concretizesAtSomeTime(x,a))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>planned process in which an algorithm is realized by an agent or a machine</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Computing Process x implies x is a Planned Process that 'has participant at some time' some Agent or Machine y and that 'concretizes at some time' some Algorithm a which 'generically depends on at some time' y</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;CustomerRole">
<rdfs:subClassOf rdf:resource="&iof-core;AgentRole"/>
<rdfs:label>customer role</rdfs:label>
<iof-av:elucidation>role held by an agent when it utilizes the product or receives the service or subscribes to the commercial service agreement</iof-av:elucidation>
<iof-av:subjectMatterExpertExplanation xml:lang="en">[OAGIS] Person, organization or automated system that is the end customer of the goods or services being provided in the associated transaction.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;DescriptiveInformationContentEntity">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:label xml:lang="en">descriptive information content entity</rdfs:label>
<rdfs:comment xml:lang="en">This class is intended to be a defined class and can be used for axiomatization and assertion convenience. It is not expected that entities will be asserted a subclass of this class.</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;InformationContentEntity">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;describes"/>
<owl:someValuesFrom rdf:resource="&bfo;BFO_0000001"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example>a description of a product in a product catalogue, the wheelbase of this car is 3m, digital copy of a Mona Lisa drawing</skos:example>
<iof-av:abbreviation xml:lang="en">descriptive ICE</iof-av:abbreviation>
<iof-av:adaptedFrom rdf:datatype="&xsd;anyURI">http://www.ontologyrepository.com/CommonCoreOntologies/Mid/InformationEntityOntology</iof-av:adaptedFrom>
<iof-av:firstOrderLogicDefinition>DescriptiveInformationContentEntity(x) ↔ InformationContentEntity(x) ∧ ∃e(Entity(e) ∧ describes(x,e))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>information content entity that characterizes an entity</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Descriptive Information Content Entity is an Information Content Entity that 'describes' some Entity</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">A textual or schematic representation as it is used to characterize (give a description of) someone or something.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;DesignSpecification">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;prescribes"/>
<owl:allValuesFrom rdf:resource="&bfo;BFO_0000002"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>design specification</rdfs:label>
<rdfs:comment>1. Design specification can take the form of a model, or of a textual or graphical specification
2. This class is not intended to be used to model planned processes and for that purpose plan specification should be used
3. Something man-made’ comprehends those physical and non-physical things that are intentionally created by human beings. Hence the thing specified by a design specification may be either BFO:GDC or BFO:Material Entity.
4. A design specification specifies what the thing should be such as shape, size, tolerance, performance but not necessarily how the thing should be made
5. Typically, a design specification satisfies a set of requirements</rdfs:comment>
<skos:example>document specifying the characteristics of a pharmaceutical product; the design of a software program to schedule the work orders in a factory</skos:example>
<iof-av:adaptedFrom>http://www.ontologyrepository.com/CommonCoreOntologies/Mid/InformationEntityOntology</iof-av:adaptedFrom>
<iof-av:counterExample>process design</iof-av:counterExample>
<iof-av:firstOrderLogicDefinition>DesignSpecification(x) → InformationContentEntity(x) ∧
∀c(prescribes(x,c) → Continuant(c))</iof-av:firstOrderLogicDefinition>
<iof-av:firstOrderLogicDefinition>InformationContentEntity(x) ∧ ∃c, ∃r ( continuant(c) ∧ RequirementSpecification(r) ∧ satisfies(x,r) ∧ prescribes(x,c)) ∧ ∀c'(prescribes(x,c') → Continuant(c')) → DesignSpecification(x)</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>information content entity that prescribes something man-made</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Design Specification d implies d is an Information Content Entity and that if d 'prescribes' an entity y that y must be a 'continuant'</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>d is a Information Content Entity and d prescribes some 'continuant' c and d 'satisfies' some Requirement Specification r and all y 'prescribed by' d are continuants implies d is a Design Specification</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">1. [ISO 14813-5]: How parts or constituents are related to an organised whole, providing specification for the structure, organization, appearance, etc., of a system or entity.
2. Detailed specification or model of something man-made that may satisfy a set of requirements.[CCO]</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;DesignativeInformationContentEntity">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:label xml:lang="en">designative information content entity</rdfs:label>
<rdfs:comment xml:lang="en">This class is intended to be a defined class and can be used for axiomatization and assertion convenience. It is not expected that entities will be asserted a subclass of this class.</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;InformationContentEntity">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;designates"/>
<owl:someValuesFrom rdf:resource="&bfo;BFO_0000001"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example xml:lang="en">uri of a website, social security number of a person, lot number of a batch of products, a serial number on a machine, a credit card number, a combination of data in a database table uniquely identify each record in the table</skos:example>
<iof-av:abbreviation xml:lang="en">designative ICE</iof-av:abbreviation>
<iof-av:adaptedFrom rdf:datatype="&xsd;anyURI">http://www.ontologyrepository.com/CommonCoreOntologies/Mid/InformationEntityOntology</iof-av:adaptedFrom>
<iof-av:firstOrderLogicDefinition>DesignativeInformationContentEntity(x) ↔ InformationContentEntity(x) ∧ ∃e(Entity(e) ∧ designates(x,e))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>information content entity that uniquely identifies an entity</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Designative Information Content Entity is an Information Content Entity that 'designates' some Entity</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">some pieces of information such as a sequence of symbols that are used for uniquely identifying an entity</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;DirectiveInformationContentEntity">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:label xml:lang="en">directive information content entity</rdfs:label>
<rdfs:comment xml:lang="en">This class is intended to be a defined class and can be used for axiomatization and assertion convenience. It is not expected that entities will be asserted a subclass of this class.</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;InformationContentEntity">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;prescribes"/>
<owl:someValuesFrom rdf:resource="&bfo;BFO_0000001"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example>blueprint of a building, process plan, software functional requirement</skos:example>
<iof-av:abbreviation xml:lang="en">directive ICE</iof-av:abbreviation>
<iof-av:adaptedFrom rdf:datatype="&xsd;anyURI">http://www.ontologyrepository.com/CommonCoreOntologies/Mid/InformationEntityOntology</iof-av:adaptedFrom>
<iof-av:firstOrderLogicDefinition>DirectiveInformationContentEntity(x) ↔ InformationContentEntity(x) ∧ ∃e(Entity(e) ∧ prescribes(x,e))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>information content entity that prescribes a set of rules or guidelines for a process or a model of something man-made</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Directive Information Content Entity is an Information Content Entity that 'prescribes' some Entity</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">A textual or schematic representation as it is used to guide or govern some tasks or used as a blueprint for building something.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;EngineeredSystem">
<rdfs:subClassOf rdf:resource="&iof-core;System"/>
<rdfs:label xml:lang="en">engineered system</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;System">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000196"/>
<owl:someValuesFrom rdf:resource="&iof-core;Capability"/>
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;prescribedBy"/>
<owl:someValuesFrom rdf:resource="&iof-core;DesignSpecification"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example>machine, laptop, traffic light system</skos:example>
<iof-av:firstOrderLogicDefinition>EngineeredSystem(x) ↔ System(x) ∧ ∃d,∃c(DesignSpecification(d) ∧ Capability(c) ∧ prescribes(d,x) ∧ bearerOf(x,c))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>system which is designed to provide certain capabilities</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Engineered System is a System that is 'prescribed by' some Design Specification and that is the 'bearer of' some Capability</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;Event">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000003"/>
<rdfs:subClassOf>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&bfo;BFO_0000015">
</rdf:Description>
<rdf:Description rdf:about="&bfo;BFO_0000035">
</rdf:Description>
</owl:unionOf>
</owl:Class>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;recognizedByAtSomeTime"/>
<owl:someValuesFrom rdf:resource="&iof-core;Agent"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>event</rdfs:label>
<skos:example>a machine failure event, the amount of cells in a bioreactor reaches a certain threshold</skos:example>
<iof-av:counterExample>an event in discrete event simulation is too generic and that notion of event is just BFO:Occurrent</iof-av:counterExample>
<iof-av:firstOrderLogicDefinition>Event(x) → (Process(x) ∨ ProcessBoundary(x)) ∧ ∃a(Agent(a) ∧ recognizedByAtSomeTime(x,a))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>occurrent that is recognized by an agent and typically recorded</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Event x implies x is a 'process' or 'process boundary' and there is some Agent a that 'recognizes at some time' x</iof-av:semiFormalNaturalLanguageDefinition>
</owl:Class>
<owl:Class rdf:about="&iof-core;GroupOfAgents">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000027"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000172"/>
<owl:allValuesFrom rdf:resource="&iof-core;Agent"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>group of agents</rdfs:label>
<rdfs:comment>Group of agents being a BFO:Object Aggregate allows for a point in time where there is only one Agent present.</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&bfo;BFO_0000027">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000172"/>
<owl:someValuesFrom rdf:resource="&iof-core;Agent"/>
</owl:Restriction>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000172"/>
<owl:allValuesFrom rdf:resource="&iof-core;Agent"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<iof-av:adaptedFrom>http://www.ontologyrepository.com/CommonCoreOntologies/Mid/AgentOntology</iof-av:adaptedFrom>
<iof-av:firstOrderLogicDefinition>GroupOfAgents(x) ↔ ObjectAggregate(x) ∧ ∃y (Agent(y) ∧ memberPartOfAtAllTimes(y, x)) ∧ ∀z (memberPartOfAtAllTimes(z, x) → Agent(z))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>object aggregate that has a number of agents as member parts</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Group of Agents is an 'object aggregate' that only has Agents as 'member parts'</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>Group that typically consists of two or more (although there might be a point in time with only one member) persons, organizations or engineered systems, or any combination of these</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;InformationContentEntity">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000031"/>
<rdfs:label xml:lang="en">information content entity</rdfs:label>
<rdfs:comment>1.Information Content Entity is here intended to be a class of Entities whose instances are the informational content of Information Bearing Entities. For example, three instances of information bearers -- such as a bar chart, color-coded map, and a written report -- each of which lists the GDP of Countries for the year 2010 are each different bearers of the same information content. It is this content that is generically dependent upon its bearer. This treatment of Informational Content Entity (cf. the Information Artifact Ontology) leads to a principle of subtyping based upon the relationship that ICE's have with the Entity they are about rather than characteristics such as format, language, measurement scale, or media. The latter are treated here as being Qualities of bearers.
2. Information content entities are typically a string or array of symbols. Thus, they can be a textual or schematic representation.</rdfs:comment>
<skos:example>the content of an email, the content of a document, the content in a STEP file</skos:example>
<iof-av:abbreviation>ICE</iof-av:abbreviation>
<iof-av:adaptedFrom>Information Artifact Ontology, http://purl.obolibrary.org/obo/IAO_0000030 and also the Common Core Ontology, http://www.ontologyrepository.com/CommonCoreOntologies/Mid/InformationEntityOntology</iof-av:adaptedFrom>
<iof-av:firstOrderLogicDefinition>GenericallyDependentContinuant(x) ∧ ∃e(Entity(e) ∧ isAbout(x,e)) →
InformationContentEntity(x)</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>generically dependent continuant that is about an entity</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>x is a 'generically dependent continuant' that 'is about' some 'entity' e implies x is an Information Content Entity</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>Information, specification, pattern, thought, or idea independent from its physical media. The physical media can be virtually any physical objects such as human brain, disc, paper, cave wall (as when ancient people wrote on the wall).</iof-av:subjectMatterExpertExplanation>
<iof-av:synonym>Information Entity</iof-av:synonym>
</owl:Class>
<owl:Class rdf:about="&iof-core;LocationIdentification">
<rdfs:subClassOf rdf:resource="&iof-core;InformationContentEntity"/>
<rdfs:label>location identification</rdfs:label>
<rdfs:comment>1.more entities need to be created to be able to represent coordinates , for that purpose this OGC specification can be a good source:
http://docs.opengeospatial.org/is/18-010r7/18-010r7.html#106
2.at this point IOF:Core is only dealing with physical locations while virtual locations will be considered in a future version.
3. physical location is a synonym for BFO:Site and hence the usage of BFO:Site within the axioms should be interpreted as physical location</rdfs:comment>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;InformationContentEntity">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;designates"/>
<owl:someValuesFrom rdf:resource="&bfo;BFO_0000029"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<skos:example>postal address, GPS coordinate, GS1 global location number (GLN) for physical and digital location, 42.8864° N, 78.8784° W, London, the factory floor</skos:example>
<iof-av:firstOrderLogicDefinition>LocationIdentification(x) ↔ InformationContentEntity(x) ∧ ∃l(Site(l) ∧ designates(x,l))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>information content entity that identifies a physical location</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition xml:lang="en">Location Identification is an Information Content Entity that 'designates' some 'site'</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>Information that identifies a location typically through coordinate values or through a name or description</iof-av:subjectMatterExpertExplanation>
<iof-av:synonym>site identifier, site designator</iof-av:synonym>
</owl:Class>
<owl:Class rdf:about="&iof-core;Machine">
<rdfs:subClassOf rdf:resource="&iof-core;MaterialArtifact"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000110"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Assembly">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000163"/>
<owl:someValuesFrom rdf:resource="&bfo;BFO_0000034"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">machine</rdfs:label>
<rdfs:comment xml:lang="en">the current axiom cannot be N&S condition because it would conclude that something like a coffee mug with a lid is a machine</rdfs:comment>
<iof-av:firstOrderLogicDefinition>Machine(x) → MaterialArtifact(x) ∧ ∃c,∃f(Assembly(c) ∧ Function(f) ∧ hasMaterialBasisAtAllTimes(f,c) ∧ hasContinuantPartAtAllTimes(x,c) ∧ inheresIn(f,x))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>material artifact that contains a number of physically connected assemblies that work together to realize the artifact’s designed function</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Machine x implies x is a Material Artifact that 'has continuant part at all times', one or more Assemblies c that are the 'material basis at all times' of the 'function' f that 'inheres in' x</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation xml:lang="en">Man-made artifact containing a set of physically-connected components that work together as a unit with some designed function.
Other common definitions:
1. ISO 22096:2007(en): Is a mechanical system designed expressly to perform a specific task, such as the forming of material or the transference and transformation of motion, force or energy.
2. Is a mechanical structure that uses power to apply forces and control movement to perform an intended action. Machines can be driven by animals and people, by natural forces such as wind and water, and by chemical, thermal, or electrical power, and include a system of mechanisms that shape the actuator input to achieve a specific application of output forces and movement [WIkipedia].</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;MaintainableMaterialItem">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000040"/>
<rdfs:label>maintainable material item</rdfs:label>
<owl:equivalentClass>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;EngineeredSystem">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;MaterialArtifact">
</rdf:Description>
</owl:unionOf>
</owl:Class>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasRole"/>
<owl:someValuesFrom rdf:resource="&iof-core;MaintainableMaterialItemRole"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:equivalentClass>
<iof-av:firstOrderLogicDefinition>MaintainableMaterialItem(x) ↔ (MaterialArtifact(x) ∨ EngineeredSystem(x)) ∧ ∃y (MaintainableMaterialItemRole(y) ∧ hasRole(x,y))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>material artifact or engineered system which has the maintainable material item role</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Maintainable Material Item is a Material Artifact or an Engineered System which 'has role' some Maintainable Material Item Role</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>A physical asset on which maintenance is actioned according to a maintenance strategy.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;MaintainableMaterialItemRole">
<rdfs:subClassOf rdf:resource="&bfo;BFO_0000023"/>
<rdfs:label>maintainable material item role</rdfs:label>
<iof-av:elucidation>role played by an asset when there is a maintenance strategy prescribing its maintenance process</iof-av:elucidation>
<iof-av:subjectMatterExpertExplanation>The role played by an asset when it is assigned a maintenance strategy.</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;ManufacturerRole">
<rdfs:subClassOf rdf:resource="&iof-core;AgentRole"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;roleOf"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;BusinessOrganization">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000056"/>
<owl:someValuesFrom rdf:resource="&iof-core;ProductProductionProcess"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label>manufacturer role</rdfs:label>
<iof-av:firstOrderLogicDefinition>ManufacturerRole(x) → Role(x) ∧ ∃y,∃p (BusinessOrganization(y) ∧ ProductProductionProcess(p) ∧ participatesInAtSomeTime(y,p) ∧ roleOf(x, y))</iof-av:firstOrderLogicDefinition>
<iof-av:naturalLanguageDefinition>role held by a business organization when it produces material products</iof-av:naturalLanguageDefinition>
<iof-av:semiFormalNaturalLanguageDefinition>Manufacturer Role x implies x is an Agent Role that is the 'role of' a Business Organization y when it 'participates in at some time' some Product Production Process p</iof-av:semiFormalNaturalLanguageDefinition>
<iof-av:subjectMatterExpertExplanation>An organization has a manufacturer role when it produces goods for sale to wholesalers, retailers or end consumers.[bizfluent.com]</iof-av:subjectMatterExpertExplanation>
</owl:Class>
<owl:Class rdf:about="&iof-core;ManufacturingProcess">
<rdfs:subClassOf rdf:resource="&iof-core;PlannedProcess"/>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000057"/>
<owl:someValuesFrom>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;Machine">
</rdf:Description>
<rdf:Description rdf:about="&iof-core;Person">
</rdf:Description>
</owl:unionOf>
</owl:Class>
<owl:Restriction>
<owl:onProperty rdf:resource="&bfo;BFO_0000101"/>
<owl:someValuesFrom rdf:resource="&iof-core;PlanSpecification"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasInput"/>
<owl:someValuesFrom rdf:resource="&bfo;BFO_0000040"/>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:subClassOf>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;hasSpecifiedOutput"/>
<owl:someValuesFrom>
<owl:Class>
<owl:unionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&iof-core;MaterialArtifact">
</rdf:Description>
<owl:Class>
<owl:intersectionOf rdf:parseType="Collection">
<rdf:Description rdf:about="&bfo;BFO_0000040">
</rdf:Description>
<owl:Restriction>
<owl:onProperty rdf:resource="&iof-core;prescribedBy"/>
<owl:someValuesFrom rdf:resource="&iof-core;DesignSpecification"/>
</owl:Restriction>
</owl:intersectionOf>
</owl:Class>
</owl:unionOf>
</owl:Class>
</owl:someValuesFrom>
</owl:Restriction>
</rdfs:subClassOf>
<rdfs:label xml:lang="en">manufacturing process</rdfs:label>
<rdfs:comment>1. This definition presupposes that the outputs of a manufacturing process are in every case material artifacts or man-made substances.
2. Processes that have as their primary output, something immaterial or informational in nature (digital outputs), such as found in the production of software, will be considered speparately at a later stage.
3.. There are other processes that while they may come into direct contact with a manufactured component or substance and are often considered part of the overall set of activities planned and executed to manufacture something, they are not "transformative" in nature relative to that which is manufactured, and are specifically excluded the definition. Examples include setup, tear down, transporting components or materials between locations, inspection, and so forth.
This is addressed by output in the axiom. Setup => does not have output. Tear down like disassembly should still be considered transformative.
4. This definition places no additional restrictions on the output of a manufacturing process in terms of being in a state of completion (completed component or finished good).</rdfs:comment>