Technical Advisory Board (TAB)

I spent some time looking at this. It was introduced in 2003 and I suspect is is based on XML and XSLT. Essentially, you select the reports you want and then press the button at the bottom of the form. This creates a HTML page that you can cut and paste from. The Shopping List seems to be a minimalistic technology that we could use to make it simpler for editors create a bibliography. But I have some questions. Assuming we can get to the XML source, who would maintain the database? Also, we may want to change the format of the citations. This would involve messing with the XSL. Who would do that? -- All the best, Ashok

On Mon, Dec 9, 2013 at 11:22 AM, Ashok Malhotra < ashok.malhotra@oracle.com > wrote: I spent some time looking at this.  It was introduced in 2003 and I suspect is is based on XML and XSLT.  Essentially, you select the reports you want and then press the button at the bottom of the form.  This creates a HTML page that you can cut and paste from. The Shopping List seems to be a minimalistic technology that we could use to make it simpler for editors create a bibliography.  But I have some questions. Assuming we can get to the XML source, who would maintain the database? Also, we may want to change the format of the citations.  This would involve messing with the XSL.  Who would do that? Great questions, Ashok (as always!) 1.  "Get to the XML source" I assume this will be one of the easier parts of the problem, when we have the bibliographic metadata in any regular/structured format. We (Staff) are working on a project which would enable creation of the relevant metadata from a central DB, so if that matures, the main challenge would be the legacy bibliographic metadata content. We have that partially in hand already. 2. "change the format of the citations"... probably, but again, the generation of content/format/style should be rather straight-forward as a computer operation 3. "messing with the XSL(t)" -- we could probably use XSLT but there should be other approaches if we are generating XML and other formats from a master DB.  I think I can say that Staff is committed broadly to the task of creating the metadata (database) because we need it for several projects, including (partly) database-driven publication of the TC home pages, when Drupalized (another project). All of this -- as to pace of work -- depends upon available resourcing, for the information architecture and creation of the normalized data. end-interim-comment - Robin   -- All the best, Ashok ------------------------------ ------------------------------ --------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/ apps/org/workgroup/portal/my_ workgroups.php -- Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783

