@base          <https://w3id.org/framester/> .
@prefix geonames: <http://www.geonames.org/ontology#> .
@prefix owl:   <http://www.w3.org/2002/07/owl#> .
@prefix skos:  <http://www.w3.org/2004/02/skos/core#> .
@prefix schema-org: <http://schema.org/> .
@prefix bio:   <http://purl.org/vocab/bio/0.1/> .
@prefix conf:  <http://lodview.it/conf#> .
@prefix metalex: <http://www.metalex.eu/metalex/2008-05-02#> .
@prefix ocd:   <http://dati.camera.it/ocd/> .
@prefix rel:   <http://purl.org/vocab/relationship/> .
@prefix dcterms: <http://purl.org/dc/terms/> .
@prefix dbpprop: <http://dbpedia.org/property/> .
@prefix foaf:  <http://xmlns.com/foaf/0.1/> .
@prefix bbc:   <http://www.bbc.co.uk/ontologies/> .
@prefix void:  <http://rdfs.org/ns/void#> .
@prefix dbpedia-owl: <http://dbpedia.org/ontology/> .
@prefix dbpedia: <http://dbpedia.org/resource/> .
@prefix frbr:  <http://purl.org/vocab/frbr/core#> .
@prefix dwc:   <http://rs.tdwg.org/dwc/terms/> .
@prefix claros: <http://purl.org/NET/Claros/vocab#> .
@prefix crm-owl: <http://purl.org/NET/crm-owl#> .
@prefix meta:  <http://example.org/metadata#> .
@prefix bmuseum: <http://collection.britishmuseum.org/id/ontology/> .
@prefix ods:   <http://lod.xdams.org/ontologies/ods/> .
@prefix gml:   <http://www.opengis.net/gml/> .
@prefix muninn: <http://rdf.muninn-project.org/ontologies/documents#> .
@prefix xsd:   <http://www.w3.org/2001/XMLSchema#> .
@prefix yago:  <http://dbpedia.org/class/yago/> .
@prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .
@prefix units: <http://dbpedia.org/units/> .
@prefix rso:   <http://www.researchspace.org/ontology/> .
@prefix geo:   <http://www.w3.org/2003/01/geo/wgs84_pos#> .
@prefix oad:   <http://lod.xdams.org/reload/oad/> .
@prefix crm120111: <http://erlangen-crm.org/120111/> .
@prefix cdoc:  <http://www.cidoc-crm.org/cidoc-crm#> .
@prefix bibleontology: <http://bibleontology.com/property#> .
@prefix prov:  <http://www.w3.org/ns/prov#> .
@prefix crm:   <http://erlangen-crm.org/current/> .
@prefix cc:    <http://creativecommons.org/ns#> .
@prefix shoah: <http://dati.cdec.it/lod/shoah/> .
@prefix npg:   <http://ns.nature.com/terms/> .
@prefix org:   <http://www.w3.org/ns/org#> .
@prefix gn:    <http://www.geonames.org/ontology#> .
@prefix ibc:   <http://dati.ibc.it/ibc/> .
@prefix aemetonto: <http://aemet.linkeddata.es/ontology/> .
@prefix skos-xl: <http://www.w3.org/2008/05/skos-xl#> .
@prefix lgdo:  <http://linkedgeodata.org/ontology/capital> .
@prefix rdf:   <http://www.w3.org/1999/02/22-rdf-syntax-ns#> .
@prefix eac-cpf: <http://archivi.ibc.regione.emilia-romagna.it/ontology/eac-cpf/> .
@prefix bibo:  <http://purl.org/ontology/bibo/> .
@prefix time:  <http://www.w3.org/2006/time#> .
@prefix dc:    <http://purl.org/dc/elements/1.1/> .
@prefix prism21: <http://prismstandard.org/namespaces/basic/2.1/> .
@prefix po:    <http://purl.org/ontology/po/> .

