HTML Microdata document

This HTML5 document contains 102 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Prefix	Namespace IRI
n12	https://w3id.org/framester/framenet/abox/fe/Manner.
n19	https://w3id.org/framester/data/propbank-3.4.0/RoleSet/
n24	https://w3id.org/framester/framenet/abox/fe/Purpose.
n41	https://w3id.org/framester/framenet/abox/flu/summarize.v.
n29	https://w3id.org/framester/framenet/abox/lu/sum_up.
n22	https://w3id.org/framester/framenet/abox/fe/Means.
framestercore	https://w3id.org/framester/data/framestercore/
n39	https://w3id.org/framester/framenet/abox/flu/outline.v.
frame	https://w3id.org/framester/framenet/abox/frame/
n4	https://w3id.org/framester/framenet/abox/fe/Medium.
n11	https://w3id.org/framester/fn2d0/
n25	https://w3id.org/framester/framenet/abox/fe/Place.
n37	http://premon.fbk.eu/resource/
n23	https://w3id.org/framester/framenet/abox/fe/Time.
n35	https://w3id.org/framester/framenet/abox/fe/Communicator.
n36	https://w3id.org/framester/framenet/abox/flu/synopsis.n.
skos	http://www.w3.org/2004/02/skos/core#
n38	https://w3id.org/framester/framenet/abox/flu/sum_up.v.
n13	https://w3id.org/framester/framenet/abox/fe/Addressee.
rdfs	http://www.w3.org/2000/01/rdf-schema#
rdf	http://www.w3.org/1999/02/22-rdf-syntax-ns#
n40	https://w3id.org/framester/predmatrix/data/summary.01.
xsdh	http://www.w3.org/2001/XMLSchema#
n28	https://w3id.org/framester/framenet/abox/fe/State_of_affairs.
n6	https://w3id.org/framester/predmatrix/schema/
n26	https://w3id.org/framester/pb/data/roleset/
n21	https://w3id.org/framester/framenet/abox/lu/outline.
n42	https://w3id.org/framester/framenet/abox/lu/boil_down.
fn15schema	https://w3id.org/framester/framenet/tbox/
n15	https://w3id.org/framester/framenet/abox/lu/synopsis.
n33	https://w3id.org/framester/fn2d0/fn2d0base/
n5	https://w3id.org/framester/predmatrix/data/summarize.01.
n7	https://w3id.org/framester/framenet/abox/flu/boil_down.v.
n10	https://w3id.org/framester/fn2d0/fn2ssbase/
n34	https://w3id.org/framester/framenet/abox/fe/Containing_event.
n17	https://w3id.org/framester/framenet/abox/fe/Duration.
n27	https://w3id.org/framester/framenet/abox/lu/summarize.
n14	https://w3id.org/framester/framenet/abox/fe/Summary.
n16	https://w3id.org/framester/predmatrix/data/outline.01.
fschema	https://w3id.org/framester/schema/
n30	https://w3id.org/framester/framenet/abox/FEcoreSet/
n31	https://w3id.org/framester/framenet/abox/fe/Circumstances.
owl	http://www.w3.org/2002/07/owl#

Subject Item: n38:summarizing
fn15schema:framalLexUnitOf: frame:Summarizing

Subject Item: n39:summarizing
fn15schema:framalLexUnitOf: frame:Summarizing

Subject Item: n36:summarizing
fn15schema:framalLexUnitOf: frame:Summarizing

Subject Item: n7:summarizing
fn15schema:framalLexUnitOf: frame:Summarizing

Subject Item: n41:summarizing
fn15schema:framalLexUnitOf: frame:Summarizing

Subject Item: framestercore:Summarizing
owl:sameAs: frame:Summarizing

Subject Item: frame:Communication
fn15schema:isInheritedBy: frame:Summarizing
fn15schema:hasFrameRelation: frame:Summarizing

