final project kh

8/8/2019 Final Project Kh

http://slidepdf.com/reader/full/final-project-kh 1/17

Teams Members:

Introduction:

Todays telecommunications industry is facing many challenges. After many

years of high growth and profit the last few years has seen rapidly falling prices and

increasingly intense competition. With the advent of new technologies and recent

changes in regulations and economies, telecommunications services have grown

rabidly. Telecommunication provides a range of possibilities to perform activities at a

distance, including shopping, education, and working. Telecommuting is often

defined as arrangement for a salaried worker to work from home or at a telework

centre with remote supervision.

In this project describes a taxonomy, which uses common terms and concepts toclassify the services and features available in telecommunications systems.

Topics include: Communications Feature, Radio And Television Communications

Combined Systems, Radio Broadcasting , Television Broadcasting ,Telephone And

Telegraph, Wired Telecommunications Carriers, Communications System ,

Communication Device ,Broadcast Facility, Telephone Telegraph Facility , Wireless

Paging Systems, Transmission Station, Microwave Repeater Station Mobile



Communication Station, Wireless Station Or Transmitter ,Telegraph Station Or

Transmitter , Telegraph Message Center, Telegraph Office , and others.

Objectives:

The intention of this project is to apply some semantic web techniques,

especially the XML-based Taxonomy on Communications sector.

In this Taxonomy has been described the classification Communications to help in

GIS researches. Allowing users to understand the context of each label or term as

they navigate through.

Our research will be based on building taxonomy to provide object-naming

consistence for future cartographic, geographic information science, and modeling

and simulation production endeavors.

This ontology is a compendium of feature classes and concepts of object within the

visual domain. The objects described in this ontology are of interest to geographers,

cartographers, geographic information science (GISci)practitioners, geospatial

modeling and simulation engineers, and cognitive scientists.

Taxonomy helps us do things our would like to do:

y Searching via taxonomy may involve navigating the hierarchy, or could take

place by searching for a specific term within the hierarchy.

y It can reduce learning times as user foe telecommunication you want to know

more features about it. Common structure in different areas, making it easier

for them to be more flexible.

Project Schedule:

1- Choose an appropriate Topic to be taken up

2- Collect adequate and sufficient information and references

3- Define the basic classes and subclasses



4- Define appropriate tools to be applied to our topic

5- Explain how to apply these tools.

6- Design the classes using XML ,RDF ,OWL

Table of classes

Sub sub ClassSub ClassClass

RadioBroadcastingCommunicationsFeature

TelevisionBroadcasting

TelephoneAndTelegraph

WiredTelecommunicationsCarriers

WirelessTelecommunicationsCarriers

ExceptSatellite

CommunicationsSystem

CommunicationDevice

Broadcast StationBroadcastFacility

RadioBroadcastingFacility

TelevisionBroadcastingFacility

TelephoneTelegraphFacility

SatelliteTelecommunicationsFacility

OtherCommunicationsNEC

TelecommunicationsSiteFacilityOrCen

ter

TelecommunicationsSwitchingAndCon

trolCenter

Wireless Paging Systems



TelegraphCommunicationsFacility

TelecommunicationsSwitchingAndCon

trolCenter

SwitchingAndControlCenterMultipurp

oseExchanges

CommunicationsSiteCommunicationTransmissionFacilities

AndTower

CommunicationCente

r

RadioOrTelevisionFaci

lity

RadioAndTelevisionBroadcastingStudi

oCombinedSystem

RadioAndTelevisionBroadcastingStudi

oCombinedSystem

RadioTransmittingStationsAndTowers

TelevisionTransmittingStationsAndTo

wers

Relay Communications StationCommunicationsStation

MicrowaveCommunicationStation

LineOfSightRadioRelayStation

PointToPointRadioCommunicationsSt

ation

RadioStatio

FMRadioStationAMorFMRadioStationOrTransmitter

AMRadioStation



CellularAntennaArrayAntenna

DipoleAntennaAstron

omicalAstronomicalAntenna

HornAntennaAstrono

mical

MicrowaveAntennaAs

tronomical

MillCrossAntennaAstr

onomical



Tools:

Tools below will support telecommunication taxonomy:

1- XSL / XSLT Tools

Extensible Stylesheet Language transformation (XSLT) is a language for transforming

XML documents into other XML documents. XSLT is designed for use as part of XSL,

which is a stylesheet language for XML. Stylus Studio® includes many powerful and

intuitive XSLT tools for accelerating XSLT-related development tasks, such as a visual

