CityWeb Workshop - Revision history

imported>Niveditasinghvi at 02:12, May 6, 2017

2017-05-06T02:12:01Z

← Older revision		Revision as of 02:12, May 6, 2017
Line 2:		Line 2:
	The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of CityWeb, a Smart City Open Data Portal and Solution Resource. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CityWeb chapter will be written here in the wiki.		The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of CityWeb, a Smart City Open Data Portal and Solution Resource. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CityWeb chapter will be written here in the wiki.

	The CityWeb chapter: [[CityWeb]]		'''The CityWeb chapter: [[CityWeb]]'''

	Note that the outline for the entire GCTC Transportation SuperCluster report to NIST and US Ignite is:		Note that the outline for the entire GCTC Transportation SuperCluster report to NIST and US Ignite is:

imported>Niveditasinghvi at 02:11, May 6, 2017

2017-05-06T02:11:13Z

← Older revision		Revision as of 02:11, May 6, 2017
Line 36:		Line 36:

	{\| class="wikitable" style="color:darkblue;background-color:#DEDEB9;" cellpadding="10"		{\| class="wikitable" style="color:darkblue;background-color:#DEDEB9;" cellpadding="10"
	\|+~~City SDK~~ Workshop Agenda, 9:45AM Thursday, C-121		\|+ Workshop Agenda, 9:45AM Thursday, C-121
	\|-		\|-
	\|NIST		\|NIST

imported>Niveditasinghvi at 02:04, May 6, 2017

2017-05-06T02:04:27Z

← Older revision		Revision as of 02:04, May 6, 2017
Line 1:		Line 1:

	The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of ~~making it easier (faster~~, ~~cheaper, more interoperable) to create, develop, deploy, and maintain~~ Smart City Applications. Although beginning as a Transportation SuperCluster proposal the need for better software development tooling is transvertical, that is broader than just the Transportation SuperCluster. The goal then is the establishment of a Software Development Toolkit project and community that will support development activities across all the SuperClusters. We envision a single open source community creating and maintaining the SDK (or more properly a collection of interconnected and related SDKs supporting various APIs and ~~development functions~~. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CityWeb chapter will be written here in the wiki.		The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of CityWeb, a Smart City Open Data Portal and Solution Resource. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CityWeb chapter will be written here in the wiki.

	The CityWeb chapter: [[CityWeb]]		The CityWeb chapter: [[CityWeb]]

imported>Niveditasinghvi at 17:36, May 5, 2017

2017-05-05T17:36:14Z

← Older revision		Revision as of 17:36, May 5, 2017
Line 1:		Line 1:

	The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of making it easier (faster, cheaper, more interoperable) to create, develop, deploy, and maintain Smart City Applications. Although beginning as a Transportation SuperCluster proposal the need for better software development tooling is transvertical, that is broader than just the Transportation SuperCluster. The goal then is the establishment of a Software Development Toolkit project and community that will support development activities across all the SuperClusters. We envision a single open source community creating and maintaining the SDK (or more properly a collection of interconnected and related SDKs supporting various APIs and development functions. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The ~~CitySDK~~ chapter will be written here in the wiki.		The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of making it easier (faster, cheaper, more interoperable) to create, develop, deploy, and maintain Smart City Applications. Although beginning as a Transportation SuperCluster proposal the need for better software development tooling is transvertical, that is broader than just the Transportation SuperCluster. The goal then is the establishment of a Software Development Toolkit project and community that will support development activities across all the SuperClusters. We envision a single open source community creating and maintaining the SDK (or more properly a collection of interconnected and related SDKs supporting various APIs and development functions. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CityWeb chapter will be written here in the wiki.

	The ~~CitySDK~~ chapter: [[~~CitySDK~~]]		The CityWeb chapter: [[CityWeb]]

	Note that the outline for the entire GCTC Transportation SuperCluster report to NIST and US Ignite is:		Note that the outline for the entire GCTC Transportation SuperCluster report to NIST and US Ignite is:
Line 13:		Line 13:
	#Transportation Analytics		#Transportation Analytics
	#Policies and Procedures		#Policies and Procedures
	#~~CitySDK~~		#CityWeb
	#References		#References
	#Credits		#Credits

imported>Niveditasinghvi: Niveditasinghvi moved page Smart City SDK to CityWeb Workshop: Butterflies in South America

2017-05-05T17:31:34Z

Niveditasinghvi moved page Smart City SDK to CityWeb Workshop: Butterflies in South America

← Older revision		Revision as of 17:31, May 5, 2017
(No difference)

imported>Daniel.frye: General outline

2017-03-15T21:07:52Z

General outline

← Older revision		Revision as of 21:07, March 15, 2017
Line 2:		Line 2:
	The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of making it easier (faster, cheaper, more interoperable) to create, develop, deploy, and maintain Smart City Applications. Although beginning as a Transportation SuperCluster proposal the need for better software development tooling is transvertical, that is broader than just the Transportation SuperCluster. The goal then is the establishment of a Software Development Toolkit project and community that will support development activities across all the SuperClusters. We envision a single open source community creating and maintaining the SDK (or more properly a collection of interconnected and related SDKs supporting various APIs and development functions. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CitySDK chapter will be written here in the wiki.		The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of making it easier (faster, cheaper, more interoperable) to create, develop, deploy, and maintain Smart City Applications. Although beginning as a Transportation SuperCluster proposal the need for better software development tooling is transvertical, that is broader than just the Transportation SuperCluster. The goal then is the establishment of a Software Development Toolkit project and community that will support development activities across all the SuperClusters. We envision a single open source community creating and maintaining the SDK (or more properly a collection of interconnected and related SDKs supporting various APIs and development functions. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CitySDK chapter will be written here in the wiki.

			The CitySDK chapter: [[CitySDK]]

			Note that the outline for the entire GCTC Transportation SuperCluster report to NIST and US Ignite is:

			#Executive Summary
			#First and Last Mile Solutions
			#Sensors
			#Freight
			#Transportation Hubs
			#Transportation Analytics
			#Policies and Procedures
			#CitySDK
			#References
			#Credits

			Each of the 7 substantive sections (#2-#8 above) is being initially written a cross-function group from the SuperCluster.

	Below this line is the original wiki entry describing the breakout session at the GCTC workshop held in February 2017 in Portland as well as containing links to the talks presented in the breakout session.		Below this line is the original wiki entry describing the breakout session at the GCTC workshop held in February 2017 in Portland as well as containing links to the talks presented in the breakout session.

imported>Daniel.frye: Begin construction of chapter

2017-03-15T20:53:12Z

Begin construction of chapter

← Older revision		Revision as of 20:53, March 15, 2017
Line 1:		Line 1:

	Writing "Smart City" applications is hard. Often, the software and tooling environment is proprietary and the resulting applications fail to ~~inter-operate~~ with applications developed elsewhere. It can also be expensive due to a lack of in-house knowledge, skills and tools for such software. Having an open source Software Development Kit (SDK) that provides libraries, tools and common APIs could be valuable in addressing this problem. The goal would be to make it easier, cheaper and faster to develop, deploy and sustain Smart City applications worldwide.		The GCTC Transportation SuperCluster report to NIST and US Ignite will include a section on the topic of making it easier (faster, cheaper, more interoperable) to create, develop, deploy, and maintain Smart City Applications. Although beginning as a Transportation SuperCluster proposal the need for better software development tooling is transvertical, that is broader than just the Transportation SuperCluster. The goal then is the establishment of a Software Development Toolkit project and community that will support development activities across all the SuperClusters. We envision a single open source community creating and maintaining the SDK (or more properly a collection of interconnected and related SDKs supporting various APIs and development functions. The first draft of this report is due to NIST and US Ignite by the end of April 2017. All the chapters in the eventual report will be written via a combination of key volunteers and general crowdsourcing across the Supercluster participants. The CitySDK chapter will be written here in the wiki.



			Below this line is the original wiki entry describing the breakout session at the GCTC workshop held in February 2017 in Portland as well as containing links to the talks presented in the breakout session.
			-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


			Writing "Smart City" applications is hard. Often, the software and tooling environment is proprietary and the resulting applications fail to interoperate with applications developed elsewhere. It can also be expensive due to a lack of in-house knowledge, skills and tools for such software. Having an open source Software Development Kit (SDK) that provides libraries, tools and common APIs could be valuable in addressing this problem. The goal would be to make it easier, cheaper and faster to develop, deploy and sustain Smart City applications worldwide.

imported>Niveditasinghvi at 03:43, February 10, 2017

2017-02-10T03:43:11Z

← Older revision		Revision as of 03:43, February 10, 2017
Line 34:		Line 34:
	'''Jose Gonzalez - FIWARE''' - Since 2011, FIWARE has stood as an independent community whose mission is to build open and sustainable software platform standards that will ease the development of new Smart Applications. The potential of FIWARE for the growth and sustainable development of Smart Cities is already a reality backed by more than 100 cities around the world.		'''Jose Gonzalez - FIWARE''' - Since 2011, FIWARE has stood as an independent community whose mission is to build open and sustainable software platform standards that will ease the development of new Smart Applications. The potential of FIWARE for the growth and sustainable development of Smart Cities is already a reality backed by more than 100 cities around the world.

	'''Nivedita Singhvi - urban.systems''' - A Smart City Open Source SDK Proposal: This talk will present our initial thoughts on what a City SDK open source project might look like, what would be its benefits and scope, and the obstacles, concerns it would need to overcome		'''Nivedita Singhvi - urban.systems''' - A Smart City Open Source SDK Proposal: This talk will present our initial thoughts on what a City SDK open source project might look like, what would be its benefits and scope, and the obstacles, concerns it would need to overcome.

	Also of interest would be hearing from any Smart City application developers that might like to present or host a poster on issues they have in building modern Smart City applications.		Also of interest would be hearing from any Smart City application developers that might like to present or host a poster on issues they have in building modern Smart City applications.

imported>Niveditasinghvi at 03:36, February 10, 2017

2017-02-10T03:36:20Z

← Older revision		Revision as of 03:36, February 10, 2017
Line 9:		Line 9:


	~~Our workshop-style open meeting will discuss next steps with those interested in this effort~~. If you are interested in ~~attending~~ the ~~workshop~~ (~~will which~~ occur ~~on the morning of February 2, 9:45 am~~, ~~location TBD)~~ please ~~indicate interest on the Google Form survey. If you are interested enough in the topic~~ to ~~help organize please~~ send ~~email to~~ daniel.frye@urban.systems.		We have sent out a brief set of questions regarding interest to all the identified attendees of the Workshop Session. If you are at all interested in participating in the conversation (or even just following what might occur) and haven't received any email from us, please don't hesitate to send Dan a note at daniel.frye@urban.systems. The slides from the workshop have been uploaded and linked to in the Agenda table below.

imported>Niveditasinghvi at 03:30, February 10, 2017

2017-02-10T03:30:07Z

← Older revision		Revision as of 03:30, February 10, 2017
Line 12:		Line 12:


	{\| class="wikitable" style="color:darkblue;background-color:~~lightblue~~;" cellpadding="10"		{\| class="wikitable" style="color:darkblue;background-color:#DEDEB9;" cellpadding="10"
	\|+City SDK Workshop Agenda, 9:45AM Thursday, C-121		\|+City SDK Workshop Agenda, 9:45AM Thursday, C-121
	\|-		\|-