PASS 3: Temporal Dynamics
Case 173: Modification of Signed and Sealed Plans by Other Than Responsible Engineer
Timeline Overview
OWL-Time Temporal Structure 12 relations time: = w3.org/2006/time
Extracted Actions (9)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A prepared subdivision plans consisting of a 5-sheet grading set and a 38-sheet public improvement set, signing and sealing every sheet including the cover sheets.
Temporal Marker: Beginning of timeline, before discharge by client interval
Fluent Transitions:
- Plans Signed and Sealed by Engineer A
Mental State: deliberate
Intended Outcome: Deliver complete, professionally certified subdivision plans to the client
Obligation Engagement:
- Acknowledgment of Design Responsibility (Section III.9)
Guided By Principles:
- Acknowledgment of Design Responsibility (Section III.9)
Required Capabilities:
Field classification (triples vs literals)
fulfillsObligation: Acknowledgment of Design Responsibility (Section III.9)guidedByPrinciple: Acknowledgment of Design Responsibility (Section III.9)requiresCapability: Subdivision design; Grading and public improvement plan preparationinitiates: Plans Signed and Sealed by Engineer A
descriptioncontent: Engineer A prepared subdivision plans consisting of a 5-sheet grading set and a 38-sheet public improvement set, signing and sealing every sheet including the cover sheets.hasAgentcontent: Engineer AtemporalMarkercontent: Beginning of timeline, before discharge by clienteventRoleContextcontent: design engineer retained by clienthasMentalStatecontent: deliberateintendedOutcomecontent: Deliver complete, professionally certified subdivision plans to the clienttextReferencescontent: Engineer A prepared subdivision plans for a client. These plans included a 5-sheet set of grading plans and a 38-sheet set of public improvement plans. Each set had a cover sheet and all sheets in each set were signed and sealed by Engineer A.temporalExtentcontent: intervaltemporalSequencecontent: 1withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Plan_Preparation_and_Sealing",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026585+00:00",
"proeth:description": "Engineer A prepared subdivision plans consisting of a 5-sheet grading set and a 38-sheet public improvement set, signing and sealing every sheet including the cover sheets.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "design engineer retained by client",
"proeth:fulfillsObligation": [
"Acknowledgment of Design Responsibility (Section III.9)"
],
"proeth:guidedByPrinciple": [
"Acknowledgment of Design Responsibility (Section III.9)"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Plans Signed and Sealed by Engineer A"
],
"proeth:intendedOutcome": "Deliver complete, professionally certified subdivision plans to the client",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Subdivision design",
"Grading and public improvement plan preparation"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "Beginning of timeline, before discharge by client",
"proeth:temporalSequence": 1,
"proeth:textReferences": [
"Engineer A prepared subdivision plans for a client. These plans included a 5-sheet set of grading plans and a 38-sheet set of public improvement plans. Each set had a cover sheet and all sheets in each set were signed and sealed by Engineer A."
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Plan Preparation and Sealing"
}
Description: The client, dissatisfied with the plans, discharged Engineer A after paying the complete fee and asked Engineer A for his original drawings.
Temporal Marker: Early in timeline, after plans were produced instant
Fluent Transitions:
- Engineer A Discharged
- Engineer A Client Engagement
Mental State: deliberate
Intended Outcome: End the engagement with Engineer A and obtain the plans for use in a redesign
Field classification (triples vs literals)
initiates: Engineer A Dischargedterminates: Engineer A Client Engagement
descriptioncontent: The client, dissatisfied with the plans, discharged Engineer A after paying the complete fee and asked Engineer A for his original drawings.hasAgentcontent: ClienttemporalMarkercontent: Early in timeline, after plans were producedeventRoleContextcontent: project ownerhasMentalStatecontent: deliberateintendedOutcomecontent: End the engagement with Engineer A and obtain the plans for use in a redesigntextReferencescontent: The client was not satisfied with the plans, so he discharged Engineer A after paying the complete fee for production of the plans. The client asked Engineer A for his original drawings.temporalExtentcontent: instanttemporalSequencecontent: 3withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Engineer_Discharge",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026701+00:00",
"proeth:description": "The client, dissatisfied with the plans, discharged Engineer A after paying the complete fee and asked Engineer A for his original drawings.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "project owner",
"proeth:hasAgent": "Client",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Engineer A Discharged"
],
"proeth:intendedOutcome": "End the engagement with Engineer A and obtain the plans for use in a redesign",
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Early in timeline, after plans were produced",
"proeth:temporalSequence": 3,
"proeth:terminates": [
"Engineer A Client Engagement"
],
"proeth:textReferences": [
"The client was not satisfied with the plans, so he discharged Engineer A after paying the complete fee for production of the plans. The client asked Engineer A for his original drawings."
],
"proeth:withinCompetence": true,
"rdfs:label": "Engineer Discharge"
}
Description: Engineer A complied with the client's request and turned over his original drawings, retaining a set of reproducibles for himself.
Temporal Marker: Immediately after discharge instant
Fluent Transitions:
- Client Possession of Sealed Plans
Mental State: deliberate
Intended Outcome: Comply with the client's request for the original drawings while preserving his own record set
Foreseen Unintended Effects:
- His signed and sealed work product would pass out of his control
Field classification (triples vs literals)
initiates: Client Possession of Sealed Plans
descriptioncontent: Engineer A complied with the client's request and turned over his original drawings, retaining a set of reproducibles for himself.hasAgentcontent: Engineer AtemporalMarkercontent: Immediately after dischargeeventRoleContextcontent: discharged design engineerhasMentalStatecontent: deliberateintendedOutcomecontent: Comply with the client's request for the original drawings while preserving his own record setforeseenUnintendedEffectscontent: His signed and sealed work product would pass out of his controltextReferencescontent: Engineer A complied, retaining a set of reproducibles.temporalExtentcontent: instanttemporalSequencecontent: 5withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Original_Drawings_Transfer",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026740+00:00",
"proeth:description": "Engineer A complied with the client\u0027s request and turned over his original drawings, retaining a set of reproducibles for himself.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "discharged design engineer",
"proeth:foreseenUnintendedEffects": [
"His signed and sealed work product would pass out of his control"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Client Possession of Sealed Plans"
],
"proeth:intendedOutcome": "Comply with the client\u0027s request for the original drawings while preserving his own record set",
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Immediately after discharge",
"proeth:temporalSequence": 5,
"proeth:textReferences": [
"Engineer A complied, retaining a set of reproducibles."
],
"proeth:withinCompetence": true,
"rdfs:label": "Original Drawings Transfer"
}
Description: The client retained Engineer B to review and redesign the project and gave him the set of plans produced by Engineer A to use as a guide in the redesign.
Temporal Marker: After Engineer A's discharge instant
Fluent Transitions:
- Engineer B Retained for Redesign
Mental State: deliberate
Intended Outcome: Obtain a revised project design using Engineer A's plans as a starting point
Field classification (triples vs literals)
initiates: Engineer B Retained for Redesign
descriptioncontent: The client retained Engineer B to review and redesign the project and gave him the set of plans produced by Engineer A to use as a guide in the redesign.hasAgentcontent: ClienttemporalMarkercontent: After Engineer A's dischargeeventRoleContextcontent: project ownerhasMentalStatecontent: deliberateintendedOutcomecontent: Obtain a revised project design using Engineer A's plans as a starting pointtextReferencescontent: Engineer B was later retained by the client to review and redesign the project. The client gave Engineer B the set of plans produced by Engineer A to use as a guide in the redesign.temporalExtentcontent: instanttemporalSequencecontent: 6withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Successor_Engineer_Retention",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026768+00:00",
"proeth:description": "The client retained Engineer B to review and redesign the project and gave him the set of plans produced by Engineer A to use as a guide in the redesign.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "project owner",
"proeth:hasAgent": "Client",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Engineer B Retained for Redesign"
],
"proeth:intendedOutcome": "Obtain a revised project design using Engineer A\u0027s plans as a starting point",
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After Engineer A\u0027s discharge",
"proeth:temporalSequence": 6,
"proeth:textReferences": [
"Engineer B was later retained by the client to review and redesign the project. The client gave Engineer B the set of plans produced by Engineer A to use as a guide in the redesign."
],
"proeth:withinCompetence": true,
"rdfs:label": "Successor Engineer Retention"
}
Description: Engineer B agreed to review and redesign Engineer A's work for the same client without notifying Engineer A. The Board concedes this acceptance itself was not unethical because the client had discharged Engineer A.
Temporal Marker: Upon retention by the client instant
Fluent Transitions:
- Engineer B Review of Engineer A's Work
Mental State: deliberate
Intended Outcome: Take on the review and redesign of the project for the client
Required Capabilities:
Field classification (triples vs literals)
requiresCapability: Design review; Subdivision redesigninitiates: Engineer B Review of Engineer A's Work
descriptioncontent: Engineer B agreed to review and redesign Engineer A's work for the same client without notifying Engineer A. The Board concedes this acceptance itself was not unethical because the client had discharged Engineer A.hasAgentcontent: Engineer BtemporalMarkercontent: Upon retention by the clienteventRoleContextcontent: successor engineerhasMentalStatecontent: deliberateintendedOutcomecontent: Take on the review and redesign of the project for the clienttextReferencescontent: Engineer B did not act unethically in agreeing to review the work of Engineer A without notifying Engineer AtemporalExtentcontent: instanttemporalSequencecontent: 8withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Review_Engagement_Acceptance",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026792+00:00",
"proeth:description": "Engineer B agreed to review and redesign Engineer A\u0027s work for the same client without notifying Engineer A. The Board concedes this acceptance itself was not unethical because the client had discharged Engineer A.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "successor engineer",
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Engineer B Review of Engineer A\u0027s Work"
],
"proeth:intendedOutcome": "Take on the review and redesign of the project for the client",
"proeth:requiresCapability": [
"Design review",
"Subdivision redesign"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Upon retention by the client",
"proeth:temporalSequence": 8,
"proeth:textReferences": [
"Engineer B did not act unethically in agreeing to review the work of Engineer A without notifying Engineer A"
],
"proeth:withinCompetence": true,
"rdfs:label": "Review Engagement Acceptance"
}
Description: Engineer B undertook to modify Engineer A's plans without consulting Engineer A, and neither engineer communicated with the other at any point after Engineer B was retained. The Board states it would have been wiser and more professional for Engineer B to consult with Engineer A first.
Temporal Marker: Throughout the redesign period interval
Fluent Transitions:
- Absence of Communication Between Engineers
Mental State: deliberate omission
Intended Outcome: Proceed with the redesign without engaging the original designer
Foreseen Unintended Effects:
- Loss of the original engineer's explanations of technical decisions in the original design
Guided By Principles:
- Professional Courtesy in Review (Section III.8.a)
Field classification (triples vs literals)
guidedByPrinciple: Professional Courtesy in Review (Section III.8.a)initiates: Absence of Communication Between Engineers
descriptioncontent: Engineer B undertook to modify Engineer A's plans without consulting Engineer A, and neither engineer communicated with the other at any point after Engineer B was retained. The Board states it would have been wiser and more professional for Engineer B to consult with Engineer A first.hasAgentcontent: Engineer BtemporalMarkercontent: Throughout the redesign periodeventRoleContextcontent: successor engineerhasMentalStatecontent: deliberate omissionintendedOutcomecontent: Proceed with the redesign without engaging the original designerforeseenUnintendedEffectscontent: Loss of the original engineer's explanations of technical decisions in the original designtextReferencescontent: At no time after Engineer B was retained were there any communications between the two engineers.; we think it would have been wiser and more professional for Engineer B to consult with Engineer A before undertaking to modify the plans prepared by Engineer AtemporalExtentcontent: intervaltemporalSequencecontent: 9withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Consultation_Omission",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026817+00:00",
"proeth:description": "Engineer B undertook to modify Engineer A\u0027s plans without consulting Engineer A, and neither engineer communicated with the other at any point after Engineer B was retained. The Board states it would have been wiser and more professional for Engineer B to consult with Engineer A first.",
"proeth:discoveredInSection": "discussion",
"proeth:eventRoleContext": "successor engineer",
"proeth:foreseenUnintendedEffects": [
"Loss of the original engineer\u0027s explanations of technical decisions in the original design"
],
"proeth:guidedByPrinciple": [
"Professional Courtesy in Review (Section III.8.a)"
],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate omission",
"proeth:initiates": [
"Absence of Communication Between Engineers"
],
"proeth:intendedOutcome": "Proceed with the redesign without engaging the original designer",
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "Throughout the redesign period",
"proeth:temporalSequence": 9,
"proeth:textReferences": [
"At no time after Engineer B was retained were there any communications between the two engineers.",
"we think it would have been wiser and more professional for Engineer B to consult with Engineer A before undertaking to modify the plans prepared by Engineer A"
],
"proeth:withinCompetence": true,
"rdfs:label": "Consultation Omission"
}
Description: Engineer B changed the grading plans, deleting one sheet, raising the elevation of the housing pads, and rerouting the street, without noting what changes were made and without signing any of the sheets including the cover sheet.
Temporal Marker: During the redesign interval
Fluent Transitions:
- Misleading Plan Attribution
Mental State: deliberate as to the changes, misleading either intentionally or unwittingly as to documentation
Intended Outcome: Revise the grading design to meet the client's redesign objectives
Foreseen Unintended Effects:
- Ambiguity about who authored and bears responsibility for the modified grading plans
Obligation Engagement:
- Duty to Note All Design Changes (Section III.3.a)
- Acknowledgment of Design Responsibility (Section III.9)
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Duty to Note All Design Changes (Section III.3.a); Acknowledgment of Design Responsibility (Section III.9)requiresCapability: Grading design; Engineering judgmentinitiates: Misleading Plan Attribution
descriptioncontent: Engineer B changed the grading plans, deleting one sheet, raising the elevation of the housing pads, and rerouting the street, without noting what changes were made and without signing any of the sheets including the cover sheet.hasAgentcontent: Engineer BtemporalMarkercontent: During the redesigneventRoleContextcontent: successor engineerhasMentalStatecontent: deliberate as to the changes, misleading either intentionally or unwittingly as to documentationintendedOutcomecontent: Revise the grading design to meet the client's redesign objectivesforeseenUnintendedEffectscontent: Ambiguity about who authored and bears responsibility for the modified grading planstextReferencescontent: Engineer B reviewed the original drawings, made changes on the grading plans, including deletion of one sheet, raising the elevation of the housing pads and changing routing of the street. Engineer B did not note what changes were made nor did he sign any of the sheets, including the cover sheet.temporalExtentcontent: intervaltemporalSequencecontent: 10withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Undocumented_Grading_Plan_Modification",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026841+00:00",
"proeth:description": "Engineer B changed the grading plans, deleting one sheet, raising the elevation of the housing pads, and rerouting the street, without noting what changes were made and without signing any of the sheets including the cover sheet.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "successor engineer",
"proeth:foreseenUnintendedEffects": [
"Ambiguity about who authored and bears responsibility for the modified grading plans"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate as to the changes, misleading either intentionally or unwittingly as to documentation",
"proeth:initiates": [
"Misleading Plan Attribution"
],
"proeth:intendedOutcome": "Revise the grading design to meet the client\u0027s redesign objectives",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Grading design",
"Engineering judgment"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "During the redesign",
"proeth:temporalSequence": 10,
"proeth:textReferences": [
"Engineer B reviewed the original drawings, made changes on the grading plans, including deletion of one sheet, raising the elevation of the housing pads and changing routing of the street. Engineer B did not note what changes were made nor did he sign any of the sheets, including the cover sheet."
],
"proeth:violatesObligation": [
"Duty to Note All Design Changes (Section III.3.a)",
"Acknowledgment of Design Responsibility (Section III.9)"
],
"proeth:withinCompetence": true,
"rdfs:label": "Undocumented Grading Plan Modification"
}
Description: Engineer B made major design changes to the storm drains, pipe dimensions, sewers, and utilities in the public improvement plans, with no notation of the changes, without signing the plans, and leaving Engineer A's seal and signature intact.
Temporal Marker: During the redesign interval
Fluent Transitions:
- Engineer A Seal on Altered Plans
- Ambiguous Design Responsibility
Mental State: deliberate as to the changes, misleading either intentionally or unwittingly as to documentation
Intended Outcome: Rework the public improvement design for the client's project
Foreseen Unintended Effects:
- Engineer A's seal remaining on substantially altered plans
- Impact of the modifications on the efficacy and integrity of the entire project design
Obligation Engagement:
- Duty to Note All Design Changes (Section III.3.a)
- Acknowledgment of Design Responsibility (Section III.9)
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Duty to Note All Design Changes (Section III.3.a); Acknowledgment of Design Responsibility (Section III.9)requiresCapability: Storm drain and sewer design; Utility designinitiates: Engineer A Seal on Altered Plans; Ambiguous Design Responsibility
descriptioncontent: Engineer B made major design changes to the storm drains, pipe dimensions, sewers, and utilities in the public improvement plans, with no notation of the changes, without signing the plans, and leaving Engineer A's seal and signature intact.hasAgentcontent: Engineer BtemporalMarkercontent: During the redesigneventRoleContextcontent: successor engineerhasMentalStatecontent: deliberate as to the changes, misleading either intentionally or unwittingly as to documentationintendedOutcomecontent: Rework the public improvement design for the client's projectforeseenUnintendedEffectscontent: Engineer A's seal remaining on substantially altered plans; Impact of the modifications on the efficacy and integrity of the entire project designtextReferencescontent: Engineer B also made major design changes to the storm drains, pipe dimensions, sewers, and utilities in the public improvement plans. He made no notation of the changes, did not sign the plans, and left Engineer A's seal and signature intact.temporalExtentcontent: intervaltemporalSequencecontent: 11withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Undocumented_Utility_Design_Changes",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026863+00:00",
"proeth:description": "Engineer B made major design changes to the storm drains, pipe dimensions, sewers, and utilities in the public improvement plans, with no notation of the changes, without signing the plans, and leaving Engineer A\u0027s seal and signature intact.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "successor engineer",
"proeth:foreseenUnintendedEffects": [
"Engineer A\u0027s seal remaining on substantially altered plans",
"Impact of the modifications on the efficacy and integrity of the entire project design"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate as to the changes, misleading either intentionally or unwittingly as to documentation",
"proeth:initiates": [
"Engineer A Seal on Altered Plans",
"Ambiguous Design Responsibility"
],
"proeth:intendedOutcome": "Rework the public improvement design for the client\u0027s project",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Storm drain and sewer design",
"Utility design"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "During the redesign",
"proeth:temporalSequence": 11,
"proeth:textReferences": [
"Engineer B also made major design changes to the storm drains, pipe dimensions, sewers, and utilities in the public improvement plans. He made no notation of the changes, did not sign the plans, and left Engineer A\u0027s seal and signature intact."
],
"proeth:violatesObligation": [
"Duty to Note All Design Changes (Section III.3.a)",
"Acknowledgment of Design Responsibility (Section III.9)"
],
"proeth:withinCompetence": true,
"rdfs:label": "Undocumented Utility Design Changes"
}
Description: Engineer B placed a note on the title sheet of the public improvement plans, leaving Engineer A's signature and seal intact, stating that he was taking responsibility for the revisions of the plans, without noting what those changes were. The Board found this notation virtually meaningless and found that Engineer B failed to acknowledge responsibility for the full design.
Temporal Marker: Late in the redesign instant
Fluent Transitions:
- Limited Responsibility Claim on Plans
Mental State: deliberate, intended to limit his responsibility to only the changes he made
Intended Outcome: Claim responsibility only for the revisions rather than the full design
Foreseen Unintended Effects:
- Readers of the plans could not determine which work was Engineer A's and which was Engineer B's
Obligation Engagement:
- Duty to Note All Design Changes (Section III.3.a)
- Acknowledgment of Design Responsibility (Section III.9)
Field classification (triples vs literals)
violatesObligation: Duty to Note All Design Changes (Section III.3.a); Acknowledgment of Design Responsibility (Section III.9)initiates: Limited Responsibility Claim on Plans
descriptioncontent: Engineer B placed a note on the title sheet of the public improvement plans, leaving Engineer A's signature and seal intact, stating that he was taking responsibility for the revisions of the plans, without noting what those changes were. The Board found this notation virtually meaningless and found that Engineer B failed to acknowledge responsibility for the full design.hasAgentcontent: Engineer BtemporalMarkercontent: Late in the redesigneventRoleContextcontent: successor engineerhasMentalStatecontent: deliberate, intended to limit his responsibility to only the changes he madeintendedOutcomecontent: Claim responsibility only for the revisions rather than the full designforeseenUnintendedEffectscontent: Readers of the plans could not determine which work was Engineer A's and which was Engineer B'stextReferencescontent: Engineer B placed a note on the title sheet of the public improvement plans, leaving Engineer A's signature and seal intact, stating that he, Engineer B, is taking responsibility for the "revisions of the plans," making no notation what those changes were.; Engineer B's failure to state with specificity what those changes in fact were made such a notation on the title sheet virtually meaninglesstemporalExtentcontent: instanttemporalSequencecontent: 12withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Action_Vague_Responsibility_Notation",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-12T20:16:25.026885+00:00",
"proeth:description": "Engineer B placed a note on the title sheet of the public improvement plans, leaving Engineer A\u0027s signature and seal intact, stating that he was taking responsibility for the revisions of the plans, without noting what those changes were. The Board found this notation virtually meaningless and found that Engineer B failed to acknowledge responsibility for the full design.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "successor engineer",
"proeth:foreseenUnintendedEffects": [
"Readers of the plans could not determine which work was Engineer A\u0027s and which was Engineer B\u0027s"
],
"proeth:fulfillsObligation": [],
"proeth:hasAgent": "Engineer B",
"proeth:hasMentalState": "deliberate, intended to limit his responsibility to only the changes he made",
"proeth:initiates": [
"Limited Responsibility Claim on Plans"
],
"proeth:intendedOutcome": "Claim responsibility only for the revisions rather than the full design",
"proeth:raisesObligation": [],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Late in the redesign",
"proeth:temporalSequence": 12,
"proeth:textReferences": [
"Engineer B placed a note on the title sheet of the public improvement plans, leaving Engineer A\u0027s signature and seal intact, stating that he, Engineer B, is taking responsibility for the \"revisions of the plans,\" making no notation what those changes were.",
"Engineer B\u0027s failure to state with specificity what those changes in fact were made such a notation on the title sheet virtually meaningless"
],
"proeth:violatesObligation": [
"Duty to Note All Design Changes (Section III.3.a)",
"Acknowledgment of Design Responsibility (Section III.9)"
],
"proeth:withinCompetence": true,
"rdfs:label": "Vague Responsibility Notation"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changesDescription: The client became dissatisfied with the subdivision plans prepared by Engineer A, which set in motion the discharge and the retention of a successor engineer.
Temporal Marker: After Engineer A delivered the completed subdivision plans instant
Fluent Transitions:
- Client Dissatisfaction State
Caused By Action: Action_Plan_Preparation_and_Sealing
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/173#Action_Plan_Preparation_and_Sealinginitiates: Client Dissatisfaction State
descriptioncontent: The client became dissatisfied with the subdivision plans prepared by Engineer A, which set in motion the discharge and the retention of a successor engineer.temporalMarkercontent: After Engineer A delivered the completed subdivision planstextReferencescontent: The client was not satisfied with the plans, so he discharged Engineer A after paying the complete fee for production of the plans.eventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 2confidenceassessment: 0.9
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Event_Client_Dissatisfaction",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-12T20:16:25.026969+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/173#Action_Plan_Preparation_and_Sealing",
"proeth:confidence": "0.9",
"proeth:description": "The client became dissatisfied with the subdivision plans prepared by Engineer A, which set in motion the discharge and the retention of a successor engineer.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Client Dissatisfaction State"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After Engineer A delivered the completed subdivision plans",
"proeth:temporalSequence": 2,
"proeth:textReferences": [
"The client was not satisfied with the plans, so he discharged Engineer A after paying the complete fee for production of the plans."
],
"rdfs:label": "Client Dissatisfaction"
}
Description: The contractual relationship between Engineer A and the client came to an end as a consequence of the discharge, with the full fee paid, ending Engineer A's status as the retained engineer on the project.
Temporal Marker: Upon discharge of Engineer A by the client instant
Fluent Transitions:
- Engineer A Discharged State
- Engineer A Retention State
Caused By Action: Action_Engineer_Discharge
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/173#Action_Engineer_Dischargeinitiates: Engineer A Discharged Stateterminates: Engineer A Retention State
descriptioncontent: The contractual relationship between Engineer A and the client came to an end as a consequence of the discharge, with the full fee paid, ending Engineer A's status as the retained engineer on the project.temporalMarkercontent: Upon discharge of Engineer A by the clienttextReferencescontent: the client clearly discharged Engineer A from his services; he discharged Engineer A after paying the complete fee for production of the planseventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 4confidenceassessment: 0.88
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Event_Professional_Relationship_Termination",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-12T20:16:25.027002+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/173#Action_Engineer_Discharge",
"proeth:confidence": "0.88",
"proeth:description": "The contractual relationship between Engineer A and the client came to an end as a consequence of the discharge, with the full fee paid, ending Engineer A\u0027s status as the retained engineer on the project.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Engineer A Discharged State"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Upon discharge of Engineer A by the client",
"proeth:temporalSequence": 4,
"proeth:terminates": [
"Engineer A Retention State"
],
"proeth:textReferences": [
"the client clearly discharged Engineer A from his services",
"he discharged Engineer A after paying the complete fee for production of the plans"
],
"rdfs:label": "Professional Relationship Termination"
}
Description: Despite the discharge, Engineer A came to maintain an ongoing connection with the project because the client passed his signed and sealed work product along to Engineer B for use in the redesign.
Temporal Marker: When the client gave Engineer A's plans to Engineer B interval
Fluent Transitions:
- Engineer A Work Connection State
Caused By Action: Action_Successor_Engineer_Retention
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/173#Action_Successor_Engineer_Retentioninitiates: Engineer A Work Connection State
descriptioncontent: Despite the discharge, Engineer A came to maintain an ongoing connection with the project because the client passed his signed and sealed work product along to Engineer B for use in the redesign.temporalMarkercontent: When the client gave Engineer A's plans to Engineer BtextReferencescontent: Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A's work product to Engineer BeventTypecontent: outcometemporalExtentcontent: intervaltemporalSequencecontent: 7confidenceassessment: 0.85
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Event_Residual_Work_Connection",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-12T20:16:25.027029+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/173#Action_Successor_Engineer_Retention",
"proeth:confidence": "0.85",
"proeth:description": "Despite the discharge, Engineer A came to maintain an ongoing connection with the project because the client passed his signed and sealed work product along to Engineer B for use in the redesign.",
"proeth:discoveredInSection": "discussion",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Engineer A Work Connection State"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "When the client gave Engineer A\u0027s plans to Engineer B",
"proeth:temporalSequence": 7,
"proeth:textReferences": [
"Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A\u0027s work product to Engineer B"
],
"rdfs:label": "Residual Work Connection"
}
Description: The title sheet notation taking responsibility for revisions became virtually meaningless because Engineer B failed to specify what the changes were.
Temporal Marker: Upon placement of the vague title sheet note instant
Fluent Transitions:
- Ineffective Responsibility Disclosure State
Caused By Action: Action_Vague_Responsibility_Notation
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/173#Action_Vague_Responsibility_Notationinitiates: Ineffective Responsibility Disclosure State
descriptioncontent: The title sheet notation taking responsibility for revisions became virtually meaningless because Engineer B failed to specify what the changes were.temporalMarkercontent: Upon placement of the vague title sheet notetextReferencescontent: Engineer B's failure to state with specificity what those changes in fact were made such a notation on the title sheet virtually meaninglesseventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 13confidenceassessment: 0.82
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Event_Notation_Rendered_Meaningless",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-12T20:16:25.027074+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/173#Action_Vague_Responsibility_Notation",
"proeth:confidence": "0.82",
"proeth:description": "The title sheet notation taking responsibility for revisions became virtually meaningless because Engineer B failed to specify what the changes were.",
"proeth:discoveredInSection": "discussion",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Ineffective Responsibility Disclosure State"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Upon placement of the vague title sheet note",
"proeth:temporalSequence": 13,
"proeth:textReferences": [
"Engineer B\u0027s failure to state with specificity what those changes in fact were made such a notation on the title sheet virtually meaningless"
],
"rdfs:label": "Notation Rendered Meaningless"
}
Description: As a consequence of Engineer B's undocumented modifications while Engineer A's seal and signature remained intact, the plans became misleading, blending the work of both engineers with no indication of which work belonged to whom.
Temporal Marker: After Engineer B completed his modifications to the plans interval
Fluent Transitions:
- Misleading Plan Attribution State
- Authorship Ambiguity State
Caused By Action: Action_Undocumented_Utility_Design_Changes
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/173#Action_Undocumented_Utility_Design_Changesinitiates: Misleading Plan Attribution State; Authorship Ambiguity State
descriptioncontent: As a consequence of Engineer B's undocumented modifications while Engineer A's seal and signature remained intact, the plans became misleading, blending the work of both engineers with no indication of which work belonged to whom.temporalMarkercontent: After Engineer B completed his modifications to the planstextReferencescontent: We view the conduct of Engineer B under the facts of this case to be misleading either intentionally or unwittingly.; His failure to do so constituted a form of deception which places him in violation of Section III.3.a.; never indicating which represented the work of Engineer A and which represented his own workeventTypecontent: outcometemporalExtentcontent: intervaltemporalSequencecontent: 14confidenceassessment: 0.87
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"time": "http://www.w3.org/2006/time#"
},
"@id": "http://proethica.org/ontology/case/173#Event_Misleading_Plans_Condition",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-12T20:16:25.027052+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/173#Action_Undocumented_Utility_Design_Changes",
"proeth:confidence": "0.87",
"proeth:description": "As a consequence of Engineer B\u0027s undocumented modifications while Engineer A\u0027s seal and signature remained intact, the plans became misleading, blending the work of both engineers with no indication of which work belonged to whom.",
"proeth:discoveredInSection": "discussion",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Misleading Plan Attribution State",
"Authorship Ambiguity State"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "After Engineer B completed his modifications to the plans",
"proeth:temporalSequence": 14,
"proeth:textReferences": [
"We view the conduct of Engineer B under the facts of this case to be misleading either intentionally or unwittingly.",
"His failure to do so constituted a form of deception which places him in violation of Section III.3.a.",
"never indicating which represented the work of Engineer A and which represented his own work"
],
"rdfs:label": "Misleading Plans Condition"
}
Causal Chains (7)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: The client was not satisfied with the plans, so he discharged Engineer A after paying the complete fee for production of the plans.
Necessary Factors (NESS):
- Client's dissatisfaction with the subdivision plans
- Client's authority to terminate the engineering engagement
- Completion of the plan production for which fees were owed
Sufficient Factors:
- Client dissatisfaction combined with the client's contractual right to discharge the engineer
Responsibility Attribution:
Agent: Client
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Plan Preparation and Sealing
Engineer A prepares, signs, and seals the 5-sheet grading set and 38-sheet public improvement set -
Client Dissatisfaction
The client becomes dissatisfied with the plans produced by Engineer A -
Engineer Discharge
The client discharges Engineer A after paying the complete fee and requests the original drawings
Field classification (triples vs literals)
cause: Client Dissatisfactioneffect: Engineer DischargeresponsibleAgent: Client
causalLanguagecontent: The client was not satisfied with the plans, so he discharged Engineer A after paying the complete fee for production of the plans.necessaryFactorscontent: Client's dissatisfaction with the subdivision plans; Client's authority to terminate the engineering engagement; Completion of the plan production for which fees were owedsufficientFactorscontent: Client dissatisfaction combined with the client's contractual right to discharge the engineercounterfactualcontent: Had the client been satisfied with the plans, Engineer A would not have been discharged and the successor-engineer chain of events would not have begunagentKnowledgecontent: Client knew the plans did not meet his expectations and knew he could terminate the relationship after paying the feecausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Plan Preparation and Sealing', 'proeth:description': 'Engineer A prepares, signs, and seals the 5-sheet grading set and 38-sheet public improvement set'}; {'proeth:step': 2, 'proeth:element': 'Client Dissatisfaction', 'proeth:description': 'The client becomes dissatisfied with the plans produced by Engineer A'}; {'proeth:step': 3, 'proeth:element': 'Engineer Discharge', 'proeth:description': 'The client discharges Engineer A after paying the complete fee and requests the original drawings'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/ontology/case/173#CausalChain_1",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-12T20:16:25.027131+00:00",
"proeth:agentKnowledge": "Client knew the plans did not meet his expectations and knew he could terminate the relationship after paying the fee",
"proeth:causalLanguage": "The client was not satisfied with the plans, so he discharged Engineer A after paying the complete fee for production of the plans.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A prepares, signs, and seals the 5-sheet grading set and 38-sheet public improvement set",
"proeth:element": "Plan Preparation and Sealing",
"proeth:step": 1
},
{
"proeth:description": "The client becomes dissatisfied with the plans produced by Engineer A",
"proeth:element": "Client Dissatisfaction",
"proeth:step": 2
},
{
"proeth:description": "The client discharges Engineer A after paying the complete fee and requests the original drawings",
"proeth:element": "Engineer Discharge",
"proeth:step": 3
}
],
"proeth:cause": "Client Dissatisfaction",
"proeth:counterfactual": "Had the client been satisfied with the plans, Engineer A would not have been discharged and the successor-engineer chain of events would not have begun",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Engineer Discharge",
"proeth:necessaryFactors": [
"Client\u0027s dissatisfaction with the subdivision plans",
"Client\u0027s authority to terminate the engineering engagement",
"Completion of the plan production for which fees were owed"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Client",
"proeth:sufficientFactors": [
"Client dissatisfaction combined with the client\u0027s contractual right to discharge the engineer"
],
"proeth:withinAgentControl": true
}
Causal Language: While it is true that Engineer A had been "discharged" by the client, Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A's work product to Engineer B.
Necessary Factors (NESS):
- Client's act of discharging Engineer A
- Payment of the complete fee closing out contractual obligations
Sufficient Factors:
- Discharge with full payment was itself sufficient to end the contractual relationship
Responsibility Attribution:
Agent: Client
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Client Dissatisfaction
Client is not satisfied with the plans -
Engineer Discharge
Client discharges Engineer A after paying the complete fee -
Professional Relationship Termination
The contractual relationship between Engineer A and the client comes to an end
Field classification (triples vs literals)
cause: Engineer Dischargeeffect: Professional Relationship TerminationresponsibleAgent: Client
causalLanguagecontent: While it is true that Engineer A had been "discharged" by the client, Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A's work product to Engineer B.necessaryFactorscontent: Client's act of discharging Engineer A; Payment of the complete fee closing out contractual obligationssufficientFactorscontent: Discharge with full payment was itself sufficient to end the contractual relationshipcounterfactualcontent: Without the discharge, the contractual relationship would have continued and Section III.8.a. would have required Engineer B to obtain Engineer A's expressed knowledge before reviewing the workagentKnowledgecontent: Client knowingly ended the engagement after paying the complete feecausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Client Dissatisfaction', 'proeth:description': 'Client is not satisfied with the plans'}; {'proeth:step': 2, 'proeth:element': 'Engineer Discharge', 'proeth:description': 'Client discharges Engineer A after paying the complete fee'}; {'proeth:step': 3, 'proeth:element': 'Professional Relationship Termination', 'proeth:description': 'The contractual relationship between Engineer A and the client comes to an end'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/ontology/case/173#CausalChain_2",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-12T20:16:25.027207+00:00",
"proeth:agentKnowledge": "Client knowingly ended the engagement after paying the complete fee",
"proeth:causalLanguage": "While it is true that Engineer A had been \"discharged\" by the client, Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A\u0027s work product to Engineer B.",
"proeth:causalSequence": [
{
"proeth:description": "Client is not satisfied with the plans",
"proeth:element": "Client Dissatisfaction",
"proeth:step": 1
},
{
"proeth:description": "Client discharges Engineer A after paying the complete fee",
"proeth:element": "Engineer Discharge",
"proeth:step": 2
},
{
"proeth:description": "The contractual relationship between Engineer A and the client comes to an end",
"proeth:element": "Professional Relationship Termination",
"proeth:step": 3
}
],
"proeth:cause": "Engineer Discharge",
"proeth:counterfactual": "Without the discharge, the contractual relationship would have continued and Section III.8.a. would have required Engineer B to obtain Engineer A\u0027s expressed knowledge before reviewing the work",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Professional Relationship Termination",
"proeth:necessaryFactors": [
"Client\u0027s act of discharging Engineer A",
"Payment of the complete fee closing out contractual obligations"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Client",
"proeth:sufficientFactors": [
"Discharge with full payment was itself sufficient to end the contractual relationship"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A's work product to Engineer B.
Necessary Factors (NESS):
- Client's decision to give Engineer A's plans to Engineer B as a guide
- Engineer A's signature and seal remaining on the plans
- Engineer B's retention to review and redesign the project
Sufficient Factors:
- Transfer of Engineer A's sealed work product to Engineer B for use in the redesign
Responsibility Attribution:
Agent: Client
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Engineer Discharge
Client discharges Engineer A and asks for the original drawings -
Original Drawings Transfer
Engineer A complies, turning over the originals and retaining reproducibles -
Successor Engineer Retention
Client retains Engineer B and gives him Engineer A's plans as a guide -
Residual Work Connection
Engineer A maintains an ongoing connection with the project through his work product
Field classification (triples vs literals)
cause: Successor Engineer Retentioneffect: Residual Work ConnectionresponsibleAgent: Client
causalLanguagecontent: Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A's work product to Engineer B.necessaryFactorscontent: Client's decision to give Engineer A's plans to Engineer B as a guide; Engineer A's signature and seal remaining on the plans; Engineer B's retention to review and redesign the projectsufficientFactorscontent: Transfer of Engineer A's sealed work product to Engineer B for use in the redesigncounterfactualcontent: Had the client commissioned an entirely new design from scratch without providing Engineer A's plans, Engineer A would have had no residual connection to the ongoing workagentKnowledgecontent: Client knew the plans were Engineer A's signed and sealed work product when he passed them to Engineer B as a guideinterveningFactorscontent: Engineer A's compliance in turning over original drawingscausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Engineer Discharge', 'proeth:description': 'Client discharges Engineer A and asks for the original drawings'}; {'proeth:step': 2, 'proeth:element': 'Original Drawings Transfer', 'proeth:description': 'Engineer A complies, turning over the originals and retaining reproducibles'}; {'proeth:step': 3, 'proeth:element': 'Successor Engineer Retention', 'proeth:description': "Client retains Engineer B and gives him Engineer A's plans as a guide"}; {'proeth:step': 4, 'proeth:element': 'Residual Work Connection', 'proeth:description': 'Engineer A maintains an ongoing connection with the project through his work product'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/ontology/case/173#CausalChain_3",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-12T20:16:25.027231+00:00",
"proeth:agentKnowledge": "Client knew the plans were Engineer A\u0027s signed and sealed work product when he passed them to Engineer B as a guide",
"proeth:causalLanguage": "Engineer A still maintained a connection with the work which he had performed by virtue of the fact that the client passed along Engineer A\u0027s work product to Engineer B.",
"proeth:causalSequence": [
{
"proeth:description": "Client discharges Engineer A and asks for the original drawings",
"proeth:element": "Engineer Discharge",
"proeth:step": 1
},
{
"proeth:description": "Engineer A complies, turning over the originals and retaining reproducibles",
"proeth:element": "Original Drawings Transfer",
"proeth:step": 2
},
{
"proeth:description": "Client retains Engineer B and gives him Engineer A\u0027s plans as a guide",
"proeth:element": "Successor Engineer Retention",
"proeth:step": 3
},
{
"proeth:description": "Engineer A maintains an ongoing connection with the project through his work product",
"proeth:element": "Residual Work Connection",
"proeth:step": 4
}
],
"proeth:cause": "Successor Engineer Retention",
"proeth:counterfactual": "Had the client commissioned an entirely new design from scratch without providing Engineer A\u0027s plans, Engineer A would have had no residual connection to the ongoing work",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Residual Work Connection",
"proeth:interveningFactors": [
"Engineer A\u0027s compliance in turning over original drawings"
],
"proeth:necessaryFactors": [
"Client\u0027s decision to give Engineer A\u0027s plans to Engineer B as a guide",
"Engineer A\u0027s signature and seal remaining on the plans",
"Engineer B\u0027s retention to review and redesign the project"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Client",
"proeth:sufficientFactors": [
"Transfer of Engineer A\u0027s sealed work product to Engineer B for use in the redesign"
],
"proeth:withinAgentControl": true
}
Causal Language: At no time after Engineer B was retained were there any communications between the two engineers.
Necessary Factors (NESS):
- Engineer B's acceptance of the review and redesign engagement
- Engineer B's decision not to notify or consult Engineer A
Sufficient Factors:
- Acceptance of the engagement combined with the choice to proceed without any communication with Engineer A
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Successor Engineer Retention
Client retains Engineer B and provides Engineer A's plans -
Review Engagement Acceptance
Engineer B agrees to review and redesign without notifying Engineer A -
Consultation Omission
Engineer B modifies the plans without any communication with Engineer A
Field classification (triples vs literals)
cause: Review Engagement Acceptanceeffect: Consultation OmissionresponsibleAgent: Engineer B
causalLanguagecontent: At no time after Engineer B was retained were there any communications between the two engineers.necessaryFactorscontent: Engineer B's acceptance of the review and redesign engagement; Engineer B's decision not to notify or consult Engineer AsufficientFactorscontent: Acceptance of the engagement combined with the choice to proceed without any communication with Engineer Acounterfactualcontent: Had Engineer B declined the engagement, or had he contacted Engineer A upon retention, the consultation omission would not have occurredagentKnowledgecontent: Engineer B knew the plans were the signed and sealed work of Engineer A and knew he had not communicated with Engineer AinterveningFactorscontent: Engineer A had already been discharged, so Section III.8.a. did not strictly require notificationcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Successor Engineer Retention', 'proeth:description': "Client retains Engineer B and provides Engineer A's plans"}; {'proeth:step': 2, 'proeth:element': 'Review Engagement Acceptance', 'proeth:description': 'Engineer B agrees to review and redesign without notifying Engineer A'}; {'proeth:step': 3, 'proeth:element': 'Consultation Omission', 'proeth:description': 'Engineer B modifies the plans without any communication with Engineer A'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/ontology/case/173#CausalChain_4",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-12T20:16:25.027250+00:00",
"proeth:agentKnowledge": "Engineer B knew the plans were the signed and sealed work of Engineer A and knew he had not communicated with Engineer A",
"proeth:causalLanguage": "At no time after Engineer B was retained were there any communications between the two engineers.",
"proeth:causalSequence": [
{
"proeth:description": "Client retains Engineer B and provides Engineer A\u0027s plans",
"proeth:element": "Successor Engineer Retention",
"proeth:step": 1
},
{
"proeth:description": "Engineer B agrees to review and redesign without notifying Engineer A",
"proeth:element": "Review Engagement Acceptance",
"proeth:step": 2
},
{
"proeth:description": "Engineer B modifies the plans without any communication with Engineer A",
"proeth:element": "Consultation Omission",
"proeth:step": 3
}
],
"proeth:cause": "Review Engagement Acceptance",
"proeth:counterfactual": "Had Engineer B declined the engagement, or had he contacted Engineer A upon retention, the consultation omission would not have occurred",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Consultation Omission",
"proeth:interveningFactors": [
"Engineer A had already been discharged, so Section III.8.a. did not strictly require notification"
],
"proeth:necessaryFactors": [
"Engineer B\u0027s acceptance of the review and redesign engagement",
"Engineer B\u0027s decision not to notify or consult Engineer A"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"Acceptance of the engagement combined with the choice to proceed without any communication with Engineer A"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer B did not note what changes were made nor did he sign any of the sheets, including the cover sheet.
Necessary Factors (NESS):
- Substantive changes to the grading plans (sheet deletion, raised housing pads, rerouted street)
- Failure to note what changes were made
- Failure to sign any of the sheets, including the cover sheet
Sufficient Factors:
- Making substantive design changes while leaving no notation and no signature identifying the modifier
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Successor Engineer Retention
Client gives Engineer B the plans to use as a guide in the redesign -
Undocumented Grading Plan Modification
Engineer B deletes one sheet, raises housing pad elevations, and changes street routing without notation or signature -
Misleading Plans Condition
The plans deceptively suggest that the modified design remains the work reviewed and sealed by Engineer A
Field classification (triples vs literals)
cause: Undocumented Grading Plan Modificationeffect: Misleading Plans ConditionresponsibleAgent: Engineer B
causalLanguagecontent: Engineer B did not note what changes were made nor did he sign any of the sheets, including the cover sheet.necessaryFactorscontent: Substantive changes to the grading plans (sheet deletion, raised housing pads, rerouted street); Failure to note what changes were made; Failure to sign any of the sheets, including the cover sheetsufficientFactorscontent: Making substantive design changes while leaving no notation and no signature identifying the modifiercounterfactualcontent: Had Engineer B noted his changes and signed the modified sheets, the grading plans would have accurately represented authorship and would not have been misleadingagentKnowledgecontent: Engineer B knew he had made changes including deleting a sheet, raising pad elevations, and rerouting the street, and knew he had not documented or signed themcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Successor Engineer Retention', 'proeth:description': 'Client gives Engineer B the plans to use as a guide in the redesign'}; {'proeth:step': 2, 'proeth:element': 'Undocumented Grading Plan Modification', 'proeth:description': 'Engineer B deletes one sheet, raises housing pad elevations, and changes street routing without notation or signature'}; {'proeth:step': 3, 'proeth:element': 'Misleading Plans Condition', 'proeth:description': 'The plans deceptively suggest that the modified design remains the work reviewed and sealed by Engineer A'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/ontology/case/173#CausalChain_5",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-12T20:16:25.027269+00:00",
"proeth:agentKnowledge": "Engineer B knew he had made changes including deleting a sheet, raising pad elevations, and rerouting the street, and knew he had not documented or signed them",
"proeth:causalLanguage": "Engineer B did not note what changes were made nor did he sign any of the sheets, including the cover sheet.",
"proeth:causalSequence": [
{
"proeth:description": "Client gives Engineer B the plans to use as a guide in the redesign",
"proeth:element": "Successor Engineer Retention",
"proeth:step": 1
},
{
"proeth:description": "Engineer B deletes one sheet, raises housing pad elevations, and changes street routing without notation or signature",
"proeth:element": "Undocumented Grading Plan Modification",
"proeth:step": 2
},
{
"proeth:description": "The plans deceptively suggest that the modified design remains the work reviewed and sealed by Engineer A",
"proeth:element": "Misleading Plans Condition",
"proeth:step": 3
}
],
"proeth:cause": "Undocumented Grading Plan Modification",
"proeth:counterfactual": "Had Engineer B noted his changes and signed the modified sheets, the grading plans would have accurately represented authorship and would not have been misleading",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Misleading Plans Condition",
"proeth:necessaryFactors": [
"Substantive changes to the grading plans (sheet deletion, raised housing pads, rerouted street)",
"Failure to note what changes were made",
"Failure to sign any of the sheets, including the cover sheet"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"Making substantive design changes while leaving no notation and no signature identifying the modifier"
],
"proeth:withinAgentControl": true
}
Causal Language: His failure to do so constituted a form of deception which places him in violation of Section III.3.a.
Necessary Factors (NESS):
- Major design changes to storm drains, pipe dimensions, sewers, and utilities
- No notation of the changes and no signature by Engineer B
- Engineer A's seal and signature left intact on the plans
Sufficient Factors:
- Major undocumented modifications combined with Engineer A's intact seal, which attributes the altered design to Engineer A
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Successor Engineer Retention
Client provides Engineer A's sealed public improvement plans to Engineer B -
Undocumented Utility Design Changes
Engineer B makes major changes to storm drains, pipe dimensions, sewers, and utilities without notation or signature, leaving Engineer A's seal intact -
Misleading Plans Condition
The plans deceptively attribute the mixed-and-matched design to Engineer A, a form of deception violating Section III.3.a.
Field classification (triples vs literals)
cause: Undocumented Utility Design Changeseffect: Misleading Plans ConditionresponsibleAgent: Engineer B
causalLanguagecontent: His failure to do so constituted a form of deception which places him in violation of Section III.3.a.necessaryFactorscontent: Major design changes to storm drains, pipe dimensions, sewers, and utilities; No notation of the changes and no signature by Engineer B; Engineer A's seal and signature left intact on the planssufficientFactorscontent: Major undocumented modifications combined with Engineer A's intact seal, which attributes the altered design to Engineer Acounterfactualcontent: Had Engineer B made all necessary notations of the changes to the storm drains, pipe dimensions, sewers, and utilities, the plans would not have constituted a form of deceptionagentKnowledgecontent: Engineer B knew he had made major design changes and knew Engineer A's seal and signature remained intact on the plansinterveningFactorscontent: Client's instruction to use Engineer A's plans as a guidecausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Successor Engineer Retention', 'proeth:description': "Client provides Engineer A's sealed public improvement plans to Engineer B"}; {'proeth:step': 2, 'proeth:element': 'Undocumented Utility Design Changes', 'proeth:description': "Engineer B makes major changes to storm drains, pipe dimensions, sewers, and utilities without notation or signature, leaving Engineer A's seal intact"}; {'proeth:step': 3, 'proeth:element': 'Misleading Plans Condition', 'proeth:description': 'The plans deceptively attribute the mixed-and-matched design to Engineer A, a form of deception violating Section III.3.a.'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/ontology/case/173#CausalChain_6",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-12T20:16:25.027286+00:00",
"proeth:agentKnowledge": "Engineer B knew he had made major design changes and knew Engineer A\u0027s seal and signature remained intact on the plans",
"proeth:causalLanguage": "His failure to do so constituted a form of deception which places him in violation of Section III.3.a.",
"proeth:causalSequence": [
{
"proeth:description": "Client provides Engineer A\u0027s sealed public improvement plans to Engineer B",
"proeth:element": "Successor Engineer Retention",
"proeth:step": 1
},
{
"proeth:description": "Engineer B makes major changes to storm drains, pipe dimensions, sewers, and utilities without notation or signature, leaving Engineer A\u0027s seal intact",
"proeth:element": "Undocumented Utility Design Changes",
"proeth:step": 2
},
{
"proeth:description": "The plans deceptively attribute the mixed-and-matched design to Engineer A, a form of deception violating Section III.3.a.",
"proeth:element": "Misleading Plans Condition",
"proeth:step": 3
}
],
"proeth:cause": "Undocumented Utility Design Changes",
"proeth:counterfactual": "Had Engineer B made all necessary notations of the changes to the storm drains, pipe dimensions, sewers, and utilities, the plans would not have constituted a form of deception",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Misleading Plans Condition",
"proeth:interveningFactors": [
"Client\u0027s instruction to use Engineer A\u0027s plans as a guide"
],
"proeth:necessaryFactors": [
"Major design changes to storm drains, pipe dimensions, sewers, and utilities",
"No notation of the changes and no signature by Engineer B",
"Engineer A\u0027s seal and signature left intact on the plans"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"Major undocumented modifications combined with Engineer A\u0027s intact seal, which attributes the altered design to Engineer A"
],
"proeth:withinAgentControl": true
}
Causal Language: However, as we have indicated, Engineer B's failure to state with specificity what those changes in fact were made such a notation on the title sheet virtually meaningless.
Necessary Factors (NESS):
- Placement of a title-sheet note claiming responsibility only for unspecified "revisions of the plans"
- Absence of any notation identifying which changes were made
- Engineer A's signature and seal left intact alongside the note
Sufficient Factors:
- A responsibility notation lacking any specificity about the changes, superimposed on plans still bearing Engineer A's seal
Responsibility Attribution:
Agent: Engineer B
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Undocumented Utility Design Changes
Engineer B makes major undocumented changes to the public improvement plans -
Vague Responsibility Notation
Engineer B places a note on the title sheet taking responsibility for the 'revisions of the plans' without noting what those changes were -
Notation Rendered Meaningless
The lack of specificity makes the responsibility notation virtually meaningless
Field classification (triples vs literals)
cause: Vague Responsibility Notationeffect: Notation Rendered MeaninglessresponsibleAgent: Engineer B
causalLanguagecontent: However, as we have indicated, Engineer B's failure to state with specificity what those changes in fact were made such a notation on the title sheet virtually meaningless.necessaryFactorscontent: Placement of a title-sheet note claiming responsibility only for unspecified "revisions of the plans"; Absence of any notation identifying which changes were made; Engineer A's signature and seal left intact alongside the notesufficientFactorscontent: A responsibility notation lacking any specificity about the changes, superimposed on plans still bearing Engineer A's sealcounterfactualcontent: Had Engineer B stated with specificity what the changes were, the notation would have meaningfully allocated responsibility rather than being virtually meaninglessagentKnowledgecontent: Engineer B knew exactly which modifications he had made yet chose to describe them only as unspecified 'revisions of the plans'causalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Undocumented Utility Design Changes', 'proeth:description': 'Engineer B makes major undocumented changes to the public improvement plans'}; {'proeth:step': 2, 'proeth:element': 'Vague Responsibility Notation', 'proeth:description': "Engineer B places a note on the title sheet taking responsibility for the 'revisions of the plans' without noting what those changes were"}; {'proeth:step': 3, 'proeth:element': 'Notation Rendered Meaningless', 'proeth:description': 'The lack of specificity makes the responsibility notation virtually meaningless'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/173#",
"rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#"
},
"@id": "http://proethica.org/ontology/case/173#CausalChain_7",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-12T20:16:25.027302+00:00",
"proeth:agentKnowledge": "Engineer B knew exactly which modifications he had made yet chose to describe them only as unspecified \u0027revisions of the plans\u0027",
"proeth:causalLanguage": "However, as we have indicated, Engineer B\u0027s failure to state with specificity what those changes in fact were made such a notation on the title sheet virtually meaningless.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer B makes major undocumented changes to the public improvement plans",
"proeth:element": "Undocumented Utility Design Changes",
"proeth:step": 1
},
{
"proeth:description": "Engineer B places a note on the title sheet taking responsibility for the \u0027revisions of the plans\u0027 without noting what those changes were",
"proeth:element": "Vague Responsibility Notation",
"proeth:step": 2
},
{
"proeth:description": "The lack of specificity makes the responsibility notation virtually meaningless",
"proeth:element": "Notation Rendered Meaningless",
"proeth:step": 3
}
],
"proeth:cause": "Vague Responsibility Notation",
"proeth:counterfactual": "Had Engineer B stated with specificity what the changes were, the notation would have meaningfully allocated responsibility rather than being virtually meaningless",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Notation Rendered Meaningless",
"proeth:necessaryFactors": [
"Placement of a title-sheet note claiming responsibility only for unspecified \"revisions of the plans\"",
"Absence of any notation identifying which changes were made",
"Engineer A\u0027s signature and seal left intact alongside the note"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer B",
"proeth:sufficientFactors": [
"A responsibility notation lacking any specificity about the changes, superimposed on plans still bearing Engineer A\u0027s seal"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (12)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| Engineer A's preparation, signing, and sealing of subdivision plans |
before
Entity1 is before Entity2 |
client's discharge of Engineer A |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A prepared subdivision plans for a client... The client was not satisfied with the plans, s... [more] |
| client's payment of the complete fee |
before
Entity1 is before Entity2 |
discharge of Engineer A |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
he discharged Engineer A after paying the complete fee for production of the plans |
| discharge of Engineer A |
before
Entity1 is before Entity2 |
client's request for and receipt of original drawings |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
he discharged Engineer A after paying the complete fee... The client asked Engineer A for his origin... [more] |
| Engineer A's turnover of original drawings (retaining reproducibles) |
before
Entity1 is before Entity2 |
retention of Engineer B |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A complied, retaining a set of reproducibles. Engineer B was later retained by the client t... [more] |
| retention of Engineer B |
before
Entity1 is before Entity2 |
client giving Engineer B the set of plans produced by Engineer A |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer B was later retained by the client... The client gave Engineer B the set of plans produced ... [more] |
| Engineer B's review of the original drawings |
before
Entity1 is before Entity2 |
Engineer B's changes to the grading plans |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer B reviewed the original drawings, made changes on the grading plans, including deletion of ... [more] |
| Engineer B's review of Engineer A's work |
before
Entity1 is before Entity2 |
Engineer B's troubling actions (unmarked modifications) |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
we are troubled by much of the actions undertaken by Engineer B subsequent to his review of Engineer... [more] |
| Engineer B's major design changes to the public improvement plans |
before
Entity1 is before Entity2 |
Engineer B placing the note on the title sheet regarding 'revisions of the plans' |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer B also made major design changes to the storm drains... Engineer B placed a note on the tit... [more] |
| absence of communication between the two engineers |
during
Entity1 occurs entirely within the duration of Entity2 |
period after Engineer B was retained |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
At no time after Engineer B was retained were there any communications between the two engineers. |
| Engineer A's signing and sealing of all sheets |
before
Entity1 is before Entity2 |
Engineer B leaving Engineer A's seal and signature intact |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
all sheets in each set were signed and sealed by Engineer A... left Engineer A's seal and signature ... [more] |
| Engineer B beginning fundamental changes to the design |
before
Entity1 is before Entity2 |
potential overall impact on the entire project design |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
once he began to make fundamental changes to certain aspects of the design, his modifications might ... [more] |
| events of the case |
before
Entity1 is before Entity2 |
Board's retrospective evaluation in the Discussion |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
The Discussion section retrospectively evaluates these events, drawing on the earlier precedent of C... [more] |
About Allen Relations & OWL-Time
Allen's Interval Algebra provides 13 basic temporal relations between intervals. These relations are mapped to OWL-Time standard properties for interoperability with Semantic Web temporal reasoning systems and SPARQL queries.
Each relation includes both a ProEthica custom property and a
time:* OWL-Time property for maximum compatibility.