XSLT Mapper, Editor, Debugger and Profiler, and includes support for both XSLT 1.0

and XSLT 2.0.

We use XSL / XSLT Tools because it offers this advantages

Advantage:

y In addition to support for XSLT , the XSLT editor includes full support

for the important new XSLT and XPath specifications, which are both

used in XSLT development.

y The XSLTof these standards represent a significant upgrade compared

to the other , extending the languages with features that increase

productivity, improve code quality and reusability, and provide

powerful new functions.

y The new features in XSLT and XPath are designed to make

development simpler, more efficient, and therefore more productive,

allowing us to produce higher-quality applications in less time.

Schema-awareness in XSLT provides additional mechanisms for error

isolation, simplified debugging, and enhanced code performance.

y XML combines its implementation of XSLT and XPath with powerful

editing and debugging features, allowing us to create the most

advanced stylesheets quickly and easily.



y There is free versions in the internet this is help our to implement our

project.

2- Ontology editors :

Ontology editors are applications designed to assist in the creation or manipulation

of ontologies. They often express ontologies in one of many ontology languages.

Some provide export to other ontology languages however.

Among the most relevant criteria for choosing an ontology editor are the degree to

which the editor abstracts from the actual ontology representation language used

for persistence and the visual navigation possibilities within the knowledge model.

Next come built-in inference engines and information extraction facilities, and the

support of upper ontologies such as OWL-S, Dublin Core, etc. Another important

feature is the ability to import & export foreign knowledge representation languages

for ontology matching

Due to this attractive features, we use ontologies are now for

knowledge sharing in a distributed environment, in our project

3- protégé

Protégé is a free, open-source platform that provides a growing user community

with a suite of tools to construct domain models and knowledge-based applications

with ontologies. At its core, Protégé implements a rich set of knowledge-modeling

structures and actions that support the creation, visualization, and manipulation of

ontologies in various representation formats. Protégé can be customized to provide

domain-friendly support for creating knowledge models and entering data. Further,

Protégé can be extended by way of a plug-in architecture and a Java-based

Application Programming Interface (API) for building knowledge-based tools and

applications.



An ontology describes the concepts and relationships that are important in a

particular domain, providing a vocabulary for that domain as well as a computerized

specification of the meaning of terms used in the vocabulary. Ontologies range from

taxonomies and classifications, database schemas, to fully axiomatized theories. In

recent years, ontologies have been adopted in many business and scientific

communities as a way to share, reuse and process domain knowledge. Ontologies

are now central to many applications such as scientific knowledge portals,

information management and integration systems, electronic commerce, and

semantic web services. The Protégé platform supports two main ways of modeling

ontologies:

y The Protégé-Frames editor enables users to build and populate ontologies

that are frame-based , in accordance with the Open Knowledge Base Connectivity

protocol (OKBC). In this model, an ontology consists of a set of classes organized in

a subsumption hierarchy to represent a domain's salient concepts, a set of slots

associated to classes to describe their properties and relationships, and a set of

instances of those classes - individual exemplars of the concepts that hold specific

values for their properties.

y The Protégé-OWL editor enables users to build ontologies for the Semantic

Web, in particular in the W3C's Web Ontology Language (OWL). "An OWL ontology

may include descriptions of classes, properties and their instances. Given such an

ontology, the OWL formal semantics specifies how to derive its logical

consequences, i.e. facts not literally present in the ontology, but entailed by the

semantics. These entailments may be based on a single document or multiple

distributed documents that have been combined using defined OWL mechanisms".



4- OO jDREW

Rule Responder is an intelligent multi-agent system for collaborative teams and

virtual communities that uses RuleML as its rule interchange format. The system

allows these virtual organizations to collaborate

in an effective semi-automatic manner, and is implemented as a Web-based

application on top of the Enterprise Service Bus Mule. It supports rule execution

environments (rule/inference engines) such as the Prova distributed Semantic Web

rule engine and OO jDREW (Object Oriented java Deductive Reasoning Engine for the

Web). The paper describes the role of OO jDREW for answering queries against rule

bases in the Naf Hornlog RuleML sublanguage for the real-world use case of asymposium organization.

Rule Responder can be used to implement a wide range of use cases that require an

intelligent, semi-automated decision layer (e.g. to collect data, infer new knowledge,

answer queries, and solve problems). The middleware of Rule Responder allows

deployment of multiple running use cases concurrently. The ESB provides the

communication backbone to synchronously or asynchronously interchange messages

