Talk:Bookland

Latest comment: 14 years ago by SarekOfVulcan in topic Merge discussion

Imaginary Place?

edit

This article should be renamed Bookland (barcode). It's about a barcode, not an imaginary place. It may use a fictitious location code, but it's about a barcode.--RLent (talk) 20:12, 3 June 2008 (UTC)Reply

Move?

edit
The following discussion is an archived discussion of a requested move. Please do not modify it. Subsequent comments should be made in a new section on the talk page. No further edits should be made to this section.

The result of the move request was moved to Bookland. Aervanath (talk) 16:54, 30 March 2009 (UTC)Reply


It seems my suggestion was misinterpreted: I meant to move Bookland (imaginary place)'s info to Bookland, and redirect Bookland (imaginary place) back to Bookland; where the material is kept. Eh, seems fine now, though perhaps it should just be called Bookland instead of the clunky Bookland (imaginary place) (umm...). And *loud hacking cough*, it is supposed to be Bookland (fictional location); see Fictional location: second sentence. Wonder why no one else noticed it... *sigh* Oh, well, we just have to wait until some admin comes and reprimises everything correctly.
7h3 0N3 7h3 \/4Nl)4L5 Pl-l34R ( t / c ) 04:58, 24 March 2009 (UTC)Reply
Ummm... you read the article, right? It's a special code configuration assigning books to a corresponding fictional location on the globe... and for... please read Fictional location:second sentence again. *sigh*
7h3 0N3 7h3 \/4Nl)4L5 Pl-l34R ( t / c ) 01:13, 26 March 2009 (UTC)Reply
I think what they meant by not a fictional location, is that there is no description of bookland, other than the vague "that's where books come from". Normally with a fictional location there is a very rich description of the fictional location, like middle earth, or in the Harry Potter books. So in that sense, no it is not a fictional location, it is a fictitious location. And yes it is certainly a hack to make the system work. 199.125.109.126 (talk) 06:25, 29 March 2009 (UTC)Reply
The above discussion is preserved as an archive of a requested move. Please do not modify it. Subsequent comments should be made in a new section on this talk page. No further edits should be made to this section.


"Musicland" is a similar concept to Bookland, for the transcoding of ISMN10 sheet music id number into ISMN13 EAN prefix 979 (note this prefix is shared with ISBN, the "M" in the ISMN transcodes as 0, and the checkdigit remains the same because ISMN uses the GS1 algortihm. Hence 9790 is sheet music.) New ISMN prefixes will be issued as ISMN13 as of mid 2008 http://ismn-international.org/download/GuidelinesGeneral.pdf —Preceding unsigned comment added by 94.125.16.11 (talk) 14:20, 24 December 2009 (UTC)Reply

Merge discussion

edit
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
Uninvolved admin determined there was no consensus to merge to EAN. --SarekOfVulcan (talk) 20:31, 13 November 2010 (UTC)Reply

OK, I'm pretty annoyed by everyone here. Can we please discuss the merger rather than just edit war over it? An article which was just kept at AfD really shouldn't be merged without some form of discussion. We take it as granted that this article meets notability requirements--thus the keep. Let's move forward and see why this should be merged. I certainly believe that as it stands the merge target has way too much on this topic in proportion to its importance to the topic. A sentence or 3 would be plenty. I also don't see the reason to merge this. It is, in my opinion, an interesting topic that certainly has plenty of coverage and real-world relevance. So, why merge? Hobit (talk) 00:38, 7 October 2010 (UTC)Reply

The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.