The meeting discussed issues identified by Tobias Kunze related to mapping a PHP application use case to the TOSCA specification. Tobias had created node templates for various elements and identified 9 issues. The group discussed potential solutions to the issues, such as using nested nodes to represent components, introducing a "final" attribute to node types, and agreeing that requirements/capabilities are more flexible than inheritance relationships. Consensus was reached on some issues while others require further review.
The Semantic Web is about to grow up. By efforts such as the Linked Open Data initiative, we finally find ourselves at the edge of a Web of Data becoming reality. Standards such as OWL 2, RIF and SPARQL 1.1 shall allow us to reason with and ask complex structured queries on this data, but still they do not play together smoothly and robustly enough to cope with huge amounts of noisy Web data. In this talk, we discuss open challenges relating to querying and reasoning with Web data and raise the question: can the emerging Web of Data ever catch up with the now ubiquitous HTML Web?
The Semantic Web is about to grow up. By efforts such as the Linked Open Data initiative, we finally find ourselves at the edge of a Web of Data becoming reality. Standards such as OWL 2, RIF and SPARQL 1.1 shall allow us to reason with and ask complex structured queries on this data, but still they do not play together smoothly and robustly enough to cope with huge amounts of noisy Web data. In this talk, we discuss open challenges relating to querying and reasoning with Web data and raise the question: can the emerging Web of Data ever catch up with the now ubiquitous HTML Web?
This presentation was delivered by Tommie Usdin of Mulberry Technologies during the NISO event, XML for Standards Publishers, held on April 24, 2017 in Washington Dc.
Open Source Library System Software: Libraries Are Doing it For Themselvesloriayre
One of the great advantages of an Open Source Library System (OSLS) such as Koha or Evergreen is the ability to empower staff and optimize the user's experience by getting involved in improving the software. This is in contrast to the traditional integrated library system (ILS) model where all the software development was done by "the vendor," creating a condition of "learned helplessness" on the part of library staff. By making the transition to OSLS, you can shift the culture of your organization from "learned helplessness" to one in which everyone can contribute to enhancing their work environment.
This webinar will describe all the ways to get involved with an OSLS project -- even if you aren't a programmer. By the end of the webinar, you will understand why involving your organization in an OSLS project creates opportunities for delivering new services to customers and optimizing the work of your staff.
Open Source Community Metrics for FOSDEMDawn Foster
Presented in the Community DevRoom at FOSDEM 2013. A longer version of this presentation is available at http://fastwonderblog.com/2012/11/05/open-source-community-metrics-linuxcon-barcelona/
The Task Management project is an simple and easy-to-use plugin for IBM Lotus Notes/Domino and IBM Lotus Sametime. It collects tasks from different applications via web services.
This presentation presents the Task Management project on OpenNTF.org. It describes the architecture, user interface and how interfaces to applications can be created.
Open Source Community Metrics LibreOffice ConferenceDawn Foster
Open Source Community Metrics: Tips and Techniques for Measuring Participation
Do you know what people are really doing in your open source project? Having good community data and metrics for your open source project is a great way to understand what works and what needs improvement over time, and metrics can also be a nice way to highlight contributions from key project members. This session will focus on tips and techniques for collecting and analyzing metrics from tools commonly used by open source projects. It's like people watching, but with data.
Design Suggestions for EPA’s One Wiki in Support of the EPA OGD Work Groupguest8c518a8
1. Background:
1.1 Supporting EPA's Top Priorities
1.2 An EPA EA Roadmap
1.3 Solution Architecture 2010
1.4 My List of Action Items
1.5 EPA’s OGD Workgroup
1.6 EPA’s New Social Media Policy
2. EPA’s One Wiki:
2.1 Initial Impressions
2.2 The Environment in Wikipedia
2.3 Web 2.0 Whitepaper Pilot Wiki
2.4 Information / Data Model
2.5 Sheetster for Data.gov/semantic
3. Recommendations
Design Suggestions for EPA’s One Wiki in Support of the EPA OGD Work Groupguest8c518a8
1. Background:
1.1 Supporting EPA's Top Priorities
1.2 An EPA EA Roadmap
1.3 Solution Architecture 2010
1.4 My List of Action Items
1.5 EPA’s OGD Workgroup
1.6 EPA’s New Social Media Policy
2. EPA’s One Wiki:
2.1 Initial Impressions
2.2 The Environment in Wikipedia
2.3 Web 2.0 Whitepaper Pilot Wiki
2.4 Information / Data Model
2.5 Sheetster for Data.gov/semantic
3. Recommendations
This presentation was delivered by Tommie Usdin of Mulberry Technologies during the NISO event, XML for Standards Publishers, held on April 24, 2017 in Washington Dc.
Open Source Library System Software: Libraries Are Doing it For Themselvesloriayre
One of the great advantages of an Open Source Library System (OSLS) such as Koha or Evergreen is the ability to empower staff and optimize the user's experience by getting involved in improving the software. This is in contrast to the traditional integrated library system (ILS) model where all the software development was done by "the vendor," creating a condition of "learned helplessness" on the part of library staff. By making the transition to OSLS, you can shift the culture of your organization from "learned helplessness" to one in which everyone can contribute to enhancing their work environment.
This webinar will describe all the ways to get involved with an OSLS project -- even if you aren't a programmer. By the end of the webinar, you will understand why involving your organization in an OSLS project creates opportunities for delivering new services to customers and optimizing the work of your staff.
Open Source Community Metrics for FOSDEMDawn Foster
Presented in the Community DevRoom at FOSDEM 2013. A longer version of this presentation is available at http://fastwonderblog.com/2012/11/05/open-source-community-metrics-linuxcon-barcelona/
The Task Management project is an simple and easy-to-use plugin for IBM Lotus Notes/Domino and IBM Lotus Sametime. It collects tasks from different applications via web services.
This presentation presents the Task Management project on OpenNTF.org. It describes the architecture, user interface and how interfaces to applications can be created.
Open Source Community Metrics LibreOffice ConferenceDawn Foster
Open Source Community Metrics: Tips and Techniques for Measuring Participation
Do you know what people are really doing in your open source project? Having good community data and metrics for your open source project is a great way to understand what works and what needs improvement over time, and metrics can also be a nice way to highlight contributions from key project members. This session will focus on tips and techniques for collecting and analyzing metrics from tools commonly used by open source projects. It's like people watching, but with data.
Design Suggestions for EPA’s One Wiki in Support of the EPA OGD Work Groupguest8c518a8
1. Background:
1.1 Supporting EPA's Top Priorities
1.2 An EPA EA Roadmap
1.3 Solution Architecture 2010
1.4 My List of Action Items
1.5 EPA’s OGD Workgroup
1.6 EPA’s New Social Media Policy
2. EPA’s One Wiki:
2.1 Initial Impressions
2.2 The Environment in Wikipedia
2.3 Web 2.0 Whitepaper Pilot Wiki
2.4 Information / Data Model
2.5 Sheetster for Data.gov/semantic
3. Recommendations
Design Suggestions for EPA’s One Wiki in Support of the EPA OGD Work Groupguest8c518a8
1. Background:
1.1 Supporting EPA's Top Priorities
1.2 An EPA EA Roadmap
1.3 Solution Architecture 2010
1.4 My List of Action Items
1.5 EPA’s OGD Workgroup
1.6 EPA’s New Social Media Policy
2. EPA’s One Wiki:
2.1 Initial Impressions
2.2 The Environment in Wikipedia
2.3 Web 2.0 Whitepaper Pilot Wiki
2.4 Information / Data Model
2.5 Sheetster for Data.gov/semantic
3. Recommendations
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
UiPath Test Automation using UiPath Test Suite series, part 3DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 3. In this session, we will cover desktop automation along with UI automation.
Topics covered:
UI automation Introduction,
UI automation Sample
Desktop automation flow
Pradeep Chinnala, Senior Consultant Automation Developer @WonderBotz and UiPath MVP
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
SAP Sapphire 2024 - ASUG301 building better apps with SAP Fiori.pdfPeter Spielvogel
Building better applications for business users with SAP Fiori.
• What is SAP Fiori and why it matters to you
• How a better user experience drives measurable business benefits
• How to get started with SAP Fiori today
• How SAP Fiori elements accelerates application development
• How SAP Build Code includes SAP Fiori tools and other generative artificial intelligence capabilities
• How SAP Fiori paves the way for using AI in SAP apps
Dev Dives: Train smarter, not harder – active learning and UiPath LLMs for do...UiPathCommunity
💥 Speed, accuracy, and scaling – discover the superpowers of GenAI in action with UiPath Document Understanding and Communications Mining™:
See how to accelerate model training and optimize model performance with active learning
Learn about the latest enhancements to out-of-the-box document processing – with little to no training required
Get an exclusive demo of the new family of UiPath LLMs – GenAI models specialized for processing different types of documents and messages
This is a hands-on session specifically designed for automation developers and AI enthusiasts seeking to enhance their knowledge in leveraging the latest intelligent document processing capabilities offered by UiPath.
Speakers:
👨🏫 Andras Palfi, Senior Product Manager, UiPath
👩🏫 Lenka Dulovicova, Product Program Manager, UiPath
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Transcript: Selling digital books in 2024: Insights from industry leaders - T...
Tosca tc minutes 2012 06-07
1. Draft Minutes of OASIS TOSCA TC Meeting
URL OF CALENDAR EVENT (this also has meeting attendance): https://www.oasis-
open.org/apps/org/workgroup/tosca/event.php?event_id=32586
DATE: June 7, 2012
TIME: 12:00 noon EDT
Scribe: Richard Probst (SAP)
Meeting was quorate: YES
Observers:
Cloudsoft Corporation Limited Rich Miller
Hewlett-Packard Bryan Murray
Roster
[The co-chairs maintain the roster based on the TC Process rules. Since rights are
gained/lost at the end of a meeting and the co-chairs update between meetings, the roster
should be accurate at the start of each meeting. You can view it at: http://www.oasis-
open.org/apps/org/workgroup/tosca/members/roster.php]
Approval of Minutes
Simon Mosermoved for the below draft minutes to be approved. Seconded by Paul Lipton.
Date of meeting: May 31, 2012: https://www.oasis-
open.org/apps/org/workgroup/tosca/download.php/46146/TOSCA%20TC%20Minutes%202012-05-
31.docx
Motion PASSES by unanimous consent
Approved Agenda:
Based on review and discussion of the proposed agenda, Simon Moser moved for the below
agenda to be approved. Seconded by Paul Lipton.Motion PASSES by unanimous consent.
PROPOSED AGENDA
Welcome / Roll for those who cannot record their own attendance
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* May 31: https://www.oasis-
open.org/apps/org/workgroup/tosca/download.php/46146/TOSCA%20TC%20Minutes%202012-05-
31.docx
* Thanks to Dale Moberg for scribing
Editors status report
* Problems, questions, etc.
Spec issues/Proposals/Bugs queue (time permitting)
2. NOTE: When practical, JIRA issues/proposals will be evaluated in the context of use cases detailed or
subtasked in TOSCA-8
* TOSCA-8: http://tools.oasis-open.org/issues/browse/TOSCA-8 (Use Case Bucket)
** Issues Related to Pretty Normal PHP Application in the formation of a Service Template - Tobias
Kunze
* TOSCA-17: http://tools.oasis-open.org/issues/browse/TOSCA-17 (Packaging Format for TOSCA)
** Follow-up on last week's discussion.
** Suggested strawpoll: consensus on eliminating Java specifics from packaging format and using
TOSCA-extended ZIP format?
General discussion: What are the primary remaining meta-language (spec only) gaps?
Continued: Spec issues/Proposals/Bugs queue (time permitting)
* TOSCA-12: http://tools.oasis-open.org/issues/browse/TOSCA-12 (Set of Basic Node Types for Defining
Topology Templates)
* TOSCA-11: http://tools.oasis-open.org/issues/browse/TOSCA-11 (Set of Fundamental Lifecycle
Operations)
* TOSCA-13 http://tools.oasis-open.org/issues/browse/TOSCA-13 (definitions of portability and
interoperability) [Subtask of TOSCA-16]
* TOSCA-16 http://tools.oasis-open.org/issues/browse/TOSCA-16 (Primer Deliverables - Uber Issue)
* TOSCA-18: http://tools.oasis-open.org/issues/browse/TOSCA-18 (Resource Requirements and
Capabilities)
* TOSCA-14: http://tools.oasis-open.org/issues/browse/TOSCA-14 (Policy Languages) [subtask of
TOSCA-3]
* TOSCA-3: http://tools.oasis-open.org/issues/browse/TOSCA-3 (Grouping element for policies - Uber
Issue)
Tabled Issues/Proposals/Bugs
* TOSCA-9: http://tools.oasis-open.org/issues/browse/TOSCA-9 (Relationship of Plans to
Infrastructure)
General discussion (time permitting)
* REMINDER: While a general approach can be decided by motion, specific technical proposals need to
be JIRA issues
* Next meeting
* AOB
Other Motions and Results (broken out from below):
None
Motion to Adjourn:
MOTION to adjourn by Simon Moser.Second byPaul Lipton. Motion PASSES by unanimous
consent. Meeting adjourned at 1:30 PMEDT
3. Raw Chat Log:
Paul Lipton (Co-Chair) C: Hi, all. Welcome to today's meeting of the TOSCA TC
(starting promptly at 5 minutes after the hour)!
Attendance Recording: Participants are responsible to log their attendance on
the Kavi calendar event at http://www.oasis-
open.org/apps/org/workgroup/tosca/event.php?event_id=32585. This page also
has phone bridge, proposed agenda, links to resources and more. Please look
now, if you have not already done so.
When you join the meeting, use this page to record your attendance by
clicking "Record My Attendance". If you are not on the internet, you can
request the co-chair to record your attendance on your behalf.
PHONE BRIDGE AND WEB CONFERENCING: THIS MEETING ONLY. PLEASE SEE THE EMAIL
AT:
https://www.oasis-
open.org/apps/org/workgroup/tosca/email/archives/201206/msg00005.html
Scribe Queue (we need volunteers!):
Michael Schuster (21 June)
Simon Moser will be running today's meeting.
anonymous1 morphed into Dale Moberg, Axwat
Dale Moberg, Axwat morphed into Dale Moberg, Axway
anonymous morphed into Simon Moser (co-chair)
Simon Moser (co-chair): Hello everybody
Simon Moser (co-chair): Please note that the teleconference information has
changed - today we need to use a different call-in number
anonymous morphed into Bryan Haynie (VCE)
Simon Moser (co-chair):https://www.oasis-
open.org/apps/org/workgroup/tosca/email/archives/201206/msg00005.html
anonymous morphed into Paul Zhang (Huawei)
Paul Lipton (Co-Chair) C: I seem to be on mute. How do you get off mute on
this bridge (and hi)?
Aaron(Huawei): Can anyone tell me what the access code is for the meeting?
Paul Lipton (Co-Chair) C: Also, the web conference did not work with Google
Chrome for me, FYI*.
Thomas Spatzier (IBM): @Paul: try *6
Simon Moser (co-chair): 12533845
Simon Moser (co-chair): is the access code
Paul Lipton (Co-Chair) C: Tried *6 and it didn't work. Will dial in again.
Aaron(Huawei): Thanks
anonymous morphed into Doug Neuse (CA)
Richard Probst (SAP) morphed into scribe - Richard Probst (SAP)
scribe - Richard Probst (SAP): meeting is quorate
Simon Moser (co-chair): P R O P O S E D A G E N D A
Welcome / Roll for those who cannot record their own attendance
Co-chair appoints a scribe
Review/approve draft proposed agenda
Review/approve draft minutes
* May 31: https://www.oasis-
open.org/apps/org/workgroup/tosca/download.php/46146/TOSCA%20TC%20Minutes%202
012-05-31.docx
* Thanks to Dale Moberg for scribing
4. Editors status report
* Problems, questions, etc.
Spec issues/Proposals/Bugs queue (time permitting)
NOTE: When practical, JIRA issues/proposals will be evaluated in the context
of use cases detailed or subtasked in TOSCA-8
* TOSCA-8: http://tools.oasis-open.org/issues/browse/TOSCA-8 (Use Case
Bucket)
** Issues Related to Pretty Normal PHP Application in the formation of a
Service Template - Tobias Kunze
* TOSCA-17: http://tools.oasis-open.org/issues/browse/TOSCA-17 (Packaging
Format for TOSCA)
** Follow-up on last week's discussion.
** Suggested strawpoll: consensus on eliminating Java specifics from
packaging format and using TOSCA-extended ZIP format?
General discussion: What are the primary remaining meta-language (spec only)
gaps?
Continued: Spec issues/Proposals/Bugs queue (time permitting)
* TOSCA-12: http://tools.oasis-open.org/issues/browse/TOSCA-12 (Set of Basic
Node Types for Defining Topology Templates)
* TOSCA-11: http://tools.oasis-open.org/issues/browse/TOSCA-11 (Set of
Fundamental Lifecycle Operations)
* TOSCA-13 http://tools.oasis-open.org/issues/browse/TOSCA-13 (definitions of
portability and interoperability) [Subtask of TOSCA-16]
* TOSCA-16 http://tools.oasis-open.org/issues/browse/TOSCA-16 (Primer
Deliverables - Uber Issue)
* TOSCA-18: http://tools.oasis-open.org/issues/browse/TOSCA-18 (Resource
Requirements and Capabilities)
* TOSCA-14: http://tools.oasis-open.org/issues/browse/TOSCA-14 (Policy
Languages) [subtask of TOSCA-3]
* TOSCA-3: http://tools.oasis-open.org/issues/browse/TOSCA-3 (Grouping
element for policies - Uber Issue)
Tabled Issues/Proposals/Bugs
* TOSCA-9: http://tools.oasis-open.org/issues/browse/TOSCA-9 (Relationship of
Plans to Infrastructure)
General discussion (time permitting)
* REMINDER: While a general approach can be decided by motion, specific
technical proposals need to be JIRA issues
* Next meeting
* AOB
Paul Lipton (Co-Chair) C: Sorry about the phone bridge and web access, but I
wasn't sure I'd have connectivity.
Paul Lipton (Co-Chair) C: Simon kindly provided both.
Paul Lipton (Co-Chair) C: Paul seconds motion to approve agenda
scribe - Richard Probst (SAP): Simon moves agenda, Paul seconds
scribe - Richard Probst (SAP): agenda accepted without objection
Paul Lipton (Co-Chair) C:@Richard, just wanted to see if I could type faster
than you, Richard.
scribe - Richard Probst (SAP): Simon moves to accept minutes, Paul seconds
scribe - Richard Probst (SAP): minutes accepted without objection
5. scribe - Richard Probst (SAP): editor update from Thomas: work in progress
but nothing to discuss this week
scribe - Richard Probst (SAP): continue discussion on TOSCA-8
Paul Lipton (Co-Chair) C:Wanna put this in the web conference?
scribe - Richard Probst (SAP): Tobias has been mapping his use-case to TOSCA,
has come up with about 9 node types
Alex Heneveld (Cloudsoft): I'm on Chrome and it's okay for me ... but that's
no guarantee
Bryan Haynie (VCE): chrome works for me
scribe - Richard Probst (SAP): Tobias created node templates for the elements
of his PHP use-case, using YAML (hopefully easier to parse)
scribe - Richard Probst (SAP): PHP use-case expects a PaaS -- the service
template references services provided by the platform
scribe - Richard Probst (SAP): Tobias has not yet added relationships to
service template
scribe - Richard Probst (SAP): showed internal document how RedHat thinks of
relationships -- they have operations
scribe - Richard Probst (SAP): Tobias has identified 9 issues
Paul Lipton (Co-Chair) C: # ISSUES
8 #
9 # 1 Node Type components need to be addressable, either via interfaces or
10 # in a more structured way. Component role must be understood (e.g.
11 # what is PHP, what is ZF)
12 # Suggest to introduce "Component" as a technical term, denoting the,
13 # well, components of a NodeType. Also, suggest that these
14 # components are addressed using period (".") as a separator
15 # 2 Some NodeTypes are "abstract", e.g. "myapp". Static files (kind of)
16 # become part of *staticserver and Code (kind of) becomes part of
17 # *zendserver.php
18 # 3 "Require"/"Provide" is a much more flexible mechanism than just
19 # referencing NodeTypes with "DerivedFrom".
20 # 4 The inheritance aspects of the "DerivedFrom" element need to be
21 # complemented with a separate, immutable form that occurs when a
22 # NodeType is provided by the platform. E.g.
23 # 5 When a NodeType is provided, the ability to express requirements
24 # (e.g. applying to resource allocation or specific run modes) becomes
25 # important
26 # 6 The NodeType ID field is superfluous
27 # 7 NodeTypes should have a "Version" field
28 # 8 NodeTypeProperties need "name", "value", and optionally maybe "type"
29 # 9 Naming and capitalization is odd, e.g. "NodeTypeProperties" vs
30 # "requestURI" vs "name"
31
Frank Leymann (IBM): Comment: I don't understand why something that is
superfluous (item #6) results in an issue.
Paul Lipton (CA) A morphed into Paul Lipton (Co-chair) A
Aaron(Huawei):execue me, but could anyone tell me the link for web
conference? I can't find the new link for today's meeting
Matt Rutkowski (IBM)1: Simon can you please record my attendance
scribe - Richard Probst (SAP): Thomas comments on issue #1 -- isn't this the
same as Deployment Artifact?
scribe - Richard Probst (SAP): at least the concept is already the same
anonymous morphed into Rich Miller
scribe - Richard Probst (SAP): Tobias agrees this seems similar, but should
PHP component be seen as a DA? PHP component is made available thru Apache as
library
6. Aaron(Huawei): ? I see Paul's (Co-chair) message in WebEX, but can't find the
link
Paul Lipton (Co-Chair) C: @Frank, let's go through each issue that Tobias has
identified. Please reserve for item #6.
scribe - Richard Probst (SAP): Tobias: more general issue is that elements
need to know about components of other elements
KoertStruijk (CA): Lotus Live:
1. Go to the URL - http://www.webdialogs.com
2. Click 'Join a Meeting' button in the top right corner of the page
3. Enter the Conference ID 1204304
4. Enter your name and email address
5. Click the 'Log In' button
Paul Lipton (Co-Chair) C: @Aaron, see email at: https://www.oasis-
open.org/apps/org/workgroup/tosca/email/archives/201206/msg00005.html
scribe - Richard Probst (SAP): Thomas thinks a node contained in a node can
satisfy the need to name components, without introducing a new top-level
concept
Aaron(Huawei): @Koert: Many thanks. Got it.
scribe - Richard Probst (SAP): Tobias will try to use nested nodes to
represent components
scribe - Richard Probst (SAP): and also will try using DAs, and also doing it
with a new "component" concept, to see which works best
Thomas Spatzier (IBM): So "nested" Nodes would be: NodeTemplate A (of
NodeType a) -> contains relationship ->NodeTemplate B (of NodeType b)
scribe - Richard Probst (SAP):<scribe hat off> +1 to Requires/Provides !
Alex Heneveld (Cloudsoft): +1 require/provide definitely
scribe - Richard Probst (SAP): Paul asks to test consensus around Tobias's
issues
scribe - Richard Probst (SAP): Tobias: issue 4 means a service provided by a
platform should not be modeled as DerivedFrom since it cannot be modified
Derek Palma (Vnomic): To me point 3 means: Node Type derivation should not
allow extension beyond the restricted domains of the super Node Type
Frank Leymann (IBM): Can we solve #4 by introducing a "final" attribute for
properties...?
Derek Palma (Vnomic): that is one common way
scribe - Richard Probst (SAP):<scribe hat off> how would over-provisioning be
modeled?
Derek Palma (Vnomic): but it really has to enforce that the domain is not
expanded. I.e. it's a subset.
Simon Moser (co-chair): (co-chair hat off) +1 to Franks suggestion to
introduce things like "final" on node type attributes
scribe - Richard Probst (SAP): Tobias agrees a "final" attribute could be a
solution to issue 4
scribe - Richard Probst (SAP): Simon heard consensus on 2 and 3, agreement
that something like 4 is needed, issue 1 needs to be reviewed
scribe - Richard Probst (SAP): issue 5 is more a demonstration of need than
an issue
scribe - Richard Probst (SAP): Simon (with co-chair hat off) says issue 6
(NodeType ID is superfluous) may apply to YAML but not to other
implementations
Thomas Spatzier (IBM): In TOSCA in the current spec, we state that the fully-
qualified name (QName) of a NodeType is built from targetNamespace and id.
Therefore it is required.
scribe - Richard Probst (SAP): Tobias: 3 choices: (1) name is required, ID is
optional; (2) ID is required, name is optional; (3) YAML uses name, XML uses
ID
7. Thomas Spatzier (IBM): The name attribute is optional and meant to be a
human-readable name.
Derek Palma (Vnomic): id guarantees uniqueness. name is not necessarily
unique. We need some notion of identity to be carried across all
serializations.
Frank Leymann (IBM): +1 to derek
scribe - Richard Probst (SAP): Marv says names may not be unique
scribe - Richard Probst (SAP): Tobias agrees names might not be unique, which
would be a problem
Matt Rutkowski (IBM): You would have to qualify an ID as a GUID and decide if
you want it URI based or not
Paul Lipton (Co-Chair) C: @Marv, did you say id may not be unique, either?
Matt Rutkowski (IBM): or a UUID for instances
Paul Lipton (Co-Chair) C: gotcha
Marv Waschke (CA): @Matt Exactly!
Matt Rutkowski (IBM): then you would have to decide if the UUIDs are time
dependent or not and reference approved mechanisms/algorithms
Marv Waschke (CA): Global uniqueness is always an issue. I prefer a name
space approach, myself.
scribe - Richard Probst (SAP): Tobias proposes to replace ID with human-
readable name, to remove 1 "geek field"
Matt Rutkowski (IBM): Then TOSCA would have to decide who the "authority"
would be (DNS may not work)
KoertStruijk (CA): You might want to be able to have a group of items - if
you reuse the same name, the id allows you to still individually address the
items. I can't think of a use case for this at the moment, though.
scribe - Richard Probst (SAP): Tobias has similar reaction to some of the
details of the packaging proposal -- remove the geek fields!
Paul Lipton (Co-Chair) C: Do Service Template names really need to be
globally unique (just wonderin')?
Paul Lipton (Co-Chair) C: I mean names within a Service Template. I guess so,
if you were to import, for example.
scribe - Richard Probst (SAP): Derek says that translation between XML and
YAML need to be handled carefully to preserve what is guaranteed to be unique
Marv Waschke (CA): If templates are to be shared, it seems awkward to have to
change the id as it moves from installation to installation.
scribe - Richard Probst (SAP): Especially if you translate back and forth XML
to YAML to XML to YAML
Paul Lipton (Co-Chair) C: So, is consensus that we need to make this work on
YAML and on XML side? Does this need to be a JIRA issue?
Paul Lipton (Co-Chair) C: Oops! Somebody just asked the same thing.
Alex Heneveld (Cloudsoft): ID=1 is not likely be globally unique
Alex Heneveld (Cloudsoft): what about ID="user-agent", with convention it
should be locally unique, inheriting a namespace which gives it global
uniqueness
scribe - Richard Probst (SAP): Simon proposes we should open JIRA issues on
most / all of Tobias's issues
scribe - Richard Probst (SAP): Paul would prefer not to open so many tiny
JIRA issues -- maybe just aggregate as 1
scribe - Richard Probst (SAP): Thomas says issue 8 is already in the spec
scribe - Richard Probst (SAP): Thomas says capitalization (issue 9) was on
purpose -- maybe only a problem when translating to YAML?
scribe - Richard Probst (SAP): Tobias argues for being language-agnostic and
readable -- remove the Java-isms
Marv Waschke (CA): @alex- that would satisfy my concerns.
Frank Leymann (IBM): I don't understand at all what the Java-isms are.
8. scribe - Richard Probst (SAP): Simon agrees with goal of maximizing adoption,
so let's look at the proposals
Frank Leymann (IBM): The style of naming currently used in TOSCA (e.g.) can
be found in many other standards too.
scribe - Richard Probst (SAP): Paul has created TOSCA-20 and asks Tobias to
fill with references to today's document and today's minutes
Derek Palma (Vnomic): Can we get a list of what these Java-isms are because
at the XML level they are not obvious to me.
Frank Leymann (IBM): +1 to Derek
scribe - Richard Probst (SAP): Paul asks re consensus on issues 6 thru 9
scribe - Richard Probst (SAP): Tobias likes idea of making ID a string, but
then why not call it "name"
Thomas Spatzier (IBM): ID can be a string today.
Thomas Spatzier (IBM): It's of type xs:ID
Derek Palma (Vnomic): We have to have a notion of identity for uniqueness. We
don't need to dictate this for specific serializations.
Alex Heneveld (Cloudsoft): would it be useful to be able to refer to
NodeTypes defined in other projects?
Alex Heneveld (Cloudsoft): +1 ... ID and NAME serve the same function don't
they?
scribe - Richard Probst (SAP): Paul asks if we should remove ID? Tobias says
eliminate either name or ID
Sundaresh(CA) : Agree with Tobias. Remove ID
scribe - Richard Probst (SAP): Marv agrees with Tobias
Derek Palma (Vnomic): Currently we have ID and display name. We have to have
ID.
Thomas Spatzier (IBM): name is optional
Doug Davis (IBM): why not keep a user-friendly "name" ?
Frank Leymann (IBM): IDs are for uniqueness, Names are for humans
Doug Davis (IBM): exactly
Frank Leymann (IBM): names are optional, if you don't like them, omit then
Matt Rutkowski (IBM): I disagree
Doug Davis (IBM): names do not need to be unique at all
Matt Rutkowski (IBM): Names and IDs are necessary
Frank Leymann (IBM): Many XML based standards work exactly the same as we
have it in TOSCA today
Matt Rutkowski (IBM): Please see comments I made above
scribe - Richard Probst (SAP): Derek says we need ID in XML, and we can map
it when translating to YAML
Doug Davis (IBM): ID should be globally unique, Name should be optional and
not requirement for it to be unique. Make it clear that Name is for humans.
Matt Rutkowski (IBM): +1 Doug
Matt Rutkowski (IBM): GUID at the very least
scribe - Richard Probst (SAP): Tobias asks if ID is required by XML
validator?
Alex Heneveld (Cloudsoft): can ID be something like "user-agent" ?
Frank Leymann (IBM): +1 to Doug, that's in the spec today
Alex Heneveld (Cloudsoft): best of both worlds
Thomas Spatzier (IBM): @Alex: Yes, it can.
Doug Davis (IBM): to me "Name" goes along with a "description" type of field
- for humans - provider shouldn't do anything with them except echo them back
to clients.
Alex Heneveld (Cloudsoft): thanks @Thomas. great. nice if these _files_ can
be written by a user ... if we use class-name style for ID's that's possible
harder if i'm expected to write 243A4E0
scribe - Richard Probst (SAP): Derek says don't worry about this, just
provide a (good) translator
9. scribe - Richard Probst (SAP): from XML to YAML and vice versa
Doug Davis (IBM): that's a yaml issue, not a tosca model issue, no?
scribe - Richard Probst (SAP): Tobias doesn't see why we have to use XML IDs
Doug Davis (IBM): maybe some serializations won't expose all fields - would
be a shame but that's their choice as long as those fields are optional.
Thomas Spatzier (IBM): If the XSD type is xs:ID, the XML processor ensures
that the id is unique in the document.
Thomas Spatzier (IBM): For global uniqueness we have the namespace in
addition.
scribe - Richard Probst (SAP): Simon: let's split the issues into those we
have consensus on and those we still need to debate
scribe - Richard Probst (SAP): Paul asks Tobias to create TOSCA-21 for just
his issue 6
Matt Rutkowski (IBM): Namespace does NOT guarantee uniqueness unless
"authority" guarantees it
Tobias Kunze (Red Hat): @Thomas: but XML doesn't force you to do it that way
scribe - Richard Probst (SAP): Simon moves to adjourn, Paul seconds
Matt Rutkowski (IBM): the discussion of GUID is too XML centric
Doug Davis (IBM): btw - you don't need a motion to end the meeting if your at
the designated endtime
Thomas Spatzier (IBM): But nice to leverage features of the XML processor.
scribe - Richard Probst (SAP): adjourned without objection
Matt Rutkowski (IBM): it should be more about a unique reference mechanism
Alex Heneveld (Cloudsoft): bye all