User Facing Documents Task Force Objective: to produce less technical documents for potential authors and users of OWL content Participants: Alan Ruttenberg,

Slides:



Advertisements
Similar presentations
May 23, 2004OWL-S straw proposal for SWSL1 OWL-S Straw Proposal Presentation to SWSL Committee May 23, 2004 David Martin Mark Burstein Drew McDermott Deb.
Advertisements

Outreach Jeff Good UC Berkeley. OLAC's Needs Maximal involvement from the whole community –The more data providers involved the more useful the services.
Your name Institution/organization Meeting Date. Introduction.
Issue 134 Metamodel for OWL 2 Peter Haase, Elisa Kendall, Boris Motik, Evan Wallace.
Reading and writing reports
PARRT THREE: Processes and Guidelines in Technical Writing.
Dobrin / Keller / Weisser : Technical Communication in the Twenty-First Century. © 2008 Pearson Education. Upper Saddle River, NJ, All Rights Reserved.
Informatics 43 – April 16, Homework 1 What is the purpose and goal of each section in the document? Two audiences: non-technical users and technical.
Writing Skills Improvement Guide Dr. Zubair A. Baig Computer Engineering Department KFUPM, Dhahran.
I NTRODUCTION RESEARCH METHOD FOR ACADEMIC PROJECT I.
Identifying Needs and Establishing Requirements John Thiesfeld Jeff Morton Josh Edwards.
The Information School of the University of Washington INFO 310 Web Site Evaluation How to evaluate a Web site for general purposes.
TIPS ON WRITING AN ABSTRACT Presented by: Vernal G. Alford III, P.E. Adjunct Associate Professor and Director of Outreach College of Engineering, NC A&T.
Carlos Lamsfus. ISWDS 2005 Galway, November 7th 2005 CENTRO DE TECNOLOGÍAS DE INTERACCIÓN VISUAL Y COMUNICACIONES VISUAL INTERACTION AND COMMUNICATIONS.
The Software Development Life Cycle: An Overview
What is the value of audience to technical communicators? A Survey of Audience Research.
CMSC 345, Version 1/11 Software Requirements 1. 2 CMSC 345, Version 1/11 What’s the big deal about requirements? The Tree Swing Project.
Chapter 19 Writing Instructions and Manuals. Analyze your audience and purpose. Gather and organize your information. Design the document. Draft the document.
Preparing Written Reports Effective Communication in Chemical Engineering Freshman Design.
K-12 Web Content Development Process
Writing Quality Requirements Karl E. Wiegers Presented by: Ricardo Carlos.
Copyright © 2010 Pearson Education InternationalChapter Writing Reports and Proposals.
Product Documentation Chapter 5. Required Medical Device Documentation  Business proposal  Product specification  Design specification  Software.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
TECHNICAL WRITING [UWB20302 / UMB1042]
Copyright 2008  Project management process groups progress from initiating activities to planning activities, executing activities, monitoring and controlling.
Copyright © 2010 Pearson Education, Inc. publishing as Prentice HallChapter Writing Reports and Proposals.
Audience Analysis TCO 341 Fall 2002 Dr. Codone. Audience Analysis Identifying primary & secondary audiences Identifying primary & secondary audiences.
1 Chapter 10 Delivering the System Training Documentation.
Sponsored by the National Science Foundation Substrate Working Group GENI Engineering Conference 4 Miami, FL Peter O’Neil April 1,
Doc.: IEEE /087 Submission September 1999 Richard J. Holleman, IEEE-SASlide 1 IEEE Standards Association IEEE, ETSI, and Bluetooth Meeting August.
Discourse and Genre. What is Genre? Genre – is an activity that people engage in through the use of language. Two types of genre 1. Spoken genres – academic.
(SRS) SOFTWARE REQUIREMENT SPECIFICATION(SRS) 1. Topics to be discussed.. What is an SRS? Purpose of an SRS Who reads the SRS? Who writes the SRS? Characteristics.
The future of the Web: Semantic Web 9/30/2004 Xiangming Mu.
Preparation of a Research Report Literature review.
Processes and Guidelines Writing Process: from Audience to Rough Draft: 1.Finding a Topic 2.Analyzing audience and purpose 3.Narrowing down your topic.
Users’ Office News Doris Chromek-Burckhart Head of Users Office Changes to Procedures and Forms Action item.
Doc.: IEEE /0147r0 Submission January 2012 Rolf de Vegt (Qualcomm)) Slide ai Spec Development Process Update Proposal Date:
OWL Web Ontology Language Summary IHan HSIAO (Sharon)
Chapter 3 of Your Research Project AED 615 Fall 2006 Dr. Franklin.
Persuasive Letter Scoring Guide Category4321 Audience Demonstrates a clear understanding of the potential reader and uses appropriate vocabulary and arguments.
Representing nursing in SNOMED CT Proposal for TR or Guideline.
FEPRE IT Presentation Peter Dolukhanov. Aims & Objectives Give an overview of the current proposed IT infrastructure Discuss and get feedback on the current.
WebQuest. The WebQuest model was developed by Bernie Dodge at the San Diego State University in 1995.
INTRODUCTION TO THE WIDA FRAMEWORK Presenter Affiliation Date.
Planning Coordinator - Gap Resolution Team Lorissa Jones – GRT Chair PCC Update March 2016 W ESTERN E LECTRICITY C OORDINATING C OUNCIL.
© Cloud Security Alliance, 2015 March 2, Agenda © Cloud Security Alliance, 2015 The SecaaS Working Group Recent Activity Charter Category outline/templates.
CMGT 410 Week 2 Learning Team Project Charter Check this A+ tutorial guideline at 410-Week-2-Learning-Team-Project-Charter.
Technical Manual Writing and Content
Insert Product Photograph Here
How to do an Internal Audit
Report Writing.
Microsoft MB6-885 Exam Verified Questions And Answer Dumps4download.in
Abstracts.
Reading and writing reports
Introduction to the 2009 Special Education Rights Guide
Product Name.
Informatics 43 – April 14, 2016.
Structure–Feedback on Structure ED-2 and Task Force Proposals
[insert Name of team here] [insert name of project here]
Partnership Collections
Foundations of Technical Communication Module 2
Introduction to Requirements Management
Semantic Web Update W3C RDF, OWL Standards, Development and Applications Dave Beckett.
Product Name.
EC Update on TV Whitespace ECSG
Directive on the assessment and management of flood risks - towards implementation SCG, By Maria Brättemark, European Commission, DG Environment,
Communication Skills for Engineers
Communication Skills for Engineers
Abstracts.
Presentation transcript:

