Document schema subsetting/customization

[tcatapano]

From Schema Team meeting notes of 2017-01-10:

Terry will also document how the new EAD3 schema can be customized locally since that new feature hasn’t been documented yet; Terry will include at least one use case and example of this.

[fordmadox]

@tcatapano just noting that we discussed creating a new repository for this. whenever you have time to put something up there, just let us know. i think @regineheberlein might also want to work on this, too. it would be a great way to show folks how they could exclude numbered components, etc.

[kerstarno]

Issue review in preparation to upcoming EAD subteam call on 23 September:

@tcatapano and @fordmadox - what's the current status for this issue?
Also, is this something that could be combined with EAD3 #467 and #501 in a more general documentation on the topic of validation with and customisation of schema(s)?

@karinbredenberg and @fordmadox - if the above is the case, might this rather be an issue for the Schema subteam?

[karinbredenberg]

@kerstarno in the final end it might even end in the handbook? But it sure is part of documentation for the use of the schemas and should be used for all of them. When/if we have a repository it should be moved to that repository and assigned to the Schema team.

Not sure where the things @tcatapano have written is placed. There is no separate repository for it yet, @fordmadox ?

[kerstarno]

During their meeting on 28 October, EAD team of TS-EAS decided to assign this issue along with issues #467 and #501 to @fordmadox as team lead of the Schema team to indicate ownership being with that team.

Given that Schematron is only used with EAD3 at the moment, there remains, however, a close connection to the EAD team in finalising these issues.

[fordmadox]

Just a note / reminder that after EAC-CPF revision goes out for comment, I will create a customized extension for EAD3/EAC-CPF 2.0 which demonstrates how both can be extended and document that on our wiki.