Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

TimeItemWhoNotes

AnnouncementsJKPersonally identifiable information in the NAAN registry.  John is looking at Github actions to automatically strip.  Pre-generated 10,000 NAANs to remove need for running eggnog to mint.

Continued discussion of "?info" inflection proposal (latest at the end)

JSON encodings/formats: JSON-LD, geoJSON?

  • what about comments and repeated element keys, which were possible with ERC?

(JK) Proposing ? and ?? be left untouched, "reserved for future use," but ?info would be required.  ?info return metadata would not be detailed in the ARK spec per previous meeting.  Looking for couple volunteers over next month to help brainstorm over what ?info might return. KH, CM, GJ willing to help.

General discussion on JSON, JSON-LD, etc.  (TC) If intent is for machine readability, then JSON is the answer.  TC's group has adopted JSON-LD extensively.  (GJ) JSON-LD is the mainstream practice on the web, and Data Citation Roadmap paper (Fenner et al) recommends it.  Is there any reason to do something different? (GJ) JSON-LD is implementation/serialization of RDF.  Defined by W3C standard, which specifies content negotiation and application/ld+json content type.  (TC) Good reference on understanding JSON-LD, schema.org, etc.: https://developers.google.com/search/docs/guides/intro-structured-data


Status check on milestones; remaining to-do list, and rough estimates for objectives and deliverables

(Technical Working Group)

  • ARK spec (finish draft, circulate, submit to IETF)
  • NAAN procedures
  • ARKS counting

All deliverables delayed.  Deliverables page, charter need updating.  Will visit topic next meeting.

Action items

  •