Metadata Generation

Cantor, Scott cantor.2 at osu.edu
Tue Sep 23 10:04:02 EDT 2014


On 9/23/14, 3:58 AM, "Rod Widdowson" <rdw at steadingsoftware.com> wrote:
>
>It did occur to me that idp.properties has all the information needed to
>do
>simple metadata configuration:  entityID, tls and signing keys and
>(eventually) back channel support and so it is the natural source for
>information for a program to go between a template metadata file and an
>example metadata file.

If so, that's a happy accident, but that would be useful.

>Does this make sense?  I'm sure we can do it in Ant (after all that¹s what
>V2 does), but given that the long term aim is to be able to drop entire
>sections would XPATH be a better bet?

I don't know that XSLT gives you that much advantage over just brute force
generating something. I suppose it makes it a bit easier to store the
"template" as XML rather than as scripting code, but for now I don't think
it matters all that much.

Something akin to what my metagen script in the SP does is probably good
enough for a start, but in Java code rather than shell.

-- Scott



More information about the dev mailing list