@prefix : . @prefix schema: . @prefix rdf: . @prefix rdfs: . @prefix owl: . @prefix skos: . @prefix prov: . @prefix xsd: . a schema:CreativeWork ; schema:name "060. ILOVEYOU RDF collection document"@en ; schema:description "An RDF rendition of Steven Sinofsky's account of the Concept, Melissa, and ILOVEYOU malware incidents and Microsoft's security response."@en ; schema:dateCreated "2026-08-11"^^xsd:date ; schema:author ; schema:accountablePerson ; schema:about :article ; prov:wasGeneratedBy , , . :ontology a owl:Ontology ; schema:name "Office Security Incident and Response Ontology"@en ; schema:description "A lightweight vocabulary for incidents, design tradeoffs, response decisions, and consequences described in the ILOVEYOU chapter."@en ; schema:identifier "https://hardcoresoftware.learningbyshipping.com/p/060-iloveyou" ; rdfs:label "Office Security Incident and Response Ontology"@en ; rdfs:comment "Terms minted for the incident chronology and security-response analysis in this collection."@en . :MalwareIncident a rdfs:Class ; rdfs:subClassOf schema:Event ; rdfs:label "Malware incident"@en ; rdfs:comment "A security incident involving self-propagating malicious or disruptive software."@en ; rdfs:isDefinedBy :ontology . :ProductSecurityDecision a rdfs:Class ; rdfs:subClassOf schema:Action ; rdfs:label "Product security decision"@en ; rdfs:comment "A deliberate product change that reduces attack surface or limits unsafe automation."@en ; rdfs:isDefinedBy :ontology . :SecurityTradeoff a rdfs:Class ; rdfs:subClassOf schema:CreativeWork ; rdfs:label "Security tradeoff"@en ; rdfs:comment "A documented tension between valued product capabilities and dependable operation."@en ; rdfs:isDefinedBy :ontology . :exploitedCapability a rdf:Property ; rdfs:label "exploited capability"@en ; rdfs:comment "Relates an incident to a legitimate capability used as a propagation mechanism."@en ; rdfs:domain :MalwareIncident ; rdfs:range schema:Thing ; rdfs:isDefinedBy :ontology . :ledToDecision a rdf:Property ; rdfs:label "led to decision"@en ; rdfs:comment "Relates an incident or lesson to a product security decision it motivated."@en ; rdfs:range :ProductSecurityDecision ; rdfs:isDefinedBy :ontology . :estimatedDamage a rdf:Property ; rdfs:label "estimated damage"@en ; rdfs:comment "Records the source's stated monetary damage estimate."@en ; rdfs:domain :MalwareIncident ; rdfs:range xsd:string ; rdfs:isDefinedBy :ontology . :article a schema:Article ; schema:headline "060. ILOVEYOU"@en ; schema:description "Notes about Steven Sinofsky's account of how three escalating malware incidents forced Microsoft Office to place security and reliability ahead of unrestricted extensibility."@en ; schema:abstract "Concept showed that legitimate macros could propagate; Melissa scaled through Outlook; ILOVEYOU added destructive persistence and forced a compatibility-breaking security update."@en ; schema:datePublished "2021-12-26"^^xsd:date ; schema:url ; schema:mainEntityOfPage ; schema:author ; schema:publisher ; schema:about :wmConceptIncident, :melissaIncident, :iloveyouIncident, :extensibilitySecurityTradeoff, :guidPrivacyEpisode, :outlookSecurityUpdate ; schema:hasPart :ontology, :overviewSection, :preconditionsSection, :guidSection, :escalationSection, :responseSection, :lessonsSection, :faqSection, :glossarySection, :howtoSection, :sourceCommentsSection ; prov:wasGeneratedBy . a schema:Person ; schema:name "Steven Sinofsky"@en ; schema:url ; schema:identifier "https://www.linkedin.com/in/sinofsky" ; owl:sameAs , . a schema:Organization ; schema:name "Hardcore Software by Steven Sinofsky"@en ; schema:url . a schema:Organization ; schema:name "Microsoft"@en ; schema:url ; owl:sameAs . a schema:Organization ; schema:name "Intel"@en ; schema:url ; owl:sameAs . a schema:Organization ; schema:name "New York Times"@en ; schema:url ; owl:sameAs . a schema:Organization ; schema:name "Johnson & Johnson"@en ; schema:url ; owl:sameAs . a schema:Person ; schema:name "John Markoff"@en ; schema:url ; schema:identifier "https://www.linkedin.com/in/johnmarkoff" . :richardSmith a schema:Person ; schema:name "Richard Smith"@en ; schema:description "The Phar Lap executive whom the article credits with tracing Melissa-related metadata to the malware creator."@en . :robPrice a schema:Person ; schema:name "Rob Price"@en ; schema:description "The Outlook program-management leader identified in the article as a leader of the security-response discussion."@en . :willKennedy a schema:Person ; schema:name "Will Kennedy"@en ; schema:description "The development manager associated with Office GUID removal and later Outlook security-response work."@en . :peterPathe a schema:Person ; schema:name "PPathe"@en ; schema:alternateName "Blue"@en ; schema:description "The Word general manager named in the source who initiated macro-warning changes after WM/Concept.A."@en . :overviewSection a schema:CreativeWork ; schema:name "Crossing the line from annoyance to systemic risk"@en ; schema:abstract "Connected PCs, network file sharing, email, and trusted automation converted localized nuisances into global business interruptions."@en ; schema:isPartOf :article ; schema:about :connectedWorkplace, :systemicRisk . :preconditionsSection a schema:CreativeWork ; schema:name "The capabilities that enabled scale"@en ; schema:abstract "Macros, automatic execution, address-book access, and familiar messages were useful features whose composition created an efficient propagation path."@en ; schema:isPartOf :article ; schema:about :macroProgrammability, :automaticExecution, :addressBookAutomation, :socialEngineering . :guidSection a schema:CreativeWork ; schema:name "GUIDs, privacy, and forensic metadata"@en ; schema:abstract "A document identifier criticized as a privacy risk later helped investigators trace the Melissa creator, demonstrating metadata's dual use."@en ; schema:isPartOf :article ; schema:about :guidPrivacyEpisode, :metadata . :escalationSection a schema:CreativeWork ; schema:name "Concept to Melissa to ILOVEYOU"@en ; schema:abstract "Each incident reused trusted Office automation while increasing propagation reach, operational disruption, or destructive behavior."@en ; schema:isPartOf :article ; schema:hasPart :wmConceptIncident, :melissaIncident, :iloveyouIncident . :responseSection a schema:CreativeWork ; schema:name "Breaking compatibility to restore trust"@en ; schema:abstract "The Outlook team blocked risky attachment types, guarded automation, treated email as untrusted, and accepted customer disruption as the cost of prevention."@en ; schema:isPartOf :article ; schema:hasPart :blockRiskyAttachments, :guardAddressBook, :treatEmailAsUntrusted, :outlookSecurityUpdate . :lessonsSection a schema:CreativeWork ; schema:name "Enduring engineering and management lessons"@en ; schema:abstract "Warnings are weak controls, secure defaults matter, compatibility has limits, and leaders must support teams when safety requires breaking valued workflows."@en ; schema:isPartOf :article ; schema:about :warningFatigue, :secureByDefault, :leadershipPermission, :compatibilityBoundary . :wmConceptIncident a :MalwareIncident ; schema:name "WM/Concept.A incident"@en ; schema:description "A mid-1990s Word macro virus that propagated through documents by using macros, automatic start-up, and networked file sharing as designed."@en ; schema:startDate "1995"^^xsd:gYear ; :exploitedCapability :macroProgrammability, :automaticExecution, :networkFileSharing ; :ledToDecision :wordMacroWarnings ; schema:isPartOf :escalationSection . :melissaIncident a :MalwareIncident ; schema:name "W97M.Melissa.A incident"@en ; schema:alternateName "Melissa"@en ; schema:description "A 1999 Word macro virus that used Outlook automation to send an enticing message to the first 50 address-book contacts and overloaded mail systems."@en ; schema:startDate "1999-03"^^xsd:gYearMonth ; :exploitedCapability :macroProgrammability, :addressBookAutomation, :socialEngineering ; :ledToDecision :outlookMacroPrompts ; schema:isPartOf :escalationSection . :iloveyouIncident a :MalwareIncident ; schema:name "ILOVEYOU incident"@en ; schema:alternateName "Love Bug"@en ; schema:description "A May 2000 email worm that silently mailed itself to all Outlook contacts, persisted on infected computers, and replaced or deleted files."@en ; schema:startDate "2000-05"^^xsd:gYearMonth ; schema:location ; schema:attendee :affectedOrganizations ; :estimatedDamage "At least $8 billion and as high as $15 billion"@en ; :exploitedCapability :addressBookAutomation, :hiddenExecutableAttachment, :socialEngineering ; :ledToDecision :blockRiskyAttachments, :guardAddressBook, :treatEmailAsUntrusted, :outlookSecurityUpdate ; schema:isPartOf :escalationSection . :affectedOrganizations a schema:Audience ; schema:name "Affected organizations and computer users"@en ; schema:description "The source reports more than 10 million infected computers worldwide, widespread mail-server shutdowns, and major productivity losses."@en . :guidPrivacyEpisode a schema:Event ; schema:name "Office and Windows GUID privacy episode"@en ; schema:description "Reporting showed that Office document GUIDs and Windows registration data could theoretically be correlated through embedded network-card identifiers."@en ; schema:startDate "1999"^^xsd:gYear ; schema:participant , :richardSmith, , ; schema:result :guidRemovalPatch, :metadataForensicsLesson . :wordMacroWarnings a :ProductSecurityDecision ; schema:name "Add Word macro warnings"@en ; schema:description "Warn users that a document contains macros and make automatic execution more difficult."@en ; schema:agent :peterPathe ; schema:object :macroProgrammability . :outlookMacroPrompts a :ProductSecurityDecision ; schema:name "Prompt on Outlook automation"@en ; schema:description "Require confirmation when automation accesses Outlook data or sends mail, disrupting add-ins that previously operated silently."@en ; schema:object :addressBookAutomation . :guidRemovalPatch a :ProductSecurityDecision ; schema:name "Remove unused Office document GUIDs"@en ; schema:description "Stop writing unused GUIDs to Office files and provide a tool to remove them from existing documents."@en ; schema:agent :willKennedy, . :blockRiskyAttachments a :ProductSecurityDecision ; schema:name "Block risky attachment types"@en ; schema:description "Prevent executable and other dangerous attachment types from being sent or opened through Outlook."@en ; schema:agent :robPrice, :willKennedy ; schema:isPartOf :responseSection . :guardAddressBook a :ProductSecurityDecision ; schema:name "Guard programmatic address-book and send access"@en ; schema:description "Warn and constrain software attempting to read contacts or send messages silently through Outlook APIs."@en ; schema:agent :robPrice, :willKennedy ; schema:isPartOf :responseSection . :treatEmailAsUntrusted a :ProductSecurityDecision ; schema:name "Treat all email as untrusted"@en ; schema:description "Quarantine messages conceptually and isolate Outlook data from code regardless of how code reaches a message."@en ; schema:agent :robPrice, :willKennedy ; schema:isPartOf :responseSection . :outlookSecurityUpdate a schema:SoftwareApplication, :ProductSecurityDecision ; schema:name "Outlook Email Security Update"@en ; schema:description "The June 8, 2000 security update for Office 97 and 2000, Outlook 98, and Outlook 2000 that restricted attachments and automation."@en ; schema:datePublished "2000-06-08"^^xsd:date ; schema:provider ; schema:isPartOf :responseSection ; schema:result :reducedOfficeVirusSeverity . :extensibilitySecurityTradeoff a :SecurityTradeoff ; schema:name "Extensibility versus security"@en ; schema:description "The legitimate programmability that made Office valuable and sticky also enabled self-propagating automation at global scale."@en ; schema:about :macroProgrammability, :addressBookAutomation, :compatibilityBoundary . :connectedWorkplace a schema:DefinedTerm ; schema:name "Connected workplace"@en ; schema:description "A business environment where PCs, networked files, and email create rapid paths for both collaboration and propagation."@en . :systemicRisk a schema:DefinedTerm ; schema:name "Systemic software risk"@en ; schema:description "Risk that a common product capability can trigger correlated disruption across many organizations."@en . :macroProgrammability a schema:DefinedTerm ; schema:name "Macro programmability"@en ; schema:description "End-user automation embedded in documents or applications to perform repeatable tasks."@en . :automaticExecution a schema:DefinedTerm ; schema:name "Automatic execution"@en ; schema:description "Starting code when a document opens or another familiar user action occurs."@en . :networkFileSharing a schema:DefinedTerm ; schema:name "Networked file sharing"@en ; schema:description "Distributing documents across connected computers, enabling both collaboration and infection propagation."@en . :addressBookAutomation a schema:DefinedTerm ; schema:name "Address-book automation"@en ; schema:description "Programmatic access to contacts and mail-sending functions in Outlook."@en . :socialEngineering a schema:DefinedTerm ; schema:name "Social engineering"@en ; schema:description "Designing a message or attachment to appear familiar, urgent, or enticing so a recipient opens it."@en . :hiddenExecutableAttachment a schema:DefinedTerm ; schema:name "Hidden executable attachment"@en ; schema:description "A program presented with a name or interface cue that makes it appear to be an ordinary document."@en . :metadata a schema:DefinedTerm ; schema:name "Metadata"@en ; schema:description "Data about data; in this story, document identifiers became both a privacy concern and forensic evidence."@en . :warningFatigue a schema:DefinedTerm ; schema:name "Warning fatigue"@en ; schema:description "The tendency to dismiss repeated dialogs that interrupt a task, weakening warnings as a security control."@en . :secureByDefault a schema:DefinedTerm ; schema:name "Secure by default"@en ; schema:description "A product posture that enables safer constraints without requiring every user or administrator to choose them."@en . :compatibilityBoundary a schema:DefinedTerm ; schema:name "Compatibility boundary"@en ; schema:description "The point at which preserving existing behavior imposes more systemic risk than breaking dependent workflows."@en . :leadershipPermission a schema:DefinedTerm ; schema:name "Leadership permission to cause pain"@en ; schema:description "Explicit executive support for a team whose necessary security changes will generate customer and ecosystem opposition."@en . :metadataForensicsLesson a schema:CreativeWork ; schema:name "Metadata can create privacy risk and forensic value"@en ; schema:description "The same embedded identifier criticized as a privacy risk helped investigators connect Melissa evidence to its creator."@en . :reducedOfficeVirusSeverity a schema:CreativeWork ; schema:name "Fewer and less severe Office viruses"@en ; schema:description "The article credits the Outlook Email Security Update with contributing to reduced Office virus severity over subsequent decades."@en . :glossarySection a schema:DefinedTermSet, skos:ConceptScheme ; schema:name "Glossary of security and product-design concepts"@en ; schema:description "Terms central to the article's incident history and engineering lessons."@en ; schema:hasDefinedTerm :connectedWorkplace, :systemicRisk, :macroProgrammability, :automaticExecution, :networkFileSharing, :addressBookAutomation, :socialEngineering, :hiddenExecutableAttachment, :metadata, :warningFatigue, :secureByDefault, :compatibilityBoundary, :leadershipPermission ; schema:isPartOf :article . :connectedWorkplace schema:inDefinedTermSet :glossarySection . :systemicRisk schema:inDefinedTermSet :glossarySection . :macroProgrammability schema:inDefinedTermSet :glossarySection . :automaticExecution schema:inDefinedTermSet :glossarySection . :networkFileSharing schema:inDefinedTermSet :glossarySection . :addressBookAutomation schema:inDefinedTermSet :glossarySection . :socialEngineering schema:inDefinedTermSet :glossarySection . :hiddenExecutableAttachment schema:inDefinedTermSet :glossarySection . :metadata schema:inDefinedTermSet :glossarySection . :warningFatigue schema:inDefinedTermSet :glossarySection . :secureByDefault schema:inDefinedTermSet :glossarySection . :compatibilityBoundary schema:inDefinedTermSet :glossarySection . :leadershipPermission schema:inDefinedTermSet :glossarySection . :faqSection a schema:FAQPage ; schema:name "Questions raised by the ILOVEYOU history"@en ; schema:description "Answers grounded in the article's chronology, response decisions, and product-design lessons."@en ; schema:mainEntity :q1, :q2, :q3, :q4, :q5, :q6, :q7, :q8, :q9, :q10, :q11, :q12, :q13, :q14 ; schema:isPartOf :article . :q1 a schema:Question ; schema:name "Why did WM/Concept.A matter if it caused little direct damage?"@en ; schema:acceptedAnswer :a1 ; schema:isPartOf :faqSection . :a1 a schema:Answer ; schema:text "It demonstrated that legitimate macro and file-sharing features could propagate globally and could easily be adapted for destructive behavior."@en ; schema:isPartOf :q1 . :q2 a schema:Question ; schema:name "What legitimate value did macros provide?"@en ; schema:acceptedAnswer :a2 ; schema:isPartOf :faqSection . :a2 a schema:Answer ; schema:text "Macros automated repetitive work and supported a substantial ecosystem of customized business workflows, consulting, and training."@en ; schema:isPartOf :q2 . :q3 a schema:Question ; schema:name "How did Melissa increase propagation speed?"@en ; schema:acceptedAnswer :a3 ; schema:isPartOf :faqSection . :a3 a schema:Answer ; schema:text "It combined a Word macro with Outlook automation and sent itself to the first 50 contacts in each infected user's address book."@en ; schema:isPartOf :q3 . :q4 a schema:Question ; schema:name "What role did social engineering play?"@en ; schema:acceptedAnswer :a4 ; schema:isPartOf :faqSection . :a4 a schema:Answer ; schema:text "Familiar-looking subjects, messages, and attachment names encouraged recipients to open content that activated the propagation chain."@en ; schema:isPartOf :q4 . :q5 a schema:Question ; schema:name "How did ILOVEYOU differ from Melissa?"@en ; schema:acceptedAnswer :a5 ; schema:isPartOf :faqSection . :a5 a schema:Answer ; schema:text "ILOVEYOU silently sent itself to every address-book contact, persisted on infected computers, and replaced or deleted files."@en ; schema:isPartOf :q5 . :q6 a schema:Question ; schema:name "What damage estimate does the article report for ILOVEYOU?"@en ; schema:acceptedAnswer :a6 ; schema:isPartOf :faqSection . :a6 a schema:Answer ; schema:text "The article reports estimates of at least $8 billion and as high as $15 billion."@en ; schema:isPartOf :q6 . :q7 a schema:Question ; schema:name "Why were warning dialogs insufficient?"@en ; schema:acceptedAnswer :a7 ; schema:isPartOf :faqSection . :a7 a schema:Answer ; schema:text "Repeated warnings interrupt task flow and are commonly dismissed, so they cannot reliably contain automation-driven threats by themselves."@en ; schema:isPartOf :q7 . :q8 a schema:Question ; schema:name "Why was the GUID episode relevant to malware response?"@en ; schema:acceptedAnswer :a8 ; schema:isPartOf :faqSection . :a8 a schema:Answer ; schema:text "Document metadata that created privacy concerns also supplied evidence that investigators used while tracing Melissa's creator."@en ; schema:isPartOf :q8 . :q9 a schema:Question ; schema:name "What did the Outlook team decide after ILOVEYOU?"@en ; schema:acceptedAnswer :a9 ; schema:isPartOf :faqSection . :a9 a schema:Answer ; schema:text "The team blocked dangerous attachment types, guarded programmatic access to contacts and sending, and treated email content as untrusted."@en ; schema:isPartOf :q9 . :q10 a schema:Question ; schema:name "Why did customers resist the security changes?"@en ; schema:acceptedAnswer :a10 ; schema:isPartOf :faqSection . :a10 a schema:Answer ; schema:text "The restrictions broke valued add-ins, automated workflows, and familiar methods of exchanging executable or self-extracting content."@en ; schema:isPartOf :q10 . :q11 a schema:Question ; schema:name "What was the central compatibility tradeoff?"@en ; schema:acceptedAnswer :a11 ; schema:isPartOf :faqSection . :a11 a schema:Answer ; schema:text "Microsoft had to choose between preserving ecosystem behavior and reducing the systemic risk created by that behavior in a connected workplace."@en ; schema:isPartOf :q11 . :q12 a schema:Question ; schema:name "What leadership support did the Outlook team need?"@en ; schema:acceptedAnswer :a12 ; schema:isPartOf :faqSection . :a12 a schema:Answer ; schema:text "The team needed explicit permission to impose necessary customer pain and assurance that leadership would support it through predictable pushback."@en ; schema:isPartOf :q12 . :q13 a schema:Question ; schema:name "When was the Outlook Email Security Update released?"@en ; schema:acceptedAnswer :a13 ; schema:isPartOf :faqSection . :a13 a schema:Answer ; schema:text "The team completed and released the update on June 8, 2000, four weeks after the crisis response began."@en ; schema:isPartOf :q13 . :q14 a schema:Question ; schema:name "What enduring product lesson does the article offer?"@en ; schema:acceptedAnswer :a14 ; schema:isPartOf :faqSection . :a14 a schema:Answer ; schema:text "Capabilities designed for expert users must be reassessed when scale, connectivity, and mainstream use turn local misuse into correlated global harm."@en ; schema:isPartOf :q14 . :howtoSection a schema:HowTo ; schema:name "How to respond when a valued capability becomes an attack path"@en ; schema:description "A defensive product-response sequence distilled from the article's Microsoft Office experience."@en ; schema:step :step1, :step2, :step3, :step4, :step5, :step6, :step7 ; schema:isPartOf :article . :step1 a schema:HowToStep ; schema:position 1 ; schema:name "Establish the real blast radius"@en ; schema:text "Measure affected users, systems, operational downtime, propagation paths, and customer recovery costs before debating feature preservation."@en ; schema:isPartOf :howtoSection . :step2 a schema:HowToStep ; schema:position 2 ; schema:name "Map the legitimate capabilities used in the chain"@en ; schema:text "Identify which trusted features, automation interfaces, defaults, and social cues compose the attack path."@en ; schema:isPartOf :howtoSection . :step3 a schema:HowToStep ; schema:position 3 ; schema:name "Treat warnings as transitional controls"@en ; schema:text "Use prompts only where necessary while designing structural restrictions that do not depend on sustained user attention."@en ; schema:isPartOf :howtoSection . :step4 a schema:HowToStep ; schema:position 4 ; schema:name "Choose secure defaults at the compatibility boundary"@en ; schema:text "Block or constrain high-risk behavior by default when the expected systemic harm exceeds the value of unchanged workflows."@en ; schema:isPartOf :howtoSection . :step5 a schema:HowToStep ; schema:position 5 ; schema:name "Give the response team explicit leadership backing"@en ; schema:text "Authorize the team to make necessary breaking changes and support it through criticism from users, administrators, and ecosystem partners."@en ; schema:isPartOf :howtoSection . :step6 a schema:HowToStep ; schema:position 6 ; schema:name "Ship across supported versions and operational channels"@en ; schema:text "Coordinate engineering, testing, support, field teams, documentation, and security vendors so mitigations reach affected environments."@en ; schema:isPartOf :howtoSection . :step7 a schema:HowToStep ; schema:position 7 ; schema:name "Institutionalize the safer operating model"@en ; schema:text "Use after-action reports and observed workarounds to refine defaults, administrative controls, ecosystem guidance, and future product architecture."@en ; schema:isPartOf :howtoSection . :sourceCommentsSection a schema:CreativeWork ; schema:name "Visible reader recollections"@en ; schema:description "Two comments visible on the source page recall the patch team's intense schedule and later application workarounds."@en ; schema:hasPart :commentMikeTholfsen, :commentMichaelDragone ; schema:isPartOf :article . :commentMikeTholfsen a schema:Comment ; schema:author :mikeTholfsen ; schema:datePublished "2022-12-30"^^xsd:date ; schema:position 1 ; schema:text "Mike Tholfsen recalls that Outlook team members worked through Memorial Day weekend to build and test the ILOVEYOU patches, followed later by a team celebration."@en ; schema:parentItem :article ; schema:isPartOf :sourceCommentsSection . :mikeTholfsen a schema:Person ; schema:name "Mike Tholfsen"@en ; schema:url . :commentMichaelDragone a schema:Comment ; schema:author :michaelDragone ; schema:datePublished "2021-12-26"^^xsd:date ; schema:position 2 ; schema:text "Michael Dragone recalls selectively re-enabling compatibility for an internal line-of-business application after the Email Security Update."@en ; schema:parentItem :article ; schema:isPartOf :sourceCommentsSection . :michaelDragone a schema:Person ; schema:name "Michael Dragone"@en ; schema:url . a schema:SoftwareApplication, prov:SoftwareAgent ; schema:name "kg-generator"@en ; schema:url ; schema:description "Skill used to model the source article as RDF."@en ; prov:actedOnBehalfOf . a schema:SoftwareApplication, prov:SoftwareAgent ; schema:name "rdf-infographic-skill"@en ; schema:url ; schema:description "Skill used to render the validated RDF collection as an interactive HTML document."@en ; prov:actedOnBehalfOf . a schema:SoftwareApplication, prov:SoftwareAgent ; schema:name "GPT-5 in Codex"@en ; schema:url ; schema:description "The language-model environment that executed the RDF and HTML generation workflow."@en ; prov:actedOnBehalfOf . a schema:Person ; schema:name "Kingsley Idehen"@en ; schema:url .