I vote for no change. I don’t think it is a problem. The entire element is open for interpretation. EHL From: drummond.reed@gmail.com [mailto:drummond.reed@gmail.com] On Behalf Of Drummond Reed
Sent: Tuesday, April 20, 2010 3:24 PM
To: Joseph Smarr
Cc: Eran Hammer-Lahav; xri-comment@lists.oasis-open.org
Subject: Re: [xri-comment] constraint on one-title-per-lang under Link? Joseph, the biggest challenge we have is that any normative change to the spec now that it is in its second public review will require a third public review before it can move on in the OASIS process.
So we could add non-normative language recommending not using more than one Title element with the same lang attribute, but that's as far as we could go unless it's worth a whole 'nother review cycle.
=Drummond On Tue, Apr 20, 2010 at 12:49 PM, Joseph Smarr <jsmarr@google.com> wrote: Hmm, ok I guess that makes sense, and I agree it's unlikely to be a common problem in practice. Do you think it's worth adding any clarifying/recommending language around, or do you want to just leave it alone (honestly, it was a bit unclear/ambiguous to me, so even if you don't want to forbid it, you might clarify that it's not strictly unique, but it's not advisable to have duplicate titles in the same language without some other future differentiating attribute). Thanks, js On Tue, Apr 20, 2010 at 12:24 PM, Eran Hammer-Lahav <eran@hueniverse.com> wrote: There isn’t any. Document authors should not include two titles with the same language. At the same time, I don’t see this as a problem that requires changing the spec to forbid it. Additionally, someone can later extend the Title element to make this useful (differentiating titles with the same language using another attribute). It would be safe to assume that you can just use the first and ignore the rest. Since this is purely a human-readable label with no implications on link selection, it does not pose an interop problem. How people react to XRD information presented to them is outside our scope… EHL In reading through the current draft spec, it's not clear to me whether there is an explicit/implied constraint that there can be at most one <Title> element under a <Link> element per value of xml:lang. In other words, I'm hoping that the following is invalid, but I don't see that explicitly stated anywhere: <Link rel="http://spec.example.net/photo/1.0" type="image/jpeg" href=""http://photos.example.com/gpburdell.jpg"> <Title xml:lang="en">User Photo</Title> <Title xml:lang="en">Second English Title</Title> </Link> I don't see any value in providing multiple titles in the same language, and it's not clear what consumers should do with such a document if they find one (just take the first one and ignore the rest?). If you agree, I'd like to see that explicitly stated in the spec. Any objections? (The reason I bring this up is that I'd like to specify a JSON representation of XRD, and I'm hoping I can have titles be represented as a map/object where the lang value is the key, e.g. "titles": { "en": "User Photo", "de": "German title", ... }, but I can only do that if the spec guarantees that each language can only appear once in a list of Title elements under a given <Link> element.)Thanks, js |