Thanks a lot for catching this!
> I just sent a response mentioning ResourceSync,
I don't see your response at
. Looking at the thread, I think ResourceSync is definitely in scope.
Even though it's not JSON-based, which seems to be a must, nowadays.
> but I notice there's no
> defined MIME content type for change lists (etc.), which appears to be a
> requirement (from subsequent discussions in that thread).
> Is this an omission?
That question never came up actually. Allow me to break this down:
1. All ResourceSync documents are XML, mime type application/xml
2. All ResourceSync document comply to the same "profile", ie Sitemap
XML document formats.
3. The difference in semantics of the various documents is conveyed by
the top level rs:md element, e.g.:
=> Resource List: <rs:md capability="resourcelist" at="2013-01-03T09:00:00Z"/>
=> Change List: <rs:md capability="changelist"
I could imagine trying to register application/resourcesync+xml. But I
doubt that an attempt to register e.g.
application/resourcesync+changelist+xml would be met with a lot of
enthusiasm at IETF/IANA. But you would be a much better judge than me
in that realm.
> You received this message because you are subscribed to the Google Groups
> "ResourceSync" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to resourcesync...@googlegroups.com
> For more options, visit https://groups.google.com/groups/opt_out
Herbert Van de Sompel
Digital Library Research & Prototyping
Los Alamos National Laboratory, Research Library