MD_ProjectionParameters

ISO standard of projection parameter is given in MD_ProjectionParameters of ISO 19115.

Unfortunately it is not in WMO Core Profile v1.1 of Metadata.

But at least we can safely say that if we are going to define something, we have to respect that.

Thanks for response: relative URI in OAI

Glad to see a response. 

http://www.openarchives.org/pipermail/oai-general/2010-May/000507.html

It's good to see the OAI community shares my sense that relative URI is no good.  I have nothing to add, but i didn't know TAG httpRange-14 which is pretty informative.

• http://www.w3.org/2001/tag/issues.html#httpRange-14
• http://www.kanzaki.com/memo/2005/06/22-1 (in Japanese language)

IPET-MDI-1 final report about to conclude

there seems to be no new issue is coming arise.  I think it must conclude this week.
i haven't finished the task list I've offered though....

an essay on OAI-PMH in WIS

http://docs.google.com/Doc?docid=0AdzHt7XJp45TZGY0a21ncXNfNTJ4N3FjbjRobQ&hl=en

(Gmail) keyboard shortcut to remove label?

I use several labels as multiple inboxes so I'm frustrated everyday
when I mark read threads and try to delete label. Maybe there is
better style of working....

mail to blog was so nice

I found blogspot.com accepts email to secret address as a post. It's
so nice! This would be my memopad. And some open discussion could be
blogged by BCC:-ing.

How to insert multiple language texts into ISO 19139 metadata document

I was long wondering. I knew there is xml:lang global attribute, but
as stated in Section 6.6 of the standard, "[i]f a particular element
can only occur once based on the encoding rules discussed in Clause 8
then the technique of using the special xml:lang attribute to indicate
the language does not allow for the specification of the same element
in two or more languages."

But Appendix D.4 shows alternative way.

Firstly, there must be default locale (set of language and character
set) as MD_Metadata/*[language or characterSet]:

<language>
<LanguageCode codeList="resources/Codelist/gmxcodelists.xml#LanguageCode"
codeListValue="eng"> English </LanguageCode>
</language>
<characterSet>
<MD_CharacterSetCode
codeList="resources/Codelist/gmxcodelists.xml#MD_CharacterSetCode"
codeListValue="utf8"> UTF-8 </MD_CharacterSetCode>
</characterSet>

And then there must also be alternate locale at MD_Metadata/locale:

<locale>
<PT_Locale id="locale-fr">
<languageCode>
<LanguageCode codeList="resources/Codelist/gmxcodelists.xml#LanguageCode"
codeListValue="fra"> French </LanguageCode>
</languageCode>
<characterEncoding>
<MD_CharacterSetCode
codeList="resources/Codelist/gmxcodelists.xml#MD_CharacterSetCode"
codeListValue="utf8">UTF 8</MD_CharacterSetCode>
</characterEncoding>
</PT_Locale>
</locale>

Finally we can use this construct in <abstract>

<abstract xsi:type="PT_FreeText_PropertyType">
<gco:CharacterString>Brief narrative summary of the content of the
resource</gco:CharacterString>
<!--== Alternative value ==-->
<PT_FreeText>
<textGroup>
<LocalisedCharacterString locale="#locale-fr">Résumé succinct du
contenu de la ressource</LocalisedCharacterString>
</textGroup>
</PT_FreeText>
</abstract>

Complex, isn't it?

If we cannot speak French, we can prepare a reference and let French
guy write translation file:

<abstract xsi:type="PT_FreeText_PropertyType">
<gco:CharacterString>Brief narrative summary of the content of the
resource</gco:CharacterString>
<!--== Alternative value ==-->
<PT_FreeText>
<textGroup xlink:href="fr-fr.xml#abstract-fr"/>
</PT_FreeText>
</abstract>

In this way there must <textGroup>. If none, we have to edit
English-only version.