Subject Item: frame:Summarizing
rdf:type: fn15schema:Frame owl:Class
owl:sameAs: n37:fn17-summarizing
rdfs:subClassOf: frame:Communication
rdfs:comment: A Communicator processes some information (either from textual or real-world/perceptual sources) regarding a State_of_affairs into a concise form (a summary) that contains the essential content in briefer form, and communicates this summary to an Addressee, or records it in a Medium. The State_of_affairs may be represented directly (e.g., outline what happened, the situation abroad), or as a textual source (summarizing the documents), or metonymically as some focal entity (a synopsis of the candidates). Frank has already summarized some of the reactions on his weblog. Director Van Auken gave a brief informational synopsis of each applicant. He boiled down the argument for domestic wiretapping in one plainspoken and effective, if also deceptive, line... You should be able to summarize your findings to a lay audience. In her materials, she also outlined the situation and major problems facing the company. Some LUs, such as summarize and synopsis entail a preexisting body of information that has been processed into a briefer form by the Communicator. Others, such as outline and blueprint are compatible with, but do not entail, a preexisting, fully fleshed-out concept. E.g., Her book outlines a new proposal for handling grammaticalization, though she doesn't flesh it out entirely.
skos:closeMatch: n19:outline-01 n19:summarize-01
rdfs:label: Summarizing
fn15schema:definition: <def-root>A <fen>Communicator</fen> processes some information (either from textual or real-world/perceptual sources) regarding a <fen>State_of_affairs</fen> into a concise form (a summary) that contains the essential content in briefer form, and communicates this summary to an <fen>Addressee</fen>, or records it in a <fen>Medium</fen>. The <fen>State_of_affairs</fen> may be represented directly (e.g., outline <ment>what happened</ment>, <ment>the situation abroad</ment>), or as a textual source (summarizing <ment>the documents</ment>), or metonymically as some focal entity (a synopsis <ment>of the candidates</ment>). <ex><fex name="Communicator">Frank</fex> has already <t>summarized</t> <fex name="State_of_affairs">some of the reactions</fex> <fex name="med">on his weblog</fex>.</ex> <ex><fex name="com">Director Van Auken</fex> <ment>gave</ment> a brief informational <t>synopsis</t> <fex name="sta">of each applicant</fex>. </ex> <ex><fex name="Communicator">He</fex> <t>boiled</t> <t>down</t> <fex name="State_of_affairs">the argument for domestic wiretapping</fex> in one plainspoken and effective, if also deceptive, line...</ex> <ex><fex name="Communicator">You</fex> should be able to <t>summarize</t> <fex name="State_of_affairs">your findings</fex> <fex name="Addressee">to a lay audience</fex>.</ex> <ex><fex name="Medium">In her materials</fex>, <fex name="Communicator">she</fex> also <t>outlined</t> <fex name="State_of_affairs">the situation and major problems facing the company</fex>.</ex> Some LUs, such as <ment>summarize</ment> and <ment>synopsis</ment> entail a preexisting body of information that has been processed into a briefer form by the <fen>Communicator</fen>. Others, such as <ment>outline</ment> and <ment>blueprint</ment> are compatible with, but do not entail, a preexisting, fully fleshed-out concept. E.g., <ex><fex name="Medium">Her book</fex> <t>outlines</t> <fex name="State_of_affairs">a new proposal for handling grammaticalization</fex>, though she doesn't flesh it out entirely.</ex></def-root> A Communicator processes some information (either from textual or real-world/perceptual sources) regarding a State_of_affairs into a concise form (a summary) that contains the essential content in briefer form, and communicates this summary to an Addressee, or records it in a Medium. The State_of_affairs may be represented directly (e.g., outline what happened, the situation abroad), or as a textual source (summarizing the documents), or metonymically as some focal entity (a synopsis of the candidates). Frank has already summarized some of the reactions on his weblog. Director Van Auken gave a brief informational synopsis of each applicant. He boiled down the argument for domestic wiretapping in one plainspoken and effective, if also deceptive, line... You should be able to summarize your findings to a lay audience. In her materials, she also outlined the situation and major problems facing the company. Some LUs, such as summarize and synopsis entail a preexisting body of information that has been processed into a briefer form by the Communicator. Others, such as outline and blueprint are compatible with, but do not entail, a preexisting, fully fleshed-out concept. E.g., Her book outlines a new proposal for handling grammaticalization, though she doesn't flesh it out entirely. A Communicator processes some information (either from textual or real-world/perceptual sources) regarding a State_of_affairs into a concise form (a summary) that contains the essential content in briefer form, and communicates this summary to an Addressee, or records it in a Medium. The State_of_affairs may be represented directly (e.g., outline <ment>what happened</ment>, <ment>the situation abroad</ment>), or as a textual source (summarizing <ment>the documents</ment>), or metonymically as some focal entity (a synopsis <ment>of the candidates</ment>). Frank has already summarized some of the reactions on his weblog. Director Van Auken <ment>gave</ment> a brief informational synopsis of each applicant. He boiled down the argument for domestic wiretapping in one plainspoken and effective, if also deceptive, line... You should be able to summarize your findings to a lay audience. In her materials, she also outlined the situation and major problems facing the company. Some LUs, such as <ment>summarize</ment> and <ment>synopsis</ment> entail a preexisting body of information that has been processed into a briefer form by the Communicator. Others, such as <ment>outline</ment> and <ment>blueprint</ment> are compatible with, but do not entail, a preexisting, fully fleshed-out concept. E.g., Her book outlines a new proposal for handling grammaticalization, though she doesn't flesh it out entirely.
fn15schema:frame_name: Summarizing Summarizing
fn15schema:hasFrameElement: n12:summarizing n13:summarizing n14:summarizing n23:summarizing n22:summarizing n4:summarizing n28:summarizing n34:summarizing n25:summarizing n35:summarizing n17:summarizing n31:summarizing n24:summarizing
fn15schema:hasLexUnit: n21:v n27:v n29:v n15:n n42:v
fn15schema:inheritsFrom: frame:Communication
fn15schema:frame_ID: 1722
fn15schema:frame_cBy: RLG
fn15schema:frame_cDate: 2006-03-17T20:16:54+01:00
fn15schema:hasFEcoreSet: n30:summarizing_coreSet1
fn15schema:hasFrameRelation: frame:Communication

