Okay to update file names to saml-x instead of sstc-saml-x ??

Hi Scott and all,

Noting that:

1 - almost all of the TC's Work Products started since early 2011 have used file names beginning simply "saml-x" instead of "sstc-saml-x" [1]

2 - These two latest documents [2] are being published for the first time (although the templates were initiated in 2010)

Is there any objection to modifying the file names to match the more modern style?

That is:

saml-channel-binding-ext-v1.0.xxx instead of sstc-saml-channel-binding-ext-v1.0.xxx

and

saml-ecp-v2.0.xxx instead of sstc-saml-ecp-v2.0.xxx

The schema file for ECP already follows (somewhat) this pattern:

saml-schema-ecp-2.0

I note that the schema file for "channel-binding" contains a self-referential line in the "documentation" element:

Document identifier: sstc-saml-channel-binding-ext-v1.0.xsd

which would need to be modified in a future stage of publication.

Neither of the prose document files contains any references which would need to be modified.

If there is no serious objection, I'd like to use the current naming practice for these publications, since it will set the pattern for all the future publications of these Work Products.

Presumably, you would want to similarly modify the file names for future Working Drafts, as well.

Thanks and best regards,

Paul

[1] for example:

saml-async-slo

saml-kerberos-browser-sso

saml-metadata-rpi

saml-session-token

[2] https://tools.oasis-open.org/issues/browse/TCADMIN-1289

SAML V2.0 Channel Binding Extensions Version 1.0

https://tools.oasis-open.org/issues/browse/TCADMIN-1291

SAML V2.0 Enhanced Client or Proxy Profile Version 2.0

-- 
Paul Knight  - Tel: +1 781-861-1013
OASIS - Advancing open standards for the information society

Document Process Analyst