Thanks, Robin! I am happy to hear that the staff are committed to such a database because that would make the bibliography easier to create and improve the quality.  Let me know if I can help. This completes my action item -:) All the best, Ashok On 12/9/2013 12:52 PM, Robin Cover wrote: On Mon, Dec 9, 2013 at 11:22 AM, Ashok Malhotra < ashok.malhotra@oracle.com > wrote: I spent some time looking at this.  It was introduced in 2003 and I suspect is is based on XML and XSLT.  Essentially, you select the reports you want and then press the button at the bottom of the form.  This creates a HTML page that you can cut and paste from. The Shopping List seems to be a minimalistic technology that we could use to make it simpler for editors create a bibliography.  But I have some questions. Assuming we can get to the XML source, who would maintain the database? Also, we may want to change the format of the citations.  This would involve messing with the XSL.  Who would do that? Great questions, Ashok (as always!) 1.   Get to the XML source I assume this will be one of the easier parts of the problem, when we have the bibliographic metadata in any regular/structured format. We (Staff) are working on a project which would enable creation of the relevant metadata from a central DB, so if that matures, the main challenge would be the legacy bibliographic metadata content. We have that partially in hand already. 2. change the format of the citations ... probably, but again, the generation of content/format/style should be rather straight-forward as a computer operation 3. messing with the XSL(t) -- we could probably use XSLT but there should be other approaches if we are generating XML and other formats from a master DB.  I think I can say that Staff is committed broadly to the task of creating the metadata (database) because we need it for several projects, including (partly) database-driven publication of the TC home pages, when Drupalized (another project). All of this -- as to pace of work -- depends upon available resourcing, for the information architecture and creation of the normalized data. end-interim-comment - Robin   -- All the best, Ashok --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php -- Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ashok, If by source you mean the W3C source for the data, yes, it can be downloaded along with the script. Here's the data: http://www.w3.org/2002/01/tr-automation/tr.rdf Updated on Tues/Thurs and at other times as well. Fully automated loading into a local store would be a necessity. In what way would you want to change the W3C's citations of their own work? I am assuming the bibliographic database Robin speaks of is for OASIS publications. Yes? Hope you are at the start of a great week! Patrick On 12/09/2013 01:07 PM, Ashok Malhotra wrote: > Thanks, Robin! I am happy to hear that the staff are committed to > such a database because that would make the bibliography easier to > create and improve the quality. Let me know if I can help. This > completes my action item -:) All the best, Ashok > > On 12/9/2013 12:52 PM, Robin Cover wrote: >> On Mon, Dec 9, 2013 at 11:22 AM, Ashok Malhotra >> <ashok.malhotra@oracle.com < mailto:ashok.malhotra@oracle.com >> >> wrote: >> >> I spent some time looking at this. It was introduced in 2003 >> and I suspect is is based on XML and XSLT. Essentially, you >> select the reports you want and then press the button at the >> bottom of the form. This creates a HTML page that you can cut >> and paste from. >> >> The Shopping List seems to be a minimalistic technology that we >> could use to make it simpler for editors create a bibliography. >> But I have some questions. Assuming we can get to the XML source, >> who would maintain the database? Also, we may want to change the >> format of the citations. This would involve messing with the >> XSL. Who would do that? >> >> >> Great questions, Ashok (as always!) >> >> 1. "Get to the XML source" >> >> I assume this will be one of the easier parts of the problem, >> when we have the bibliographic metadata in any >> regular/structured format. >> >> We (Staff) are working on a project which would enable creation >> of the relevant metadata from a central DB, so if that matures, >> the main challenge would be the legacy bibliographic metadata >> content. We have that partially in hand already. >> >> 2. "change the format of the citations"... probably, but again, >> the generation of content/format/style should be rather >> straight-forward as a computer operation >> >> 3. "messing with the XSL(t)" -- we could probably use XSLT but >> there should be other approaches if we are generating XML and >> other formats from a master DB. >> >> I think I can say that Staff is committed broadly to the task of >> creating the metadata (database) because we need it for several >> projects, including (partly) database-driven publication of the >> TC home pages, when Drupalized (another project). >> >> All of this -- as to pace of work -- depends upon available >> resourcing, for the information architecture and creation of the >> normalized data. >> >> end-interim-comment >> >> - Robin >> >> >> >> >> >> >> >> >> >> >> >> -- All the best, Ashok >> >> --------------------------------------------------------------------- >> >> To unsubscribe from this mail list, you must leave the OASIS TC >> that generates this mail. Follow this link to all your TCs in >> OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> >> >> >> >> >> - -- >> Robin Cover OASIS, Director of Information Services Editor, Cover >> Pages and XML Daily Newslink Email: robin@oasis-open.org >> < mailto:robin@oasis-open.org > Staff bio: >> http://www.oasis-open.org/people/staff/robin-cover Cover Pages: >> http://xml.coverpages.org/ Newsletter: >> http://xml.coverpages.org/newsletterArchive.html Tel: +1 >> 972-296-1783 > - -- Patrick Durusau patrick@durusau.net Technical Advisory Board, OASIS (TAB) Co-Chair, OpenDocument Format TC (OASIS) Editor, OpenDocument Format TC, Project Editor ISO/IEC 26300 Former Chair, V1 - US TAG to JTC 1/SC 34 Convener, JTC 1/SC 34/WG 3 (Topic Maps) Co-Editor, ISO 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSpho2AAoJEAudyeI2QFGoidwP/jDcwIT0zIE5viP2/17TnYA/ JupS1yuln5f2rxdFsrrvRa8vORt70dbv5QAxF+xWzicHvRuhncl94GugDqWk0oI0 wc5H0JwVdw6oFanyrt+CrcN/tNwuhbWO9Tn2kigt8JYGQOENUduox89Yp59R6G1E yie1IialmxUmDmkduhIruPMv7vwaTXPB3w2crkbJJlTT0lMHiRZzSKi5qZbmzh+H n4+ZoW1EVTBEtadUQ9+6HgsmYXpM9xPUXIBx9ub/MLK+LC5RE6AmF+F3LWrucPhZ A6SV2hmx1Pfu9Moc2iD8W5VRZ3jPNRS7Fjt1uiSG7rBLJvjpu5svUZYMHlnA4uGO U6eikT8RKKwqOGMHBpIVbWxN3A7A5tt8zCh8orSXepRV6TUt4EDwFxzMS9J3kYEk okyiCW3BzhtLa253DnXRrM986RityaB3/ervDq+a2b7svlgkL0tMhCl6pTfDE3sM VGQhS2zQiPxTHluIfm3FfovbXsY9YoSNrWW/we4PDKepn3jy7A7vBdV83rSQes6V VJdERhH6I7RhJZYag4iw6AX1u1h7j0S3Oad5ITGzvcTSZeXQpfTI0VB2w1AEMljI tvpf3eG1QTImZTNp+gElKbidPs+4ndoBqkcaRwNiuShGk+9vxyfwnGaYTxELhBul xtR2CuO14yo+1TrnMowQ =ezcD -----END PGP SIGNATURE-----

On 12/9/2013 2:30 PM, Patrick Durusau wrote: In what way would you want to change the W3C's citations of their own work? I was not thinking of that. I was worrying about updating the database with new citations and perhaps changing the format of the citations to the OASIS format. Ashok