• Facets (new session)
• Description
• Metadata
• Settings
  • Rule: ActivityStreamsMapasEquivalentb3sb3sifpdbprdf-labelfacetshttp://dbpedia.org/resource/inference/rules/dbpedia#http://dbpedia.org/resource/inference/rules/opencyc#http://dbpedia.org/resource/inference/rules/umbel#http://dbpedia.org/resource/inference/rules/yago#http://dbpedia.org/schema/property_rules#http://www.ontologyportal.org/inference/rules/SUMO#http://www.ontologyportal.org/inference/rules/WordNet#http://www.w3.org/2002/07/owl#ldpoplwebskos-transurn:det:rdf:labelvirtrdf-labelvirtrdf-urlNone
    
  • Inverse Functional Properties: Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects
  • "Same As": Disabled (fastest) Apply to subjects only Apply to objects only Apply to both subjects and objects (recommended) Apply to subjects, objects and predicates (not recommended on big datasets) Apply to predicates only (special use cases only)

About: Operational Requirement     Goto   Sponge   NotDistinct   Permalink

An Entity of Type : dbo:Book, within Data Space : dbpedia.demo.openlinksw.com associated with source document(s)

Type: book New Facet based on Instances of this Class

An Operational Requirement, commonly abbreviated OR, was a United Kingdom (UK) Air Ministry document setting out the required characteristics for a future (i.e., as-yet unbuilt) military aircraft or weapon system. The numbered OR would describe what intended role the aircraft would be used for, e.g., bomber, fighter, etc., or what type of weapon was required, e.g., gun, armament, bomb type, etc. In conjunction with any official specification, prospective manufacturers would then choose whether to design an aircraft or weapon for this particular requirement.