Skip to content
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

Update index.html #172

Merged
merged 1 commit into from
Apr 6, 2018
Merged

Update index.html #172

merged 1 commit into from
Apr 6, 2018

Conversation

laudrain
Copy link

@laudrain laudrain commented Apr 5, 2018

identifiers and/or addresses allow to retrieve the WP, why representation?


Preview | Diff

the address allow access to the WP.
@mattgarrish
Copy link
Member

mattgarrish commented Apr 5, 2018

Removing "representation of" looks fine to me, but I believe @iherman authored this section so I'm hesitant to approve. Was this written when we were thinking there might be different ways of crafting web publications? (html or json manifests, for example)

FYI, I removed the emoji that's breaking the diff from the first comment in issue #36, but it looks like the program is building from a cached snapshot.

@iherman
Copy link
Member

iherman commented Apr 5, 2018

@mattgarrish @laudrain I am fine with the removal. Using the term "representation" tries to be overly precise (per Web Architecture) but is not necessary here imho. (I do not know whether it is indeed I who wrote it...)

@dauwhe
Copy link
Contributor

dauwhe commented Apr 5, 2018

I'm fine with the change, but what function does this paragraph serve? It's saying that a WP might have more than one URL.

  1. Does this paragraph have any normative force? This doesn't seem testable.

  2. Is it a good idea for a WP to be available at multiple URLs? If so, is this something that needs to be discussed in the spec, or are we telling people how to design servers, business models, etc.?

@mattgarrish
Copy link
Member

Does this paragraph have any normative force? This doesn't seem testable.

I don't think the paragraph has much practical value, to be honest. We don't normatively restrict a WP to one URL, so we're sort of affirming the reality of the web. It looks like it should also be a note, especially the way its positioned between two other notes.

Is it a good idea for a WP to be available at multiple URLs?

I don't see how this could be prevented. As I read the statement, all I see it saying is:

  1. it's possible to retrieve the web publication without going through the address (e.g., from one of the constituent resources)
  2. there may be many paths to the address via different urls (e.g., the output of a url shortener; redirects on alternate addresses that are more human-friendly to remember; DOIs and the like).

Whether it's necessary to say this is debatable.

@dauwhe dauwhe merged commit 3b69d3a into master Apr 6, 2018
@dauwhe
Copy link
Contributor

dauwhe commented Apr 6, 2018

We seem to have consensus on the smaller issue of the language. This was discussed a bit during the PBG steering committee meeting, so I'm comfortable merging this. We can open a new issue on the normative value of this paragraph.

@dauwhe dauwhe deleted the infoset branch April 6, 2018 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants