User:AmandaVizedom

From Odp

(Difference between revisions)
Jump to: navigation, search
m (Creating user page with biography of new user.)
Current revision (21:14, 5 February 2009) (view source)
m (added (masked) email, fixed my typos. :-))
 
Line 3: Line 3:
|LastName=Vizedom
|LastName=Vizedom
|Gender=Female
|Gender=Female
 +
|Picture=ODPUser.png
 +
|EmailAddress=amanda.vizedom (at) gmail.com
|Organization=USAF Enterprise Vocabulary Team (contractor)
|Organization=USAF Enterprise Vocabulary Team (contractor)
|OrganizationType=Governmental Organization
|OrganizationType=Governmental Organization
|Country=United States United States  (US)
|Country=United States United States  (US)
|Role=Developer
|Role=Developer
-
|Picture=ODPUser.png
 
}}
}}
{{Account Request Template
{{Account Request Template
-
|Motivation=I'm the technical lead for a team of applied ontologists with varied backgrounds, approaches, and experience. The ODP concept capture something that is not only critical to our internal consistency and training, but also largely outside the consciousness of most working ontologists and not well-supported by existing tools.  What's more, our ontologists support Communities of Interest in developing ontologies based in their own domains and practices. If we are to avoid the classic difficulties (bottlenecks, knowledge loss, etc.) of expert-to-ontologist-to-formal-representation translations, we have to enable the Communities, and their experts, to do some ontology development themselves. We're putting in place the collaboration tools for this, but this is not enough. We also need to put in place the formal model "templates" to help them model their domain concepts without having to think like an ontologist. I see ODP as good fit for this -- better than the approaches I've made at it so far, and am very excited about working with the ODP way of thinking.
+
|Motivation=I'm the technical lead for a team of applied ontologists with varied backgrounds, approaches, and experience. The ODP concept captures something that is not only critical to our internal consistency and training, but also largely outside the consciousness of most working ontologists and not well-supported by existing tools.  What's more, our ontologists support Communities of Interest in developing ontologies based on their own domains and practices. If we are to avoid the classic difficulties (bottlenecks, knowledge loss, etc.) of expert-to-ontologist-to-formal-representation translations, we have to enable the Communities, and their experts, to do some ontology development themselves. We're putting in place the collaboration tools for this, but this is not enough. We also need to put in place the formal model "templates" to help them model their domain concepts without having to think like an ontologist. I see ODP as good fit for this -- better than the approaches I've made at it so far -- and am very excited about working with the ODP community and way of thinking.
|PossibleMainContribution=To have some help to solve modeling problems, To help other users to solve modeling problems
|PossibleMainContribution=To have some help to solve modeling problems, To help other users to solve modeling problems
-
|DomainsOfInterest=Community:Workflow
+
|DomainsOfInterest=Community:General, Community:Ontology, Community:Workflow
|DomainsOfInterestOther=Processes, roles, and actors; authority and governance; information quality; mapping  ontology to language and datat
|DomainsOfInterestOther=Processes, roles, and actors; authority and governance; information quality; mapping  ontology to language and datat
|HowDidIKnowAbout=conference/public events
|HowDidIKnowAbout=conference/public events
}}
}}

Current revision

First name Amanda
Last name Vizedom
Email address amanda.vizedom (at) gmail.com
Personal web site -
Organization USAF Enterprise Vocabulary Team (contractor)
Organization type Governmental Organization
Organization web site
Country United States United States (US)
Role in the organization Developer

Image:ODPUser.png


Main motivation for joining ODP community: I'm the technical lead for a team of applied ontologists with varied backgrounds, approaches, and experience. The ODP concept captures something that is not only critical to our internal consistency and training, but also largely outside the consciousness of most working ontologists and not well-supported by existing tools. What's more, our ontologists support Communities of Interest in developing ontologies based on their own domains and practices. If we are to avoid the classic difficulties (bottlenecks, knowledge loss, etc.) of expert-to-ontologist-to-formal-representation translations, we have to enable the Communities, and their experts, to do some ontology development themselves. We're putting in place the collaboration tools for this, but this is not enough. We also need to put in place the formal model "templates" to help them model their domain concepts without having to think like an ontologist. I see ODP as good fit for this -- better than the approaches I've made at it so far -- and am very excited about working with the ODP community and way of thinking.

Possible main contribution to ODP community: To have some help to solve modeling problems, To help other users to solve modeling problems

Domains of interest:

Is expert of:


How did I know about ODP: conference/public events

Retrieved from "http://ontologydesignpatterns.org/wiki/User:AmandaVizedom"
Personal tools
Quality Committee
Content OP publishers