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

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

Subject Item

frame:Holding_off_on

fn15schema:hasFrameElement

n2:holding_off_on

Subject Item

st2wn:weightedst_12298

st2wn:onFE

n2:holding_off_on

Subject Item

n2:holding_off_on

rdf:type

fn15schema:FrameElement owl:ObjectProperty

rdfs:subPropertyOf

n5:location_in_time n5:calendric_unit n9:cause_change n11:change_event_time n2:waiting

owl:sameAs

n12:end_point

rdfs:domain

frame:Change_event_time frame:Cause_change frame:Holding_off_on frame:Location_in_time frame:Calendric_unit frame:Waiting

rdfs:range

owl:Thing st:Time

rdfs:comment

The point in time, defined either as a clock time or in terms of an event that takes place, at which the Agent engages in the Desirable_action or interacts with the Salient_entity. We waited on technology development until we had made instructional plans.

rdfs:label

End_point

fn15schema:FE_coreType

Peripheral Peripheral

fn15schema:FE_name

End_point End_point

fn15schema:definition

The point in time, defined either as a clock time or in terms of an event that takes place, at which the Agent engages in the Desirable_action or interacts with the Salient_entity. We waited on technology development until we had made instructional plans. <def-root>The point in time, defined either as a clock time or in terms of an event that takes place, at which the <fen>Agent</fen> engages in the <fen>Desirable_action</fen> or interacts with the <fen>Salient_entity</fen>. <ex>We <t>waited</t> on technology development <fex name="End_point">until we had made instructional plans</fex>.</ex></def-root>

fn15schema:hasSuperFE

n2:waiting n11:change_event_time

fn15schema:FE_ID

8642

fn15schema:FE_abbrev

end

fn15schema:FE_cBy

JKR

fn15schema:FE_cDate

2005-07-18T19:44:25+02:00

fn15schema:frameElementOf

frame:Holding_off_on