Markus, In general you should link to the highest level page, e.g. I-Card Service [1], because from that page you can drill down into [2] whereas going opposite direction is harder (because there aren¹t links in the reverse direction). Here¹s [3] another example of a page that links to [1].
But you¹re right it all isn¹t as clear as it should be. For example, I think ideally the API (e.g. The I-Card Service API) would be documented in [1], yet at present it is only documented [2]. BTW, speaking of organizing things. If you¹ll notice in [3] I slot your Cloud Selector in as a ³Service² and not as a ³Selector². Just feels more natural to me. I think the diagram on that page works well too. Frankly, the more I work with it, the more I don¹t think ³Cloud Selector² is a very helpful name. You¹ll notice I include the string ³& OpenID OP² in [3], for example. ³Cloud Selector² stretches the ³selector² definition too far and I think that makes it confusing. I¹m not proposing we change it, I¹m just musing about it. -Paul [1] http://wiki.eclipse.org/I-Card_Service [2] http://wiki.eclipse.org/Components_1.X#I-Card_Service_Web_App [3] http://wiki.eclipse.org/Selector_Overview On 7/11/09 5:12 PM, "Markus Sabadello" <[email protected]> wrote: > Looks right. > BTW there are separate pages for "I-Card Service" and "I-Card Service Web > App". That makes sense I guess, but sometimes when I write a page I don't know > to which one of the two I should link. > > Markus > > On Sat, Jul 11, 2009 at 9:52 PM, Paul Trevithick <[email protected]> > wrote: >> Hi Markus, >> >> As I¹ve been combing through all of the Higgins solutions & diagrams, I took >> a moment to update [1] and add a diagram along with links to the components >> and the I-Card Service. >> >> [1] http://wiki.eclipse.org/IPhone_Selector_1.1#Architecture > >
_______________________________________________ higgins-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/higgins-dev
