PASS 3: Temporal Dynamics
Case 83: Sustainable Development—Threatened Species
Timeline Overview
OWL-Time Temporal Structure 7 relations time: = w3.org/2006/time
Extracted Actions (7)
Volitional professional decisions with intentions and ethical contextDescription: Engineer A, a principal in an environmental engineering firm, undertakes an analysis for a developer client of a property adjacent to a protected wetlands area for potential residential condominium development.
Temporal Marker: At the outset of the engagement, before the biologist's report interval
Fluent Transitions:
- Client Engagement Active
Mental State: deliberate
Intended Outcome: Provide the developer client with a professional analysis of the property's development potential
Guided By Principles:
- Faithfulness to Client
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Faithfulness to ClientrequiresCapability: Environmental engineering analysis; Wetlands assessmentinitiates: Client Engagement Active
descriptioncontent: Engineer A, a principal in an environmental engineering firm, undertakes an analysis for a developer client of a property adjacent to a protected wetlands area for potential residential condominium development.hasAgentcontent: Engineer AtemporalMarkercontent: At the outset of the engagement, before the biologist's reporteventRoleContextcontent: principal, environmental engineering firmhasMentalStatecontent: deliberateintendedOutcomecontent: Provide the developer client with a professional analysis of the property's development potentialtextReferencescontent: Engineer A is a principal in an environmental engineering firm and is requested by a developer client to prepare an analysis of a piece of property adjacent to a wetlands area for potential development as a residential condominium.temporalExtentcontent: intervaltemporalSequencecontent: 5withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Action_Environmental_Analysis_Undertaking",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T19:54:33.112404+00:00",
"proeth:description": "Engineer A, a principal in an environmental engineering firm, undertakes an analysis for a developer client of a property adjacent to a protected wetlands area for potential residential condominium development.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "principal, environmental engineering firm",
"proeth:guidedByPrinciple": [
"Faithfulness to Client"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Client Engagement Active"
],
"proeth:intendedOutcome": "Provide the developer client with a professional analysis of the property\u0027s development potential",
"proeth:requiresCapability": [
"Environmental engineering analysis",
"Wetlands assessment"
],
"proeth:temporalExtent": "interval",
"proeth:temporalMarker": "At the outset of the engagement, before the biologist\u0027s report",
"proeth:temporalSequence": 5,
"proeth:textReferences": [
"Engineer A is a principal in an environmental engineering firm and is requested by a developer client to prepare an analysis of a piece of property adjacent to a wetlands area for potential development as a residential condominium."
],
"proeth:withinCompetence": true,
"rdfs:label": "Environmental Analysis Undertaking"
}
Description: The firm's biologist reports to Engineer A his professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species designated as threatened by federal and state regulators.
Temporal Marker: During the firm's analysis instant
Fluent Transitions:
- Threatened Species Concern Known to Engineer A
Mental State: deliberate
Intended Outcome: Inform Engineer A of the environmental threat identified during the analysis
Obligation Engagement:
- Protect the Environment for Future Generations
Guided By Principles:
- Sustainable Development
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Sustainable DevelopmentrequiresCapability: Biological species assessmentinitiates: Threatened Species Concern Known to Engineer AraisesObligation: Protect the Environment for Future Generations
descriptioncontent: The firm's biologist reports to Engineer A his professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species designated as threatened by federal and state regulators.hasAgentcontent: Firm biologisttemporalMarkercontent: During the firm's analysiseventRoleContextcontent: staff biologist, Engineer A's firmhasMentalStatecontent: deliberateintendedOutcomecontent: Inform Engineer A of the environmental threat identified during the analysistextReferencescontent: one of the engineering firm’s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands areatemporalExtentcontent: instanttemporalSequencecontent: 7withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Action_Species_Threat_Reporting",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T19:54:33.112555+00:00",
"proeth:description": "The firm\u0027s biologist reports to Engineer A his professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species designated as threatened by federal and state regulators.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "staff biologist, Engineer A\u0027s firm",
"proeth:fulfillsObligation": [],
"proeth:guidedByPrinciple": [
"Sustainable Development"
],
"proeth:hasAgent": "Firm biologist",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Threatened Species Concern Known to Engineer A"
],
"proeth:intendedOutcome": "Inform Engineer A of the environmental threat identified during the analysis",
"proeth:raisesObligation": [
"Protect the Environment for Future Generations"
],
"proeth:requiresCapability": [
"Biological species assessment"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During the firm\u0027s analysis",
"proeth:temporalSequence": 7,
"proeth:textReferences": [
"one of the engineering firm\u2019s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area"
],
"proeth:violatesObligation": [],
"proeth:withinCompetence": true,
"rdfs:label": "Species Threat Reporting"
}
Description: Engineer A verbally mentions the threatened species concern to the developer client during subsequent discussions.
Temporal Marker: In subsequent discussions with the developer client, after the biologist's report instant
Fluent Transitions:
- Client Aware of Species Threat
Mental State: deliberate
Intended Outcome: Make the client aware of the potential threat to the bird species
Guided By Principles:
- Faithfulness to Client
- Sustainable Development
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Faithfulness to Client; Sustainable DevelopmentrequiresCapability: Professional communication; Environmental engineering judgmentinitiates: Client Aware of Species Threat
descriptioncontent: Engineer A verbally mentions the threatened species concern to the developer client during subsequent discussions.hasAgentcontent: Engineer AtemporalMarkercontent: In subsequent discussions with the developer client, after the biologist's reporteventRoleContextcontent: principal, environmental engineering firmhasMentalStatecontent: deliberateintendedOutcomecontent: Make the client aware of the potential threat to the bird speciestextReferencescontent: In subsequent discussions with the developer client, Engineer A verbally mentions the concerntemporalExtentcontent: instanttemporalSequencecontent: 8withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Action_Verbal_Concern_Disclosure",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T19:54:33.112598+00:00",
"proeth:description": "Engineer A verbally mentions the threatened species concern to the developer client during subsequent discussions.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "principal, environmental engineering firm",
"proeth:guidedByPrinciple": [
"Faithfulness to Client",
"Sustainable Development"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate",
"proeth:initiates": [
"Client Aware of Species Threat"
],
"proeth:intendedOutcome": "Make the client aware of the potential threat to the bird species",
"proeth:requiresCapability": [
"Professional communication",
"Environmental engineering judgment"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "In subsequent discussions with the developer client, after the biologist\u0027s report",
"proeth:temporalSequence": 8,
"proeth:textReferences": [
"In subsequent discussions with the developer client, Engineer A verbally mentions the concern"
],
"proeth:withinCompetence": true,
"rdfs:label": "Verbal Concern Disclosure"
}
Description: Engineer A omits the threatened species information from the written report that will be submitted to the public authority considering the developer's proposal. The Board treats this non-performance as Engineer A's conduct and the central ethical decision.
Temporal Marker: At preparation of the written report for the public authority, after the verbal disclosure to the client instant
Fluent Transitions:
- Public Authority Uninformed of Species Threat
- Incomplete Written Report
Mental State: deliberate omission
Intended Outcome: Limit the written report submitted to the public authority to information favorable to the client's proposal
Foreseen Unintended Effects:
- Public authority deprived of information relevant to its approval decision
- Potential harm to the threatened bird species and the protected wetlands
Obligation Engagement:
- Include All Relevant and Pertinent Information in Reports
- Protect the Environment for Future Generations
Guided By Principles:
- Faithfulness to Client
Required Capabilities:
Field classification (triples vs literals)
violatesObligation: Include All Relevant and Pertinent Information in Reports; Protect the Environment for Future GenerationsguidedByPrinciple: Faithfulness to ClientrequiresCapability: Professional report preparation; Environmental engineering judgmentinitiates: Public Authority Uninformed of Species Threat; Incomplete Written Report
descriptioncontent: Engineer A omits the threatened species information from the written report that will be submitted to the public authority considering the developer's proposal. The Board treats this non-performance as Engineer A's conduct and the central ethical decision.hasAgentcontent: Engineer AtemporalMarkercontent: At preparation of the written report for the public authority, after the verbal disclosure to the clienteventRoleContextcontent: principal, environmental engineering firmhasMentalStatecontent: deliberate omissionintendedOutcomecontent: Limit the written report submitted to the public authority to information favorable to the client's proposalforeseenUnintendedEffectscontent: Public authority deprived of information relevant to its approval decision; Potential harm to the threatened bird species and the protected wetlandstextReferencescontent: Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer’s proposaltemporalExtentcontent: instanttemporalSequencecontent: 9withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Action_Written_Report_Omission",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T19:54:33.112628+00:00",
"proeth:description": "Engineer A omits the threatened species information from the written report that will be submitted to the public authority considering the developer\u0027s proposal. The Board treats this non-performance as Engineer A\u0027s conduct and the central ethical decision.",
"proeth:discoveredInSection": "facts",
"proeth:eventRoleContext": "principal, environmental engineering firm",
"proeth:foreseenUnintendedEffects": [
"Public authority deprived of information relevant to its approval decision",
"Potential harm to the threatened bird species and the protected wetlands"
],
"proeth:fulfillsObligation": [],
"proeth:guidedByPrinciple": [
"Faithfulness to Client"
],
"proeth:hasAgent": "Engineer A",
"proeth:hasMentalState": "deliberate omission",
"proeth:initiates": [
"Public Authority Uninformed of Species Threat",
"Incomplete Written Report"
],
"proeth:intendedOutcome": "Limit the written report submitted to the public authority to information favorable to the client\u0027s proposal",
"proeth:raisesObligation": [],
"proeth:requiresCapability": [
"Professional report preparation",
"Environmental engineering judgment"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "At preparation of the written report for the public authority, after the verbal disclosure to the client",
"proeth:temporalSequence": 9,
"proeth:textReferences": [
"Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer\u2019s proposal"
],
"proeth:violatesObligation": [
"Include All Relevant and Pertinent Information in Reports",
"Protect the Environment for Future Generations"
],
"proeth:withinCompetence": true,
"rdfs:label": "Written Report Omission"
}
Description: The NSPE Board of Directors approves adding Section III.2.d. on sustainable development to the NSPE Code of Ethics, together with a clarifying footnote defining the term.
Temporal Marker: January 2006 instant
Fluent Transitions:
- Sustainable Development Provision in Force
Mental State: deliberate institutional decision
Intended Outcome: Place additional responsibilities on engineers to protect the environment for future generations
Guided By Principles:
- Sustainable Development
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Sustainable DevelopmentrequiresCapability: Professional code governanceinitiates: Sustainable Development Provision in Force
descriptioncontent: The NSPE Board of Directors approves adding Section III.2.d. on sustainable development to the NSPE Code of Ethics, together with a clarifying footnote defining the term.hasAgentcontent: NSPE Board of DirectorstemporalMarkercontent: January 2006hasMentalStatecontent: deliberate institutional decisionintendedOutcomecontent: Place additional responsibilities on engineers to protect the environment for future generationstextReferencescontent: In January 2006, the NSPE Board of Directors approved a change to the NSPE Code of Ethics to add Section III.2.d. to the NSPE Code.temporalExtentcontent: instanttemporalSequencecontent: 10withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Action_Code_Section_Addition",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T19:54:33.112704+00:00",
"proeth:description": "The NSPE Board of Directors approves adding Section III.2.d. on sustainable development to the NSPE Code of Ethics, together with a clarifying footnote defining the term.",
"proeth:discoveredInSection": "discussion",
"proeth:guidedByPrinciple": [
"Sustainable Development"
],
"proeth:hasAgent": "NSPE Board of Directors",
"proeth:hasMentalState": "deliberate institutional decision",
"proeth:initiates": [
"Sustainable Development Provision in Force"
],
"proeth:intendedOutcome": "Place additional responsibilities on engineers to protect the environment for future generations",
"proeth:requiresCapability": [
"Professional code governance"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "January 2006",
"proeth:temporalSequence": 10,
"proeth:textReferences": [
"In January 2006, the NSPE Board of Directors approved a change to the NSPE Code of Ethics to add Section III.2.d. to the NSPE Code."
],
"proeth:withinCompetence": true,
"rdfs:label": "Code Section Addition"
}
Description: The NSPE House of Delegates votes to modify Section III.2.d. so that engineers are encouraged, rather than shall strive, to adhere to the principles of sustainable development.
Temporal Marker: July 2007 instant
Fluent Transitions:
- Modified Sustainable Development Provision in Force
Mental State: deliberate institutional decision
Intended Outcome: Clarify and adjust the modality of the sustainable development provision
Guided By Principles:
- Sustainable Development
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Sustainable DevelopmentrequiresCapability: Professional code governanceinitiates: Modified Sustainable Development Provision in Force
descriptioncontent: The NSPE House of Delegates votes to modify Section III.2.d. so that engineers are encouraged, rather than shall strive, to adhere to the principles of sustainable development.hasAgentcontent: NSPE House of DelegatestemporalMarkercontent: July 2007hasMentalStatecontent: deliberate institutional decisionintendedOutcomecontent: Clarify and adjust the modality of the sustainable development provisiontextReferencescontent: in July 2007, the NSPE House of Delegates voted to modify the language in NSPE Code Section III.2.d. to state that “engineers are encouraged to adhere to the principles of sustainable development in order to protect the environment for future generations.temporalExtentcontent: instanttemporalSequencecontent: 11withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Action_Code_Language_Modification",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T19:54:33.112744+00:00",
"proeth:description": "The NSPE House of Delegates votes to modify Section III.2.d. so that engineers are encouraged, rather than shall strive, to adhere to the principles of sustainable development.",
"proeth:discoveredInSection": "discussion",
"proeth:guidedByPrinciple": [
"Sustainable Development"
],
"proeth:hasAgent": "NSPE House of Delegates",
"proeth:hasMentalState": "deliberate institutional decision",
"proeth:initiates": [
"Modified Sustainable Development Provision in Force"
],
"proeth:intendedOutcome": "Clarify and adjust the modality of the sustainable development provision",
"proeth:requiresCapability": [
"Professional code governance"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "July 2007",
"proeth:temporalSequence": 11,
"proeth:textReferences": [
"in July 2007, the NSPE House of Delegates voted to modify the language in NSPE Code Section III.2.d. to state that \u201cengineers are encouraged to adhere to the principles of sustainable development in order to protect the environment for future generations."
],
"proeth:withinCompetence": true,
"rdfs:label": "Code Language Modification"
}
Description: Applying new Code Section III.2.d. and Section II.3.a. as a matter of first impression, the Board concludes that Engineer A had an obligation to include the threatened species information in the written report and to advise the client of its inclusion.
Temporal Marker: After July 2007, upon review of the present case instant
Fluent Transitions:
- Duty to Disclose in Written Report Established
Mental State: deliberate adjudicative reasoning
Intended Outcome: Resolve the conflict between client confidentiality and environmental and reporting duties, and establish guidance under the new Code language
Guided By Principles:
- Sustainable Development
- Objectivity and Truthfulness in Reports
- Public Health and Safety Paramountcy
Required Capabilities:
Field classification (triples vs literals)
guidedByPrinciple: Sustainable Development; Objectivity and Truthfulness in Reports; Public Health and Safety ParamountcyrequiresCapability: Ethical review and adjudicationinitiates: Duty to Disclose in Written Report Established
descriptioncontent: Applying new Code Section III.2.d. and Section II.3.a. as a matter of first impression, the Board concludes that Engineer A had an obligation to include the threatened species information in the written report and to advise the client of its inclusion.hasAgentcontent: NSPE Board of Ethical ReviewtemporalMarkercontent: After July 2007, upon review of the present casehasMentalStatecontent: deliberate adjudicative reasoningintendedOutcomecontent: Resolve the conflict between client confidentiality and environmental and reporting duties, and establish guidance under the new Code languagetextReferencescontent: Engineer A, therefore, had an obligation to include it in the written report and advise the client of its inclusion.temporalExtentcontent: instanttemporalSequencecontent: 12withinCompetenceassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Action_Board_Ethical_Determination",
"@type": "proeth:Action",
"generatedAtTime": "2026-07-13T19:54:33.112773+00:00",
"proeth:description": "Applying new Code Section III.2.d. and Section II.3.a. as a matter of first impression, the Board concludes that Engineer A had an obligation to include the threatened species information in the written report and to advise the client of its inclusion.",
"proeth:discoveredInSection": "discussion",
"proeth:guidedByPrinciple": [
"Sustainable Development",
"Objectivity and Truthfulness in Reports",
"Public Health and Safety Paramountcy"
],
"proeth:hasAgent": "NSPE Board of Ethical Review",
"proeth:hasMentalState": "deliberate adjudicative reasoning",
"proeth:initiates": [
"Duty to Disclose in Written Report Established"
],
"proeth:intendedOutcome": "Resolve the conflict between client confidentiality and environmental and reporting duties, and establish guidance under the new Code language",
"proeth:requiresCapability": [
"Ethical review and adjudication"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "After July 2007, upon review of the present case",
"proeth:temporalSequence": 12,
"proeth:textReferences": [
"Engineer A, therefore, had an obligation to include it in the written report and advise the client of its inclusion."
],
"proeth:withinCompetence": true,
"rdfs:label": "Board Ethical Determination"
}
Extracted Events (5)
Occurrences that trigger ethical considerations and state changesDescription: In BER Case No. 97-13, while conducting the bridge inspection, Engineer A noticed an apparent preexisting defective condition in the wall close to where the fatal accident occurred, and surmised it may have contributed to the wall failure.
Temporal Marker: During the bridge inspection (BER Case No. 97-13) instant
Fluent Transitions:
- Suspected Preexisting Wall Defect
- Out-of-Scope Safety Information Held
Field classification (triples vs literals)
initiates: Suspected Preexisting Wall Defect; Out-of-Scope Safety Information Held
descriptioncontent: In BER Case No. 97-13, while conducting the bridge inspection, Engineer A noticed an apparent preexisting defective condition in the wall close to where the fatal accident occurred, and surmised it may have contributed to the wall failure.temporalMarkercontent: During the bridge inspection (BER Case No. 97-13)textReferencescontent: While conducting the bridge inspection, and although not part of the scope of services for which he was retained, Engineer A noticed an apparent preexisting defective condition in the wall close to where the accident involving Police Officer B occurred.; Engineer A surmised that the defective condition may have been a contributing factor in the wall failure and noted this in his engineering notes.eventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 1confidenceassessment: 0.9
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Event_Wall_Defect_Discovery",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T19:54:33.112953+00:00",
"proeth:confidence": "0.9",
"proeth:description": "In BER Case No. 97-13, while conducting the bridge inspection, Engineer A noticed an apparent preexisting defective condition in the wall close to where the fatal accident occurred, and surmised it may have contributed to the wall failure.",
"proeth:discoveredInSection": "discussion",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Suspected Preexisting Wall Defect",
"Out-of-Scope Safety Information Held"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During the bridge inspection (BER Case No. 97-13)",
"proeth:temporalSequence": 1,
"proeth:textReferences": [
"While conducting the bridge inspection, and although not part of the scope of services for which he was retained, Engineer A noticed an apparent preexisting defective condition in the wall close to where the accident involving Police Officer B occurred.",
"Engineer A surmised that the defective condition may have been a contributing factor in the wall failure and noted this in his engineering notes."
],
"rdfs:label": "Wall Defect Discovery"
}
Description: In BER Case No. 97-13, Police Officer B lost control of his patrol car while traveling across the bridge and crashed into the bridge wall.
Temporal Marker: Three months prior to the scheduled bridge overhaul (BER Case No. 97-13) instant
Fluent Transitions:
- Vehicle Impact on Bridge Wall
Field classification (triples vs literals)
initiates: Vehicle Impact on Bridge Wall
descriptioncontent: In BER Case No. 97-13, Police Officer B lost control of his patrol car while traveling across the bridge and crashed into the bridge wall.temporalMarkercontent: Three months prior to the scheduled bridge overhaul (BER Case No. 97-13)textReferencescontent: Three months prior to the beginning of the scheduled overhaul of the bridge, while traveling across the bridge, Police Officer B lost control of his patrol car. The vehicle crashed into the bridge wall.eventTypecontent: exogenoustemporalExtentcontent: instanttemporalSequencecontent: 2confidenceassessment: 0.95
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Event_Vehicle_Control_Loss",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T19:54:33.112846+00:00",
"proeth:confidence": "0.95",
"proeth:description": "In BER Case No. 97-13, Police Officer B lost control of his patrol car while traveling across the bridge and crashed into the bridge wall.",
"proeth:discoveredInSection": "discussion",
"proeth:eventType": "exogenous",
"proeth:initiates": [
"Vehicle Impact on Bridge Wall"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Three months prior to the scheduled bridge overhaul (BER Case No. 97-13)",
"proeth:temporalSequence": 2,
"proeth:textReferences": [
"Three months prior to the beginning of the scheduled overhaul of the bridge, while traveling across the bridge, Police Officer B lost control of his patrol car. The vehicle crashed into the bridge wall."
],
"rdfs:label": "Vehicle Control Loss"
}
Description: In BER Case No. 97-13, the bridge wall failed to restrain the crashing patrol car, which fell to the river below, killing Police Officer B. An apparent preexisting defective condition may have been a contributing factor.
Temporal Marker: Three months prior to the scheduled bridge overhaul (BER Case No. 97-13) instant
Fluent Transitions:
- Police Officer Fatality
- Bridge Safety Concern
Field classification (triples vs literals)
initiates: Police Officer Fatality; Bridge Safety Concern
descriptioncontent: In BER Case No. 97-13, the bridge wall failed to restrain the crashing patrol car, which fell to the river below, killing Police Officer B. An apparent preexisting defective condition may have been a contributing factor.temporalMarkercontent: Three months prior to the scheduled bridge overhaul (BER Case No. 97-13)textReferencescontent: The wall failed to restrain the vehicle, which fell to the river below, killing Police Officer B.eventTypecontent: exogenoustemporalExtentcontent: instanttemporalSequencecontent: 3confidenceassessment: 0.93
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Event_Bridge_Wall_Failure",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T19:54:33.112929+00:00",
"proeth:confidence": "0.93",
"proeth:description": "In BER Case No. 97-13, the bridge wall failed to restrain the crashing patrol car, which fell to the river below, killing Police Officer B. An apparent preexisting defective condition may have been a contributing factor.",
"proeth:discoveredInSection": "discussion",
"proeth:eventType": "exogenous",
"proeth:initiates": [
"Police Officer Fatality",
"Bridge Safety Concern"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "Three months prior to the scheduled bridge overhaul (BER Case No. 97-13)",
"proeth:temporalSequence": 3,
"proeth:textReferences": [
"The wall failed to restrain the vehicle, which fell to the river below, killing Police Officer B."
],
"rdfs:label": "Bridge Wall Failure"
}
Description: In BER Case No. 04-8, a few months after completing wetland delineation services, Engineer A drove by the client's property and noticed the client had installed substantial fill material across a portion of the wetlands without permits, variances, or permissions, a substantial violation of federal and state law.
Temporal Marker: A few months after Engineer A completed the wetland delineation services (BER Case No. 04-8) instant
Fluent Transitions:
- Known Environmental Law Violation
Field classification (triples vs literals)
initiates: Known Environmental Law Violation
descriptioncontent: In BER Case No. 04-8, a few months after completing wetland delineation services, Engineer A drove by the client's property and noticed the client had installed substantial fill material across a portion of the wetlands without permits, variances, or permissions, a substantial violation of federal and state law.temporalMarkercontent: A few months after Engineer A completed the wetland delineation services (BER Case No. 04-8)textReferencescontent: A few months after Engineer A completed the services, he drove by his client’s property and noticed that the client had installed a substantial amount of fill material on more than half an acre across a portion of the wetlands without any permits, variances, or permissions.; The installation of the fill material was a substantial violation of the federal and state laws and regulations.eventTypecontent: exogenoustemporalExtentcontent: instanttemporalSequencecontent: 4confidenceassessment: 0.92
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Event_Illegal_Fill_Discovery",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T19:54:33.112975+00:00",
"proeth:confidence": "0.92",
"proeth:description": "In BER Case No. 04-8, a few months after completing wetland delineation services, Engineer A drove by the client\u0027s property and noticed the client had installed substantial fill material across a portion of the wetlands without permits, variances, or permissions, a substantial violation of federal and state law.",
"proeth:discoveredInSection": "discussion",
"proeth:eventType": "exogenous",
"proeth:initiates": [
"Known Environmental Law Violation"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "A few months after Engineer A completed the wetland delineation services (BER Case No. 04-8)",
"proeth:temporalSequence": 4,
"proeth:textReferences": [
"A few months after Engineer A completed the services, he drove by his client\u2019s property and noticed that the client had installed a substantial amount of fill material on more than half an acre across a portion of the wetlands without any permits, variances, or permissions.",
"The installation of the fill material was a substantial violation of the federal and state laws and regulations."
],
"rdfs:label": "Illegal Fill Discovery"
}
Description: During the firm's analysis of the property in the present case, the firm's biologist forms the professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species considered threatened by federal and state environmental regulators.
Temporal Marker: During the firm's analysis of the property (present case) instant
Fluent Transitions:
- Threatened Species Risk
- Relevant Environmental Information Held
Caused By Action: Action_Environmental_Analysis_Undertaking
Field classification (triples vs literals)
causedByAction: http://proethica.org/ontology/case/83#Action_Environmental_Analysis_Undertakinginitiates: Threatened Species Risk; Relevant Environmental Information Held
descriptioncontent: During the firm's analysis of the property in the present case, the firm's biologist forms the professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species considered threatened by federal and state environmental regulators.temporalMarkercontent: During the firm's analysis of the property (present case)textReferencescontent: During the firm’s analysis, one of the engineering firm’s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area.; The bird species in not an “endangered species,” but it is considered a “threatened species” by federal and state environmental regulators.eventTypecontent: outcometemporalExtentcontent: instanttemporalSequencecontent: 6confidenceassessment: 0.88
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#Event_Species_Threat_Identification",
"@type": "proeth:Event",
"generatedAtTime": "2026-07-13T19:54:33.112998+00:00",
"proeth:causedByAction": "http://proethica.org/ontology/case/83#Action_Environmental_Analysis_Undertaking",
"proeth:confidence": "0.88",
"proeth:description": "During the firm\u0027s analysis of the property in the present case, the firm\u0027s biologist forms the professional opinion that the condominium project could threaten a bird species inhabiting the adjacent protected wetlands, a species considered threatened by federal and state environmental regulators.",
"proeth:discoveredInSection": "facts",
"proeth:eventType": "outcome",
"proeth:initiates": [
"Threatened Species Risk",
"Relevant Environmental Information Held"
],
"proeth:temporalExtent": "instant",
"proeth:temporalMarker": "During the firm\u0027s analysis of the property (present case)",
"proeth:temporalSequence": 6,
"proeth:textReferences": [
"During the firm\u2019s analysis, one of the engineering firm\u2019s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area.",
"The bird species in not an \u201cendangered species,\u201d but it is considered a \u201cthreatened species\u201d by federal and state environmental regulators."
],
"rdfs:label": "Species Threat Identification"
}
Causal Chains (11)
NESS test analysis: Necessary Element of Sufficient SetCausal Language: one of the engineering firm’s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area
Necessary Factors (NESS):
- Biologist forming the professional opinion of a threat
- Biologist's role within the firm reporting to Engineer A
Sufficient Factors:
- Professional identification of the threat + internal firm reporting structure
Responsibility Attribution:
Agent: Firm's biologist
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Species Threat Identification
Biologist forms professional opinion during the firm's analysis -
Species Threat Reporting
Biologist reports the opinion to Engineer A
Field classification (triples vs literals)
cause: Species Threat Identificationeffect: Species Threat ReportingresponsibleAgent: Firm's biologist
causalLanguagecontent: one of the engineering firm’s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands areanecessaryFactorscontent: Biologist forming the professional opinion of a threat; Biologist's role within the firm reporting to Engineer AsufficientFactorscontent: Professional identification of the threat + internal firm reporting structurecounterfactualcontent: Had the biologist not identified the threat, there would have been nothing to report to Engineer AagentKnowledgecontent: Knew the species was considered a 'threatened species' by federal and state environmental regulatorscausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Species Threat Identification', 'proeth:description': "Biologist forms professional opinion during the firm's analysis"}; {'proeth:step': 2, 'proeth:element': 'Species Threat Reporting', 'proeth:description': 'Biologist reports the opinion to Engineer A'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_2",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113089+00:00",
"proeth:agentKnowledge": "Knew the species was considered a \u0027threatened species\u0027 by federal and state environmental regulators",
"proeth:causalLanguage": "one of the engineering firm\u2019s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area",
"proeth:causalSequence": [
{
"proeth:description": "Biologist forms professional opinion during the firm\u0027s analysis",
"proeth:element": "Species Threat Identification",
"proeth:step": 1
},
{
"proeth:description": "Biologist reports the opinion to Engineer A",
"proeth:element": "Species Threat Reporting",
"proeth:step": 2
}
],
"proeth:cause": "Species Threat Identification",
"proeth:counterfactual": "Had the biologist not identified the threat, there would have been nothing to report to Engineer A",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Species Threat Reporting",
"proeth:necessaryFactors": [
"Biologist forming the professional opinion of a threat",
"Biologist\u0027s role within the firm reporting to Engineer A"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Firm\u0027s biologist",
"proeth:sufficientFactors": [
"Professional identification of the threat + internal firm reporting structure"
],
"proeth:withinAgentControl": true
}
Causal Language: In subsequent discussions with the developer client, Engineer A verbally mentions the concern
Necessary Factors (NESS):
- Engineer A receiving the biologist's report
- Ongoing discussions between Engineer A and the developer client
Sufficient Factors:
- Knowledge of the threat + occasion of client discussions + Engineer A's decision to disclose verbally
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Species Threat Reporting
Biologist informs Engineer A of the threat to the bird species -
Client Discussions
Engineer A engages in subsequent discussions with the developer client -
Verbal Concern Disclosure
Engineer A verbally mentions the concern to the client
Field classification (triples vs literals)
cause: Species Threat Reportingeffect: Verbal Concern DisclosureresponsibleAgent: Engineer A
causalLanguagecontent: In subsequent discussions with the developer client, Engineer A verbally mentions the concernnecessaryFactorscontent: Engineer A receiving the biologist's report; Ongoing discussions between Engineer A and the developer clientsufficientFactorscontent: Knowledge of the threat + occasion of client discussions + Engineer A's decision to disclose verballycounterfactualcontent: Without the biologist's report, Engineer A would have had no concern to mention to the clientagentKnowledgecontent: Knew from a qualified biologist that the project could threaten a federally and state recognized 'threatened species'causalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Species Threat Reporting', 'proeth:description': 'Biologist informs Engineer A of the threat to the bird species'}; {'proeth:step': 2, 'proeth:element': 'Client Discussions', 'proeth:description': 'Engineer A engages in subsequent discussions with the developer client'}; {'proeth:step': 3, 'proeth:element': 'Verbal Concern Disclosure', 'proeth:description': 'Engineer A verbally mentions the concern to the client'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_3",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113112+00:00",
"proeth:agentKnowledge": "Knew from a qualified biologist that the project could threaten a federally and state recognized \u0027threatened species\u0027",
"proeth:causalLanguage": "In subsequent discussions with the developer client, Engineer A verbally mentions the concern",
"proeth:causalSequence": [
{
"proeth:description": "Biologist informs Engineer A of the threat to the bird species",
"proeth:element": "Species Threat Reporting",
"proeth:step": 1
},
{
"proeth:description": "Engineer A engages in subsequent discussions with the developer client",
"proeth:element": "Client Discussions",
"proeth:step": 2
},
{
"proeth:description": "Engineer A verbally mentions the concern to the client",
"proeth:element": "Verbal Concern Disclosure",
"proeth:step": 3
}
],
"proeth:cause": "Species Threat Reporting",
"proeth:counterfactual": "Without the biologist\u0027s report, Engineer A would have had no concern to mention to the client",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Verbal Concern Disclosure",
"proeth:necessaryFactors": [
"Engineer A receiving the biologist\u0027s report",
"Ongoing discussions between Engineer A and the developer client"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Knowledge of the threat + occasion of client discussions + Engineer A\u0027s decision to disclose verbally"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer’s proposal
Necessary Factors (NESS):
- Engineer A's possession of the species threat information
- Preparation of a written report destined for the public authority
- Engineer A's volitional choice to exclude the information
Sufficient Factors:
- Possession of material information + control over report content + decision to omit
Responsibility Attribution:
Agent: Engineer A
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Species Threat Reporting
Biologist reports the threat to Engineer A -
Verbal Concern Disclosure
Engineer A verbally mentions the concern only to the client -
Written Report Omission
Engineer A prepares the written report to the public authority without the species information
Field classification (triples vs literals)
cause: Species Threat Reportingeffect: Written Report OmissionresponsibleAgent: Engineer A
causalLanguagecontent: Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer’s proposalnecessaryFactorscontent: Engineer A's possession of the species threat information; Preparation of a written report destined for the public authority; Engineer A's volitional choice to exclude the informationsufficientFactorscontent: Possession of material information + control over report content + decision to omitcounterfactualcontent: Without the biologist's report there would have been no information to omit; with the information, inclusion was fully within Engineer A's control, so the omission was not inevitableagentKnowledgecontent: Knew the species was a 'threatened species' and that the report would be submitted to a public authority considering the developer's proposalinterveningFactorscontent: Client's business interest in the development proceeding; General confidentiality expectations of the engineer-client relationshipcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Species Threat Reporting', 'proeth:description': 'Biologist reports the threat to Engineer A'}; {'proeth:step': 2, 'proeth:element': 'Verbal Concern Disclosure', 'proeth:description': 'Engineer A verbally mentions the concern only to the client'}; {'proeth:step': 3, 'proeth:element': 'Written Report Omission', 'proeth:description': 'Engineer A prepares the written report to the public authority without the species information'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_4",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113134+00:00",
"proeth:agentKnowledge": "Knew the species was a \u0027threatened species\u0027 and that the report would be submitted to a public authority considering the developer\u0027s proposal",
"proeth:causalLanguage": "Engineer A does not include the information in a written report that will be submitted to a public authority that is considering the developer\u2019s proposal",
"proeth:causalSequence": [
{
"proeth:description": "Biologist reports the threat to Engineer A",
"proeth:element": "Species Threat Reporting",
"proeth:step": 1
},
{
"proeth:description": "Engineer A verbally mentions the concern only to the client",
"proeth:element": "Verbal Concern Disclosure",
"proeth:step": 2
},
{
"proeth:description": "Engineer A prepares the written report to the public authority without the species information",
"proeth:element": "Written Report Omission",
"proeth:step": 3
}
],
"proeth:cause": "Species Threat Reporting",
"proeth:counterfactual": "Without the biologist\u0027s report there would have been no information to omit; with the information, inclusion was fully within Engineer A\u0027s control, so the omission was not inevitable",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Written Report Omission",
"proeth:interveningFactors": [
"Client\u0027s business interest in the development proceeding",
"General confidentiality expectations of the engineer-client relationship"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s possession of the species threat information",
"Preparation of a written report destined for the public authority",
"Engineer A\u0027s volitional choice to exclude the information"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A",
"proeth:sufficientFactors": [
"Possession of material information + control over report content + decision to omit"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A, therefore, had an obligation to include it in the written report and advise the client of its inclusion.
Necessary Factors (NESS):
- Engineer A's omission of relevant information from a report to a public authority
- NSPE Code Section II.3.a. requiring truthfulness and inclusion of all relevant and pertinent information
- NSPE Code Section III.2.d. on sustainable development
Sufficient Factors:
- Omission of unambiguous, competently derived information + absence of any client confidentiality request + Code obligations
Responsibility Attribution:
Agent: Engineer A (conduct reviewed); NSPE Board of Ethical Review (determination made)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Written Report Omission
Engineer A omits the threatened species information from the public-authority report -
Precedent Comparison
Board distinguishes the facts from BER 89-7 and 97-13 (no confidentiality request, no speculation, established competence) -
Code Application
Board applies Sections II.3.a. and III.2.d. as a matter of first impression -
Board Ethical Determination
Board concludes Engineer A had an obligation to include the information and advise the client
Field classification (triples vs literals)
cause: Written Report Omissioneffect: Board Ethical DeterminationresponsibleAgent: Engineer A (conduct reviewed); NSPE Board of Ethical Review (determination made)
causalLanguagecontent: Engineer A, therefore, had an obligation to include it in the written report and advise the client of its inclusion.necessaryFactorscontent: Engineer A's omission of relevant information from a report to a public authority; NSPE Code Section II.3.a. requiring truthfulness and inclusion of all relevant and pertinent information; NSPE Code Section III.2.d. on sustainable developmentsufficientFactorscontent: Omission of unambiguous, competently derived information + absence of any client confidentiality request + Code obligationscounterfactualcontent: Had Engineer A included the information in the written report, the Board would have had no omission to adjudicate and no finding of breached obligationagentKnowledgecontent: Board knew the information was neither confidential nor speculative: 'the client never directly requested that Engineer A maintain it as confidential' and 'the facts are relatively unambiguous and obvious'interveningFactorscontent: Adoption and modification of Code Section III.2.d. prior to review; Precedent in BER Case Nos. 89-7, 97-13, and 04-8causalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Written Report Omission', 'proeth:description': 'Engineer A omits the threatened species information from the public-authority report'}; {'proeth:step': 2, 'proeth:element': 'Precedent Comparison', 'proeth:description': 'Board distinguishes the facts from BER 89-7 and 97-13 (no confidentiality request, no speculation, established competence)'}; {'proeth:step': 3, 'proeth:element': 'Code Application', 'proeth:description': 'Board applies Sections II.3.a. and III.2.d. as a matter of first impression'}; {'proeth:step': 4, 'proeth:element': 'Board Ethical Determination', 'proeth:description': 'Board concludes Engineer A had an obligation to include the information and advise the client'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_5",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113154+00:00",
"proeth:agentKnowledge": "Board knew the information was neither confidential nor speculative: \u0027the client never directly requested that Engineer A maintain it as confidential\u0027 and \u0027the facts are relatively unambiguous and obvious\u0027",
"proeth:causalLanguage": "Engineer A, therefore, had an obligation to include it in the written report and advise the client of its inclusion.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A omits the threatened species information from the public-authority report",
"proeth:element": "Written Report Omission",
"proeth:step": 1
},
{
"proeth:description": "Board distinguishes the facts from BER 89-7 and 97-13 (no confidentiality request, no speculation, established competence)",
"proeth:element": "Precedent Comparison",
"proeth:step": 2
},
{
"proeth:description": "Board applies Sections II.3.a. and III.2.d. as a matter of first impression",
"proeth:element": "Code Application",
"proeth:step": 3
},
{
"proeth:description": "Board concludes Engineer A had an obligation to include the information and advise the client",
"proeth:element": "Board Ethical Determination",
"proeth:step": 4
}
],
"proeth:cause": "Written Report Omission",
"proeth:counterfactual": "Had Engineer A included the information in the written report, the Board would have had no omission to adjudicate and no finding of breached obligation",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Board Ethical Determination",
"proeth:interveningFactors": [
"Adoption and modification of Code Section III.2.d. prior to review",
"Precedent in BER Case Nos. 89-7, 97-13, and 04-8"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s omission of relevant information from a report to a public authority",
"NSPE Code Section II.3.a. requiring truthfulness and inclusion of all relevant and pertinent information",
"NSPE Code Section III.2.d. on sustainable development"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A (conduct reviewed); NSPE Board of Ethical Review (determination made)",
"proeth:sufficientFactors": [
"Omission of unambiguous, competently derived information + absence of any client confidentiality request + Code obligations"
],
"proeth:withinAgentControl": true
}
Causal Language: Thereafter, in July 2007, the NSPE House of Delegates voted to modify the language in NSPE Code Section III.2.d. to state that “engineers are encouraged to adhere to the principles of sustainable development in order to protect the environment for future generations.
Necessary Factors (NESS):
- Existence of Section III.2.d. as adopted in January 2006
- House of Delegates' authority to modify Code language
Sufficient Factors:
- Existing section language + House of Delegates vote to modify
Responsibility Attribution:
Agent: NSPE Board of Directors (addition); NSPE House of Delegates (modification)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Code Section Addition
January 2006: Board of Directors approves adding Section III.2.d. ('shall strive to adhere') -
Code Language Modification
July 2007: House of Delegates modifies language to 'are encouraged to adhere' -
First Impression Review
Board of Ethical Review reviews the language as a matter of first impression in the present case
Field classification (triples vs literals)
cause: Code Section Additioneffect: Code Language ModificationresponsibleAgent: NSPE Board of Directors (addition); NSPE House of Delegates (modification)
causalLanguagecontent: Thereafter, in July 2007, the NSPE House of Delegates voted to modify the language in NSPE Code Section III.2.d. to state that “engineers are encouraged to adhere to the principles of sustainable development in order to protect the environment for future generations.necessaryFactorscontent: Existence of Section III.2.d. as adopted in January 2006; House of Delegates' authority to modify Code languagesufficientFactorscontent: Existing section language + House of Delegates vote to modifycounterfactualcontent: Without the January 2006 addition, there would have been no Section III.2.d. language to modify in July 2007agentKnowledgecontent: Both bodies understood the sustainable development language and its footnoted definitioncausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Code Section Addition', 'proeth:description': "January 2006: Board of Directors approves adding Section III.2.d. ('shall strive to adhere')"}; {'proeth:step': 2, 'proeth:element': 'Code Language Modification', 'proeth:description': "July 2007: House of Delegates modifies language to 'are encouraged to adhere'"}; {'proeth:step': 3, 'proeth:element': 'First Impression Review', 'proeth:description': 'Board of Ethical Review reviews the language as a matter of first impression in the present case'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_6",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113173+00:00",
"proeth:agentKnowledge": "Both bodies understood the sustainable development language and its footnoted definition",
"proeth:causalLanguage": "Thereafter, in July 2007, the NSPE House of Delegates voted to modify the language in NSPE Code Section III.2.d. to state that \u201cengineers are encouraged to adhere to the principles of sustainable development in order to protect the environment for future generations.",
"proeth:causalSequence": [
{
"proeth:description": "January 2006: Board of Directors approves adding Section III.2.d. (\u0027shall strive to adhere\u0027)",
"proeth:element": "Code Section Addition",
"proeth:step": 1
},
{
"proeth:description": "July 2007: House of Delegates modifies language to \u0027are encouraged to adhere\u0027",
"proeth:element": "Code Language Modification",
"proeth:step": 2
},
{
"proeth:description": "Board of Ethical Review reviews the language as a matter of first impression in the present case",
"proeth:element": "First Impression Review",
"proeth:step": 3
}
],
"proeth:cause": "Code Section Addition",
"proeth:counterfactual": "Without the January 2006 addition, there would have been no Section III.2.d. language to modify in July 2007",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Code Language Modification",
"proeth:necessaryFactors": [
"Existence of Section III.2.d. as adopted in January 2006",
"House of Delegates\u0027 authority to modify Code language"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "NSPE Board of Directors (addition); NSPE House of Delegates (modification)",
"proeth:sufficientFactors": [
"Existing section language + House of Delegates vote to modify"
],
"proeth:withinAgentControl": true
}
Causal Language: Police Officer B lost control of his patrol car. The vehicle crashed into the bridge wall. The wall failed to restrain the vehicle, which fell to the river below, killing Police Officer B.
Necessary Factors (NESS):
- Loss of vehicle control causing impact with the wall
- Apparent preexisting defective condition in the wall
Sufficient Factors:
- Vehicle impact + defective wall condition together were sufficient for the wall's failure to restrain the vehicle
Responsibility Attribution:
Agent: Police Officer B (loss of control); responsibility for the wall condition undetermined in the facts
Type: shared
Within Agent Control:
No
Causal Sequence:
-
Vehicle Control Loss
Police Officer B loses control of his patrol car on the bridge -
Wall Impact
The vehicle crashes into the bridge wall -
Bridge Wall Failure
The wall fails to restrain the vehicle, which falls to the river below, killing Police Officer B
Field classification (triples vs literals)
cause: Vehicle Control Losseffect: Bridge Wall FailureresponsibleAgent: Police Officer B (loss of control); responsibility for the wall condition undetermined in the facts
causalLanguagecontent: Police Officer B lost control of his patrol car. The vehicle crashed into the bridge wall. The wall failed to restrain the vehicle, which fell to the river below, killing Police Officer B.necessaryFactorscontent: Loss of vehicle control causing impact with the wall; Apparent preexisting defective condition in the wallsufficientFactorscontent: Vehicle impact + defective wall condition together were sufficient for the wall's failure to restrain the vehiclecounterfactualcontent: Without the loss of vehicle control there would have been no impact; per Engineer A's surmise, without the defective condition the wall may have restrained the vehicleagentKnowledgecontent: No party is stated to have known of the defective condition prior to the accidentinterveningFactorscontent: Apparent preexisting defective condition in the wall, which 'may have been a contributing factor in the wall failure'causalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Vehicle Control Loss', 'proeth:description': 'Police Officer B loses control of his patrol car on the bridge'}; {'proeth:step': 2, 'proeth:element': 'Wall Impact', 'proeth:description': 'The vehicle crashes into the bridge wall'}; {'proeth:step': 3, 'proeth:element': 'Bridge Wall Failure', 'proeth:description': 'The wall fails to restrain the vehicle, which falls to the river below, killing Police Officer B'}responsibilityTypeassessment: sharedwithinAgentControlassessment: False
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_8",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113210+00:00",
"proeth:agentKnowledge": "No party is stated to have known of the defective condition prior to the accident",
"proeth:causalLanguage": "Police Officer B lost control of his patrol car. The vehicle crashed into the bridge wall. The wall failed to restrain the vehicle, which fell to the river below, killing Police Officer B.",
"proeth:causalSequence": [
{
"proeth:description": "Police Officer B loses control of his patrol car on the bridge",
"proeth:element": "Vehicle Control Loss",
"proeth:step": 1
},
{
"proeth:description": "The vehicle crashes into the bridge wall",
"proeth:element": "Wall Impact",
"proeth:step": 2
},
{
"proeth:description": "The wall fails to restrain the vehicle, which falls to the river below, killing Police Officer B",
"proeth:element": "Bridge Wall Failure",
"proeth:step": 3
}
],
"proeth:cause": "Vehicle Control Loss",
"proeth:counterfactual": "Without the loss of vehicle control there would have been no impact; per Engineer A\u0027s surmise, without the defective condition the wall may have restrained the vehicle",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Bridge Wall Failure",
"proeth:interveningFactors": [
"Apparent preexisting defective condition in the wall, which \u0027may have been a contributing factor in the wall failure\u0027"
],
"proeth:necessaryFactors": [
"Loss of vehicle control causing impact with the wall",
"Apparent preexisting defective condition in the wall"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "Police Officer B (loss of control); responsibility for the wall condition undetermined in the facts",
"proeth:sufficientFactors": [
"Vehicle impact + defective wall condition together were sufficient for the wall\u0027s failure to restrain the vehicle"
],
"proeth:withinAgentControl": false
}
Causal Language: Engineer A surmised that the defective condition may have been a contributing factor in the wall failure and noted this in his engineering notes.
Necessary Factors (NESS):
- Engineer A conducting the bridge inspection
- Visual observation of the apparent preexisting defective condition
Sufficient Factors:
- Observation of the defect + Engineer A's professional practice of documenting observations
Responsibility Attribution:
Agent: Engineer A (bridge inspection subconsultant, BER 97-13)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Wall Defect Discovery
Engineer A notices the apparent preexisting defective condition while inspecting the bridge -
Defect Documentation
Engineer A notes the surmise in his engineering notes -
Verbal Defect Reporting
Engineer A verbally reports the information to his client, VWX
Field classification (triples vs literals)
cause: Wall Defect Discoveryeffect: Defect DocumentationresponsibleAgent: Engineer A (bridge inspection subconsultant, BER 97-13)
causalLanguagecontent: Engineer A surmised that the defective condition may have been a contributing factor in the wall failure and noted this in his engineering notes.necessaryFactorscontent: Engineer A conducting the bridge inspection; Visual observation of the apparent preexisting defective conditionsufficientFactorscontent: Observation of the defect + Engineer A's professional practice of documenting observationscounterfactualcontent: Had Engineer A not noticed the defective condition during inspection, no note would have been madeagentKnowledgecontent: Observation was based on visual inspection only; he lacked stated expertise in structural engineering and the defect was outside his scope of workinterveningFactorscontent: Scope of work limited solely to pavement damage identificationcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Wall Defect Discovery', 'proeth:description': 'Engineer A notices the apparent preexisting defective condition while inspecting the bridge'}; {'proeth:step': 2, 'proeth:element': 'Defect Documentation', 'proeth:description': 'Engineer A notes the surmise in his engineering notes'}; {'proeth:step': 3, 'proeth:element': 'Verbal Defect Reporting', 'proeth:description': 'Engineer A verbally reports the information to his client, VWX'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_9",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113227+00:00",
"proeth:agentKnowledge": "Observation was based on visual inspection only; he lacked stated expertise in structural engineering and the defect was outside his scope of work",
"proeth:causalLanguage": "Engineer A surmised that the defective condition may have been a contributing factor in the wall failure and noted this in his engineering notes.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A notices the apparent preexisting defective condition while inspecting the bridge",
"proeth:element": "Wall Defect Discovery",
"proeth:step": 1
},
{
"proeth:description": "Engineer A notes the surmise in his engineering notes",
"proeth:element": "Defect Documentation",
"proeth:step": 2
},
{
"proeth:description": "Engineer A verbally reports the information to his client, VWX",
"proeth:element": "Verbal Defect Reporting",
"proeth:step": 3
}
],
"proeth:cause": "Wall Defect Discovery",
"proeth:counterfactual": "Had Engineer A not noticed the defective condition during inspection, no note would have been made",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Defect Documentation",
"proeth:interveningFactors": [
"Scope of work limited solely to pavement damage identification"
],
"proeth:necessaryFactors": [
"Engineer A conducting the bridge inspection",
"Visual observation of the apparent preexisting defective condition"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A (bridge inspection subconsultant, BER 97-13)",
"proeth:sufficientFactors": [
"Observation of the defect + Engineer A\u0027s professional practice of documenting observations"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A verbally reported this information to his client, who then verbally reported the information to the public agency. The public agency contacted VWX Architects and Engineers, who then contacted Engineer A and asked Engineer A not to include this additional information in his final report since it was not part of his scope of work.
Necessary Factors (NESS):
- Engineer A's verbal report to VWX
- VWX's report to the public agency
- Public agency contacting VWX about the information
Sufficient Factors:
- Chain of verbal notifications + agency response + scope-of-work rationale motivated VWX's request
Responsibility Attribution:
Agent: VWX Architects and Engineers (made the request); public agency (indirect)
Type: shared
Within Agent Control:
Yes
Causal Sequence:
-
Verbal Defect Reporting
Engineer A verbally reports the defect to VWX -
Agency Notification
VWX verbally reports the information to the public agency -
Agency Contact
The public agency contacts VWX about the information -
Report Omission Request
VWX asks Engineer A not to include the information in his final report
Field classification (triples vs literals)
cause: Verbal Defect Reportingeffect: Report Omission RequestresponsibleAgent: VWX Architects and Engineers (made the request); public agency (indirect)
causalLanguagecontent: Engineer A verbally reported this information to his client, who then verbally reported the information to the public agency. The public agency contacted VWX Architects and Engineers, who then contacted Engineer A and asked Engineer A not to include this additional information in his final report since it was not part of his scope of work.necessaryFactorscontent: Engineer A's verbal report to VWX; VWX's report to the public agency; Public agency contacting VWX about the informationsufficientFactorscontent: Chain of verbal notifications + agency response + scope-of-work rationale motivated VWX's requestcounterfactualcontent: Had Engineer A never verbally reported the defect, VWX and the public agency would have had no information prompting the omission requestagentKnowledgecontent: VWX knew the observation was outside Engineer A's scope of work and beyond his stated structural expertiseinterveningFactorscontent: Public agency's contact with VWX; Scope-of-work limitations of the subconsultant contractcausalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Verbal Defect Reporting', 'proeth:description': 'Engineer A verbally reports the defect to VWX'}; {'proeth:step': 2, 'proeth:element': 'Agency Notification', 'proeth:description': 'VWX verbally reports the information to the public agency'}; {'proeth:step': 3, 'proeth:element': 'Agency Contact', 'proeth:description': 'The public agency contacts VWX about the information'}; {'proeth:step': 4, 'proeth:element': 'Report Omission Request', 'proeth:description': 'VWX asks Engineer A not to include the information in his final report'}responsibilityTypeassessment: sharedwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_10",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113245+00:00",
"proeth:agentKnowledge": "VWX knew the observation was outside Engineer A\u0027s scope of work and beyond his stated structural expertise",
"proeth:causalLanguage": "Engineer A verbally reported this information to his client, who then verbally reported the information to the public agency. The public agency contacted VWX Architects and Engineers, who then contacted Engineer A and asked Engineer A not to include this additional information in his final report since it was not part of his scope of work.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A verbally reports the defect to VWX",
"proeth:element": "Verbal Defect Reporting",
"proeth:step": 1
},
{
"proeth:description": "VWX verbally reports the information to the public agency",
"proeth:element": "Agency Notification",
"proeth:step": 2
},
{
"proeth:description": "The public agency contacts VWX about the information",
"proeth:element": "Agency Contact",
"proeth:step": 3
},
{
"proeth:description": "VWX asks Engineer A not to include the information in his final report",
"proeth:element": "Report Omission Request",
"proeth:step": 4
}
],
"proeth:cause": "Verbal Defect Reporting",
"proeth:counterfactual": "Had Engineer A never verbally reported the defect, VWX and the public agency would have had no information prompting the omission request",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Report Omission Request",
"proeth:interveningFactors": [
"Public agency\u0027s contact with VWX",
"Scope-of-work limitations of the subconsultant contract"
],
"proeth:necessaryFactors": [
"Engineer A\u0027s verbal report to VWX",
"VWX\u0027s report to the public agency",
"Public agency contacting VWX about the information"
],
"proeth:responsibilityType": "shared",
"proeth:responsibleAgent": "VWX Architects and Engineers (made the request); public agency (indirect)",
"proeth:sufficientFactors": [
"Chain of verbal notifications + agency response + scope-of-work rationale motivated VWX\u0027s request"
],
"proeth:withinAgentControl": true
}
Causal Language: Engineer A stated that he would retain the information for his engineering notes but not include it in the final report, as requested.
Necessary Factors (NESS):
- VWX's request that the information be excluded from the final report
- Engineer A's judgment that the observation was speculative and outside his scope and expertise
Sufficient Factors:
- Client request + speculative basis of the observation + retention of the information in engineering notes as a safeguard
Responsibility Attribution:
Agent: Engineer A (BER 97-13 subconsultant)
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Report Omission Request
VWX asks Engineer A to exclude the defect information from the final report -
Requested Omission Compliance
Engineer A agrees, retaining the information in his engineering notes but excluding it from the final report -
Follow-up Obligation
Board holds Engineer A must 'follow through to see that correct follow-up action was taken by the public agency'
Field classification (triples vs literals)
cause: Report Omission Requesteffect: Requested Omission ComplianceresponsibleAgent: Engineer A (BER 97-13 subconsultant)
causalLanguagecontent: Engineer A stated that he would retain the information for his engineering notes but not include it in the final report, as requested.necessaryFactorscontent: VWX's request that the information be excluded from the final report; Engineer A's judgment that the observation was speculative and outside his scope and expertisesufficientFactorscontent: Client request + speculative basis of the observation + retention of the information in engineering notes as a safeguardcounterfactualcontent: Without VWX's request, Engineer A would have had no occasion to agree 'as requested'; the Board found the compliance ethical because 'there was nothing under the facts to indicate anything more than Engineer A’s general surmise and speculation'agentKnowledgecontent: Knew his surmise rested on visual inspection alone and that VWX 'was in a far better position than Engineer A to understand the interrelationships between various elements of the projects'interveningFactorscontent: Board's condition that compliance was ethical only 'as long as corrective action was taken by the public agency within a relatively short period of time'causalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Report Omission Request', 'proeth:description': 'VWX asks Engineer A to exclude the defect information from the final report'}; {'proeth:step': 2, 'proeth:element': 'Requested Omission Compliance', 'proeth:description': 'Engineer A agrees, retaining the information in his engineering notes but excluding it from the final report'}; {'proeth:step': 3, 'proeth:element': 'Follow-up Obligation', 'proeth:description': "Board holds Engineer A must 'follow through to see that correct follow-up action was taken by the public agency'"}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_11",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113264+00:00",
"proeth:agentKnowledge": "Knew his surmise rested on visual inspection alone and that VWX \u0027was in a far better position than Engineer A to understand the interrelationships between various elements of the projects\u0027",
"proeth:causalLanguage": "Engineer A stated that he would retain the information for his engineering notes but not include it in the final report, as requested.",
"proeth:causalSequence": [
{
"proeth:description": "VWX asks Engineer A to exclude the defect information from the final report",
"proeth:element": "Report Omission Request",
"proeth:step": 1
},
{
"proeth:description": "Engineer A agrees, retaining the information in his engineering notes but excluding it from the final report",
"proeth:element": "Requested Omission Compliance",
"proeth:step": 2
},
{
"proeth:description": "Board holds Engineer A must \u0027follow through to see that correct follow-up action was taken by the public agency\u0027",
"proeth:element": "Follow-up Obligation",
"proeth:step": 3
}
],
"proeth:cause": "Report Omission Request",
"proeth:counterfactual": "Without VWX\u0027s request, Engineer A would have had no occasion to agree \u0027as requested\u0027; the Board found the compliance ethical because \u0027there was nothing under the facts to indicate anything more than Engineer A\u2019s general surmise and speculation\u0027",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Requested Omission Compliance",
"proeth:interveningFactors": [
"Board\u0027s condition that compliance was ethical only \u0027as long as corrective action was taken by the public agency within a relatively short period of time\u0027"
],
"proeth:necessaryFactors": [
"VWX\u0027s request that the information be excluded from the final report",
"Engineer A\u0027s judgment that the observation was speculative and outside his scope and expertise"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "Engineer A (BER 97-13 subconsultant)",
"proeth:sufficientFactors": [
"Client request + speculative basis of the observation + retention of the information in engineering notes as a safeguard"
],
"proeth:withinAgentControl": true
}
Causal Language: During the firm’s analysis, one of the engineering firm’s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area.
Necessary Factors (NESS):
- Engineer A accepting the developer's request to analyze the property
- The firm's biologist participating in the analysis
- The property's adjacency to the protected wetlands area inhabited by the threatened species
Sufficient Factors:
- Combination of the firm's analysis being underway + qualified biologist examining the site + presence of the threatened bird species in the adjacent wetlands
Responsibility Attribution:
Agent: Engineer A (as principal directing the firm's analysis)
Type: indirect
Within Agent Control:
Yes
Causal Sequence:
-
Environmental Analysis Undertaking
Engineer A undertakes analysis of property adjacent to wetlands for developer client -
Biologist Site Examination
The firm's biologist examines the property as part of the analysis -
Species Threat Identification
Biologist forms professional opinion that the condominium project could threaten the bird species
Field classification (triples vs literals)
cause: Environmental Analysis Undertakingeffect: Species Threat IdentificationresponsibleAgent: Engineer A (as principal directing the firm's analysis)
causalLanguagecontent: During the firm’s analysis, one of the engineering firm’s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area.necessaryFactorscontent: Engineer A accepting the developer's request to analyze the property; The firm's biologist participating in the analysis; The property's adjacency to the protected wetlands area inhabited by the threatened speciessufficientFactorscontent: Combination of the firm's analysis being underway + qualified biologist examining the site + presence of the threatened bird species in the adjacent wetlandscounterfactualcontent: Without the firm's analysis being undertaken, the biologist would not have examined the site and the threat to the bird species would not have been professionally identifiedagentKnowledgecontent: Knew the property was adjacent to a wetlands area when accepting the engagementinterveningFactorscontent: Pre-existing presence of the threatened bird species; Federal and state regulatory classification of the species as 'threatened'causalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Environmental Analysis Undertaking', 'proeth:description': 'Engineer A undertakes analysis of property adjacent to wetlands for developer client'}; {'proeth:step': 2, 'proeth:element': 'Biologist Site Examination', 'proeth:description': "The firm's biologist examines the property as part of the analysis"}; {'proeth:step': 3, 'proeth:element': 'Species Threat Identification', 'proeth:description': 'Biologist forms professional opinion that the condominium project could threaten the bird species'}responsibilityTypeassessment: indirectwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_1",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113059+00:00",
"proeth:agentKnowledge": "Knew the property was adjacent to a wetlands area when accepting the engagement",
"proeth:causalLanguage": "During the firm\u2019s analysis, one of the engineering firm\u2019s biologists reports to Engineer A that in his opinion, the condominium project could threaten a bird species that inhabits the adjacent protected wetlands area.",
"proeth:causalSequence": [
{
"proeth:description": "Engineer A undertakes analysis of property adjacent to wetlands for developer client",
"proeth:element": "Environmental Analysis Undertaking",
"proeth:step": 1
},
{
"proeth:description": "The firm\u0027s biologist examines the property as part of the analysis",
"proeth:element": "Biologist Site Examination",
"proeth:step": 2
},
{
"proeth:description": "Biologist forms professional opinion that the condominium project could threaten the bird species",
"proeth:element": "Species Threat Identification",
"proeth:step": 3
}
],
"proeth:cause": "Environmental Analysis Undertaking",
"proeth:counterfactual": "Without the firm\u0027s analysis being undertaken, the biologist would not have examined the site and the threat to the bird species would not have been professionally identified",
"proeth:discoveredInSection": "facts",
"proeth:effect": "Species Threat Identification",
"proeth:interveningFactors": [
"Pre-existing presence of the threatened bird species",
"Federal and state regulatory classification of the species as \u0027threatened\u0027"
],
"proeth:necessaryFactors": [
"Engineer A accepting the developer\u0027s request to analyze the property",
"The firm\u0027s biologist participating in the analysis",
"The property\u0027s adjacency to the protected wetlands area inhabited by the threatened species"
],
"proeth:responsibilityType": "indirect",
"proeth:responsibleAgent": "Engineer A (as principal directing the firm\u0027s analysis)",
"proeth:sufficientFactors": [
"Combination of the firm\u0027s analysis being underway + qualified biologist examining the site + presence of the threatened bird species in the adjacent wetlands"
],
"proeth:withinAgentControl": true
}
Causal Language: With this added language a further clarification, the NSPE Board of Ethical Review will review this language as a matter of first impression and in the context of other language in the NSPE Code and earlier NSPE Board of Ethical Review Opinions.
Necessary Factors (NESS):
- Modified Section III.2.d. language being in effect
- A live case (Engineer A's omission) requiring application of the new language
Sufficient Factors:
- New Code language + present case facts + Board's mandate to issue opinions
Responsibility Attribution:
Agent: NSPE Board of Ethical Review
Type: direct
Within Agent Control:
Yes
Causal Sequence:
-
Code Language Modification
House of Delegates finalizes the 'encouraged to adhere' language -
Case Submission
The present facts come before the Board for review -
Board Ethical Determination
Board applies III.2.d. and II.3.a., concluding Engineer A had an obligation to include the information in the written report
Field classification (triples vs literals)
cause: Code Language Modificationeffect: Board Ethical DeterminationresponsibleAgent: NSPE Board of Ethical Review
causalLanguagecontent: With this added language a further clarification, the NSPE Board of Ethical Review will review this language as a matter of first impression and in the context of other language in the NSPE Code and earlier NSPE Board of Ethical Review Opinions.necessaryFactorscontent: Modified Section III.2.d. language being in effect; A live case (Engineer A's omission) requiring application of the new languagesufficientFactorscontent: New Code language + present case facts + Board's mandate to issue opinionscounterfactualcontent: The Board could still have found the omission unethical under pre-existing Section II.3.a., but the analysis would not have applied III.2.d. as a matter of first impressionagentKnowledgecontent: Knew the prior precedents were 'decided prior to the addition of the language contained in NSPE Code Section III.2.d.'interveningFactorscontent: Precedent cases BER 89-7, 97-13, and 04-8causalSequencecontent: {'proeth:step': 1, 'proeth:element': 'Code Language Modification', 'proeth:description': "House of Delegates finalizes the 'encouraged to adhere' language"}; {'proeth:step': 2, 'proeth:element': 'Case Submission', 'proeth:description': 'The present facts come before the Board for review'}; {'proeth:step': 3, 'proeth:element': 'Board Ethical Determination', 'proeth:description': 'Board applies III.2.d. and II.3.a., concluding Engineer A had an obligation to include the information in the written report'}responsibilityTypeassessment: directwithinAgentControlassessment: True
RDF JSON-LD
{
"@context": {
"proeth": "http://proethica.org/ontology/intermediate#",
"proeth-case": "http://proethica.org/ontology/case/83#",
"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/83#CausalChain_7",
"@type": "proeth:CausalChain",
"generatedAtTime": "2026-07-13T19:54:33.113192+00:00",
"proeth:agentKnowledge": "Knew the prior precedents were \u0027decided prior to the addition of the language contained in NSPE Code Section III.2.d.\u0027",
"proeth:causalLanguage": "With this added language a further clarification, the NSPE Board of Ethical Review will review this language as a matter of first impression and in the context of other language in the NSPE Code and earlier NSPE Board of Ethical Review Opinions.",
"proeth:causalSequence": [
{
"proeth:description": "House of Delegates finalizes the \u0027encouraged to adhere\u0027 language",
"proeth:element": "Code Language Modification",
"proeth:step": 1
},
{
"proeth:description": "The present facts come before the Board for review",
"proeth:element": "Case Submission",
"proeth:step": 2
},
{
"proeth:description": "Board applies III.2.d. and II.3.a., concluding Engineer A had an obligation to include the information in the written report",
"proeth:element": "Board Ethical Determination",
"proeth:step": 3
}
],
"proeth:cause": "Code Language Modification",
"proeth:counterfactual": "The Board could still have found the omission unethical under pre-existing Section II.3.a., but the analysis would not have applied III.2.d. as a matter of first impression",
"proeth:discoveredInSection": "discussion",
"proeth:effect": "Board Ethical Determination",
"proeth:interveningFactors": [
"Precedent cases BER 89-7, 97-13, and 04-8"
],
"proeth:necessaryFactors": [
"Modified Section III.2.d. language being in effect",
"A live case (Engineer A\u0027s omission) requiring application of the new language"
],
"proeth:responsibilityType": "direct",
"proeth:responsibleAgent": "NSPE Board of Ethical Review",
"proeth:sufficientFactors": [
"New Code language + present case facts + Board\u0027s mandate to issue opinions"
],
"proeth:withinAgentControl": true
}
Allen Temporal Relations (7)
Interval algebra relationships with OWL-Time standard properties| From Entity | Allen Relation | To Entity | OWL-Time Property | Evidence |
|---|---|---|---|---|
| NSPE Board of Directors approval of Section III.2.d. (January 2006) |
before
Entity1 is before Entity2 |
House of Delegates modification of Section III.2.d. language (July 2007) |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
In January 2006, the NSPE Board of Directors approved a change... Thereafter, in July 2007, the NSPE... [more] |
| Decisions in BER Cases 89-7, 97-13, and 04-8 |
before
Entity1 is before Entity2 |
Addition of NSPE Code Section III.2.d. (January 2006) |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
It should be noted that these cases were decided prior to the addition of the language contained in ... [more] |
| Biologist's report of threat to bird species |
during
Entity1 occurs entirely within the duration of Entity2 |
Firm's analysis of the property |
time:intervalDuring
http://www.w3.org/2006/time#intervalDuring |
During the firm’s analysis, one of the engineering firm’s biologists reports to Engineer A that... t... [more] |
| Biologist's report to Engineer A |
before
Entity1 is before Entity2 |
Engineer A's verbal mention of the concern to the developer client |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
In subsequent discussions with the developer client, Engineer A verbally mentions the concern |
| Engineer A's verbal mention to client |
before
Entity1 is before Entity2 |
Submission of written report to public authority |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
Engineer A verbally mentions the concern, but Engineer A does not include the information in a writt... [more] |
| Modification of Section III.2.d. language (July 2007) |
before
Entity1 is before Entity2 |
Board's first-impression review applying the new language to the present case |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
With this added language a further clarification, the NSPE Board of Ethical Review will review this ... [more] |
| Client's unawareness of the threatened species issue |
before
Entity1 is before Entity2 |
Engineer A bringing the issue to the client's attention |
time:intervalBefore
http://www.w3.org/2006/time#intervalBefore |
it appears that the client was not even aware of the situation prior to it being brought to the clie... [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.