[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [regrep-semantic] Revisions for Use Case feedback Document - no call tuesday 29th
Dear Colleagues,
I would like to participate to your teleconferences
particularly for the work on making ebXML registries OWL aware.
However, toll free numbers are not accesible outside US. I
would like to propose an Internet based teleconferencing tool and Skype
from www.skype.com seems an efficient one.
Thank you,
Asuman Dogac
> The attached document contains the changes supplied by Evan W & David W.
>
> In addition to editing the introduction statement (to provide a cohesive
> overview) I propose that the following tasks be performed :
>
>
> - An additional use case be added that describes how 'Core Components' are
> used for semantic mapping. This use case will be based on the CC work I
> am doing for the e-gov / registry project.
>
> - all use cases be reviewed / extended so that it is synchronized with the
> contents of the DAPD document (posted recently). This will primarily be
> performed by Prof Asuman Dogac's team.
>
>
> Given the critical nature of the task - I hope these changes can be
> applied before the conference call scheduled for July 13. .. AND ...
>
> Since I will be in a workshop for 3 days next week I propose that we
> CANCEL next weeks call and use email discussions to agree to placing a
> freeze on new use cases after JULY 12.
>
>
>
> --
> Carl Mattocks
>
> co-Chair OASIS (ISO/TS 15000) ebXMLRegistry Semantic Content SC
> co-Chair OASIS Business Centric Methodology TC
> CEO CHECKMi
> v/f (usa) 908 322 8715
> www.CHECKMi.com
> Semantically Smart Compendiums
> (AOL) IM CarlCHECKMi
> ------=_20040624154654_51631
> Content-Type: text/richtext; name="usacasedocv3.rtf"
> Content-Transfer-Encoding: 8bit
> Content-Disposition: attachment; filename="usacasedocv3.rtf"
>
> {\rtf1\ansi\ansicpg1252\uc1 \deff0\deflang1033\deflangfe1033{\fonttbl{\f0\froman\fcharset0\fprq2{\*\panose 02020603050405020304}Times New Roman;}{\f15\fswiss\fcharset0\fprq2{\*\panose 020b0604030504040204}Tahoma;}
> {\f123\froman\fcharset238\fprq2 Times New Roman CE;}{\f124\froman\fcharset204\fprq2 Times New Roman Cyr;}{\f126\froman\fcharset161\fprq2 Times New Roman Greek;}{\f127\froman\fcharset162\fprq2 Times New Roman Tur;}
> {\f128\froman\fcharset186\fprq2 Times New Roman Baltic;}{\f213\fswiss\fcharset238\fprq2 Tahoma CE;}{\f214\fswiss\fcharset204\fprq2 Tahoma Cyr;}{\f216\fswiss\fcharset161\fprq2 Tahoma Greek;}{\f217\fswiss\fcharset162\fprq2 Tahoma Tur;}
> {\f218\fswiss\fcharset186\fprq2 Tahoma Baltic;}}{\colortbl;\red0\green0\blue0;\red0\green0\blue255;\red0\green255\blue255;\red0\green255\blue0;\red255\green0\blue255;\red255\green0\blue0;\red255\green255\blue0;\red255\green255\blue255;
> \red0\green0\blue128;\red0\green128\blue128;\red0\green128\blue0;\red128\green0\blue128;\red128\green0\blue0;\red128\green128\blue0;\red128\green128\blue128;\red192\green192\blue192;}{\stylesheet{\widctlpar\adjustright \fs20\cgrid \snext0 Normal;}{
> \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid \sbasedon0 \snext0 heading 1;}{\*\cs10 \additive Default Paragraph Font;}{\s15\qc\widctlpar\adjustright \b\cgrid \sbasedon0 \snext15 Title;}{\s16\widctlpar\adjustright \f15\fs16\cgrid
> \sbasedon0 \snext16 Balloon Text;}}{\*\listtable{\list\listtemplateid1648025960\listsimple{\listlevel\levelnfc0\leveljc0\levelfollow0\levelstartat1\levelspace0\levelindent0{\leveltext\'03(\'00);}{\levelnumbers\'02;}\fbias0 \fi-360\li360\jclisttab\tx360 }
> {\listname ;}\listid1736200401}}{\*\listoverridetable{\listoverride\listid1736200401\listoverridecount0\ls1}}{\*\revtbl {Unknown;}{ewallace;}}{\info{\title ebXMLRegistry Semantic Content Management SC}{\author CarlM}{\operator CarlM}{\creatim\yr2004\mo5\dy25\hr11\min18}
> {\revtim\yr2004\mo6\dy24\hr15\min23}{\printim\yr2004\mo5\dy25\hr10\min30}{\version11}{\edmins414}{\nofpages12}{\nofwords2986}{\nofchars17024}{\*\company www.CHECKMi.com}{\nofcharsws20906}{\vern113}}
> \widowctrl\ftnbj\aenddoc\noxlattoyen\expshrtn\noultrlspc\dntblnsbdb\nospaceforul\hyphcaps0\formshade\viewkind1\viewscale100\pgbrdrhead\pgbrdrfoot \fet0\sectd \linex0\endnhere\sectdefaultcl {\*\pnseclvl1\pnucrm\pnstart1\pnindent720\pnhang{\pntxta .}}
> {\*\pnseclvl2\pnucltr\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl3\pndec\pnstart1\pnindent720\pnhang{\pntxta .}}{\*\pnseclvl4\pnlcltr\pnstart1\pnindent720\pnhang{\pntxta )}}{\*\pnseclvl5\pndec\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}
> {\*\pnseclvl6\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl7\pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl8\pnlcltr\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}{\*\pnseclvl9
> \pnlcrm\pnstart1\pnindent720\pnhang{\pntxtb (}{\pntxta )}}\pard\plain \s15\qc\widctlpar\adjustright \b\cgrid {Use Cases : ebXMLRegistry Semantic Content Management SC
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {
> \par }\pard \qc\widctlpar\adjustright {\i ebXML Registry will become for the semantic web what web servers are to the web today
> \par
> \par
> \par
> \par
> \par }\pard \widctlpar\adjustright {
> \par }\pard\plain \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid {Introduction
> \par }{\b0
> Reviewers are invited to comment on the Use Cases produced by the members of OASIS ebXMLRegistry Semantic Content Management SC . Comments regarding flaws in logic, missing functionality and mis-appropriated concepts are most welcome. Feedback will be u
> sed to create a specification for Registering and Storing semantic content in the ebXMLRegistry.\page }{1 Use Case : eBusiness Industry Dictionary: nouns
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {Priority (L/M/H) : High
> \par
> \par Description :\~
> \par }{Organizations such as Open Applications Group (OAGi), RosettaNet, and the UDEF and STEP communities along with eGov initiatives such as Integrated Justice Information, European EPR (Electronic PRocess)
> , as well as others in the UK Ministry of Defence, and US Department of Justice require interoperable semantics of noun definitions for their industry domains. OASIS Technical Committees such as the Customer Information Quality TC need the
> means to document their noun semantics in Registry.
> \par
> \par To date the Registry provides Classifications, Taxonomies, the ebXML Registry I
> nformation Model (RIM) and logical models such as Core Components Technical Specification (CCTS) but no means to capture consistent semantics around the physical noun details. W3C XSD schema provides some small limited subset of this - datatype, use, anno
> tation, tokenized values, but much more is required, and especially the ability to support context driven semantics, language localization and consistent versioning.
> \par
> \par Coupled to this is the ability to support assembly of eBusiness transaction documents from the noun dictionary both as models (CCTS) and physical transactions through the Content Assembly Mechanism
> (CAM). The ability to link in Web Ontology Language (OWL) descriptions and Topic Maps to further add semantics to the nouns should be part of the design considerations, with the aim to enhance the physical noun collections for discovery and re-use.
> \par
> \par Support for Nouns and associated semantic content in ebXML repositories will allow implementers to have a consistent
> set of nouns across industry domains and provide the building block for adopters to rapidly implement ebXML Registry based dictionaries from their existing manually managed dictionary content.
> \par
> \par The noun details will be defined as an XML instance structure (XSD) for storing the individual noun semantics into the registry. Multi-lingual locale support is required in this structure along with an extensible facet support
> \par }{
> \par }{Actors :
> \par business information analyst
> \par Pre-Conditions: ability to associate to taxonomies or richer semantic content already in registry
> \par Post-Conditions: none
> \par Basic Flow :
> \par analyst #1 publishes a semantic noun as XML to registry
> \par analyst #1 assigns classification and taxonomy to noun entry
> \par analyst #2 queries and retrieves noun based on industry search criteria
> \par analyst #2 uses browse and drill down to locate specific noun meeting industry criteria
> \par Alternate Flow :
> \par machine process retrieves semantic noun details as XML
> \par referencing is done via direct external key value look up and using http-binding interface
> \par machine process scans registry for matching industry nouns and produces catalogue of same as human readable report
> \par Exceptions : none
> \par Includes Use Cases: None
> \par Special Requirements: None
> \par Assumptions:
> \par Industry analyst creates dictionary content using domain expertise.
> \par Noun details may be spread across multiple registries that may or may not be federated
> \par Use Case Relationships:
> \par None
> \par Issues :
> \par none
> \par }{
> \par
> \par }{\b \page 2 Use Case : eBusiness Industry Dictionary: BP catalogue
> \par }{Priority (L/M/H) : High
> \par
> \par Description :\~
> \par }{The ebXML architecture calls for a registry of re-usable business process definitions that can be used to configure eBusiness interactions dynamically with software.
> \par
> \par Industry groups such as OAGi, and RosettaNet have developed dictionaries using a variety of tools such as HTML and spreadsheets to manage their own sets of business processes (BODs, PIPs, etc) in a manual way.
> \par
> \par Today ebXML has available Collaborative Process Agreements (CPA) with Business Process Specification Schema (BPSS) and associated transaction handling instructions such as CAM template scripts to provide the physical implementation.
> \par
> \par By defining semantics for BP catalogue entries in Registry we can provide a consistent way to package a BP definition, including all the necessary components (CPA, BPSS, Transactions, XSD,
> Context use rules) so that industry groups can quickly build re-usable dictionaries of BP catalogues. BP semantics will be captured in ebXML registries either using currently supported classification mechanisms or through enhancements
> to the registry supporting languages such as Topic Maps, OWL or some other formalism. These languages support machine reasoning which can enhance re-use and discovery of registry content such as BP entries
> . A further goal is so that application implementers can reliably download and install BP catalogue definitions into their systems to configure them and provide directives for the runtime systems
> \par }{
> \par }{Actors :
> \par business process analyst
> \par
> \par Pre-Conditions: BP structure and semantics already described in registry content.
> \par Post-Conditions: none
> \par Basic Flow :
> \par analyst #1 assembles a collection of BP components, such as CPA, BPSS, business transaction definitions, and context mechanism details and publishes as a semantic object in XML to registry
> \par analyst #1 assigns classification and taxonomy to BP catalogue entry
> \par analyst #2 queries and retrieves BP catalogue entry based on industry search criteria
> \par analyst #2 uses browse and drill down to locate specific BP catalogue item meeting industry criteria
> \par Alternate Flow :
> \par machine process retrieves semantic details of BP catalogue entry as XML and then automatically configures ebXML components accordingly (CPA - directs ebMS, BPSS - directs BP engine, et al).
> \par machine process queries and/or scans registry for matching industry BP catalogue entries and produces catalogue of same as human readable report.
> \par
> \par Exceptions : none
> \par Includes Use Cases: None
> \par Special Requirements: None
> \par Assumptions:
> \par Industry analyst creates BP catalogue content using domain expertise.
> \par BP catalogue details and associated objects (CPA, BPSS, XSD, context configuration) may be spread across multiple registries that may or may not be federated
> \par Use Case Relationships:
> \par None
> \par Issues :
> \par none
> \par Examples:
> \par }{
> \par
> \par
> \par
> \par }\pard\plain \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid {3 Use Case : Collaborative ontology development
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {Priority (L/M/H) : High
> \par
> \par Description :\~
> \par Ontologies often need to be developed collaboratively by a group of geographically dispersed Domain Experts within a certain domain.}{\revised\revauth1\revdttm1183173551 }{\deleted\revauthdel1\revdttmdel1183173551
> \par }{Each Domain Experts builds }{\deleted\revauthdel1\revdttmdel1183173730 a }{different sub-graphs (networks) of }{\deleted\revauthdel1\revdttmdel1183173732 the }{\revised\revauth1\revdttm1183173732 an }{
> ontology. Each Domain Expert may review the ontology sub-graphs}{\revised\revauth1\revdttm1183173551 }{\deleted\revauthdel1\revdttmdel1183173551
> \par }{produced by others. Each Domain Expert may edit ontology sub-graphs that they or another Domain Expert created with appropriate access control.
> \par
> \par Actors :
> \par Domain Expert
> \par
> \par Pre-Conditions:
> \par none
> \par Post-Conditions:
> \par none
> \par Basic Flow :
> \par Domain expert #1 publishes an ontology sub-graph
> \par Domain expert #2 publishes another ontology sub-graph and connects it to first sub-graph
> \par Domain expert #1 and #2 review each others sub-graphs
> \par Domain expert #1 and #2 edits sub-graphs to address comments or fix errors
> \par Alternate Flow :
> \par none
> \par Exceptions :
> \par none
> \par Includes Use Cases:
> \par None
> \par Special Requirements:
> \par None
> \par Assumptions:
> \par Proper }{\revised\revauth1\revdttm1183173552 configuration management and }{access control policies are defined for coll}{\revised\revauth1\revdttm1183173552 a}{boration on shared ontology content}{\revised\revauth1\revdttm1183173552 .}{
> \par Inter-connected ontology sub-graphs may be spread across multiple registries that may or may not be federated
> \par
> \par Use Case Relationships:
> \par None
> \par Issues :
> \par none
> \par Examples:
> \par
> \par
> \par
> \par
> \par
> \par
> \par }{\b \page 4 Use Case : Classify content using Ontology class
> \par Priority (L/M/H) : High
> \par }{
> \par Description :\~
> \par Currently ebXML Registry allows content to be classified using a ClassificationNode within a ClassificationScheme.}{\revised\revauth1\revdttm1183173553 }{\deleted\revauthdel1\revdttmdel1183173553
> \par }{This use case envisions allowing content to be classified using a}{\revised\revauth1\revdttm1183173632 class}{\deleted\revauthdel1\revdttmdel1183173632 }{\deleted\revauthdel1\revdttmdel1183173563 Class }{\revised\revauth1\revdttm1183173563 }{
> within an Ontology.}{\revised\revauth1\revdttm1183173553 }{\deleted\revauthdel1\revdttmdel1183173553
> \par }{The resulting classification would carry much clearer semantic content.}{\revised\revauth1\revdttm1183173577 }{\revised\revauth1\revdttm1183173568
> \par }\pard \widctlpar
> \widctlpar\pnrauth1\pnrdate1183173568\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {\revised\revauth1\revdttm1183173568
> \par }{\revised\revauth1\revdttm1183173576 RIM s}{\revised\revauth1\revdttm1183173568 upport for ontologies brings rich and precise semantic content to ebXML registries. A}{\revised\revauth1\revdttm1183173573 dding the }{\revised\revauth1\revdttm1183173568
> ability for binding non-semantic registry entries to elements of these ontologies infers }{\revised\revauth1\revdttm1183173574 semantics }{\revised\revauth1\revdttm1183173568 to this content}{\revised\revauth1\revdttm1183173574 . Th}{
> \revised\revauth1\revdttm1183173576 ese}{\revised\revauth1\revdttm1183173574 semantics}{\revised\revauth1\revdttm1183173568 can }{\revised\revauth1\revdttm1183173576 then }{\revised\revauth1\revdttm1183173568 be exploited }{
> \revised\revauth1\revdttm1183173571 for automated support of a number of content analysis tasks}{\revised\revauth1\revdttm1183173576 ,}{\revised\revauth1\revdttm1183173574 including:}{\revised\revauth1\revdttm1183173571 classification, consistency c
> hecking and schema and instance comparison.}{\revised\revauth1\revdttm1183173568 }{
> \par }\pard \widctlpar\adjustright {
> \par See attached use case diagram.
> \par
> \par Actors :
> \par Domain Expert , Registry
> \par Pre-Conditions:
> \par Ontology must already be defined or be submitted along with the content being classified
> \par Post-Conditions:
> \par none
> \par Basic Flow :
> \par Domain experts publishes an ontology
> \par Content Publisher publishes content
> \par Content Publisher classified content using an ontology class reference within a Classification
> \par
> \par Alternate Flow :
> \par none
> \par Exceptions :
> \par none
> \par Includes Use Cases:
> \par None
> \par Special Requirements:
> \par None
> \par Assumptions:
> \par Domain experts publishes an ontology
> \par Content Publisher publishes content
> \par Content Publisher classified content using an ontology class reference within a Classification
> \par
> \par Use Case Relationships:
> \par }{\deleted\revauthdel1\revdttmdel1183173578 None}{\revised\revauth1\revdttm1183173578 This use case is either a component of or }{\revised\revauth1\revdttm1183173658 a }{\revised\revauth1\revdttm1183173578 precondition for most other SCM use cases.}{
>
> \par Issues :
> \par none
> \par Examples:
> \par
> \par
> \par
> \par
> \par
> \par
> \par }\pard\plain \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid {\page 5 Use Case : Associate 2 RegistryObjects using an Ontology }{\deleted\revauthdel1\revdttmdel1183173659 Class}{\revised\revauth1\revdttm1183173659 elements}{
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {Priority (L/M/H) :
> \par High
> \par Description :\~
> \par Currently ebXML Registry allows content to be associated using an Association which has an optional associationType that is defined by }{\deleted\revauthdel1\revdttmdel1183173603 }{a ClassificationNode within a ClassificationScheme.
> \par
> \par This use case envisions allowing content to be associated using an Association which has an optional associationType that is defined by }{\deleted\revauthdel1\revdttmdel1183173604 }{a }{\revised\revauth1\revdttm1183173656 pair of }{
> \deleted\revauthdel1\revdttmdel1183173655 Class }{\revised\revauth1\revdttm1183173655 Properties }{within an Ontology.
> \par \~
> \par The meaning of the resulting association would be much more clear}{\deleted\revauthdel1\revdttmdel1183173604 er}{ and precise.
> \par
> \par Actors :
> \par Domain Expert , Content Publisher , Registry
> \par Pre-Conditions:
> \par A repository populated with domain and higher level ontologies
> \par Post-Conditions:
> \par none
> \par Basic Flow :
> \par Domain experts publishes an ontology
> \par Content Publisher publishes content #1
> \par Content Publisher publishes content #2
> \par Content Publisher publishes an Association that associates content #1 and content #2 using an ontology class reference as an associationType
> \par Alternate Flow :
> \par none
> \par Exceptions :
> \par none
> \par Includes Use Cases:
> \par None
> \par Special Requirements:
> \par None
> \par Assumptions:
> \par An Association class is used to associate the two content instances as is the case in version ebXML Registry 2.5
> \par Queries (different use case) may be submitted that discover associated content not only based on associationType but also specific attributes}{\deleted\revauthdel1\revdttmdel1183173662 }{ of the }{\deleted\revauthdel1\revdttmdel1183173662 ontology class
> }{\revised\revauth1\revdttm1183173662 properties}{ that }{\deleted\revauthdel1\revdttmdel1183173662 was }{\revised\revauth1\revdttm1183173662 were }{used }{\deleted\revauthdel1\revdttmdel1183173662 as }{\revised\revauth1\revdttm1183173662 to define }{
> associationType.
> \par Use Case Relationships:
> \par None
> \par Issues :
> \par none
> \par Examples:
> \par
> \par
> \par }\pard\plain \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid {\page 6 Use Case : Discover content using semantic queries
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {Priority (L/M/H) : High
> \par
> \par Description :\~
> \par Currently ebXML Registry allows content to be discovered using ad hoc queries which are based on predicates defined over attributes of RIM classes.
> \par
> \par This use case envisions allowing content to be discovered using semantic ad hoc queries which are based on predicates defined over attributes of Ontology class instances in addition to attributes of RIM classes .
> \par \~
> \par The result is that a Registry Client may now discover content by expressing their intended target using enhanced expressive power, semantic clarity and reduced ambiguity.
> \par Actors :
> \par Domain Expert , Content Publisher, Registry Client, Registry
> \par
> \par Pre-Conditions:
> \par Ontology is already be defined or be submitted along with the content being associated
> \par Content to be discovered is submitted to registry and be classified using ontology class instance(s)
> \par Post-Conditions:
> \par none
> \par Basic Flow :
> \par Registry Client discovers the ontology that fits the contenty they seek.
> \par Registry Client performs a semantic query that predicates on attributes of an ontology class
> \par Alternate Flow :
> \par none
> \par Exceptions :
> \par none
> \par Includes Use Cases:
> \par None
> \par Special Requirements:
> \par None
> \par Assumptions:
> \par Inference using ontology knowledge is supported and can aid in discovery of content that is not directly classified by the specified ontology class but may classi
> fied by a more general concept represented by an ancestor class of teh specified ontology class
> \par Use Case Relationships:
> \par None
> \par Issues :
> \par none
> \par Examples:
> \par
> \par
> \par }\pard\plain \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid {\page 7 Use Case : Extend information model with user-defined classes
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {Priority (L/M/H) : High
> \par
> \par Description :\~
> \par Currently ebXML Registry allow clients to extend Registry Information Model (RIM) only via attribute extension using Slots on existing RIM classes.
> \par New RIM classes cannot be defined.
> \par
> \par This use case envisions allowing clients to extend Registry Information Model (RIM) classes }{\deleted\revauthdel1\revdttmdel1183173688 be }{\revised\revauth1\revdttm1183173688 by }{defining new classes that may be sub-classes of existing}{
> \deleted\revauthdel1\revdttmdel1183173690 }{ RIM classes .
> \par \~
> \par The result is that verticals and enterprises may specialize ebXML RIM to meet their domain specific needs.
> \par
> \par Actors :
> \par Domain Expert , Content Publisher, Registry
> \par
> \par Pre-Conditions:
> \par none
> \par Post-Conditions:
> \par none
> \par Basic Flow :
> \par Domain expert defines extension to RIM by submitting new RIM classes to the Registry
> \par
> \par Content publisher may now submit instances of new RIM classes to the Registry
> \par Alternate Flow :
> \par none
> \par Exceptions :
> \par none
> \par Includes Use Cases:
> \par None
> \par Special Requirements:
> \par None
> \par Assumptions:
> \par It is envisioned that in order to support this use case the RIM would have to be expressed in an ontology syntax chosen by}{\deleted\revauthdel1\revdttmdel1183173689 u}{ the registry}{\revised\revauth1\revdttm1183173689 . }{
> \deleted\revauthdel1\revdttmdel1183173689
> \par }{It is likely that the Ontology syntax chosen by the registry will be OWL.
> \par Use Case Relationships:
> \par None
> \par Issues :
> \par none
> \par Examples:
> \par
> \par }\pard\plain \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid {\page 8 Use Case : Ontology search}{\revised\revauth1\revdttm1183173729 ing}{ }{\deleted\revauthdel1\revdttmdel1183173704 supporting ontology development}{
> \revised\revauth1\revdttm1183173704 and browsing}{
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {Priority (L/M/H) : High
> \par
> \par Description :\~
> \par One of the premises of the Semantic Web is that terms will be reused rather than reinvented. RDF, RDFS, and OWL support this through the ability to reference resources described outside a document as easily as those described within. They also}{
> \deleted\revauthdel1\revdttmdel1183173704 provide}{ encourage this with various constructs for descr
> ibing equivalence and other relationships between terms. But for reuse to occur, people will also need to be able to find the correct terms on which to build. This will require ontology repositories with appropriate search or query capabilities. This use
> case describes how an ontology developer might interact with such a repository to discover appropriate terms upon which to build a local ontology.
> \par Actors :
> \par Ontology developer
> \par Pre-Conditions:
> \par A repository populated with domain and higher level ontologies
> \par Post-Conditions: none
> \par Basic Flow :
> \par Ontology developer searches }{\revised\revauth1\revdttm1183173722 a }{repository for ontologies which contain classes specifically mentioned in the domain of identified property restrictions}{\revised\revauth1\revdttm1183173723 (global or local)}{.}{
> \revised\revauth1\revdttm1183173724 A}{\deleted\revauthdel1\revdttmdel1183173724 }{\deleted\revauthdel1\revdttmdel1183173723 Where }{\deleted\revauthdel1\revdttmdel1183173724 a}{ }{\revised\revauth1\revdttm1183173710 user specifies a }{set of }{
> \revised\revauth1\revdttm1183173721 matching }{property terms }{\deleted\revauthdel1\revdttmdel1183173712 is specified }{using a regular expression. Something like: return all classes where
> <class> *[m,M]ember <range>. See Examples below for OWL fragments that match this query. Repository returns a list of ontologies matching the query, probably presented with some standard metadata for each. Ontology developer chooses an ontology from the l
> ist and asks to browse that ontology. Ontology developer chooses to view the classes in the chosen ontology. Repository returns the classes with the }{\deleted\revauthdel1\revdttmdel1183173726 ones in the domain requested }{earlier }{
> \deleted\revauthdel1\revdttmdel1183173726 somehow }{\revised\revauth1\revdttm1183173726 query }{tagged as such. Ontologist requests download of entire on
> tology for more detailed examination. Ontologist refines the terms from downloaded ontology in an organization ontology he creates for his enterprise.
> \par Alternate Flow :
> \par Alt flow 1: No suitable ontology found }{\revised\revauth1\revdttm1183173726
> \par }\pard \widctlpar
> \widctlpar\pnrauth1\pnrdate1183173726\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {
> Ontologist finds no suitable general ontology, so he creates one. Ontologist uploads new reusable ontology to repository.
> \par }\pard \widctlpar\adjustright {Alt flow 2: }{\revised\revauth1\revdttm1183173742 Navigate through ontology}{\revised\revauth1\revdttm1183173740
> \par }\pard \widctlpar
> \widctlpar\pnrauth1\pnrdate1183173740\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {\deleted\revauthdel1\revdttmdel1183173742 Navigate through }{
> \deleted\revauthdel1\revdttmdel1183173741 specialized }{\deleted\revauthdel1\revdttmdel1183173742 ontology }{Query returns terms too specialized for intended use. Howe
> ver, some are subtyped from another term defined in another ontology within the repository. Ontologist requests to follow link to ontology in which the supertype is defined. Repository selects ontology for browsing and returns list of the metatype (either
> properties or classes) of terms from the ontology containing the supertype of interest.
> \par }\pard \widctlpar\adjustright {Exceptions :
> \par Alt flow 1 Ontologist does not have permission to upload to the repository.
> \par Alt flow 2 Supertype of interest is not described in the repository.
> \par Includes Use Cases: }{\deleted\revauthdel1\revdttmdel1183173734 None}{\revised\revauth1\revdttm1183173734 6 Discover content using semantic queries}{
> \par Special Requirements: None
> \par Assumptions:
> \par This scenario assumes sufficient (property and class) information grouped in a single file. It also assumes that english words will be a useful tool in identify
> ing concepts in ontology repositories. Note no subsumption reasoning is used for responses to these queries. This significantly scopes the query results, but could result in filtering the ontology desired
> \par Use Case Relationships: }{\deleted\revauthdel1\revdttmdel1183173735 None}{\revised\revauth1\revdttm1183173735 Part of 3: Collaborative ontology development}{
> \par Issues :
> \par Ontology files in the repository may not have names that help explain their content, and may not even contain an owl:Ontology keyword to help distinguish them from rdf data files.
> \par }{\revised\revauth1\revdttm1183173714 \sect }\sectd \linex0\endnhere\sectdefaultcl \pard\plain \widctlpar\adjustright \fs20\cgrid {Examples:
> \par Files containing the following sample rdf/xml would match the example query described in the main flow above: (from http://www.mindswap.org/~golbeck/web/www04photo.owl) }{\revised\revauth1\revdttm1183173712
> \par }\pard \widctlpar
> \widctlpar\pnrauth1\pnrdate1183173712\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {<owl:Class rdf:ID="Group"/> }{\revised\revauth1\revdttm1183173712
> \par }{<owl:ObjectProperty rdf:ID="hasMember"> }{\revised\revauth1\revdttm1183173713
> \par }\pard \fi720\widctlpar\prauth1\prdate1183173713
> \fi720\widctlpar\prauth1\prdate1183173713\pnrauth1\pnrdate1183173713\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {<rdfs:domain rdf:resource="#Group"/> }{
> \revised\revauth1\revdttm1183173713
> \par }{<rdfs:range rdf:resource="#Person"/> }{\revised\revauth1\revdttm1183173713
> \par }{<owl:inverseOf rdf:resource="#memberOf"/> }{\revised\revauth1\revdttm1183173714
> \par }\pard \widctlpar
> \widctlpar\pnrauth1\pnrdate1183173714\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {</owl:ObjectProperty}{\deleted\revauthdel1\revdttmdel1183173714 > }{
> \revised\revauth1\revdttm1183173714 >
> \par
> \par }{or (from my imagination) }{\revised\revauth1\revdttm1183173715
> \par }{<owl:Class rdf:ID="OMGVotingList"> }{\revised\revauth1\revdttm1183173715
> \par }\pard \fi720\widctlpar\prauth1\prdate1183173715
> \fi720\widctlpar\prauth1\prdate1183173715\pnrauth1\pnrdate1183173715\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {<rdfs:subClassOf> }{
> \revised\revauth1\revdttm1183173715
> \par }\pard \fi720\li720\widctlpar\prauth1\prdate1183173715
> \fi720\li720\widctlpar\prauth1\prdate1183173715\pnrauth1\pnrdate1183173715\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {<owl:Restriction> }{
> \revised\revauth1\revdttm1183173715
> \par }\pard \fi720\li1440\widctlpar\prauth1\prdate1183173715
> \fi720\li1440\widctlpar\prauth1\prdate1183173715\pnrauth1\pnrdate1183173715\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {
> <owl:onProperty rdf:resource="#hasMember"/> }{\revised\revauth1\revdttm1183173715
> \par }{<owl:allValuesFrom rdf:resource="#OMGMember"/> }{\revised\revauth1\revdttm1183173715
> \par }\pard \fi720\li720\widctlpar\prauth1\prdate1183173715
> \fi720\li720\widctlpar\prauth1\prdate1183173715\pnrauth1\pnrdate1183173715\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {</owl:Restriction> }{
> \revised\revauth1\revdttm1183173715
> \par }\pard \li720\widctlpar\prauth1\prdate1183173715
> \li720\widctlpar\prauth1\prdate1183173715\pnrauth1\pnrdate1183173715\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {</rdfs:subClassOf> }{
> \revised\revauth1\revdttm1183173716
> \par }\pard \widctlpar
> \widctlpar\pnrauth1\pnrdate1183173716\pnrstart1\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrrgb0\pnrstop9\pnrstart2\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0
> \pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrnfc0\pnrstop18\pnrstart3\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0
> \pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrpnbr0\pnrstop36\pnrnot1\adjustright {</owl:Class>
> \par }\pard \widctlpar\adjustright {
> \par }\pard\plain \s1\keepn\widctlpar\outlinelevel0\adjustright \b\fs20\cgrid {\page 9 Use Case : Attach semantic Objects to Stored Content\~
> \par }\pard\plain \widctlpar\adjustright \fs20\cgrid {Priority (L/M/H) : High
> \par
> \par Description :\~
> \par This use case envisions allowing previously existing Repository Stored Content to be attached to a Semantic Object (Ontology Class).}{\revised\revauth1\revdttm1183173751 }{\deleted\revauthdel1\revdttmdel1183173751
> \par }{The meaning of previously existing Repository Stored Content would be much more clear}{\deleted\revauthdel1\revdttmdel1183173751 er}{ and precise.
> \par
> \par Domain Expert , Content Publisher , Registry
> \par Pre-Conditions:
> \par A repository previously populated with Stored Content
> \par A repository populated with domain specific ontology
> \par
> \par Post-Conditions:
> \par none
> \par Basic Flow :
> \par Content Publisher publishes content #1
> \par Domain experts publishes an ontology
> \par Content Publisher publishes an Association that associates content #1 with an ontology class reference as an associationType
> \par Alternate Flow :
> \par none
> \par
> \par Assumptions: Objects are registered as described in Use Case 5 : Associate 2 RegistryObjects using an Ontology Class
> \par None
> \par Issues :
> \par none
> \par Examples:
> \par Repository was populated with (content #1) information based upon a "citizen-centered" content model and classified using a controlled vocabulary describing .gov functions, products, and services in terms th
> at are meaningful to the public. At a later point-in-time a \lquote Government Function\rquote specific domain Ontology is registered. Content publisher associates a subset of}{\deleted\revauthdel1\revdttmdel1183173753 }{
> the citizen-centered information with the Ontology Class for that specific domain.
> \par
> \par
> \par \page }{\b 10 Use Case : Support Association of Semantically Equivalent Objects
> \par }{Priority (L/M/H) : High
> \par
> \par Description :\~
> \par This use case envisions allowing 2 types of Semantic Objects}{\deleted\revauthdel1\revdttmdel1183173754 }{ to be associated using an Equivalence Association .}{\revised\revauth1\revdttm1183173760 This allows a partial mapping of semanti
> c models of different domains potentially leading to some integration across those domains.}{
> \par \~
> \par }{\deleted\revauthdel1\revdttmdel1183173754 The meaning of the associated Semantic Objects and associated content would be much more clearer and precise.
> \par }{
> \par Actors :
> \par Domain Expert , Content Publisher , Registry
> \par Pre-Conditions:
> \par none
> \par Post-Conditions:
> \par none
> \par Basic Flow :
> \par Domain experts publishes a Semantic Object #1 e.g. OWL-S Ontology for Automobile Sales
> \par Domain experts publishes a Semantic Object #2 e.g. RDFS }{\revised\revauth1\revdttm1183173761 rendering }{of UDEF (Universal Data Element Framework) Class modeling Automobile parts
> \par Domain experts publishes an Association that associates a subset of Semantic Object #1 and subset Semantic Object #2 using a Semantic Equivalence class reference as an associationType
> \par Alternate Flow :
> \par none
> \par Exceptions :
> \par none
> \par Includes Use Cases:
> \par None
> \par Special Requirements:
> \par None
> \par Assumptions:
> \par An Association class is used to associate the two class instances\~
> \par Use Case Relationships:
> \par None
> \par Issues :
> \par none
> \par Examples:
> \par (1) Registry was populated
> with Semantic Object #1 a RDFS identifying an UDEF (Universal Data Element Framework) Class model of Product-specific concepts. Registry is also populated with Semantic Object #2 an OWL-S Ontology for Automobile Sales. Domain experts publishes an Associat
> ion that associates \lquote Winter Package\rquote a property of the automobile sales ontology with \lquote Heated Seats\rquote }{\deleted\revauthdel1\revdttmdel1183173773 }{property of the Automobile Parts model.
> \par
> \par
> \par }}
> ------=_20040624154654_51631--
>
____________________________________________________________________________
Professor Asuman Dogac Internet: asuman@srdc.metu.edu.tr
Director Phone: +90 (312) 210 5598, or
Software R&D Center +90 (312) 210 2076
Department of Computer Eng. Fax: +90 (312) 210 1259
Middle East Technical University WWW: http://www.srdc.metu.edu.tr/~asuman/
06531 Ankara Turkey
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]