RE: Glossary for editor's copy ready

Right, I think that the attachment doc should not have the definitions
inline that it does..  They should all be sourced from the glossary
extract. 

I'm running short on time today, can you do that change?  If not, I'll
get to it tomorrow before doing the email to the WG.

Cheers,
Dave
> 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
> >>
> > 
> 
> 
>

Received on Tuesday, 5 September 2006 00:23:26 UTC