Downloadable PowerPoint newest version -
http://docs.google.com/leaf?id=0Bx_KguSfl6vSYTg5NTVhYTAtODFkOS00Njc0LTkzZWYtYjQ0NmE4YmRmNTI3.
Downloadable PowerPoint 1997-2003 version -
http://docs.google.com/fileview?id=0Bx_KguSfl6vSZjg5ZGYzOTUtZTc0Ny00OGQ5LWE4NzUtN2YwZWY3M2Q3NTg4&hl=en
Abstract
User Driven Modelling and Systematic Interaction for End-User Programming
This talk discusses PhD research (just submitted) into building a systematic infrastructure and capability, and how to solve problems which could hamper this. This approach is based on creation of systems that can be customised to produce other systems and models, and translation from abstract diagrammatic representations to computer representations. The conclusion explains how this approach to modelling and end-user programming enables interoperability, and collaboration, and that this assists with Maintenance, Extensibility, Ease of Use, and Sharing of Information.
Systems Engineering is involved in the analysis of the relating of interdisciplinary research requirements, in both engineering and computing, for this research. Systems engineering is also important in that the application area of modelling, for aerospace (Airbus and Rolls-Royce) has been one where complex engineering products are created, and a systematic approach is needed. Further to this the research has required systematic production of systems that in turn must be usable by a wide range of users to produce and share their customised engineering models.
24/03/2010 - 24/03/201018:30
Bristol Local GroupUniversity of Bristol, venue is TBA.
Systems Research Showcase Following on from last year’s popular event, this event will provide another chance to see some of the latest postgraduate research in the systems arena being conducted in the south west. This event will take place at the University of Bristol.
There is 1 Document for this event, click here to view
To book for this event, please click here.
Tuesday, March 09, 2010
Monday, February 15, 2010
Translation between models/programs
As well as user to computer translation, an important area of research is similar semi-automated translation between computer programs and models. Much of the structure of programs/models is the same regardless of what particular programming language is used. Making translations of a program/model available on multiple systems by translation from one to the other eases maintenance and re-use and widens availability. Also involving users in such a process would enable sharing and understanding of models/programs, so aiding Decision Support.
Monday, February 08, 2010
A history of end user programming - SiftMedia
SiftMedia have published online this article of mine.
03-Feb-10
A brief history of the evolution of computer programming from the 60s to the present day, by Peter Hale.
- http://www.knowledgeboard.com/item/3058/23/5/3.
03-Feb-10
A brief history of the evolution of computer programming from the 60s to the present day, by Peter Hale.
- http://www.knowledgeboard.com/item/3058/23/5/3.
Tuesday, February 02, 2010
User Driven Modelling and Systematic Interaction for End-User Programming
This is the abstract of a talk I'll give to - Systems Research Showcase, INCOSE UK, Bristol Local Group, Wednesday 24th March 2010 - at Bristol University -
http://www.bristol.ac.uk/engineering/systemscentre/news/2010/incoseblg.html.
This talk discusses PhD research (just submitted) into building a systematic infrastructure and capability, and how to solve problems which could hamper this. This approach is based on creation of systems that can be customised to produce other systems and models, and translation from abstract diagrammatic representations to computer representations.The conclusion explains how this approach to modelling and end-user programming enables interoperability, and collaboration, and that this assists with Maintenance, Extensibility, Ease of Use, and Sharing of Information.
Systems Engineering is involved in the analysis of the relating of interdisciplinary research requirements, in both engineering and computing, for this research. Systems engineering is also important in that the application area of modelling, for aerospace (Airbus and Rolls-Royce) has been one where complex engineering products are created, and a systematic approach is needed. Further to this the research has required systematic production of systems that in tern must be usuable by a wide range of users to produce and share their customised engineering models.
http://www.bristol.ac.uk/engineering/systemscentre/news/2010/incoseblg.html.
This talk discusses PhD research (just submitted) into building a systematic infrastructure and capability, and how to solve problems which could hamper this. This approach is based on creation of systems that can be customised to produce other systems and models, and translation from abstract diagrammatic representations to computer representations.The conclusion explains how this approach to modelling and end-user programming enables interoperability, and collaboration, and that this assists with Maintenance, Extensibility, Ease of Use, and Sharing of Information.
Systems Engineering is involved in the analysis of the relating of interdisciplinary research requirements, in both engineering and computing, for this research. Systems engineering is also important in that the application area of modelling, for aerospace (Airbus and Rolls-Royce) has been one where complex engineering products are created, and a systematic approach is needed. Further to this the research has required systematic production of systems that in tern must be usuable by a wide range of users to produce and share their customised engineering models.
Thursday, January 21, 2010
BBC article - Tim Berners-Lee unveils government data project
This is an interesting article about use of the Semantic Web for Government data -
"Web founder Sir Tim Berners-Lee has unveiled his latest venture for the UK government, which offers the public better access to official data.
A new website, data.gov.uk, will offer reams of public sector data, ranging from traffic statistics to crime figures, for private or commercial use.
The target is to kickstart a new wave of services that find novel ways to make use of the information.
Sir Tim was hired by PM Gordon "
Tim Berners-Lee unveils government data project - http://news.bbc.co.uk/1/hi/technology/8470797.stm - 21 January 2010
British Computer Society Interview -
Sir Tim Berners-Lee talks to BCS
November 2009
In an exclusive interview with the Institute, Sir Tim Berners-Lee spoke about the latest on the semantic web, his view on the advent of artificial life forms on the internet, the biggest barriers to enabling the information society for all, where the mobile web is going and more. - http://www.bcs.org/server.php?show=ConWebDoc.33535.
"Web founder Sir Tim Berners-Lee has unveiled his latest venture for the UK government, which offers the public better access to official data.
A new website, data.gov.uk, will offer reams of public sector data, ranging from traffic statistics to crime figures, for private or commercial use.
The target is to kickstart a new wave of services that find novel ways to make use of the information.
Sir Tim was hired by PM Gordon "
Tim Berners-Lee unveils government data project - http://news.bbc.co.uk/1/hi/technology/8470797.stm - 21 January 2010
British Computer Society Interview -
Sir Tim Berners-Lee talks to BCS
November 2009
In an exclusive interview with the Institute, Sir Tim Berners-Lee spoke about the latest on the semantic web, his view on the advent of artificial life forms on the internet, the biggest barriers to enabling the information society for all, where the mobile web is going and more. - http://www.bcs.org/server.php?show=ConWebDoc.33535.
Friday, January 08, 2010
User driven modelling: Visualisation and systematic interaction for end user programming - SiftMedia
SiftMedia have published online this article of mine.
Article for Knowledge Board - SiftMedia - User driven modelling: Visualisation and systematic interaction for end user programming - http://www.knowledgeboard.com/item/3053/23/5/3.
04-Jan-10
Peter Hale explores to what extent it is possible to improve user-driven collaborative software development through interaction with diagrams and without requiring people to learn computer languages.
Article for Knowledge Board - SiftMedia - User driven modelling: Visualisation and systematic interaction for end user programming - http://www.knowledgeboard.com/item/3053/23/5/3.
04-Jan-10
Peter Hale explores to what extent it is possible to improve user-driven collaborative software development through interaction with diagrams and without requiring people to learn computer languages.
Thursday, December 31, 2009
Methodology for creation of modelling systems
This approach is based on creation of systems that can be customised to produce other systems and models, and translation from abstract diagrammatic representations to computer representations.The conclusion explains how this approach to modelling and end-user programming enables interoperability, and collaboration, and that this assists with Maintenance, Extensibility, Ease of Use, and Sharing of Information.
This methodology can be seen as an attempt to semi-automate knowledge acquisition and representation approaches such as the SEPA Funnel (Systems Engineering Process Activities) . This methodology was prototyped in the research that led to the User Driven Modelling/Programming Approach. This provides a translation process from Knowledge Acquisition to modelling (User Driven Modelling), and automated translation of model to software (User Driven Programming), and so takes this SEPA Funnel to a further stage of translation/transformation of the model/system design specification. This can be facilitated by using XML (eXtensible Markup Language) as a programming language, for the representation of data and formulae, and of the user interface e.g. XAML (eXtensible Application Markup Language).
The methodology suits top-down ontology and model creation e.g. from those responsible for the root item in a product data structure downwards, and bottom-up ontology development, e.g. alternative solutions, tagging of items to allow discussion and enable disambiguation, and agreement on terminology, and mapping of alternative names to each other. This dual approach is facilitated by the translation being provided in both directions.
This model-driven approach examines how links between engineers and modellers/modelling tools can be improved, by visualising a modelling structure that mirrors the structure of the engineering product design. This provides traceability for calculation and decision making in a more clear, structured and visualised way than the audit trail in spreadsheets. This work concentrates mainly on requirements (Airbus, Rolls-Royce), software, and HCI aspects of systems. The main method for this is diagrammatic modelling which was used in gathering requirements, and is also implemented within the modelling system developed.
Making the structure of a model be the same as the structure of the engineering component modelled, and visualising both turns two problems into one. This speeds up co-operation in prototyping of both the software model and the component. Both rapid prototyping and rapid application design/development involve iterative fast development with prototypes communicated for feedback and refinement.
Requirements emerge gradually as part of this process, so early stage design can begin, in co-operation with life-cycle management, marketing, accounts etc. To get full benefit from this all staff who are part of this design process, manufacturing, management, and life-cycle management need to be able to access the models. The longer term aim is to enable direct modelling/prototyping of this by customers of the modelling tool e.g. engineers/end-user programmers. Such a system documents itself as the structure of the engineering product and software model are displayed/visualised. This would make it possible for emergent properties of a system to become known.
Despite object-oriented programming techniques being heavily influenced by the approach used by engineers for Bill of Materials/Product Data Structure modelling this link is difficult. Much of object-oriented programming was developed before graphical user interfaces became practical and common. So objects/classes are often represented mainly by text with visualisation/representation being added as an afterthought. This is not useful for engineers who are used to objects being physical things, or at least diagrams. A further problem has been an over-emphasis on encapsulation (hiding an objects' details, while creating an interface for its use, and re-use). This can lead to errors due to re-use of objects not fully understood. So the classes/objects must be visualised, even if the user does not intend to change their contents, then the user of objects has sufficient understanding of how to use them. This would improve the link and co-operation between engineers and modellers/models. The advantage is that engineers can iterate back and forth between problem and solution, this avoids two risks - going straight to a solution too early, or the problem being so abstract that no solution is achieved. Rapid iteration that semi-automating of the system provides enables an improved chance for finding a good solution. This approach is particularly suitable to taxonomy tree structures, so is best applied for process modelling (business and engineering), product data and work breakdown structures, and scientific taxonomies/phylogenies.
A requirement for use of such a system by engineers (or business and science) is to eliminate or minimise the need for code writing. This then would enable engineers to create models by linking of formulae, as they do when using spreadsheets, but provide a more structured (tree based) representation and visualisation of model(s). To find alternative ways of representing models that do not require the user to write code it must be easier to interact with and change the models, and to share and develop information with colleagues. It would also be useful to more closely align and link UML, and code development environments. Too much need for coding leads engineers to lose influence on the system to be developed, as the model needs to be created by software experts who have less understanding of the engineering problem.
Conclusion
This work involved development of a system for creating systems. Advantages of this approach are Maintenance, Extensibility, Ease of Use, and Sharing of Information. The use of open standards and representation enables this system to interact and interoperate with other systems and enable collaboration. This makes this system a ‘white box’ which can interact with and be viewable to other systems rather than a proprietary ‘black box’. This systematic design and representation of engineering modelling systems, enables semi-automated translation. This enables rapid iteration around a cycle of knowledge acquisition, specification of the problem, prototypes, and alternate potential solutions. This assists with deciding when to adapt and re-use existing solutions and when to innovate.
Such a system could be used to rebuild the system engineering for aerospace capabilities at UWE, and is being developed further at Bath University. A further advantage of the approach outlined here is that it shows promise for use in the SALT (Sharing Approaches to Learning and Teaching) project and for the Tearfund disaster relief project, so the flexibility built into it makes the process applicable to problems for which it was not envisaged and designed. Although these tools can be regarded as software related, they are also and more importantly a way of empowering computer literate end-users (e.g. engineers) with the autonomy to collaboratively model problems more free of constraints of software development. This enables better collaboration across disciplines and more independent of management structure and hierarchy.
SEPA Funnel - http://www.umcs.maine.edu/~ftp/wisr/wisr9/final-papers/Barber.html - K. Suzanne Barber, Thomas J. Graser, and Stephen R. Jernigan.
Systems Engineering MSc Module Assignment - Main part - http://docs.google.com/View?id=dgp7zcg6_344cxn8sxhs - Appendix - http://docs.google.com/View?id=dgp7zcg6_352c8j2w5cg.
This methodology can be seen as an attempt to semi-automate knowledge acquisition and representation approaches such as the SEPA Funnel (Systems Engineering Process Activities) . This methodology was prototyped in the research that led to the User Driven Modelling/Programming Approach. This provides a translation process from Knowledge Acquisition to modelling (User Driven Modelling), and automated translation of model to software (User Driven Programming), and so takes this SEPA Funnel to a further stage of translation/transformation of the model/system design specification. This can be facilitated by using XML (eXtensible Markup Language) as a programming language, for the representation of data and formulae, and of the user interface e.g. XAML (eXtensible Application Markup Language).
The methodology suits top-down ontology and model creation e.g. from those responsible for the root item in a product data structure downwards, and bottom-up ontology development, e.g. alternative solutions, tagging of items to allow discussion and enable disambiguation, and agreement on terminology, and mapping of alternative names to each other. This dual approach is facilitated by the translation being provided in both directions.
This model-driven approach examines how links between engineers and modellers/modelling tools can be improved, by visualising a modelling structure that mirrors the structure of the engineering product design. This provides traceability for calculation and decision making in a more clear, structured and visualised way than the audit trail in spreadsheets. This work concentrates mainly on requirements (Airbus, Rolls-Royce), software, and HCI aspects of systems. The main method for this is diagrammatic modelling which was used in gathering requirements, and is also implemented within the modelling system developed.
Making the structure of a model be the same as the structure of the engineering component modelled, and visualising both turns two problems into one. This speeds up co-operation in prototyping of both the software model and the component. Both rapid prototyping and rapid application design/development involve iterative fast development with prototypes communicated for feedback and refinement.
Requirements emerge gradually as part of this process, so early stage design can begin, in co-operation with life-cycle management, marketing, accounts etc. To get full benefit from this all staff who are part of this design process, manufacturing, management, and life-cycle management need to be able to access the models. The longer term aim is to enable direct modelling/prototyping of this by customers of the modelling tool e.g. engineers/end-user programmers. Such a system documents itself as the structure of the engineering product and software model are displayed/visualised. This would make it possible for emergent properties of a system to become known.
Despite object-oriented programming techniques being heavily influenced by the approach used by engineers for Bill of Materials/Product Data Structure modelling this link is difficult. Much of object-oriented programming was developed before graphical user interfaces became practical and common. So objects/classes are often represented mainly by text with visualisation/representation being added as an afterthought. This is not useful for engineers who are used to objects being physical things, or at least diagrams. A further problem has been an over-emphasis on encapsulation (hiding an objects' details, while creating an interface for its use, and re-use). This can lead to errors due to re-use of objects not fully understood. So the classes/objects must be visualised, even if the user does not intend to change their contents, then the user of objects has sufficient understanding of how to use them. This would improve the link and co-operation between engineers and modellers/models. The advantage is that engineers can iterate back and forth between problem and solution, this avoids two risks - going straight to a solution too early, or the problem being so abstract that no solution is achieved. Rapid iteration that semi-automating of the system provides enables an improved chance for finding a good solution. This approach is particularly suitable to taxonomy tree structures, so is best applied for process modelling (business and engineering), product data and work breakdown structures, and scientific taxonomies/phylogenies.
A requirement for use of such a system by engineers (or business and science) is to eliminate or minimise the need for code writing. This then would enable engineers to create models by linking of formulae, as they do when using spreadsheets, but provide a more structured (tree based) representation and visualisation of model(s). To find alternative ways of representing models that do not require the user to write code it must be easier to interact with and change the models, and to share and develop information with colleagues. It would also be useful to more closely align and link UML, and code development environments. Too much need for coding leads engineers to lose influence on the system to be developed, as the model needs to be created by software experts who have less understanding of the engineering problem.
Conclusion
This work involved development of a system for creating systems. Advantages of this approach are Maintenance, Extensibility, Ease of Use, and Sharing of Information. The use of open standards and representation enables this system to interact and interoperate with other systems and enable collaboration. This makes this system a ‘white box’ which can interact with and be viewable to other systems rather than a proprietary ‘black box’. This systematic design and representation of engineering modelling systems, enables semi-automated translation. This enables rapid iteration around a cycle of knowledge acquisition, specification of the problem, prototypes, and alternate potential solutions. This assists with deciding when to adapt and re-use existing solutions and when to innovate.
Such a system could be used to rebuild the system engineering for aerospace capabilities at UWE, and is being developed further at Bath University. A further advantage of the approach outlined here is that it shows promise for use in the SALT (Sharing Approaches to Learning and Teaching) project and for the Tearfund disaster relief project, so the flexibility built into it makes the process applicable to problems for which it was not envisaged and designed. Although these tools can be regarded as software related, they are also and more importantly a way of empowering computer literate end-users (e.g. engineers) with the autonomy to collaboratively model problems more free of constraints of software development. This enables better collaboration across disciplines and more independent of management structure and hierarchy.
SEPA Funnel - http://www.umcs.maine.edu/~ftp/wisr/wisr9/final-papers/Barber.html - K. Suzanne Barber, Thomas J. Graser, and Stephen R. Jernigan.
Systems Engineering MSc Module Assignment - Main part - http://docs.google.com/View?id=dgp7zcg6_344cxn8sxhs - Appendix - http://docs.google.com/View?id=dgp7zcg6_352c8j2w5cg.
Wednesday, December 30, 2009
Systems Engineering MSc Assignment
Cover Sheet
Peter Hale, University of the West of England, Bristol (UWE)
Continuing Professional Development in Aerospace - Systems Engineering
28th - 30th October & 16th - 17th November
Executive Summary
This assignment examines the systems engineering work at the University of the West of England, Bristol (my employer 2000-2008, and 2009-10). The particular focus is on application of this towards aerospace and modelling for Airbus and Rolls-Royce. It is argued in part a) that poor decision making by UWE led to this work being restricted, and that it needs rebuilding. Section 1 explains the reasons behind the problems, and ideas for recreating this system capability.
Section 2 part a) examines how change can be brought about to repair this damaged capability and a plan for rebuilding this, taking into account the problems already faced. Part b) describes the approach used to try to rebuild this capability and how to avoid problems which could hamper this. This approach is based on creation of systems that can be customised to produce other systems and models, and translation from abstract diagrammatic representations to computer representations.
The conclusion explains how this approach to modelling and end-user programming enables interoperability, and collaboration, and that this assists with Maintenance, Extensibility, Ease of Use, and Sharing of Information.
Systems Engineering MSc Module Assignment - Main part - http://docs.google.com/View?id=dgp7zcg6_344cxn8sxhs - Appendix - http://docs.google.com/View?id=dgp7zcg6_352c8j2w5cg.
Peter Hale, University of the West of England, Bristol (UWE)
Continuing Professional Development in Aerospace - Systems Engineering
28th - 30th October & 16th - 17th November
Executive Summary
This assignment examines the systems engineering work at the University of the West of England, Bristol (my employer 2000-2008, and 2009-10). The particular focus is on application of this towards aerospace and modelling for Airbus and Rolls-Royce. It is argued in part a) that poor decision making by UWE led to this work being restricted, and that it needs rebuilding. Section 1 explains the reasons behind the problems, and ideas for recreating this system capability.
Section 2 part a) examines how change can be brought about to repair this damaged capability and a plan for rebuilding this, taking into account the problems already faced. Part b) describes the approach used to try to rebuild this capability and how to avoid problems which could hamper this. This approach is based on creation of systems that can be customised to produce other systems and models, and translation from abstract diagrammatic representations to computer representations.
The conclusion explains how this approach to modelling and end-user programming enables interoperability, and collaboration, and that this assists with Maintenance, Extensibility, Ease of Use, and Sharing of Information.
Systems Engineering MSc Module Assignment - Main part - http://docs.google.com/View?id=dgp7zcg6_344cxn8sxhs - Appendix - http://docs.google.com/View?id=dgp7zcg6_352c8j2w5cg.
Tuesday, December 08, 2009
Microsoft Imagine Cup
These are ideas put together from what I've heard from others that are interested in forming a team to enter with this kind of project. I'm hopeful we'll form a team and enter.
Maybe a start of the case then is for Tearfund disaster management, creation of a form using Microsoft Infopath, for feedback and sharing of disaster management information, uploaded to Sharepoint (could be tested on the UWE Sharepoint site). This then could be linked to stylesheets e.g. CSS for presentation in different regions and to a Microsoft translation service. The XML could be searchable on the web and maybe link with and be a way of uploading information for lost and found people. The forms must be usable on mobile phones, as much of a range as possible. Results to go to a server for help with systematic co-ordination of relief efforts.
Imagine Cup - http://imaginecup.com/, http://imaginecup.co.uk/.
A relevant event which I'm going to and will give a short presentation (PhD work, and Imagine Cup ideas is - Bristol Knowledge Unconference 2009 - 12th and 13th December - http://www.craftivism.net/wiki/UnCraftivism/Bristol_Knowledge_Unconference_2009
Themes - Knowledge Management/Semantic Web - Location: Arnolfini, 16 Narrow Quay, Bristol, BS1 4QA - UnCraftivism event, in association with the Craftivism Exhibition at the Arnolfini in Bristol.
My Presentation - User Driven Modelling - PhD
Visualisation for knowledge editing and creation by users -
Maybe a start of the case then is for Tearfund disaster management, creation of a form using Microsoft Infopath, for feedback and sharing of disaster management information, uploaded to Sharepoint (could be tested on the UWE Sharepoint site). This then could be linked to stylesheets e.g. CSS for presentation in different regions and to a Microsoft translation service. The XML could be searchable on the web and maybe link with and be a way of uploading information for lost and found people. The forms must be usable on mobile phones, as much of a range as possible. Results to go to a server for help with systematic co-ordination of relief efforts.
Imagine Cup - http://imaginecup.com/, http://imaginecup.co.uk/.
A relevant event which I'm going to and will give a short presentation (PhD work, and Imagine Cup ideas is - Bristol Knowledge Unconference 2009 - 12th and 13th December - http://www.craftivism.net/wiki/UnCraftivism/Bristol_Knowledge_Unconference_2009
Themes - Knowledge Management/Semantic Web - Location: Arnolfini, 16 Narrow Quay, Bristol, BS1 4QA - UnCraftivism event, in association with the Craftivism Exhibition at the Arnolfini in Bristol.
My Presentation - User Driven Modelling - PhD
Visualisation for knowledge editing and creation by users -
Friday, November 27, 2009
Social media 'could transform public services' - BBC website
http://news.bbc.co.uk/1/hi/technology/8382252.stm - By Mark Ward Technology correspondent, BBC News.
This article describes the usefulness of Web 2.0 in providing user involvement in health and public services. This report is from the MyPublicServices conference. This provides a useful solution to current problems that centralised systems don't give patients and users enough involvement, but plans such as relying on Google tools for the management of systems are misguided. This conference investigated ways of involving users to a degree that is practical.
"Social media could transform the NHS and other public services in the same way that file-sharing changed the music industry, a conference has heard.
Growing use of tools, such as Facebook and Twitter, offered an opportunity to reinvent services, delegates heard.
The MyPublicServices event debated ways to harness these conversations, many of which are critical, to make services better and more inclusive.
If this was not done, many services would be undermined, speakers said.
"It's happened to the music and travel industries and it's going to happen to public services," said Dr Paul Hodgkin, founder of the Patient Opinion site that organised the MyPublicServices conference.
Said Dr Hodgkin: "The question is how do we cope with it in a useful and productive way and not spend decades beating each other up?" "
Here are more interesting articles about this debate -
Tories attack leaked five-year IT plan as 'unambitious' - BBC News Website - http://news.bbc.co.uk/1/hi/uk_politics/8387972.stm.
The politics of crowdsourcing - BBC News Website -
http://www.bbc.co.uk/blogs/technology/2009/12/the_politics_of_crowdsourcing.html -
- "Politicians in opposition and in government are latching onto the idea of using the web to engage with the wider public
Rory Cellan-Jones
BBC's technology correspondent"
- "This leak isn't likely to generate lurid headlines, as the report on transforming government by using "interactive (web 2.0) tools and processes, cloud computing technology and service-oriented architecture (SOA)" isn't exactly dynamite.
Still, the Conservatives have come up with quite a clever idea - they've put the document online and are inviting the public to comment on every part of it as they frame the party's response. "
This article describes the usefulness of Web 2.0 in providing user involvement in health and public services. This report is from the MyPublicServices conference. This provides a useful solution to current problems that centralised systems don't give patients and users enough involvement, but plans such as relying on Google tools for the management of systems are misguided. This conference investigated ways of involving users to a degree that is practical.
"Social media could transform the NHS and other public services in the same way that file-sharing changed the music industry, a conference has heard.
Growing use of tools, such as Facebook and Twitter, offered an opportunity to reinvent services, delegates heard.
The MyPublicServices event debated ways to harness these conversations, many of which are critical, to make services better and more inclusive.
If this was not done, many services would be undermined, speakers said.
"It's happened to the music and travel industries and it's going to happen to public services," said Dr Paul Hodgkin, founder of the Patient Opinion site that organised the MyPublicServices conference.
Said Dr Hodgkin: "The question is how do we cope with it in a useful and productive way and not spend decades beating each other up?" "
Here are more interesting articles about this debate -
Tories attack leaked five-year IT plan as 'unambitious' - BBC News Website - http://news.bbc.co.uk/1/hi/uk_politics/8387972.stm.
The politics of crowdsourcing - BBC News Website -
http://www.bbc.co.uk/blogs/technology/2009/12/the_politics_of_crowdsourcing.html -
- "Politicians in opposition and in government are latching onto the idea of using the web to engage with the wider public
Rory Cellan-Jones
BBC's technology correspondent"
- "This leak isn't likely to generate lurid headlines, as the report on transforming government by using "interactive (web 2.0) tools and processes, cloud computing technology and service-oriented architecture (SOA)" isn't exactly dynamite.
Still, the Conservatives have come up with quite a clever idea - they've put the document online and are inviting the public to comment on every part of it as they frame the party's response. "
Thursday, November 19, 2009
BBC News - Google previews Chrome open source operating system
This is an interesting development in bringing Web 2.0 web browser software on a stage -
"Internet search giant Google has lifted the lid on its operating system, known as Chrome OS.
The free and open source system is initially aimed at low-cost netbooks and does away with many of the features of a traditional programme.
All programmes are designed to run in a web browser and all the user's data is stored on Google's servers.
Engineers from the firm said the first computers running the system would be available before the end of 2010."
http://news.bbc.co.uk/1/hi/technology/8369611.stm.
"Internet search giant Google has lifted the lid on its operating system, known as Chrome OS.
The free and open source system is initially aimed at low-cost netbooks and does away with many of the features of a traditional programme.
All programmes are designed to run in a web browser and all the user's data is stored on Google's servers.
Engineers from the firm said the first computers running the system would be available before the end of 2010."
http://news.bbc.co.uk/1/hi/technology/8369611.stm.
Sunday, November 15, 2009
Researcher Collaboration - Web 2.0 - Strength in science collaboration - BBC Article
This looks like a useful Web 2.0 collaboration tool for researchers -
The BBC article is at - http://news.bbc.co.uk/1/hi/technology/8342851.stm
"Victor Henning is the co-founder of Mendeley, an online collaboration tool which was created specifically for scientists.
The free software allows scientists and researchers to upload papers which are then trawled for bibliographic data - author, title, issue and so on - and paired up with similar papers already in the database."
"Mendeley is supposed to take the work out of managing these [research] papers.," explains Mr Henning.
"You can just drag and drop your collection of PDFs into the software and it'll automatically extract all the bibliographic data - all of the stuff that you'd usually have to type in manually." - Victor Henning.
The BBC article is at - http://news.bbc.co.uk/1/hi/technology/8342851.stm
"Victor Henning is the co-founder of Mendeley, an online collaboration tool which was created specifically for scientists.
The free software allows scientists and researchers to upload papers which are then trawled for bibliographic data - author, title, issue and so on - and paired up with similar papers already in the database."
"Mendeley is supposed to take the work out of managing these [research] papers.," explains Mr Henning.
"You can just drag and drop your collection of PDFs into the software and it'll automatically extract all the bibliographic data - all of the stuff that you'd usually have to type in manually." - Victor Henning.
Sunday, November 01, 2009
Engineering modelling an iterative approach
This post discusses how links between engineers and modellers/modelling tools can be improved, using an approach of visualising a modelling structure that mirrors the structure of the engineering product design. The main method for this is diagrammatic modelling.
Making the structure of a model be the same as the structure of the engineering component modelled turns 2 problems into one. This speeds up co-operation in prototyping of both the software model and the component. Both rapid prototyping and rapid application design/development involve iterative fast development with prototypes communicated. Requirements emerge gradually as part of this process, so early stage design can begin, in co-operation with life-cycle management, marketing accounts etc. To get full benefit from this all staff who are part of this design process, manufacturing, management, and life-cycle management need to be able to access the models. The longer term aim is to enable direct modelling/prototyping of this by customers of the modelling tool e.g. engineers/end-user programmers. Such a system documents itself as the structure of the engineering product and software model are displayed/visualised.
Integration of information representation UML/Doors (http://www-01.ibm.com/software/awdtools/doors/productline/) is progress towards this. Also a user interface is required that makes it easier for engineers to model using such a combined UML/Doors solution
Despite object-oriented programming techniques being heavily influenced by the approach used by engineers for Bill of Materials/Product Data Structure modelling this link has become difficult. Much of object-oriented programming was developed before graphical user interfaces became practical and common. So objects/classes are often represented mainly by text with visualisation/representation being added as an afterthought. This is not useful for engineers who are used to objects being physical things, or at least diagrams. A further problem has been an over-emphasis on encapsulation (hiding an objects' details, while creating an interface for its use), and re-use. This can lead to errors due to re-use of objects that are not fully understood. So the classes/objects need to be visualised, even if the user does not intend to change their contents, so the user of objects has sufficient understanding of how to use them.
The above steps would improve the link and co-operation between engineers and modellers/models.
Making the structure of a model be the same as the structure of the engineering component modelled turns 2 problems into one. This speeds up co-operation in prototyping of both the software model and the component. Both rapid prototyping and rapid application design/development involve iterative fast development with prototypes communicated. Requirements emerge gradually as part of this process, so early stage design can begin, in co-operation with life-cycle management, marketing accounts etc. To get full benefit from this all staff who are part of this design process, manufacturing, management, and life-cycle management need to be able to access the models. The longer term aim is to enable direct modelling/prototyping of this by customers of the modelling tool e.g. engineers/end-user programmers. Such a system documents itself as the structure of the engineering product and software model are displayed/visualised.
Integration of information representation UML/Doors (http://www-01.ibm.com/software/awdtools/doors/productline/) is progress towards this. Also a user interface is required that makes it easier for engineers to model using such a combined UML/Doors solution
Despite object-oriented programming techniques being heavily influenced by the approach used by engineers for Bill of Materials/Product Data Structure modelling this link has become difficult. Much of object-oriented programming was developed before graphical user interfaces became practical and common. So objects/classes are often represented mainly by text with visualisation/representation being added as an afterthought. This is not useful for engineers who are used to objects being physical things, or at least diagrams. A further problem has been an over-emphasis on encapsulation (hiding an objects' details, while creating an interface for its use), and re-use. This can lead to errors due to re-use of objects that are not fully understood. So the classes/objects need to be visualised, even if the user does not intend to change their contents, so the user of objects has sufficient understanding of how to use them.
The above steps would improve the link and co-operation between engineers and modellers/models.
Wednesday, October 07, 2009
PhD Thesis Submitted
I've submitted my PhD in User Driven Programming, and continued this while my work environment changed. Previously I retrained from clerical work to engineering and computing, and developed advanced skills and experience in this through vocational and higher education. I worked for 10 years as a researcher at University of the West of England. I researched difficult problems, and helped gain funding for such research, and have written funding proposals. I'm very thorough and consistent, resolute, determined, am diplomatic, and have relevant skills for analysing research questions, and presenting findings. My home page is http://sites.google.com/site/userdrivenmodellingprogramming/Home. I devise ways for users to create software, to achieve this I apply Semantic Web techniques. I enable non-programmers to create software from a user interface that allows them to model a particular problem or scenario. I develop ways of translating this information into program code. This is useful for employees that have insufficient time to learn programming languages. This makes it easier for software systems to manage and enable sharing of information and programs people create.
Friday, October 02, 2009
Bristol Knowledge Unconference 2009
The Bristol Knowledge Unconference in 2009 - http://www.craftivism.net/wiki/UnCraftivism/Bristol_Knowledge_Unconference_2009 - will be an UnCraftivism event, in association with the Craftivism Exhibition at the Arnolfini in Bristol.
Basic Info
Date: 12th - 13th December 2009
Time: TBC
Location: Arnolfini, Bristol
Organiser: Daniel Lewis
Email: danieljohnlewis [at] gmail [dot] com
Instigator: Rui Guerra
Helpers: ...
In collaboration with:
What is Bristol Knowledge Unconference?
Bristol Knowledge Unconference is an "Unconference" specifically about Knowledge. The first Bristol Knowledge Unconference was in September 2008, and involved about 50 people who talked about Knowledge from scientific and new-media perspectives.
The knowledge unconferences are "themed" around the general subject of Knowledge, which includes:
The Semantic Web / Linked Data / Hyperdata / Data Web
Web Science
Topic Maps
Information Architecture and Design
Knowledge Acquisition and Knowledge Management
Knowledge-Based Systems, Knowledge Engineering and Rule-Based Systems (etc)
Knowledge/Information Visualisation and Graphical User Interfaces
Knowledge-orientated Search Engine Optimisation (SEO)
and maybe even, Object Oriented Databases
What will Bristol Knowledge Unconference 2009 be about?
This will be our second Bristol Knowledge Unconference. Our first one was very fun, and we hope to multiply that amount of fun - particularly as we'll be running alongside other groups involved in UnCraftivism.
As we will be in the Arnolfini, it has been decided to label this years Knowledge Unconference: The Art of Knowledge
Knowledge is both art and science. Everything we do with knowledge can be both beautiful and methodical. We will discuss these things, and talks will be established in order to think about these ideas. Other more general talks/demos are very much welcomed, no matter how arty or scientific they are. The idea of an Unconference is completely free-flowing, it is developed with minimal structure/organisation and also attempts to maximise the equality of the attendees.
We will be running simultaneously with other events happening during the unCraftivism weekend, see the Main Exhibition Page - http://www.craftivism.net/wiki/Main_Page - for more details.
I am definitely coming...
Feel free to put your name here if you know you will be attending:
Basic Info
Date: 12th - 13th December 2009
Time: TBC
Location: Arnolfini, Bristol
Organiser: Daniel Lewis
Email: danieljohnlewis [at] gmail [dot] com
Instigator: Rui Guerra
Helpers: ...
In collaboration with:
What is Bristol Knowledge Unconference?
Bristol Knowledge Unconference is an "Unconference" specifically about Knowledge. The first Bristol Knowledge Unconference was in September 2008, and involved about 50 people who talked about Knowledge from scientific and new-media perspectives.
The knowledge unconferences are "themed" around the general subject of Knowledge, which includes:
The Semantic Web / Linked Data / Hyperdata / Data Web
Web Science
Topic Maps
Information Architecture and Design
Knowledge Acquisition and Knowledge Management
Knowledge-Based Systems, Knowledge Engineering and Rule-Based Systems (etc)
Knowledge/Information Visualisation and Graphical User Interfaces
Knowledge-orientated Search Engine Optimisation (SEO)
and maybe even, Object Oriented Databases
What will Bristol Knowledge Unconference 2009 be about?
This will be our second Bristol Knowledge Unconference. Our first one was very fun, and we hope to multiply that amount of fun - particularly as we'll be running alongside other groups involved in UnCraftivism.
As we will be in the Arnolfini, it has been decided to label this years Knowledge Unconference: The Art of Knowledge
Knowledge is both art and science. Everything we do with knowledge can be both beautiful and methodical. We will discuss these things, and talks will be established in order to think about these ideas. Other more general talks/demos are very much welcomed, no matter how arty or scientific they are. The idea of an Unconference is completely free-flowing, it is developed with minimal structure/organisation and also attempts to maximise the equality of the attendees.
We will be running simultaneously with other events happening during the unCraftivism weekend, see the Main Exhibition Page - http://www.craftivism.net/wiki/Main_Page - for more details.
I am definitely coming...
Feel free to put your name here if you know you will be attending:
Tuesday, September 29, 2009
User Driven Modelling Explanation - Cube
This example was provided to illustrate the structure and process for creating the ontology, model, and visualisation/representation used for translation process from step 1 to step 3, for the User Driven Modelling approach. This also helps to demonstrate how the research provides a solution for generic and reusable engineering modelling, by providing a real but simple demonstration of this modelling approach being used for an engineering model.
The cube model, as for all the engineering/process models is made up of the definition, in this case of the cube, and a colour coded representation of all the processes, materials, tooling, consumables, resources, and rates used for the manufacture of the cube; these are read in from the ontology in response to user choices. This makes it possible to investigate scenarios such as in this case whether to manufacture using welding, or riveting, and different options for use of tooling, consumables, resources, and rates. From investigating different options, different trees are created to represent different paths/options, and from this the production cost tree is created with results and feedback on exactly what made up the process/cost. Figure 1 illustrates how the different sub ontologies/taxonomies are colour coded in order to ensure it is easier to read the meaning of the tree and the interrelationships between the different aspects of the model.
Figure 1 Cube model example - illustrates choice of process etc.
In this example, aluminium was chosen as the material, and riveting was chosen as the process. This example also illustrates how the Vanguard System modelling tool automatically combines units appropriately.
Next the implementation of this research was illustrated with the more complex example of an aircraft wingbox, using the same approach.
The cube model, as for all the engineering/process models is made up of the definition, in this case of the cube, and a colour coded representation of all the processes, materials, tooling, consumables, resources, and rates used for the manufacture of the cube; these are read in from the ontology in response to user choices. This makes it possible to investigate scenarios such as in this case whether to manufacture using welding, or riveting, and different options for use of tooling, consumables, resources, and rates. From investigating different options, different trees are created to represent different paths/options, and from this the production cost tree is created with results and feedback on exactly what made up the process/cost. Figure 1 illustrates how the different sub ontologies/taxonomies are colour coded in order to ensure it is easier to read the meaning of the tree and the interrelationships between the different aspects of the model.
Figure 1 Cube model example - illustrates choice of process etc.
Figure 2 shows the cube translated and visualised using SVG (Scalable Vector Graphics).
Figure 2. Translation to SVG Visualisation
This shows the interactive version of the diagram that works in Internet Explorer using the Adobe SVG viewer 3 http://www.cems.uwe.ac.uk/~phale/SVGCubeExample/CubePartDefinitionwithCosts.htm - SVG Viewer download - http://www.adobe.com/svg/viewer/install/.
Figure 2. Translation to SVG Visualisation
This shows the interactive version of the diagram that works in Internet Explorer using the Adobe SVG viewer 3 http://www.cems.uwe.ac.uk/~phale/SVGCubeExample/CubePartDefinitionwithCosts.htm - SVG Viewer download - http://www.adobe.com/svg/viewer/install/.
Next the implementation of this research was illustrated with the more complex example of an aircraft wingbox, using the same approach.
Friday, September 18, 2009
Collaboration and Process Modelling in Engineering and Business using Visualisation and Semantic Web techniques - Conclusion and Further Research
Conclusion
Test implementations assisted with :-
Providing clarity for process modelling and management, by creating a structured open standard visual modelling environment that is usable by non-programmers.
Further research is needed into modelling based on SWRL, to model conditional statements, and OWL-S Editor (Elenius et al., 2005) with UML style diagrams, together with investigation and use of online search facilities for services and process models. The reusable process architectures and process models held in an ontology, could also be translated as necessary between OWL-S and BPEL (Business Process Execution Language) representations. Also, Meta-Programming and Rule-based languages could be used to develop an interface to an end user programming environment. Models could be encoded and checked via languages such as MathLang (Kamareddine et el., 2005).
References
Elenius D, Denker G, Martin D, Gilham F, Khouri J, Sadaati S, Senanayake R, 2005. The OWL-S Editor - A Development Tool for Semantic Web Services, The Semantic Web: Research and Applications, Springer Berlin / Heidelberg.
Kamareddine F, Maarek M, Wells J B, 2005, Toward an Object-Oriented Structure for Mathematical Text, Mathematical Knowledge Management, 4th Int'l Conf., Proceedings LNCS Springer-Verlag.
Miller J A, Baramidze G, 2005, Simulation and the Semantic Web, 2005 Winter Simulation Conference.
Test implementations assisted with :-
Providing clarity for process modelling and management, by creating a structured open standard visual modelling environment that is usable by non-programmers.
* Collaboration, dissemination, reuse and sharing of models using web applications and services.
* Enabling people to model at a high level of abstract conceptual modelling, thereby producing better process models using tools that model at domain level, rather than at code level.
* Development of Semantic Web based process modelling to provide the means for visualisation and calculation/sequencing, together with a decision support engine for model creation and retrieval.
* Increased user involvement for model development allows savings in cost and time taken for process modelling.
* Enhanced availability of process models and interactive visualisation of model results using web browser based software, this will also be an important teaching resource.
Identification of improvements to process efficiency and effectiveness.
* Better interoperability of models and ability to identify common problems missed during creation of standalone spreadsheets. Increased model detail and ease of upgrade with layered architecture of open standard languages to eliminate inconsistencies and allow better decision making.
* New ways of enabling end user interaction, with collaborative development of process models that will allow people more scope to solve problems.
*Enabling task based access to Semantic Web information, e.g. by employees and home users who have no knowledge or interest in the Semantic Web, but who will use tools for particular tasks.
This research tested first steps towards helping to solve problems caused by lack of collaborative modelling in process design. This could also bridge the gap between industry and those advocating the use of modelling/programming using Semantic Web techniques, to improve efficiency and effectiveness.
This research has potential benefit for any problem where end user programming using Semantic Web technology is applicable. This is a very broad range, involving most modelling. The particular areas where the research is most transferable are manufacturing and business modelling, e-learning and provision of models for public understanding of science and engineering, and health and science taxonomy/ontology management.
The research in this field has reinforced the view that Semantic Web based process modelling is an appropriate and robust means of achieving end user objectives. If domain experts are not involved in creation of the model, there is no proper way for the knowledge they are encoding to emerge, or for proper collaboration. This is necessary as each expert is best focused on encapsulating the part of the model that they are most expert in. People need to be involved in model creation if they are to understand the model, decision, and how the decision was made. So there is a need for end user modelling/programming to enable this. Full automation hinders user involvement and traceability, so semi-automated systems that interact with end users and assist with all stages of the model decision are better. If a person goes straight to the answer how can it be expected that they fully understood the question?
Breaking complex mathematics into modularised traceable steps eases management of it, and visualisation, and allows modelling of different scenarios, and these scenarios demonstrate the emergent properties of the model, enabling decision support. BiDirectional Traceability is needed, traceability between nodes/sub-models, and between models, and between suppliers and buyers.
The research made some progress towards allowing end users to concentrate on the domain to be modelled rather than on computing technologies. This research can enable collaborative modelling and interaction, via applying end user programming techniques to enable domain experts such as engineers and business people to create and interact with the knowledge representation themselves, and co-operate to ensure the representations are useful for addressing their problems, with less software creation barriers. Software developers need to enable such systems to make this all possible.
Existing ontologies can be extended for modelling of software systems and engineering systems e.g. PSL, STEPML, UML, SysML can be extended/adapted for use in particular problems.
Further Research
Further research is needed into modelling based on SWRL, to model conditional statements, and OWL-S Editor (Elenius et al., 2005) with UML style diagrams, together with investigation and use of online search facilities for services and process models. The reusable process architectures and process models held in an ontology, could also be translated as necessary between OWL-S and BPEL (Business Process Execution Language) representations. Also, Meta-Programming and Rule-based languages could be used to develop an interface to an end user programming environment. Models could be encoded and checked via languages such as MathLang (Kamareddine et el., 2005).
References
Elenius D, Denker G, Martin D, Gilham F, Khouri J, Sadaati S, Senanayake R, 2005. The OWL-S Editor - A Development Tool for Semantic Web Services, The Semantic Web: Research and Applications, Springer Berlin / Heidelberg.
Kamareddine F, Maarek M, Wells J B, 2005, Toward an Object-Oriented Structure for Mathematical Text, Mathematical Knowledge Management, 4th Int'l Conf., Proceedings LNCS Springer-Verlag.
Miller J A, Baramidze G, 2005, Simulation and the Semantic Web, 2005 Winter Simulation Conference.
Friday, September 11, 2009
Petition forces No 10 apology to WWII code breaker Alan Turing
"PM apology after Turing petition" - BBC News update - http://news.bbc.co.uk/1/hi/technology/8249792.stm
Gordon Brown has said he was sorry for the "appalling" way World War II code breaker Alan Turing was treated for being gay.
A petition on the No 10 website had called for a posthumous government apology to the computer pioneer.
In 1952 Turing was prosecuted for gross indecency after admitting a sexual relationship with a man. Two years later he killed himself.
The campaign was the idea of computer scientist John Graham-Cumming.
He was seeking an apology for the way the mathematician was treated after his conviction. He also wrote to the Queen to ask for Turing to be awarded a posthumous knighthood.
The campaign was backed by Ian McEwan, scientist Richard Dawkins and gay-rights campaigner Peter Tatchell. The petition posted on the Downing Street website attracted thousands of signatures.
Mr Brown said: "While Mr Turing was dealt with under the law of the time and we can't put the clock back, his treatment was of course utterly unfair and I am pleased to have the chance to say how deeply sorry I and we all are for what happened to him."
Profile: Alan Turing - BBC - Tortured Genius - http://news.bbc.co.uk/1/hi/uk/8250592.stm.
Gordon Brown has said he was sorry for the "appalling" way World War II code breaker Alan Turing was treated for being gay.
A petition on the No 10 website had called for a posthumous government apology to the computer pioneer.
In 1952 Turing was prosecuted for gross indecency after admitting a sexual relationship with a man. Two years later he killed himself.
The campaign was the idea of computer scientist John Graham-Cumming.
He was seeking an apology for the way the mathematician was treated after his conviction. He also wrote to the Queen to ask for Turing to be awarded a posthumous knighthood.
The campaign was backed by Ian McEwan, scientist Richard Dawkins and gay-rights campaigner Peter Tatchell. The petition posted on the Downing Street website attracted thousands of signatures.
Mr Brown said: "While Mr Turing was dealt with under the law of the time and we can't put the clock back, his treatment was of course utterly unfair and I am pleased to have the chance to say how deeply sorry I and we all are for what happened to him."
Profile: Alan Turing - BBC - Tortured Genius - http://news.bbc.co.uk/1/hi/uk/8250592.stm.
Wednesday, September 09, 2009
VoCampBristol 2009 - Thursday 10th, Friday 11th September
These are the details for - The 9th ever VoCamp, and the first in Bristol.
Thursday 10th and Friday 11th September 2009. Note that this date has been changed due to a conflict - http://vocamp.org/wiki/VoCampBristol2009.
WhatIsVoCamp
What's the Problem?
Continued growth of the Web of Data/Semantic Web is heavily dependent on the availability of vocabularies/ontologies that can be used to publish data. While a number of key vocabularies are in widespread use, there are also many areas with little or no vocabulary coverage, hindering the ability to publish data in these domains.
Peter Mika outlines some of the issues he sees with the current state of vocabularies on the Semantic Web in his blog post What’s wrong with vocabularies on the Semantic Web?
What is VoCamp?
VoCamp is a series of informal events where people can spend some dedicated time creating lightweight vocabularies/ontologies for the Semantic Web/Web of Data. The emphasis of the events is not on creating the perfect ontology in a particular domain, but on creating vocabs that are good enough for people to start using for publishing data on the Web. The intention is to follow a "paper first, laptops second" format, where the modelling is done initially on paper and only later committed to code. The VoCamp idea is influenced by BarCamp, although the emphasis is different. Whereas BarCamps are oriented to demos and presentations, VoCamps are oriented to hands-on technical work and practical outputs; any presentations and demos should be short, highly on-topic to the vocabulary development process, and limited in number, to leave plenty of time for hacking on new vocabularies.
What Next?
The first VoCamp event took place in Oxford, UK in September 2008 (VoCampOxford2008), the second took place in Galway, Ireland in November 2008 (VoCampGalway2008), and the third, and first ever in the US took place in Austin, Texas (VoCampAustin2009) followed immediately by another one in Ibiza, Spain in April 2009 (VoCampIbiza2009).
Thursday 10th and Friday 11th September 2009. Note that this date has been changed due to a conflict - http://vocamp.org/wiki/VoCampBristol2009.
WhatIsVoCamp
What's the Problem?
Continued growth of the Web of Data/Semantic Web is heavily dependent on the availability of vocabularies/ontologies that can be used to publish data. While a number of key vocabularies are in widespread use, there are also many areas with little or no vocabulary coverage, hindering the ability to publish data in these domains.
Peter Mika outlines some of the issues he sees with the current state of vocabularies on the Semantic Web in his blog post What’s wrong with vocabularies on the Semantic Web?
What is VoCamp?
VoCamp is a series of informal events where people can spend some dedicated time creating lightweight vocabularies/ontologies for the Semantic Web/Web of Data. The emphasis of the events is not on creating the perfect ontology in a particular domain, but on creating vocabs that are good enough for people to start using for publishing data on the Web. The intention is to follow a "paper first, laptops second" format, where the modelling is done initially on paper and only later committed to code. The VoCamp idea is influenced by BarCamp, although the emphasis is different. Whereas BarCamps are oriented to demos and presentations, VoCamps are oriented to hands-on technical work and practical outputs; any presentations and demos should be short, highly on-topic to the vocabulary development process, and limited in number, to leave plenty of time for hacking on new vocabularies.
What Next?
The first VoCamp event took place in Oxford, UK in September 2008 (VoCampOxford2008), the second took place in Galway, Ireland in November 2008 (VoCampGalway2008), and the third, and first ever in the US took place in Austin, Texas (VoCampAustin2009) followed immediately by another one in Ibiza, Spain in April 2009 (VoCampIbiza2009).
Thursday, September 03, 2009
User Driven Modelling/Programming Definition
User Driven Modelling/Programming - is a technique for combining visualised colour coded and linked equations, into a system which models a whole program, and visualises the entirety of a program that performs modelling/calculation. This system is created via a collaborative ontology/database and translated in an automated way from the information source to the result output, in order to allow computer end-users to create programs/models, and link these, and in order for programmers to create program development systems. This is a human/computer translation and system creation system.
A particular research area I want and need to research is that of developing a modelling/programming user interface further in order to simplify tasks enough that non-programmer engineers can begin to program/model.
My research is described on my Google Sites pages - http://sites.google.com/site/userdrivenmodellingprogramming/.
A particular research area I want and need to research is that of developing a modelling/programming user interface further in order to simplify tasks enough that non-programmer engineers can begin to program/model.
My research is described on my Google Sites pages - http://sites.google.com/site/userdrivenmodellingprogramming/.
Subscribe to:
Posts (Atom)