Subject Item: n13:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n34:summarizing
rdfs:domain: frame:Summarizing

Subject Item: n17:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n22:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n12:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n4:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n25:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n24:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n28:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n14:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n31:summarizing
rdfs:domain: frame:Summarizing

Subject Item: n35:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n23:summarizing
rdfs:domain: frame:Summarizing
fn15schema:frameElementOf: frame:Summarizing

Subject Item: n33:768
n11:onFrame: frame:Summarizing

Subject Item: n29:v
fn15schema:lexUnitFrame: frame:Summarizing

Subject Item: n21:v
fn15schema:lexUnitFrame: frame:Summarizing

Subject Item: n15:n
fn15schema:lexUnitFrame: frame:Summarizing

Subject Item: n42:v
fn15schema:lexUnitFrame: frame:Summarizing

Subject Item: n27:v
fn15schema:lexUnitFrame: frame:Summarizing

Subject Item: n10:2568
n11:onFrame: frame:Summarizing

Subject Item: n10:2988
n11:onFrame: frame:Summarizing

Subject Item: n10:343
n11:onFrame: frame:Summarizing

Subject Item: n40:1
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n40:2
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n5:1
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n5:2
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n5:3
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n5:4
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n16:1
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n16:2
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n16:3
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n16:4
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n16:5
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n16:6
n6:13_FN_FRAME: frame:Summarizing

Subject Item: n19:outline-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n19:summarize-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n19:boil-down-03
fschema:subsumedUnder: frame:Summarizing

Subject Item: n19:highlight-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n19:sum-up-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n30:summarizing_coreSet1
fn15schema:isFECoreSetOf: frame:Summarizing

Subject Item: n26:highlight-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n26:outline-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n26:sum-up-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n26:summarize-01
fschema:subsumedUnder: frame:Summarizing

Subject Item: n26:boil-down-03
fschema:subsumedUnder: frame:Summarizing

Subject Item: _:vb23669
owl:someValuesFrom: frame:Summarizing