New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

collection link element properties #484

Closed
GoogleCodeExporter opened this Issue Mar 24, 2015 · 4 comments

Comments

Projects
None yet
2 participants
@GoogleCodeExporter
Copy link

GoogleCodeExporter commented Mar 24, 2015

When using link elements in the manifest collection, we find ourselves in the 
need of expressing properties of the idenfified resources, see for example DO 
2.2.2.3 
(https://docs.google.com/document/d/1Ofy-rXs_79qJmvZnOoSazRnRuKUOd2saJeBkxBynYpI
/edit#heading=h.vb4juhsy12yy). 

We should consider adding the properties attribute to Package Document link 
elements, alternatively define & bless a way to use @rel for these purposes.

Original issue reported on code.google.com by markus.g...@gmail.com on 27 Nov 2014 at 8:07

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Mar 24, 2015

[deleted comment]
@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Mar 24, 2015

The (small) problem with @rel is that it only makes sense for some values of 
@properties:

<link rel="nav" href="..."/> -- OK
<link rel="nav scripted" href="..."/> -- WEIRD

Restricting the item vocab terms that can be used in @rel might solve that 
weirdness, since the general properties can be expressed on the <item> entry 
without conflict. It's only the restricted properties that cause a headache.

Original comment by mgarrish on 15 Dec 2014 at 2:05

@GoogleCodeExporter

This comment has been minimized.

Copy link

GoogleCodeExporter commented Mar 24, 2015

"cover-image" and "nav" are the only two properties we need a unique way to 
express for collection resources, with "data-nav" in the pipeline.

Original comment by mgarrish on 15 Dec 2014 at 2:16

@mattgarrish

This comment has been minimized.

Copy link
Member

mattgarrish commented Jan 11, 2016

Attribute was added for this reason and to allow generic record types to be identified.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment