Hi Eddie and other colleagues,
Funnily enough, we were looking at just this issue yesterday when I was
reviewing our metadata standards against AGLS and other Australioan government
recommendations. HealthInsite aims to be AGLS-compliant but it was pointed out
that we use the DC convention for case in element refinements. When I was
developing the HealthInstie standards there was a lot of guess-work because DC
and AGLS were developing at the same time.
My feeling is that the issue is trivial and that harvester software can easily
be adapted to ignore any case differences in the metadata syntax.
Regards, Prue
Prue Deacon
HealthInsite Editorial Team
Commonwealth Department of Health and Aged Care (Australia)
[log in to unmask]
http://www.healthinsite.gov.au
Eddie Byrne <[log in to unmask]> on 02/05/2001 19:35:38
To: [log in to unmask]
cc: (bcc: Prue Deacon/HIID/Health)
Subject: case of elements
Forgive me, I know that this discussion was had in May 1999 (as per
archives search), but the outcome seemed inconclusive (at least re. html).
Rdf/xml lower case seems a foregone conclusion, but what about HTML, or
more specifically the case of qualifiers?
For example. DC.Relation.IsVersioOf or DC.Relation.isVersionOf ?
DC site examples indicate the first as the case to use, however I not that
AGLS specifies the second. What might be the now accepted case convention
if there is such a thing? Or might someone explain why AGLS differ? Is the
AGLS case determined in any way by issues of migration? Or does it matter?
Eddie Byrne
|