FRINK Linked Data Fragments server

Matches in SemOpenAlex for { <https://semopenalex.org/work/W2039201764> ?p ?o ?g. }

• W2039201764 endingPage "25" @default.
• W2039201764 startingPage "21" @default.
• W2039201764 abstract "This session addressed the object base and typing issues needed in support of the modeling and implementation of the life-cycle process. In this summary the terms process and life-cycle process are used interchangeably. However, I do not believe that was the case during the workshop; sometimes it seemed that the term process was used in an abstract way1, which led, at times, to some conceptual misunderstandings.Jack Wileden was the keynote speaker for the session. He started by trying to differentiate between two (2) roles in process modeling: The actual modeling of the process, i.e., how do we describe the process independent of its implementation.Process enaction and the environment needs in support of the process model descriptions.He felt most position papers dealt with the second role, even though a few talked about the first. There was not too much discussion with respect to the differences of those roles but performance was mentioned as a key issue for the second role.Wileden proceeded to distinguish an overall “world view” on data issues from specific dimensions of the data support problem (see section 2 for his list of specific dimensions). He listed several possible world views with respect to data in support of life-cycle processes, including: i) typed objects as in programming languages, ii) files (e.g., documents, code, etc), iii) traditional database view. He described his own view as based on the notion of an “object space” (i.e., collections of objects). This more modern view appears to be shared by many of the workshop participants, as reflected in many of the position papers. The group decided not to debate on the definition of the word object, but to consider it related to the concept of abstract data types. (Note: I like to think of objects as the units of data which are identifiable and accessible within a Software Engineering Environment (SEE) and of an Object Management System (OMS) as the SEE component whose objective is to manage those objects; a precise definition of an object is largely dependent on the type model provided by an OMS.)This session did not try to generate lists of issues or requirements. The objective seemed to be to discuss items which were felt important by the group. There were few agreements. Nonetheless, an emerging consensus seemed to be that the current state of the art and state of the practice in database management systems (or object management systems) do not support all the needs of process programming.This summary will concentrate on some of the key items and/or issues discussed, followed by some observations made during the session." @default.
• W2039201764 created "2016-06-24" @default.
• W2039201764 creator A5039644681 @default.
• W2039201764 date "1990-10-01" @default.
• W2039201764 modified "2023-09-24" @default.
• W2039201764 title "Data (session summary)" @default.
• W2039201764 doi "https://doi.org/10.5555/317498.317690" @default.
• W2039201764 hasPublicationYear "1990" @default.
• W2039201764 type Work @default.
• W2039201764 sameAs 2039201764 @default.
• W2039201764 citedByCount "0" @default.
• W2039201764 crossrefType "proceedings-article" @default.
• W2039201764 hasAuthorship W2039201764A5039644681 @default.
• W2039201764 hasConcept C136764020 @default.
• W2039201764 hasConcept C154945302 @default.
• W2039201764 hasConcept C177264268 @default.
• W2039201764 hasConcept C199360897 @default.
• W2039201764 hasConcept C2522767166 @default.
• W2039201764 hasConcept C26517878 @default.
• W2039201764 hasConcept C2776760102 @default.
• W2039201764 hasConcept C2779182362 @default.
• W2039201764 hasConcept C2781238097 @default.
• W2039201764 hasConcept C38652104 @default.
• W2039201764 hasConcept C41008148 @default.
• W2039201764 hasConcept C98045186 @default.
• W2039201764 hasConceptScore W2039201764C136764020 @default.
• W2039201764 hasConceptScore W2039201764C154945302 @default.
• W2039201764 hasConceptScore W2039201764C177264268 @default.
• W2039201764 hasConceptScore W2039201764C199360897 @default.
• W2039201764 hasConceptScore W2039201764C2522767166 @default.
• W2039201764 hasConceptScore W2039201764C26517878 @default.
• W2039201764 hasConceptScore W2039201764C2776760102 @default.
• W2039201764 hasConceptScore W2039201764C2779182362 @default.
• W2039201764 hasConceptScore W2039201764C2781238097 @default.
• W2039201764 hasConceptScore W2039201764C38652104 @default.
• W2039201764 hasConceptScore W2039201764C41008148 @default.
• W2039201764 hasConceptScore W2039201764C98045186 @default.
• W2039201764 hasLocation W20392017641 @default.
• W2039201764 hasOpenAccess W2039201764 @default.
• W2039201764 hasPrimaryLocation W20392017641 @default.
• W2039201764 hasRelatedWork W1481103219 @default.
• W2039201764 hasRelatedWork W1522368024 @default.
• W2039201764 hasRelatedWork W1539679283 @default.
• W2039201764 hasRelatedWork W1580941454 @default.
• W2039201764 hasRelatedWork W1964087585 @default.
• W2039201764 hasRelatedWork W1967913860 @default.
• W2039201764 hasRelatedWork W2005382715 @default.
• W2039201764 hasRelatedWork W2042159901 @default.
• W2039201764 hasRelatedWork W2049709741 @default.
• W2039201764 hasRelatedWork W2138152020 @default.
• W2039201764 hasRelatedWork W2169150898 @default.
• W2039201764 hasRelatedWork W2186860402 @default.
• W2039201764 hasRelatedWork W2189373480 @default.
• W2039201764 hasRelatedWork W2249951209 @default.
• W2039201764 hasRelatedWork W2278686610 @default.
• W2039201764 hasRelatedWork W2478896397 @default.
• W2039201764 hasRelatedWork W2745594707 @default.
• W2039201764 hasRelatedWork W27731943 @default.
• W2039201764 hasRelatedWork W3198468001 @default.
• W2039201764 hasRelatedWork W2610931548 @default.
• W2039201764 isParatext "false" @default.
• W2039201764 isRetracted "false" @default.
• W2039201764 magId "2039201764" @default.
• W2039201764 workType "article" @default.