gian/resync
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

More questions about <rs:ln>

Browse Source
This commit is contained in:
Simeon Warner 2013-06-17 17:50:48 -04:00
parent bd5a644f7e
commit e85e284550
1 changed files with 6 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
TODO.md
View File

@ -14,10 +14,15 @@ Questions about ResourceSync v0.9 spec
Example 2.7
-----------
- this is the only example that gives a content type for the <rs:ln rel="describedby" .../>. Should we either be consistent with that or maybe drop it here too?
- this is one of three examples (2.7, 9.1, 9.2) that give a content type for the <rs:ln rel="describedby" .../>. Example 2.6 does not have a type attribute. Should we either be consistent and use that always, or is a mix better?
- I am not sure the rel="describedby" within the <url> block for the capability list has the correct meaning. Doesn't it mean in that context that the capability list if descibedby the giev resource? That seems not quite the same as our usual interpretation of top level rel="describedby" which we take to be a description of the set of resources rather than the capability document.
Section 3
---------
- The description of top-level <rs:ln ... /> says "It can have several attributes and the ones defined in the ResourceSync XML Namespace are as follows:" ... and then describes just the rel and href attributes. The examples 2.7, 9.1 and 9.2 also use the type attribute which should presumably be added to this list. I would also change the description to be more specific about attributes, perhaps: "Three attributes are defined in the ResourceSync XML Namespace and are listed below, other attributes may also be used:"
Section 9.2
-----------