User Facing Documents Task Force Objective: to produce less technical documents for potential authors and users of OWL content Participants: Alan Ruttenberg, Bijan Parsia, Deb McGuinness, Evan Wallace, Jeremy, Carroll, Jim Hendler, Vipul Kashyap, Martic Dzbor, Peter F. Patel-Schneider, Elisa Kendall Charter deliverables which could be in scope: –Overview (introduction to the language) –Requirements –Descriptive specification (filling the role of OWL reference) –User Guide –Possibly additional outreach material e.g. Bijans User Guide for numerics in OWL

UF Document ideas from members: –A revision of OWL Overview from Rec –A revision of OWL Reference –Traceability doc showing features linked to requirements and use cases from multiple domains

No group agreement Different views about audience Some of the Issues: –Concern with this work slowing other WG deliverables –Disagreement with the WG producing some of these documents, particularly a Rec. docs –Concern with the organization, redundancy, length, and correctness of the OWL Rec. docs in this category –Concern about reader confusion about what is normative –Different views about preferred concrete syntax to describe (use in examples) –Disagreement on view (SemWeb –vs- DL) of language to describe Trying to reach some agreement has prevented any forward process

One possible way forward Start working on some content Perhaps working towards a document set like: –An introductory document between OWL 1.1 Overview and OWL Overview from Rec. (without the species of OWL emphasis) –A document intended as a language reference written in plain english –Requirements with traceability Use selectable views for syntax and content (see Bijans OWL tutorial document as an example)