twingle/doc/teps tep-0101.txt,1.1,1.2
[email protected] Thu, 6 Mar 2003 08:40:44 -0700 (MST)
| Newsgroups | gmane.comp.cms.oscom.twingle.cvs |
|---|---|
| Message-ID | <[email protected]> |
Update of /cvs/root/twingle/doc/teps
In directory alpha.oscom.org:/tmp/cvs-serv12705/doc/teps
Modified Files:
tep-0101.txt
Log Message:
added implementation notes
Index: tep-0101.txt
===================================================================
RCS file: /cvs/root/twingle/doc/teps/tep-0101.txt,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** tep-0101.txt 6 Mar 2003 15:12:52 -0000 1.1
--- tep-0101.txt 6 Mar 2003 15:40:42 -0000 1.2
***************
*** 53,56 ****
--- 53,77 ----
</rsd>
+ Implementation
+ There are two sides to implement this proposal. A server-specific
+ side, meaning each participating CMS needs to implement RSD. And
+ a client-specific side, which is covered here.
+
+ Various libraries for autodiscovery exist. [4] Twingle would do well
+ to incorporate one of them. After Twingle fetches the RSD, it has
+ to parse it to get at its configuration parameters.
+
+ Here is some javascript code to get the LINK element from a page:
+
+ void(d=document);
+ void(el=d.getElementsByTagName('link'));
+ for(i=0;i<el.length;i++)
+ {
+ if(el[i].getAttribute('rel').indexOf('alternate')!=-1%20&&%20el[i].getAttribute('type').indexOf('application/rsd+xml')!=-1)
+ {
+ // fetch el[i].getAttribute('href')
+ };
+ };
+
Open Issues
***************
*** 63,66 ****
--- 84,88 ----
[2] http://www.w3.org/P3P/validator/20020128/document
[3] http://archipelago.phrasewise.com/rsd
+ [4] http://dmoz.org/Reference/Libraries/Library_and_Information_Science/Technical_Services/Cataloguing/Metadata/RDF/Applications/RSS/Autodiscovery/