To get back to this...
Oh, I agree -- I think all of the fields in the abstract or API schema
would be wiki:, such that if a given implementor (such as me) wants to
use DC, any reference to say, dc:creator is automatically mapped to
wiki:author (or whatever it is) in the backend. I'm not suggesting
that
a transformation happen on the fly, as if one could change the schema
of an existing installation. This would be a configuration issue, and
I've already got a pretty good idea how to do it.
Ah, ok, now I see what you're after. I agree, this might probably be
the best thingy overall. If we have a very tight specification for
our own metadata items, they will be unambiguous to us, and it will
allow 3rd party provider developers to store them in whatever format
they want. We would probably ship with a simple mapping to a file
system/db, but you would be free to store the wiki:author under
dc:author or whatever.
This sounds fair to me.
No, it's not. That's what you use an application profile to define.
DC is designed for broad interoperability across thousands of systems,
but if you want to constrain things or use particularly encodings,
you do that in an application profile. The profile has to be in accord
with DC, IOW it is stricter than DC. DC has to be lenient by design.
I still think this creates IOP problems, but that's now outside this
discussion. I personally don't like specs which leave too much
things for "application profiles". But then again, I work for a
telecommunications device manufacturer, who tend to be very precise
when writing a spec ;-)
To reiterate, what I'd suggest is that we define an abstract
metadata
schema in our own namespace, with as tight a set of constraints and
definitions as we need to function. That's what the system uses. I
can *still* write that up as an application profile for DC, using DC
terms where they make sense and putting anything else in as
extensions.
Yup, I think we're in agreement here.
Would you like to write up the discussion to the JSPWiki3Design page,
and refresh the metadata items to what we discussed, and have a first
stab at the definitions?
/Janne
