Re: Glossary for editor's copy ready

David Orchard wrote:
> I see that you put this in a separate appendix.  Our current section 2.4
> Terminology says
> We introduce the following terms that are used throughout this document:
> 
> EdNote: script will insert termdefs here

hoops! I missed that.

> I would have thought you'd have put the terms in the terminology section
> instead of an appendix.  If it should be in the appendix, then the 2
> sentences I quoted also need to be removed.
> 
> Could you elaborate on the choice of location for the glossary?

the stylesheet you sent me creates an appendix, and I used it just "as
is". Sorry for that. The terms should now be in the right place, please
have a look.

For the attachment document, it looks a kind of strange, since many
definitions are already here.

Felix

> 
> Cheers,
> Dave 
> 
>> -----Original Message-----
>> From: public-ws-policy-eds-request@w3.org 
>> [mailto:public-ws-policy-eds-request@w3.org] On Behalf Of Felix Sasaki
>> Sent: Saturday, September 02, 2006 8:57 PM
>> To: public-ws-policy-eds@w3.org
>> Subject: Glossary for editor's copy ready
>>
>> Hi all,
>>
>> Using extract-glist.xsl from Norm, I did the following:
>>
>> - added a task "glossaries" to the build.xml file . It 
>> creates glossary-framework.xml and glossary-attachment.xml 
>> using extract-glist.xsl . The "validate-policy-specs" task 
>> depends on "glossaries".
>> - added the entities
>> <!ENTITY glossary-framework SYSTEM "glossary-framework.xml"> 
>> and <!ENTITY glossary-attachment SYSTEM 
>> "glossary-attachment.xml"> to entities.dtd .
>> - added for these entity calls to ws-policy-framework.xml and 
>> ws-policy-attachment.xml .
>>
>> To run this, you have to check out the new build.xml , 
>> entities.dtd and extract-glist.xsl . That's it.
>>
>>
>> Felix
>>
>