between multiple agents. RuleML is a descriptive rule interchange language that can

implement all logical structures that are necessary for Rule Responder.

jDREW is an easily configured, powerful deductive reasoning engine for clausal first

order logic (facts and rules) written in Java and well integrated with the Web.

Knowledge-based systems to process the declarative information and rules can use

jDREW as an embedded reasoning engine through its various application

programmer's interfaces (APIs). jDREW can be easily deployed as part of a larger

Java system, on a server or, with its small memory footprint, on a client.

jDREW was designed to be flexible also in its capabilities; It currently provides

modules to process rules in Prolog and RuleML format.



5- Microsoft XML tools :

Microsoft XML tools in Stylus Studio® 2010 XML is powerful for telecommunication

taxonomy because they provide a powerful and intuitive means for building XML-

enabled applications based on Microsoft XML technologies.

6- Rule ML

The goal of the Rule Markup Initiative is to develop RuleML as the canonical Web

language for rules using XML markup, formal semantics, and efficient

implementations.

RuleML covers the entire rule spectrum, from derivation rules to transformation

rules to reaction rules. RuleML can thus specify queries and inferences in Web

ontologies, mappings between Web ontologies, and dynamic Web behaviours of

workflows, services, and agents.

Rule Mark-up Initiative is to develop RuleML as the canonical Web language for

rules using XML mark-up, formal semantics, and efficient implementations.

Object-Orientation in OO RuleML currently comprises object-centered user level

roles, object identifiers for URI-grounded clauses, and class hierarchies over

order-sorted terms. While these OO sublanguages can be used as three independent

extensions to RuleML 0.8, they can also be modularly combined, pairwiseor all in

one. A fourth conceivable OO sublanguage consists of signature declarations

possibly roled, grounded, and/or sorted and their instantiation to new clauses

(normally facts). However, the latter would cross the borderline between declarativeKR, currently focused in RuleML, and procedural KR; this borderline has already been

touched with URI-grounded clauses



We use RuleML Tools because it this reasons:

Markup standards and initiatives related to RuleML include :

y Mathematical Markup Language (MathML): However, MathML's Content

Markup is better suited for defining functions rather than relations or

general rules

y DARPA Agent Markup Language (DAML): While the contributing SHOE

project has permitted Horn rules and a DAML-RULES is planned, the current

DAML+OIL (March 2001) does not yet include a specification of explicit

inference rules

y

Predictive Model Markup Language (PMML): With this XML-based language

one can define and share various models for data-mining results, including

association rules

y Attribute Grammars in XML (AG-markup): For AG's semantic rules, there

are various possible XML markups that are similar to Horn-rule markup

y Extensible Stylesheet Language Transformations (XSLT): This is a restricted

term-rewriting system of rules, written in XML, for transforming XML

documents into other XML documentsRules are being used for many interconnected purposes, capturing regularities in

application domains such as the following :