<framenet/abox/frame/Reserving>
        a                <framenet/tbox/Frame> , owl:Class ;
        rdfs:comment     "In this frame, a Booker brings about a situation where an Organization plans to provide Services to a Client at a particular Scheduled_time. The Organization has authority over when Services are provided to whom. The Booker usually has to communicate and negotiate with the Organization to plan the Services for a mutually agreeable Scheduled_time. Usually, there is a Payment as well. We can book you a boatride on the Somme or a special tour of the Louvre . Now booking trips to Cancunfor only $50 ! CNI INI In many cases, the Booker may be the same as the Client or the Organization. When the Booker is also the Organization providing the service, as in the first sentence below, we annotate Booker on the first layer and Organization on the second. Realizing that the Booker is also the Organization providing the service is an inference, as we can see by comparing the following two examples. In the first, it seems clear that the hotel is providing the service. In the second, it is clear that the hotel is not providing the service. The hotel gave us a reservation for two nights . The hotel gave us a reservation for two nights at the adjacent hotel to make up for screwing up our original booking . In the frequent case where the Booker is the same as the Client, we annotate Booker on the first layer and Client on the second. Client is on the second layer since, in most cases, it is an inference that may be wrong. For example, in the following sentence, the annotation indicates that Patrick is the Client. However, it is also possible that Patrick is reserving a table for a party that doesn't even include himself: Patrick tried to reserve a table at Dorsia for 7:00 . Patrick tried to reserve a table at Dorsia for 7:00 ."@en ;
        rdfs:label       "Reserving" ;
        owl:sameAs       <http://premon.fbk.eu/resource/fn17-reserving> ;
        skos:closeMatch  <wn/wn30/instances/synset-reservation-noun-6> , <wn/wn30/instances/synset-reserve-verb-3> , <wn/wn30/instances/synset-booking-noun-2> , <wn/wn30/instances/synset-book-verb-4> , <wn/wn30/instances/synset-reserve-verb-4> ;
        <framenet/tbox/definition>  "In this frame, a Booker brings about a situation where an Organization plans to provide Services to a Client at a particular Scheduled_time. The Organization has authority over when Services are provided to whom. The Booker usually has to communicate and negotiate with the Organization to plan the Services for a mutually agreeable Scheduled_time. Usually, there is a Payment as well. We can book you a boatride on the Somme or a special tour of the Louvre . Now booking trips to Cancunfor only $50 ! CNI INI In many cases, the Booker may be the same as the Client or the Organization. When the Booker is also the Organization providing the service, as in the first sentence below, we annotate Booker on the first layer and Organization on the second. Realizing that the Booker is also the Organization providing the service is an inference, as we can see by comparing the following two examples. In the first, it seems clear that the hotel is providing the service. In the second, it is clear that the hotel is not providing the service. The hotel gave us a reservation for two nights . The hotel gave us a reservation for two nights at the adjacent hotel to make up for screwing up our original booking . In the frequent case where the Booker is the same as the Client, we annotate Booker on the first layer and Client on the second. Client is on the second layer since, in most cases, it is an inference that may be wrong. For example, in the following sentence, the annotation indicates that Patrick is the Client. However, it is also possible that Patrick is reserving a table for a party that doesn't even include himself: Patrick tried to reserve a table at Dorsia for 7:00 . Patrick tried to reserve a table at Dorsia for 7:00 ."@en ;
        <framenet/tbox/frame_ID>  2679 ;
        <framenet/tbox/frame_cBy>  "RyC" ;
        <framenet/tbox/frame_cDate>  "2011-10-25T10:03:06+02:00"^^xsd:dateTime ;
        <framenet/tbox/frame_name>  "Reserving" ;
        <framenet/tbox/hasFrameElement>
                <framenet/abox/fe/Manner.reserving> , <framenet/abox/fe/Purpose.reserving> , <framenet/abox/fe/Time.reserving> , <framenet/abox/fe/Client.reserving> , <framenet/abox/fe/Means.reserving> , <framenet/abox/fe/Payment.reserving> , <framenet/abox/fe/Scheduled_time.reserving> , <framenet/abox/fe/Place.reserving> , <framenet/abox/fe/Organization.reserving> , <framenet/abox/fe/Services.reserving> , <framenet/abox/fe/Booker.reserving> ;
        <framenet/tbox/hasFrameRelation>
                <framenet/abox/frame/Scheduling> ;
        <framenet/tbox/hasLexUnit>  <framenet/abox/lu/hold.v> , <framenet/abox/lu/booking.n> , <framenet/abox/lu/reservation.n> , <framenet/abox/lu/reserve.v> , <framenet/abox/lu/book.v> ;
        <framenet/tbox/inheritsFrom>  <framenet/abox/frame/Scheduling> .
