1998
AUTHORS ABSTRACTWorkflow specification is a complex construct highly integrated (correlated) with specifications of other types. Designing a workflow we should consider semantics of workflow objects and objects related to them in an integrated way.Reusable components are treated semantically interoperable in context of a specific application. For components and for specification of requirements canonical object model semantics and ontological semantics are considered jointly to provide complete specificationsIn frame of complete specifications, a notion of the most common reduct for a pair of type specifications is introduced as the basis for detection of reusable fragments. This notion is based on a refinement technique. An approach for component-based design with reuse is outlined.The multiactivity (workflow) canonical specification framework is defined. The notion of workflow refinement is based on systematic analysis of functional and concurrent workflow specification properties merging conventional well grounded specification refinement technique with determining of process bisimulation equivalence.A simple example showing a uniform representation of heterogeneous workflow specifications in the canonical model is introduced. The example is used to show how common workflow reducts can be identified and composed in process of the information system development. More... »
PAGES439-490
Workflow Management Systems and Interoperability
ISBN
978-3-642-63786-5
978-3-642-58908-9
http://scigraph.springernature.com/pub.10.1007/978-3-642-58908-9_20
DOIhttp://dx.doi.org/10.1007/978-3-642-58908-9_20
DIMENSIONShttps://app.dimensions.ai/details/publication/pub.1006438939
JSON-LD is the canonical representation for SciGraph data.
TIP: You can open this SciGraph record using an external JSON-LD service: JSON-LD Playground Google SDTT
[
{
"@context": "https://springernature.github.io/scigraph/jsonld/sgcontext.json",
"about": [
{
"id": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/08",
"inDefinedTermSet": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/",
"name": "Information and Computing Sciences",
"type": "DefinedTerm"
},
{
"id": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/0806",
"inDefinedTermSet": "http://purl.org/au-research/vocabulary/anzsrc-for/2008/",
"name": "Information Systems",
"type": "DefinedTerm"
}
],
"author": [
{
"affiliation": {
"alternateName": "Institute for Problems of Informatics, Russian Academy of Sciences, Vavilova 30/6, V-334, 117900, Moscow, Russia",
"id": "http://www.grid.ac/institutes/grid.4886.2",
"name": [
"Institute for Problems of Informatics, Russian Academy of Sciences, Vavilova 30/6, V-334, 117900, Moscow, Russia"
],
"type": "Organization"
},
"familyName": "Kalinichenko",
"givenName": "Leonid",
"id": "sg:person.016144507043.63",
"sameAs": [
"https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.016144507043.63"
],
"type": "Person"
}
],
"datePublished": "1998",
"datePublishedReg": "1998-01-01",
"description": "Workflow specification is a complex construct highly integrated (correlated) with specifications of other types. Designing a workflow we should consider semantics of workflow objects and objects related to them in an integrated way.Reusable components are treated semantically interoperable in context of a specific application. For components and for specification of requirements canonical object model semantics and ontological semantics are considered jointly to provide complete specificationsIn frame of complete specifications, a notion of the most common reduct for a pair of type specifications is introduced as the basis for detection of reusable fragments. This notion is based on a refinement technique. An approach for component-based design with reuse is outlined.The multiactivity (workflow) canonical specification framework is defined. The notion of workflow refinement is based on systematic analysis of functional and concurrent workflow specification properties merging conventional well grounded specification refinement technique with determining of process bisimulation equivalence.A simple example showing a uniform representation of heterogeneous workflow specifications in the canonical model is introduced. The example is used to show how common workflow reducts can be identified and composed in process of the information system development.",
"editor": [
{
"familyName": "Do\u011fa\u00e7",
"givenName": "Asuman",
"type": "Person"
},
{
"familyName": "Kalinichenko",
"givenName": "Leonid",
"type": "Person"
},
{
"familyName": "\u00d6zsu",
"givenName": "M. Tamer",
"type": "Person"
},
{
"familyName": "Sheth",
"givenName": "Amit",
"type": "Person"
}
],
"genre": "chapter",
"id": "sg:pub.10.1007/978-3-642-58908-9_20",
"inLanguage": "en",
"isAccessibleForFree": false,
"isPartOf": {
"isbn": [
"978-3-642-63786-5",
"978-3-642-58908-9"
],
"name": "Workflow Management Systems and Interoperability",
"type": "Book"
},
"keywords": [
"component-based design",
"information systems development",
"workflow specification",
"reusable components",
"Workflow Reuse",
"reusable fragments",
"ontological semantics",
"workflow objects",
"specification framework",
"model semantics",
"refinement technique",
"uniform representation",
"semantics",
"complete specification",
"system development",
"integrated way",
"specification",
"reducts",
"specific applications",
"common reduct",
"reuse",
"bisimulation equivalence",
"objects",
"specification property",
"simple example",
"type specification",
"workflow",
"technique",
"framework",
"canonical model",
"representation",
"example",
"notion",
"applications",
"frame",
"complex construct",
"detection",
"issues",
"design",
"systematic analysis",
"way",
"context",
"components",
"model",
"refinement",
"process",
"development",
"equivalence",
"determining",
"pairs",
"basis",
"constructs",
"types",
"analysis",
"properties",
"fragments",
"approach"
],
"name": "Workflow Reuse and Semantic Interoperation Issues",
"pagination": "439-490",
"productId": [
{
"name": "dimensions_id",
"type": "PropertyValue",
"value": [
"pub.1006438939"
]
},
{
"name": "doi",
"type": "PropertyValue",
"value": [
"10.1007/978-3-642-58908-9_20"
]
}
],
"publisher": {
"name": "Springer Nature",
"type": "Organisation"
},
"sameAs": [
"https://doi.org/10.1007/978-3-642-58908-9_20",
"https://app.dimensions.ai/details/publication/pub.1006438939"
],
"sdDataset": "chapters",
"sdDatePublished": "2022-05-10T10:36",
"sdLicense": "https://scigraph.springernature.com/explorer/license/",
"sdPublisher": {
"name": "Springer Nature - SN SciGraph project",
"type": "Organization"
},
"sdSource": "s3://com-springernature-scigraph/baseset/20220509/entities/gbq_results/chapter/chapter_101.jsonl",
"type": "Chapter",
"url": "https://doi.org/10.1007/978-3-642-58908-9_20"
}
]
Download the RDF metadata as: json-ld nt turtle xml License info
JSON-LD is a popular format for linked data which is fully compatible with JSON.
curl -H 'Accept: application/ld+json' 'https://scigraph.springernature.com/pub.10.1007/978-3-642-58908-9_20'
N-Triples is a line-based linked data format ideal for batch operations.
curl -H 'Accept: application/n-triples' 'https://scigraph.springernature.com/pub.10.1007/978-3-642-58908-9_20'
Turtle is a human-readable linked data format.
curl -H 'Accept: text/turtle' 'https://scigraph.springernature.com/pub.10.1007/978-3-642-58908-9_20'
RDF/XML is a standard XML format for linked data.
curl -H 'Accept: application/rdf+xml' 'https://scigraph.springernature.com/pub.10.1007/978-3-642-58908-9_20'
This table displays all metadata directly associated to this object as RDF triples.
132 TRIPLES
23 PREDICATES
83 URIs
76 LITERALS
7 BLANK NODES
Subject | Predicate | Object | |
---|---|---|---|
1 | sg:pub.10.1007/978-3-642-58908-9_20 | schema:about | anzsrc-for:08 |
2 | ″ | ″ | anzsrc-for:0806 |
3 | ″ | schema:author | N2cebe04edc374e29b1deeb14bcb05ae3 |
4 | ″ | schema:datePublished | 1998 |
5 | ″ | schema:datePublishedReg | 1998-01-01 |
6 | ″ | schema:description | Workflow specification is a complex construct highly integrated (correlated) with specifications of other types. Designing a workflow we should consider semantics of workflow objects and objects related to them in an integrated way.Reusable components are treated semantically interoperable in context of a specific application. For components and for specification of requirements canonical object model semantics and ontological semantics are considered jointly to provide complete specificationsIn frame of complete specifications, a notion of the most common reduct for a pair of type specifications is introduced as the basis for detection of reusable fragments. This notion is based on a refinement technique. An approach for component-based design with reuse is outlined.The multiactivity (workflow) canonical specification framework is defined. The notion of workflow refinement is based on systematic analysis of functional and concurrent workflow specification properties merging conventional well grounded specification refinement technique with determining of process bisimulation equivalence.A simple example showing a uniform representation of heterogeneous workflow specifications in the canonical model is introduced. The example is used to show how common workflow reducts can be identified and composed in process of the information system development. |
7 | ″ | schema:editor | N92ae2a39331b41af83ea960eb4bb0a76 |
8 | ″ | schema:genre | chapter |
9 | ″ | schema:inLanguage | en |
10 | ″ | schema:isAccessibleForFree | false |
11 | ″ | schema:isPartOf | N2826cfabd32a4d03bda4f160fb19e5df |
12 | ″ | schema:keywords | Workflow Reuse |
13 | ″ | ″ | analysis |
14 | ″ | ″ | applications |
15 | ″ | ″ | approach |
16 | ″ | ″ | basis |
17 | ″ | ″ | bisimulation equivalence |
18 | ″ | ″ | canonical model |
19 | ″ | ″ | common reduct |
20 | ″ | ″ | complete specification |
21 | ″ | ″ | complex construct |
22 | ″ | ″ | component-based design |
23 | ″ | ″ | components |
24 | ″ | ″ | constructs |
25 | ″ | ″ | context |
26 | ″ | ″ | design |
27 | ″ | ″ | detection |
28 | ″ | ″ | determining |
29 | ″ | ″ | development |
30 | ″ | ″ | equivalence |
31 | ″ | ″ | example |
32 | ″ | ″ | fragments |
33 | ″ | ″ | frame |
34 | ″ | ″ | framework |
35 | ″ | ″ | information systems development |
36 | ″ | ″ | integrated way |
37 | ″ | ″ | issues |
38 | ″ | ″ | model |
39 | ″ | ″ | model semantics |
40 | ″ | ″ | notion |
41 | ″ | ″ | objects |
42 | ″ | ″ | ontological semantics |
43 | ″ | ″ | pairs |
44 | ″ | ″ | process |
45 | ″ | ″ | properties |
46 | ″ | ″ | reducts |
47 | ″ | ″ | refinement |
48 | ″ | ″ | refinement technique |
49 | ″ | ″ | representation |
50 | ″ | ″ | reusable components |
51 | ″ | ″ | reusable fragments |
52 | ″ | ″ | reuse |
53 | ″ | ″ | semantics |
54 | ″ | ″ | simple example |
55 | ″ | ″ | specific applications |
56 | ″ | ″ | specification |
57 | ″ | ″ | specification framework |
58 | ″ | ″ | specification property |
59 | ″ | ″ | system development |
60 | ″ | ″ | systematic analysis |
61 | ″ | ″ | technique |
62 | ″ | ″ | type specification |
63 | ″ | ″ | types |
64 | ″ | ″ | uniform representation |
65 | ″ | ″ | way |
66 | ″ | ″ | workflow |
67 | ″ | ″ | workflow objects |
68 | ″ | ″ | workflow specification |
69 | ″ | schema:name | Workflow Reuse and Semantic Interoperation Issues |
70 | ″ | schema:pagination | 439-490 |
71 | ″ | schema:productId | N2e8ad37bbc75401296b393aa0a3e1245 |
72 | ″ | ″ | N7665e17f7f084d098f7dac4d485791d7 |
73 | ″ | schema:publisher | N6048f5faf57b41aba4b0cc9b5e4c2bbb |
74 | ″ | schema:sameAs | https://app.dimensions.ai/details/publication/pub.1006438939 |
75 | ″ | ″ | https://doi.org/10.1007/978-3-642-58908-9_20 |
76 | ″ | schema:sdDatePublished | 2022-05-10T10:36 |
77 | ″ | schema:sdLicense | https://scigraph.springernature.com/explorer/license/ |
78 | ″ | schema:sdPublisher | N1105e59e2cf74ee48b4f60fe63799d91 |
79 | ″ | schema:url | https://doi.org/10.1007/978-3-642-58908-9_20 |
80 | ″ | sgo:license | sg:explorer/license/ |
81 | ″ | sgo:sdDataset | chapters |
82 | ″ | rdf:type | schema:Chapter |
83 | N0686c626cf28410a88cbf69dac7f681a | rdf:first | N9c0a15e3b5f24a19817d4e45ed286e4d |
84 | ″ | rdf:rest | N08b236c726934292b68f05b64762f671 |
85 | N08b236c726934292b68f05b64762f671 | rdf:first | N7afebe5c0aba4cac9ee2fc632df937cf |
86 | ″ | rdf:rest | N1045aa2a9e31404a929ed50a9816eab7 |
87 | N1045aa2a9e31404a929ed50a9816eab7 | rdf:first | N571c9bd00e84418d84bf6e47f5ac2d7f |
88 | ″ | rdf:rest | rdf:nil |
89 | N1105e59e2cf74ee48b4f60fe63799d91 | schema:name | Springer Nature - SN SciGraph project |
90 | ″ | rdf:type | schema:Organization |
91 | N2826cfabd32a4d03bda4f160fb19e5df | schema:isbn | 978-3-642-58908-9 |
92 | ″ | ″ | 978-3-642-63786-5 |
93 | ″ | schema:name | Workflow Management Systems and Interoperability |
94 | ″ | rdf:type | schema:Book |
95 | N2cebe04edc374e29b1deeb14bcb05ae3 | rdf:first | sg:person.016144507043.63 |
96 | ″ | rdf:rest | rdf:nil |
97 | N2e8ad37bbc75401296b393aa0a3e1245 | schema:name | dimensions_id |
98 | ″ | schema:value | pub.1006438939 |
99 | ″ | rdf:type | schema:PropertyValue |
100 | N571c9bd00e84418d84bf6e47f5ac2d7f | schema:familyName | Sheth |
101 | ″ | schema:givenName | Amit |
102 | ″ | rdf:type | schema:Person |
103 | N6048f5faf57b41aba4b0cc9b5e4c2bbb | schema:name | Springer Nature |
104 | ″ | rdf:type | schema:Organisation |
105 | N7665e17f7f084d098f7dac4d485791d7 | schema:name | doi |
106 | ″ | schema:value | 10.1007/978-3-642-58908-9_20 |
107 | ″ | rdf:type | schema:PropertyValue |
108 | N7afebe5c0aba4cac9ee2fc632df937cf | schema:familyName | Özsu |
109 | ″ | schema:givenName | M. Tamer |
110 | ″ | rdf:type | schema:Person |
111 | N7e199d77c10344bdb99b10816df31fef | schema:familyName | Doğaç |
112 | ″ | schema:givenName | Asuman |
113 | ″ | rdf:type | schema:Person |
114 | N92ae2a39331b41af83ea960eb4bb0a76 | rdf:first | N7e199d77c10344bdb99b10816df31fef |
115 | ″ | rdf:rest | N0686c626cf28410a88cbf69dac7f681a |
116 | N9c0a15e3b5f24a19817d4e45ed286e4d | schema:familyName | Kalinichenko |
117 | ″ | schema:givenName | Leonid |
118 | ″ | rdf:type | schema:Person |
119 | anzsrc-for:08 | schema:inDefinedTermSet | anzsrc-for: |
120 | ″ | schema:name | Information and Computing Sciences |
121 | ″ | rdf:type | schema:DefinedTerm |
122 | anzsrc-for:0806 | schema:inDefinedTermSet | anzsrc-for: |
123 | ″ | schema:name | Information Systems |
124 | ″ | rdf:type | schema:DefinedTerm |
125 | sg:person.016144507043.63 | schema:affiliation | grid-institutes:grid.4886.2 |
126 | ″ | schema:familyName | Kalinichenko |
127 | ″ | schema:givenName | Leonid |
128 | ″ | schema:sameAs | https://app.dimensions.ai/discover/publication?and_facet_researcher=ur.016144507043.63 |
129 | ″ | rdf:type | schema:Person |
130 | grid-institutes:grid.4886.2 | schema:alternateName | Institute for Problems of Informatics, Russian Academy of Sciences, Vavilova 30/6, V-334, 117900, Moscow, Russia |
131 | ″ | schema:name | Institute for Problems of Informatics, Russian Academy of Sciences, Vavilova 30/6, V-334, 117900, Moscow, Russia |
132 | ″ | rdf:type | schema:Organization |