Page tree
Skip to end of metadata
Go to start of metadata

Date

Attendees

Goals

Discussion items

TimeItemWhoNotes

announcements
None

Updates from the DWeb Camp (Decentralized Web Conference)John 

3 days devoted to decentralized approach to web; response to current threats to web preservation. JK framed AITO talk by referencing UC open scholarship culture and the current work vis a vis Elsevier.

Discussion w/Tim Berners-Lee about W3C take on persistent identifier systems. Recommendation: do a pull request to put the issue forward for consideration with W3C technical architecture group. 

Also noted: community in Argentina may have developer time to build turn-key support for ARKs in DSpace.


Strategizing for updates to the English ARK wikipedia page

Note there are two other versions of this page:
   French https://fr.wikipedia.org/wiki/Archival_Resource_Key
  Spanish https://es.wikipedia.org/wiki/Archival_Resource_Key

For comparison, here are wikipedia pages on
   https://en.wikipedia.org/wiki/Digital_object_identifier
   https://en.wikipedia.org/wiki/Handle_System
   https://en.wikipedia.org/wiki/Persistent_uniform_resource_locator
   https://en.wikipedia.org/wiki/Uniform_Resource_Name


French and Spanish appear to follow the English version of the page closely. How are they maintained? How do bilingual readers chose which version to consult? Sebastien notes that he will compare the apparent quality of FR and EN versions of Wikipedia pages, and will go w/FR if they appear to be roughly the same. EN if it looks better developed/more detailed. In general, if the topic is not found when searching a non-English wikipedia, it offers the English page if there is one.

It would be useful for us to have the FR, SP versions of the page to have the same content as the EN page. There might be things in the FR version that are not in the EN version.

Kurt: Populate Wikipedia page with more information. Pull information out of the FAQs. Add links out to some of the other resources we’ve already created.

J: is there information that you think is lacking?

Consider making it correspond more to the DOI outline.

Peter: Name assigning authority info in the current ARK Wik seems unnecessary. PURL entry has a history section (not present in DOI) – would be a good addition for ARKs.

Missing: what ARKs are and how you would use them.

Wikipedia’s strength is in helping you understand why things are – a history. This focus would prevent Wikipedia from being a duplicate of the FAQ.

Wikipedia page needs citations. That’s another way that we could boost the FAQ's prominence. What are other external sources we can cite? We don’t really have too many citable publications. Look for publications on persistent identifiers. Presentations at conferences?

Bertrand: have the architecture/anatomy section later in the document; don’t lead with it.

We always insist that persistence is a matter of service, and yet we start w/anatomy, that gives the impression that there’s something magic about it, when there’s not.

JK: On almost any tech topic, I usually choose the Wikipedia page over the main website for the thing. A little more neutrality/less marketing. “I’m glad I went to the Wikipedia page first”. More important to get that right than the ARKs.org brochure page?

Sebastien: Focus on information that is for newbies; concise, non-technical, accessible. Anyone can know what ARKs are for. That’s what Wikipedia is about.

Action items