RE: [dss] Naming convention proposal

[Tim Moses <tim.moses@entrust.com>]

Nick - I am exploring this.  It appears there is earlier work.  But, its
status is unclear.  I'll investigate.  Currently, KAVI cannot allocate file
space on command - it chooses its own file paths.  I'll let people know what
I find out.  All the best.  Tim.

-----Original Message-----
From: Nick Pope [mailto:pope@secstan.com]
Sent: Tuesday, August 26, 2003 10:32 AM
To: Rich Salz; Tim Moses
Cc: 'DSS'
Subject: RE: [dss] Naming convention proposal


I am very supprised that we are the first to get into this issue.  How do
other existing OASIS schema identify themselves?  Doesn't the OASIS web
master need to be involved so that the refences point to real objects?

Nick


> -----Original Message-----
> From: Rich Salz [mailto:rsalz@datapower.com]
> Sent: 25 August 2003 17:11
> To: Tim Moses
> Cc: 'DSS'
> Subject: Re: [dss] Naming convention proposal
>
>
> > Colleagues - Below, find a proposal for a convention for naming
> the objects
> > we will define.  To the best of my knowledge, this does not
> conflict with
> > any OASIS convention (indeed, we could lobby for this to become
> the OASIS
> > convention).  Any comments?  All the best.  Tim.
>
> Brilliant.  Lobbying is called for.  My only suggestion is to insert a
> fixed RDN before the committee part, so that it's easier to write a
> single URL redirection rule; the actual value doesn't matter.  But the
> example:
>    http://www.oasis-open.org/dss/v1.0/schema/timestamp-token/wd/v01.xsd
> could become something like (adding "/tc"):
>    http://www.oasis-open.org/tc/dss/v1.0/schema/timestamp-token/wd/v01.xsd
>
> You may leave a Technical Committee at any time by just sitting on yours
> hands....
>
> 	/r$
>
> --
> Rich Salz, Chief Security Architect
> DataPower Technology                           http://www.datapower.com
> XS40 XML Security Gateway   http://www.datapower.com/products/xs40.html
> XML Security Overview  http://www.datapower.com/xmldev/xmlsecurity.html
>
>
> You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/dss/members/leave_workgroup.php