<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.eiffelroom.com" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>eiffelroom - documentation - Comments</title>
 <link>http://www.eiffelroom.com/tag/documentation</link>
 <description>Comments for &quot;documentation&quot;</description>
 <language>en</language>
<item>
 <title>Path URI</title>
 <link>http://www.eiffelroom.com/blog/ted_eiffel/start_using_eiffel_information_system_eis#comment-446</link>
 <description>&lt;p&gt;Yes path URI sounds so much better than the name value mess, and is not exclusive with defaulting of various types, with say a magic word as first component:&lt;/p&gt;

&lt;p&gt;eiffel:///byclass/STRING/is_equal eiffel:///bycluster/foo/STRING/is_equal&lt;/p&gt;

&lt;p&gt;etc&lt;/p&gt;

</description>
 <pubDate>Fri, 16 May 2008 08:01:34 -0700</pubDate>
 <dc:creator>nenieorg</dc:creator>
 <guid isPermaLink="false">comment 446 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>Though I am not aware of</title>
 <link>http://www.eiffelroom.com/blog/ted_eiffel/start_using_eiffel_information_system_eis#comment-443</link>
 <description>&lt;p&gt;Though I am not aware of what kind of software processes the URI and how it would be useful picking up name/value pairs, it is would always be better to follow standard. Using eiffel:///? is OK for me, except that it looks uglier. Actually the .ecf is not needed for EIS incoming mechanism. Only optional system/system UUID is needed for locating project.&lt;/p&gt;

</description>
 <pubDate>Wed, 14 May 2008 07:28:24 -0700</pubDate>
 <dc:creator>ted_eiffel</dc:creator>
 <guid isPermaLink="false">comment 443 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>Perhaps a path</title>
 <link>http://www.eiffelroom.com/blog/ted_eiffel/start_using_eiffel_information_system_eis#comment-442</link>
 <description>&lt;p&gt;You would need eiffel:///?... if you expected generic URI processing software to pick up the name/value pairs.&lt;/p&gt;

&lt;p&gt;or alternatively abandon the query parameters approach, and have a structured path (something like /system/target/cluster/class/feature). But that would make it hard to default the system and target.&lt;/p&gt;

&lt;p&gt;I can&#039;t see how this is supposed to work anyway. Surely you need an ecf file? In which case the obvious syntax is:&lt;/p&gt;

&lt;p&gt;eiffel:///path/to/my.ecf?class=my_class&amp;amp;feature=my_feature&lt;/p&gt;

&lt;p&gt;and the authority field is then available for a future extension for non-local access.&lt;/p&gt;

&lt;p&gt;Colin Adams&lt;/p&gt;

</description>
 <pubDate>Tue, 13 May 2008 07:35:48 -0700</pubDate>
 <dc:creator>colin-adams</dc:creator>
 <guid isPermaLink="false">comment 442 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>Indeed. I think eiffel:///</title>
 <link>http://www.eiffelroom.com/blog/ted_eiffel/start_using_eiffel_information_system_eis#comment-441</link>
 <description>&lt;p&gt;Indeed. I think eiffel:/// would be nicer.&lt;/p&gt;

</description>
 <pubDate>Tue, 13 May 2008 05:04:22 -0700</pubDate>
 <dc:creator>ted_eiffel</dc:creator>
 <guid isPermaLink="false">comment 441 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>Invalid URIs</title>
 <link>http://www.eiffelroom.com/blog/ted_eiffel/start_using_eiffel_information_system_eis#comment-440</link>
 <description>&lt;p&gt;The syntax of the eiffel: URIs is invalid.&lt;/p&gt;

&lt;p&gt;That is, the presence of the // indicates that what follows is an authority segment:&lt;/p&gt;

&lt;p&gt;According to RFC 3986, this is terminated by the first /, ? or # character.&lt;/p&gt;

&lt;p&gt;None of those is present, so the remainder of the URI needs to match the authority production syntax. As there is no @ or : present, this in turn means matching the syntax for host. Clearly it does not.&lt;/p&gt;

&lt;p&gt;I suggest that you appear to be parameter/value pairs, and that therefore this remainder should actually be part of the query segment.&lt;/p&gt;

&lt;p&gt;Accordingly, change eiffel:// into eiffel://? in order to conform to URI syntax.&lt;/p&gt;

&lt;p&gt;I assume that by protocol link you actually meant URI scheme.&lt;/p&gt;

&lt;p&gt;Colin Adams&lt;/p&gt;

</description>
 <pubDate>Tue, 13 May 2008 03:18:33 -0700</pubDate>
 <dc:creator>colin-adams</dc:creator>
 <guid isPermaLink="false">comment 440 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>and a module to integrate</title>
 <link>http://www.eiffelroom.com/tool/edoc#comment-118</link>
 <description>&lt;p&gt;and a module to integrate the whole output into eiffelroom and origo, by Peter.&lt;/p&gt;

</description>
 <pubDate>Tue, 13 Mar 2007 00:18:05 -0700</pubDate>
 <dc:creator>bayt</dc:creator>
 <guid isPermaLink="false">comment 118 at http://www.eiffelroom.com</guid>
</item>
<item>
 <title>xml</title>
 <link>http://www.eiffelroom.com/tool/edoc#comment-117</link>
 <description>&lt;p&gt;just to let you know: there&#039;s also XML output in the works (by me :))&lt;/p&gt;

</description>
 <pubDate>Mon, 12 Mar 2007 14:47:00 -0700</pubDate>
 <dc:creator>sanakan</dc:creator>
 <guid isPermaLink="false">comment 117 at http://www.eiffelroom.com</guid>
</item>
</channel>
</rss>
