decoration decoration
Stories

GROKLAW
When you want to know more...
decoration
For layout only
Home
Archives
Site Map
Search
About Groklaw
Awards
Legal Research
Timelines
ApplevSamsung
ApplevSamsung p.2
ArchiveExplorer
Autozone
Bilski
Cases
Cast: Lawyers
Comes v. MS
Contracts/Documents
Courts
DRM
Gordon v MS
GPL
Grokdoc
HTML How To
IPI v RH
IV v. Google
Legal Docs
Lodsys
MS Litigations
MSvB&N
News Picks
Novell v. MS
Novell-MS Deal
ODF/OOXML
OOXML Appeals
OraclevGoogle
Patents
ProjectMonterey
Psystar
Quote Database
Red Hat v SCO
Salus Book
SCEA v Hotz
SCO Appeals
SCO Bankruptcy
SCO Financials
SCO Overview
SCO v IBM
SCO v Novell
SCO:Soup2Nuts
SCOsource
Sean Daly
Software Patents
Switch to Linux
Transcripts
Unix Books

Gear

Groklaw Gear

Click here to send an email to the editor of this weblog.


You won't find me on Facebook


Donate

Donate Paypal


No Legal Advice

The information on Groklaw is not intended to constitute legal advice. While Mark is a lawyer and he has asked other lawyers and law students to contribute articles, all of these articles are offered to help educate, not to provide specific legal advice. They are not your lawyers.

Here's Groklaw's comments policy.


What's New

STORIES
No new stories

COMMENTS last 48 hrs
No new comments


Sponsors

Hosting:
hosted by ibiblio

On servers donated to ibiblio by AMD.

Webmaster
Isn't it Oracle's burden to identify the SSO | 451 comments | Create New Account
Comments belong to whoever posts them. Please notify us of inappropriate comments.
Isn't it Oracle's burden to identify the SSO
Authored by: Anonymous on Friday, May 04 2012 @ 05:34 AM EDT
See the other answer from 'Anonymous' (not myself!) to the same post:
Your structure is the same (heirarchical).
Your sequence is the same (alphabetical) and
Your organization is the same (clustered by function)
I think that describes what SSO is and how it is not really about names. It is like the meta-language for the Java naming.

Take for example the java.lang package. You can replace all names with something else, such as use alfa.bravo or x.y, but it will have the same SSO as Java because it will have the same organization and structure.

But this makes me wonder... if I write a book with the following TOC:

  1. Introduction
  2. Background
  3. System architecture
  4. Result
  5. Conclusion
Can I sue anybody using the same TOC, even if they use different names? Crazy!

[ Reply to This | Parent | # ]

Groklaw © Copyright 2003-2013 Pamela Jones.
All trademarks and copyrights on this page are owned by their respective owners.
Comments are owned by the individual posters.

PJ's articles are licensed under a Creative Commons License. ( Details )