IdP 3.4: Deprecated items in custom Syntax

[Takeshi NISHIMURA]

We have experienced troubles about old format and new format of attribute-resolver.xml. For example, our example snippet in old format cannot apply to attribute-resolver.xml in 3.3.1.

So we need a conversion guide from old format to new format. Newer
deployers can use this guide to convert snippets before applying them to
their system.

As for deprecated features, we need to clarify "non-deprecated feature" in
the following text:
https://wiki.shibboleth.net/confluence/display/IDP30/AttributeResolverConfiguration
> With V3.3, every non-deprecated feature can be defined in the main urn:mace:shibboleth:2.0:resolver namespace

I know ad:SAML2NameID is deprecated but also exists in resolver: namespace.
There may be a timing issue (it was not deprecated til 3.3 release) or
there may be two types of deprecated features.

Would all currently deprecated features (and possibly in future but before
4.0) be removed from 4.0?

>> The definite downside is that we would now have the "this is deprecated" information in two places

Another method come to my mind is labeling "DEPRECATED3.4" or so in each deprecated feature page. A deprecated list can be generated using these labels.

Best regards,
Takeshi

On 2017/09/22 1:26, Cantor, Scott wrote:
> On 9/21/17, 6:32 AM, "dev on behalf of Rod Widdowson" <dev-bounces at shibboleth.net on behalf of rdw at steadingsoftware.com> wrote:
> 
>> Does anyone think that this is a bad idea?
>>
>> Does anyone have any observations about the wider problem and how/whether to document it?
> 
> Well, the out of sync issue is an issue, but I guess I view this as something that mostly comes into being when we're working towards 4.0 and obviously part of that transition material would include what's been removed.
> 
> So it wasn't something I wasn't going to do, I just didn't see it as necessary at this stage.
> 
>> Does anyone have suggestions of where to put such page(s)?
> 
> If it's separate from the 4.0 upgrade material, I guess probably in a top level page under Configuration down near the bottom of that list.
> 
> -- Scott