y Engineering: Diagnosis rules (also model-based approaches appreciate and

combine with rules, as described by Adnan Darwiche in Model-based

diagnosis under real-world constraints, AI Magazine, Summer 2000

y Commerce: Business rules (including XML versions such as the Business

Rules Markup Language (BRML) of IBM's Business Rules for Electronic

Commerce project

y Law: Legal reasoning (Robert Kowalski and Marek Sergot have been

formalizing legal rules in an Imperial College group )

y Internet: Access authentication (Tim Berners-Lee proposed registration

engines that use authentication rules such as the following: Any person



who was some time in the last 2 months an employee of an organization

which was some time in the last 2 months a W3C member may register)

Q uestions:

What problem area does the tool address?

We mentioned it in introduction and objectives

Exactly what does the tools do?

1- XSL / XSLT Tools:

Includes many powerful and intuitive XSLT tools for accelerating XSLT-related

development tasks, such as a visual XSLT Mapper, Editor, Debugger and

Profiler, and includes support for both XSLT 1.0 and XSLT 2.0.

2- Ontology editors :

Creation or manipulation of ontologies. Another important feature is the

ability to import & export foreign knowledge representation languages forontology matching.

3- Protégé:

Protégé is a free. Protégé implements a rich set of knowledge-modeling

structures and actions that support the creation, visualization, and manipulation

of ontologies in various representation formats.

4- OO jDREW:

Implement a wide range of use cases that require an intelligent, semi-automated

decision layer. Can be easily deployed as part of a larger Java system, on a server

or, with its small memory footprint, on a client.



5- Rule ML:

Specify queries and inferences in Web ontologies, mappings between Web

ontologies, and dynamic Web behaviours of workflows, services, and agents.

What are the characteristics of an ideal solution to problems in this area?

We solve the problem by building taxonomy to help geographers, cartographers,

geographic information science (GISci) practitioners, geospatial modeling and

simulation engineers, and cognitive scientists

To understand and to provide object-naming consistence for future cartographic,

geographic information science, and modeling and simulation production endeavors.

Does the tool offer an effective solution to such problems? Why? Did the tool help

you solve your chosen problem/task?

Yes, these tools offer best solution to solve and improve information in

Communication sector. For many reasons like:

Markup standards and initiatives related to RuleML include :

y Mathematical Markup Language (MathML): However, MathML's Content

Markup is better suited for defining functions rather than relations or

general rules

y DARPA Agent Markup Language (DAML): While the contributing SHOE

project has permitted Horn rules and a DAML-RULES is planned, the current

DAML+OIL (March 2001) does not yet include a specification of explicit

inference rules

y Predictive Model Markup Language (PMML): With this XML-based language

one can define and share various models for data-mining results, including

association rules

y Attribute Grammars in XML (AG-markup): For AG's semantic rules, there

are various possible XML markups that are similar to Horn-rule markup



y Extensible Stylesheet Language Transformations (XSLT): This is a restricted

term-rewriting system of rules, written in XML, for transforming XML

documents into other XML documents.

Also We use XSL / XSLT Tools because it offers this advantages :

y In addition to support for XSLT , the XSLT editor includes full support

for the important new XSLT and XPath specifications, which are both

used in XSLT development.

y The XSLTof these standards represent a significant upgrade compared

to the other , extending the languages with features that increase

productivity, improve code quality and reusability, and provide

powerful new functions.

y The new features in XSLT and XPath are designed to make

development simpler, more efficient, and therefore more productive,

allowing us to produce higher-quality applications in less time.

Schema-awareness in XSLT provides additional mechanisms for error

isolation, simplified debugging, and enhanced code performance.

y XML combines its implementation of XSLT and XPath with powerful

editing and debugging features, allowing us to create the most

advanced stylesheets quickly and easily.

y There is free versions in the internet this is help our to implement our

project.

What other tools might have applied?

Protégé.



Visual Objects Taxonomy (VOT) for telecommunication:

This ontology is a compendium of feature classes and concepts of object within the visual

domain. The objects described in this ontology are of interest to geographers, cartographers,

geographic information science (GISci) practitioners, geospatial modeling and simulation

engineers, and cognitive scientists those objects that we see when we look out a picture

window; or objects we see when we look out an aircraft window; even those objects that we

see when we view any urban setting. The intent of this data structure is to provide object-

naming consistence for future cartographic, geographic information science, and modeling

and simulation production endeavors.

Visual Objects Taxonomy (VOT) Communications Features:

An initial installment of ontology of visible object on the Communications derived from the

Visual Objects Taxonomy (VOT) developed at the University of West Florida. This release

contains telecommunications and communications associated object definitions

Sample code implemented for classes telecommunication:

<?xml version="1.0" encoding="UTF-8"?><rdf:RDF xmlns:vissim="http://vissim.uwf.edu/VOT_Ontology/#" xml:base="http://vissim.uwf.edu/VOT_Ontology/#"xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:owl="http://www.w3.org/2002/07/owl#"

xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:dc="http://purl.org/dc/elements/1.1/"xmlns:edcs="http://www.sedris.org/sdk_4.0/src/lib/edcs/facc2p1_to_edcs4p0/docs/facc2p1_edcs4p0.htm#Data_Structures#"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xsi:noNamespaceSchemaLocation="C:\A_bitters\AA_Nima_Nuri\OWL_Export\VOT_OWL.xsd"><owl:Class rdf:ID="CommunicationsFeature"><rdfs:label xml:lang="en">Communications Feature</rdfs:label>

<vissim:VOT_ID>7000000</vissim:VOT_ID><vissim:REFERENCES>VOTT</vissim:REFERENCES></owl:Class>

<owl:Class rdf:ID="RadioBroadcasting"><rdfs:label xml:lang="en">Radio Broadcasting</rdfs:label>

<vissim:VOT_ID>7000002</vissim:VOT_ID><rdfs:subClassOf>

<vissim:VOT_BT>CommunicationsFeature<vissim:VOT_SC>7000000</vissim:VOT_SC>

</vissim:VOT_BT>

</rdfs:subClassOf></owl:Class>

<owl:Class rdf:ID="TelevisionBroadcasting">

<rdfs:label xml:lang="en">Television Broadcasting</rdfs:label><vissim:VOT_ID>7000003</vissim:VOT_ID><rdfs:subClassOf>


</vissim:VOT_BT>

</rdfs:subClassOf>

</owl:Class><owl:Class rdf:ID="TelephoneAndTelegraph">

<rdfs:label xml:lang="en">Telephone And Telegraph</rdfs:label><vissim:VOT_ID>7000004</vissim:VOT_ID><rdfs:subClassOf>


</vissim:VOT_BT>

</rdfs:subClassOf>

</owl:Class><owl:Class rdf:ID="WiredTelecommunicationsCarriers">

<rdfs:label xml:lang="en">Wired Telecommunications Carriers</rdfs:label><vissim:VOT_ID>7000005</vissim:VOT_ID><rdfs:subClassOf>




</vissim:VOT_BT></rdfs:subClassOf>

</owl:Class>

<owl:Class rdf:ID="WirelessTelecommunicationsCarriersExceptSatellite"><rdfs:label xml:lang="en">Wireless Telecommunications Carriers Except Satellite</rdfs:label>

<vissim:VOT_ID>7000006</vissim:VOT_ID>

<rdfs:subClassOf><vissim:VOT_BT>CommunicationsFeature

<vissim:VOT_SC>7000000</vissim:VOT_SC>


</owl:Class>

<owl:Class rdf:ID="CommunicationsSystem">

<rdfs:label xml:lang="en">Communications System</rdfs:label><vissim:VOT_ID>7000020</vissim:VOT_ID>

<rdfs:subClassOf><vissim:VOT_BT>CommunicationsFeature



</owl:Class>

<owl:Class rdf:ID="CommunicationDevice"><rdfs:label xml:lang="en">Communication Device</rdfs:label>



</vissim:VOT_BT>


<owl:Class rdf:ID="BroadcastFacility"><rdfs:label xml:lang="en">Broadcast Facility</rdfs:label><vissim:VOT_ID>7000200</vissim:VOT_ID>

</owl:Class><owl:Class rdf:ID="BroadcastStation">

<rdfs:label xml:lang="en">Broadcast Station</rdfs:label>


<vissim:VOT_BT>BroadcastFacility

<vissim:VOT_SC>7000200</vissim:VOT_SC></vissim:VOT_BT>

</rdfs:subClassOf>

</owl:Class>

<owl:Class rdf:ID="RadioBroadcastingFacility"><rdfs:label xml:lang="en">Radio Broadcasting Facility</rdfs:label>


<vissim:VOT_BT>BroadcastFacility

<vissim:VOT_SC>7000200</vissim:VOT_SC></vissim:VOT_BT>

</rdfs:subClassOf>

</owl:Class>

<owl:Class rdf:ID="TelevisionBroadcastingFacility"><rdfs:label xml:lang="en">Television Broadcasting Facility</rdfs:label><vissim:VOT_ID>7000212</vissim:VOT_ID>

<rdfs:subClassOf>

<vissim:VOT_BT>BroadcastFacility<vissim:VOT_SC>7000200</vissim:VOT_SC>

</vissim:VOT_BT>


<owl:Class rdf:ID="TelephoneTelegraphFacility"><rdfs:label xml:lang="en">Telephone and Telegraph Facility</rdfs:label><vissim:VOT_ID>7000213</vissim:VOT_ID>

<rdfs:subClassOf><vissim:VOT_BT>BroadcastFacility





Reference:

y http://articles.techrepublic.com.com/5100-10878_11-5054221.html

y http://www.konsult.leeds.ac.uk/private/level2/instruments/instru

ment021/l2 _021a.htm

y http://www.sciencedirect.com/science?_ob=ArticleURL&_udi=B6VC

C466GN7412&_user=10&_coverDate=06%2F30%2F1986&_rdoc=1&

_fmt=high&_orig=search&_sort=d&_docanchor=&view=c&_searchS

trId=1359793801&_rerunOrigin=google&_acct=C000050221&_versi

on=1&_urlVersion=0&_userid=10&md5=0b1aa67b2d6c765a1c7a2f7

a8a324

bf0 y http://www.taxonomywarehouse.com/ordersubmit_include.asp

y http://www.stylusstudio.com/xslt.html

y http://www.wdvl.com/Authoring/Languages/XSL/

y http://www.antennahouse.com/product/designer/

y http://wiki.eclipse.org/XSLT_Project

final project kh

Documents