The Dublin Core metadata element set
is a standard for cross-domain information resource description.
|
||
Element | Description | Value |
---|---|---|
Identifier | resource ID | http://old.zope.org/Collectors/ZopeOrg/307 |
Title | resource name | Zope/Plone Chinese website/mailing list |
Description | resource summary | Hi Webmaster, Happy New Year! :) I'd be most grateful if you could list our Zope and Python Chinese forums / user groups. (Since the site is UTF-8 you can just copy paste the Chinese characters into it, even if you probably can't see them.) I suggest something like this: ZOPE USER GROUPS http://www.zope.org/Resources/UserGroups/ : Chinese speaking Zope and Python users should consider visiting the <A HREF="http://zope.cn/">Zope/Plone Chinese User Group</A> (<A HREF="http://zope.cn/">Zope/Plone中文社区</A>) and the <A HREF="http://python.cn/">Python Chinese User Group</A> (<A HREF="http://python.cn/">Python中文社区</A>). ZOPE MAILING LISTS http://www.zope.org/Resources/MailingLists <A HREF="http://zope.cn/">Zope/Plone中文 (Chinese)</A> Zope/Plone list for Chinese speakers [[email protected]]. See also <A HREF="http://zope.cn/">Zope/Plone Chinese User Group</A> (<A HREF="http://zope.cn/">Zope/Plone中文社区</A>). ZOPE EXITS Finally, I don't know what your requirements are for being a "Zope Exit", but it would really help us build steam behind the Chinese community if you under Zope Exists also added a "Zope/Plone Chinese" link to http://zope.cn/ Even better if you can write it like this: "Zope/Plone 中文" (the last two characters mean Chinese in Chinese). If you like, you can remove Plone, so it's just "Zope 中文". |
Creator | resource creator | bjorn |
Date | default date | 2004-01-11 08:46:03 |
Format | resource format | text/html |
Type | resource type | Collector Issue |
Subject | resource keywords | content, doc, medium |
Contributors | resource collaborators | |
Language | resource language | |
Publisher | resource publisher | No publisher |
Rights | resource copyright | |
|
||
Element | Description | Value |
CreationDate | date resource created | 2004-01-11 08:46:00 |
ModificationDate | date resource last modified | 2004-01-11 08:46:03 |
EffectiveDate | date resource becomes effective | None |
ExpirationDate | date resource expires | None |
Backlinks:
via
Google
/
Technorati
RDF:
view RDF data