<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: the WMATA/Nextbus contract</title>
	<atom:link href="http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 07 Sep 2010 23:10:52 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: End in the Boy &#187; Blog Archive &#187; The Wmata/nextbus Contract Manifest Density</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-9707</link>
		<dc:creator>End in the Boy &#187; Blog Archive &#187; The Wmata/nextbus Contract Manifest Density</dc:creator>
		<pubDate>Fri, 12 Feb 2010 20:59:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-9707</guid>
		<description>[...] Source: www.manifestdensity.net [...]</description>
		<content:encoded><![CDATA[<p>[...] Source: <a href="http://www.manifestdensity.net" rel="nofollow">http://www.manifestdensity.net</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kansas Jack</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-9050</link>
		<dc:creator>Kansas Jack</dc:creator>
		<pubDate>Thu, 04 Feb 2010 02:43:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-9050</guid>
		<description>Hey Tom - when you&#039;re meeting with WMATA, maybe you could ask them why they omitted the even pages (or odd pages, depending on the document) from the materials they sent to Michael Perkins.  Right?  I mean, look at paragraph 30, which you excerpt above.  It goes (a), (1), (2) and then skips to (e).  What happened to the page with paragraphs (b), (c) and (d)?

Second, I think your concern is well-founded.  The language surrounding data use rights is quite vague, and I&#039;m not sure the language in Sec. 3.9 is all that favorable.  What does &quot;full rights&quot; mean?  Maybe that&#039;s normal for procurement, but that&#039;s very ambiguous phrasing in most other contexts.  If &quot;full rights&quot; really meant full rights, then the second sentence shouldn&#039;t be there.  The second sentence is unfavorable from a developer&#039;s perspective because arguably it can be read as a limitation on the first sentence.  If you read it that way, all WMATA received is the right to share data to, say, MARC to display to MARC travelers, such that WMATA has no rights to sublicense rights to data to developers.

Similarly, the part of Section 30 excerpted above doesn&#039;t seem all that helpful.  It deals with &quot;technical data,&quot; which is defined in paragraph (e), and generally appears to include certain systems documentation and software.  Nowhere does the definition reference CIS data or, frankly, any other data.

It would be interesting to see what&#039;s in Section 4.5.1 of Part II of the Technical Specs (referenced on pg. 103 of the PDF), which also purports to address data rights.

Finally, here&#039;s some cynicism for you ~ statements from business people and engineers at Nextbus, NBI and WMATA are nice, but not perfect.  The contract language ultimately governs.  The folks who you&#039;re working with now maybe very cooperative, but they may not have their jobs tomorrow and their replacements may take a very different view of who owns what.

Best of luck, kick ass and keep up the great work.</description>
		<content:encoded><![CDATA[<p>Hey Tom &#8211; when you&#8217;re meeting with WMATA, maybe you could ask them why they omitted the even pages (or odd pages, depending on the document) from the materials they sent to Michael Perkins.  Right?  I mean, look at paragraph 30, which you excerpt above.  It goes (a), (1), (2) and then skips to (e).  What happened to the page with paragraphs (b), (c) and (d)?</p>
<p>Second, I think your concern is well-founded.  The language surrounding data use rights is quite vague, and I&#8217;m not sure the language in Sec. 3.9 is all that favorable.  What does &#8220;full rights&#8221; mean?  Maybe that&#8217;s normal for procurement, but that&#8217;s very ambiguous phrasing in most other contexts.  If &#8220;full rights&#8221; really meant full rights, then the second sentence shouldn&#8217;t be there.  The second sentence is unfavorable from a developer&#8217;s perspective because arguably it can be read as a limitation on the first sentence.  If you read it that way, all WMATA received is the right to share data to, say, MARC to display to MARC travelers, such that WMATA has no rights to sublicense rights to data to developers.</p>
<p>Similarly, the part of Section 30 excerpted above doesn&#8217;t seem all that helpful.  It deals with &#8220;technical data,&#8221; which is defined in paragraph (e), and generally appears to include certain systems documentation and software.  Nowhere does the definition reference CIS data or, frankly, any other data.</p>
<p>It would be interesting to see what&#8217;s in Section 4.5.1 of Part II of the Technical Specs (referenced on pg. 103 of the PDF), which also purports to address data rights.</p>
<p>Finally, here&#8217;s some cynicism for you ~ statements from business people and engineers at Nextbus, NBI and WMATA are nice, but not perfect.  The contract language ultimately governs.  The folks who you&#8217;re working with now maybe very cooperative, but they may not have their jobs tomorrow and their replacements may take a very different view of who owns what.</p>
<p>Best of luck, kick ass and keep up the great work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-9004</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Wed, 03 Feb 2010 17:03:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-9004</guid>
		<description>Again, that&#039;s great, but I think you&#039;re mistaken when you claim that this is obvious.  I suggest googling for &quot;Routesy&quot; and doing a bit of background reading.</description>
		<content:encoded><![CDATA[<p>Again, that&#8217;s great, but I think you&#8217;re mistaken when you claim that this is obvious.  I suggest googling for &#8220;Routesy&#8221; and doing a bit of background reading.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TransitHappy</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-8996</link>
		<dc:creator>TransitHappy</dc:creator>
		<pubDate>Wed, 03 Feb 2010 15:40:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-8996</guid>
		<description>Too much time - I&#039;m embarrassed to even be reading this stuff.  The data is owned by WMATA and they can tell NextBus (the real one) whatever they want.  MBTA, another NextBus customer, has completely opened up their data feed so that third-party developers can build anything they want with the data.</description>
		<content:encoded><![CDATA[<p>Too much time &#8211; I&#8217;m embarrassed to even be reading this stuff.  The data is owned by WMATA and they can tell NextBus (the real one) whatever they want.  MBTA, another NextBus customer, has completely opened up their data feed so that third-party developers can build anything they want with the data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-8946</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Wed, 03 Feb 2010 02:52:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-8946</guid>
		<description>Great! The thing is, nobody&#039;s been willing to put that in writing. NBIS has been happy to talk about licensing arrangements, and Nextbus Inc. has been happy to make assertions but not go on the record. Meanwhile, WMATA has... well, they haven&#039;t said much.  For those working at one of these three institutions -- which I assume means you -- this is all probably really obvious.  But for those of us considering investing time into developing applications based on Nextbus data, this has not been as clear, and it&#039;s good to have the situation delineated clearly by the contract.</description>
		<content:encoded><![CDATA[<p>Great! The thing is, nobody&#8217;s been willing to put that in writing. NBIS has been happy to talk about licensing arrangements, and Nextbus Inc. has been happy to make assertions but not go on the record. Meanwhile, WMATA has&#8230; well, they haven&#8217;t said much.  For those working at one of these three institutions &#8212; which I assume means you &#8212; this is all probably really obvious.  But for those of us considering investing time into developing applications based on Nextbus data, this has not been as clear, and it&#8217;s good to have the situation delineated clearly by the contract.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: I Know</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-8943</link>
		<dc:creator>I Know</dc:creator>
		<pubDate>Wed, 03 Feb 2010 02:33:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-8943</guid>
		<description>Wow, talk about making a big deal out of nothing.  WMATA owns the rights to the data - this has been asserted by both WMATA and the real NextBus, Inc.  It is up to WMATA, and WMATA alone, to decide if you can make apps without paying licensing fees.  Why does this keep coming up?  A: Too many bored people with lots of time on their hands trying to find more problems with Metro.</description>
		<content:encoded><![CDATA[<p>Wow, talk about making a big deal out of nothing.  WMATA owns the rights to the data &#8211; this has been asserted by both WMATA and the real NextBus, Inc.  It is up to WMATA, and WMATA alone, to decide if you can make apps without paying licensing fees.  Why does this keep coming up?  A: Too many bored people with lots of time on their hands trying to find more problems with Metro.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tom</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-8910</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Tue, 02 Feb 2010 20:56:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-8910</guid>
		<description>I admit that that specific phrasing struck me as... troublesome.

But WMATA can save us!  If they just, uh, agree to sacrifice a potential revenue stream.  Hm.  This may not be the best time to ask.</description>
		<content:encoded><![CDATA[<p>I admit that that specific phrasing struck me as&#8230; troublesome.</p>
<p>But WMATA can save us!  If they just, uh, agree to sacrifice a potential revenue stream.  Hm.  This may not be the best time to ask.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sommer</title>
		<link>http://www.manifestdensity.net/2010/02/02/the-wmatanextbus-contract/comment-page-1/#comment-8909</link>
		<dc:creator>Sommer</dc:creator>
		<pubDate>Tue, 02 Feb 2010 20:46:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.manifestdensity.net/?p=1229#comment-8909</guid>
		<description>&quot;small low-cost electronic devices intended for home use&quot; -- oh man, you must be peeing yourself.</description>
		<content:encoded><![CDATA[<p>&#8220;small low-cost electronic devices intended for home use&#8221; &#8212; oh man, you must be peeing yourself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
