Upload
kelsey-long
View
20
Download
0
Embed Size (px)
DESCRIPTION
Issue: Standardized Categorization, Partitioning, Collections,and Unique Identification to support Discovery and Use through a Registry or Namespace or Namespace URI + filepath conventions. Names, IDs, Categorization, Classification. - PowerPoint PPT Presentation
Citation preview
Issue:Standardized
Categorization,Partitioning,
Collections,and Unique Identification
to supportDiscovery and Use
through a Registry or
Namespace or Namespace URI + filepath
conventions
Names, IDs, Categorization, ClassificationPerspective Formal
UMM ViewCategorization
& Association
Collection ID Unique ID or
Name for ObjectRelated Worksheet
Business Domain Modeling
Business Domain View (BDV)
Business Model Identification
Business Area
Business Process
Business Process Area
Business Context
Business Collaboration Modeling
Business Requirements View (BRV)
Business Process Use Case
Business Entity Type Description
Business Entity Type State Model
Business Collaboration
Business Collaboration Rules Table
Economic Contract
Economic Resource Type
Economic Event
Business Transaction Modeling
Business Transaction View (BTV)
Business Transaction
Business Transaction Property Value
Initiating/Responding Activity Information
Business Information Content Description
Business Information Content Mapping
Core Components Discovery
What goes here to support registry?? And web services??
CollaborationService
Resources
Process Agreements
Global Registry of ThangsGlobal Registry of Thangs
Documentation
ebxmlModels
UDDI Reg Agreements
NamespacesebXML Reg Agreements
Subscriptions
TranslationDependencies Events
Actors
How does REA, UDEF, Catalog of BPC, and Catalog of CCsupport attaching metadata that provides business context, application context, hierarchy of collections, associations?
application
service
Standardization ofpartitioning decisions
by a Enterprise,
Consortium, Standards Body,
Community of Practice, orDomain
Responsibility, Accountability, and Authority (RAA) Established to Govern Functioning of Business, Process, Data, and System Areas
Partitioning of Business Supported by Taxonomies:
?
Partitioning of Types of Ownership
Supported by:
?
Business Area
Supplier MgmtBusiness Area
EngineeringBusiness Area
ManufacturingBusiness Area
Customer Supprt
Business - Transport
DataOwner
ProcessOwner
SystemOwner
BusinessArea
Owner
DataOwner
ProcessOwner
SystemOwner
BusinessArea
Owner
DataOwner
ProcessOwner
SystemOwner
BusinessArea
Owner
DataOwner
ProcessOwner
SystemOwner
BusinessArea
Owner
ServiceOwner
ServiceOwner
ServiceOwner
ServiceOwner
GuidingGoal/Objective
Governing Body
M:1Supports
Attr: Area of Applicability Has 1:M
Issue/Opportunity
M:MPromptsAction
Governing Artifact
Vision
Mission
Strategy
BusinessPlan
BusinessDriver
ProcessDriver
1:M Supports
1:M Supports
M:MSupports
M:M Supports
Attr: Area of Applicability Has 1:M
1:M Drives
Out
M:M Drives
Out
M:M Drives
Out
**
*
TechnologyDriver
GuidingGoal/Objective
Governing Body
M:1Supports
Attr: Area of Applicability Has 1:M
Issue/Opportunity
M:MPromptsAction
Governing Artifact
Vision
Mission
Strategy
BusinessPlan
BusinessDriver
ProcessDriver
1:M Supports
1:M Supports
M:MSupports
M:M Supports
Attr: Area of Applicability Has 1:M
1:M Drives
Out
M:M Drives
Out
M:M Drives
Out
**
*
TechnologyDriver
GuidingGoal/Objective
Governing Body
M:1Supports
Attr: Area of Applicability Has 1:M
Issue/Opportunity
M:MPromptsAction
Governing Artifact
Vision
Mission
Strategy
BusinessPlan
BusinessDriver
ProcessDriver
1:M Supports
1:M Supports
M:MSupports
M:M Supports
Attr: Area of Applicability Has 1:M
1:M Drives
Out
M:M Drives
Out
M:M Drives
Out
**
*
TechnologyDriver
GuidingGoal/Objective
Governing Body
M:1Supports
Attr: Area of Applicability Has 1:M
Issue/Opportunity
M:MPromptsAction
Governing Artifact
Vision
Mission
Strategy
BusinessPlan
BusinessDriver
ProcessDriver
1:M Supports
1:M Supports
M:MSupports
M:M Supports
Attr: Area of Applicability Has 1:M
1:M Drives
Out
M:M Drives
Out
M:M Drives
Out
**
*
TechnologyDriver
Governing Artifacts (GAs) Established Which Provide Parameters to
Business, Process, Data, and Systems
GuidingGoal/Objective
Governing Body
M:1Supports
Attr: Area of Applicability Has 1:M
Issue/Opportunity
M:MPromptsAction
Governing Artifact
Vision
Mission
Strategy
BusinessPlan
BusinessDriver
ProcessDriver
1:M Supports
1:M Supports
M:MSupports
M:M Supports
Attr: Area of Applicability Has 1:M
1:M Drives
Out
M:M Drives
Out
M:M Drives
Out
**
*
TechnologyDriver
The GAs have applicability to 1 or More 1 or More Communities of Practitioners Communities of Practitioners who have different focuses and who apply these in ways applicable to their focus.
Domain
Registrars
Domain Content Owners
DomainStewards
Community of Practice
DomainRegistry
DomainRepository
Domain
Registrars
Domain Content Owners
DomainStewards
Community of Practice
DomainRegistry
DomainRepository
Domain
Registrars
Domain Content Owners
DomainStewards
Community of Practice
DomainRegistry
DomainRepository
Partitioning of Domains Supported by:
?
DataOwner
ProcessOwner
SystemOwner
BusinessArea
OwnerServiceOwner
Domain
Registrars
Domain Content Owners
DomainStewards
Community of Practice
DomainRegistry
DomainRepository
InterchangeInformation
Modeling
InterchangeInformation
Modeling PatternsPatterns
LibrariesLibraries
MethodologyMethodology
PatternsPatterns
LibrariesLibraries
MethodologyMethodology
Business Process &
Collaboration Modeling
Business Process &
Collaboration Modeling
MetamodelMetamodel
RulesRulesRulesRules
Sole Authority Design Artifacts
Models, Rules, Policies, Procedures
The Domain organizational mechanism is set up to give a Community of Practitioners the RAA to establish the Models, Rules, Policies, Procedures, and Sole Authority Design Artifacts which will support Data Sharing and Interoperability as we move towards a eBusiness internet connectivity and websevices business applications model.
The Domain organizational mechanism allows the Community of Practitioners to establish Configuration Control over the Artifacts they create (their GAs).
The Domain Stewardship mechanism also provides the dispute resolution processes to drive down interoperability into sub-domains and ensure interoperability across domains.
Partitioning of Views Supported by:
?
Registry Mirrors thesePartitioning decisions
via
Collections &Associations
RegistryRecord
RegistryEntry MetadataExpirationmajorVersionminorVersionStability = Dynamic, DynamicCompatible, StaticStatus = Submitted, Approved, Deprecated, WithdrawnuserVersionId
RegistryObject MetadataobjectType = (see slide 5 for collections)NameDescriptionaccessControlPolicy
IntramuralAssociation
Key to RegObjassociationType =
RelatedToHasMemberExternallyLInksContainsEquivalentToExtendsImplementsInstanceOfSupersedesUsesReplacesSubmitterOfResponsibleFor
sourceObjectTargetObject
ClassificationScheme
TaxonomyIDisInternal = T,F
ClassificationNode
TaxonomyIDcode
1..*
1..*
nodeType
UniqueCodeEmbeddedPathNonUniqueCode
1..1
Classification
classifiedObject = Reg Obj ID
externalClassifcation Scheme idnodeRepresentationinternalclassificationNode id
1..*
Business Consortia Stds Body
SubmittingOrganization
RegistryUser
Subscription
Dependency
ExternalIdentifier
Key to RegObjIdentificationSchemeregistryObjectvalue
0..*
ExternalLink
Key to RegObjKey to OrganizationexternalURI
Slot
Key to RegObjNameslotType
0..*
ValuesKey to Slot
0.*
ExtrinsicObject
Key to RegObjisOpaquemimeType
0.*serviceBinding
Key to RegObjaccessURItargetBinding
specificationLink
specificationObjectuseageDescriptionusageParameters
1..1
1..*
1..1
0..*
0..*
0..*
Priviledge
Role
Identity 1..1
1..*
1..* 1..1
1..* 1..* 1..*Namespace
domain
1..*
1..* Namespace
Collection ofRegistryObjectids
domain
Collection ofRegistryObjectids
Reg
istr
yIn
form
atio
nM
od
el (
RIM
)
Ownership
InformationAsset
Collections
Classification
Association
Repository/External Link
Configuration Mgmt
Object Specific Metadata
Registry Specific Metadata
Resource Package
Collection ofRegistryObjectids
RegistryPackage
Collection ofRegistryObjectids
1. How do I show this collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it? The Resource Package could map to RegistryPackage in RIM map
2. How do I register the pieces that make up this collection & associate them to a collection? How can I reuse pieces to make other similar collections? Collection members may be submitted together or independently and may be members of different packages
3. Is Translation a registryPackage? How is this accomplished in the Reg/Rep? What is Translation? It could mapto ExtrinsicObject
4. Are each one of the pieces of a Resource Package their own separate Registry Record? Do they have to be registered if the package is registered? Yes. Each is a RegistryObject/repository item and must be registered.
5. How do I identify this collection as being used by a domain or a namespace which did not create it? Use Content Cataloging
6. Does Slot have any purpose beyond support Service Parameter passing? Yes Slots are used for dynamic extensibility via arbitrary user-defined attribute
ConversionResources
DisplayResources
Data Resources
Input file address
Output filesAddress
Translation
ResourcePackage
Namespace
Events
DomainDependencySubscription
Namespace
domain
Classification
UDEFREACBPCBoeing TaxonomyBoeing ThesaurusAIA TaxonomyATA TaxonomyDomain Taxonomy
RIDDL
XSLT
Schema
Tables
XSL-FO
FOP
User
RegistryGuest
Project
Appl
Service
Service
Port Binding Address
Server Path
ResourcePackage
NamespaceDomainDependencySubscription
Namespace
domain
Classification
UDEFREACBPCBoeing TaxonomyBoeing ThesaurusAIA TaxonomyATA TaxonomyDomain Taxonomy
WSDL
Port
Documentation
Binding
Parameters
Server Address
Path
User
RegistryGuest
Project
Appl
Service
Event
1. How do I show that this service has been identified as being used domain which did not create it? Use ad hoc SQL or XML filter query2. How do I show that this service is part of Registry Package including a WDSL, service agreements, & documentation? Add the WDSL etc.
to the RegistryPackage.3. Is the serviceBinding a separate Registry object into itself with its own RegistryRecord? Yes.4. How do I show this as belonging to a Namespace Use Content cataloging and add namespaces as Slots5. When are external object and extrinsic link used?6. How are slot and Service Binding used with this type of collection? Slots may be added to any object in the package or the package itself.
ServiceBinding may be included in the RegistryPackage as a member.
ExternalLink
ExtrinsicObject
Slot
Values
0.*
serviceBindingspecificationLink
1..1
1..*
Collaboration
Element Attribute
Transaction
XML Schemas
Core Components
1. How do I show this collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it?
2. How do I register the pieces that make up this collection & associate them to a collection? How do I put collections in collections?
3. Are each one of the pieces their own separate Registry Record?
4. How do I identify this collection as being used by a domain or a namespace which did not create it?
5. How do I reflect that the various pieces that make up the collaboration may have come from different Namespaces or been extended by my company? Namespaces may be a Slot or Classification. Can define “Extends” Assoc to what you extended from.
6. If someone want to search down to the element and attribute level can they find this information out? Use content cataloging and SQL and/or XML filter query.
7. When are external Link and Extrinsic Object used?
8. Does Slot have any purpose beyond support Service Parameter passing?
ResourcePackage
NamespaceDomainDependencySubscription
Namespace
domain
Classification
UDEFREACBPCBoeing TaxonomyBoeing ThesaurusAIA TaxonomyATA TaxonomyDomain Taxonomy
Worksheets
BPSS
BCP
BTP
Schemas
User
RegistryGuest
Project
Appl
Service
Specification
CCP/A
TPA
InfoModel
Event
Event
Event
Event
ExternalLink
ExtrinsicObject
Domain
1. How do I show this domain collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it?
2. How do I register the pieces that make up this domain & associate them to a domain? How do I put collections in collections?
3. Are each one of the pieces their own separate Registry Record?
4. How do I identify this collection or pieces of this collection as being used by a domain or a namespace which did not create it?
5. How do I reflect that the various pieces that make up the collaboration may have come from different Namespaces or been extended by my company?
6. Does Slot have any purpose beyond support Service Parameter passing?
7. When are External Link and Extrinsic Object used?
ResourcePackage
NamespaceDomainDependencySubscription
Namespace
Submitting Organization
Classification
UDEFREACBPCBoeing TaxonomyBoeing ThesaurusAIA TaxonomyATA TaxonomyDomain Taxonomy
User
RegistryGuest
Project
Appl
Service
Specifications
Guidelines
Best PracticesPapers
Policies Procedures
TechNotes
Directions
ExternalLink
ExtrinsicObject
Namespace
1. How do I show this namespace collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it?
2. How do I register the pieces that make up this namespace & associate them to a domain? How do I put namespaces in namespaces?
3. Are each one of the pieces belonging to the namespace their own separate Registry Record?
4. How do I identify this namespace as being used by a domain or a namespace which did not create it?
5. How do I reflect that the various pieces that make up the Namespaces may have come from different Namespaces or been extended by my company?
6. Does Slot have any purpose beyond support Service Parameter passing?
7. When are External Link and Extrinsic Object used?
ResourcePackage
NamespaceDomainDependencySubscription
Domain
Submitting Organization
Classification
UDEFREACBPCBoeing TaxonomyBoeing ThesaurusAIA TaxonomyATA TaxonomyDomain Taxonomy
User
RegistryGuest
Project
Appl
Service
Specifications
Guidelines
Best PracticesPapers
Policies Procedures
TechNotes
Directions
ExternalLink
ExtrinsicObject
Collaboration
Element Attribute
Transaction
XML Schemas
Core Components
1. How do I show this collection in the registry as an addressable thing so subscriptions, dependencies, and other association types can be tied to it?
2. How do I register the pieces that make up this collection & associate them to a collection? How do I put collections in collections?
3. Are each one of the pieces their own separate Registry Record?
4. How do I identify this collection as being used by a domain or a namespace which did not create it?
5. How do I reflect that the various pieces that make up the collaboration may have come from different Namespaces or been extended by my company?
6. If someone want to search down to the element and attribute level can they find this information out?
7. Does Slot have any purpose beyond support Service Parameter passing?
ResourcePackage
NamespaceDomainDependencySubscription
Namespace
domain
Classification
UDEFREACBPCBoeing TaxonomyBoeing ThesaurusAIA TaxonomyATA TaxonomyDomain Taxonomy
Worksheets
BPSS
BCP
BTP
Schemas
User
RegistryGuest
Project
Appl
Service
Specification
CCP/A
TPA
Model
Event
Event
Event
Event
ResourcePackage
Domains Namespaces Events
1. How do I register a dependency on a record as an addressable thing (domain, namespace, record, collection) in the registry so that I get notice?
2. How does a service or a conversion/translation or a collaboration register the list of events in registry they cause so that I can register a dependency on event and get notice when it occurs? Use V3 event notification feature.
3. How will these be categorized to guide selection of which one to subscribe to?
4. How do I the owner of this registered item find out who has registered a dependency on the things belonging to my domain? Use ad hoc SQL or XML filter query.
DependencySubscription
User
RegistryGuest
Project
Appl
Service
BusinessProcess
Agreements
InformationModels ver
UDDI Reg APIs ver
ebXML Reg APIs ver
ApplicationProcess
Agreements
Namespace domainClassification
UDEFREACBPCBoeing TaxonomyBoeing ThesaurusAIA TaxonomyATA TaxonomyDomain Taxonomy
ExternalIdentifier
IntramuralAssociation
sourceObjectTargetObject
ExternalLink
ExtrinsicObject
Registry Mirrors thesePartitioning decisions
via
Categorization
Behavior
State
Actors
Sequence
Collection
Pattern
Collections?
Business Context
Collaboration
Core Components
Transaction
Element
Documents
Attribute
Business C
ontext
Categorization- of Collaboration Components to State & Context
UDEF?
REA?
CBPC?CCC?Where
does BusinessContextfit?
CBPC Business Area
Planning Identification Negotiation Actualization Post-Actualization
Procurement / Sales (Goods)
Design
Recruitment -and-Training
Logistics
Manufacturing
Financial Services
Regulation
Health Care
PROCESS AREA
- Plan procurement and supply of raw materials or finished product
-Identify potential customer/ vendor- Provide catalog- Request pricing- Request availability
- Negotiate contract- Provide purchase order-Agree delivery schedule
- Acknowledge delivery notice- Query delivery status- Receive goods-Obtain payment Authorization- Make/Receive Payment
- Discover delivery discrepancy- Return shipment- Negotiate/Receive allowance or payment from vendor
-Plan design service offering and use of design services
-Identify Vendor who can supply product design work-Identify potential customer-Request examples of prior design work
- Submit Bid- Negotiate Contract-Make counter-offers- Send design contract
- Receive designs- Inspect for conformance
- Make payment -Receive payment
-Discover discrepancy in agreed upon designs- Negotiate / receive allowance or payment from vendor
- Identify places in company where new staff of contract labor is needed.-Plan agency offerings.-Plan student Intake
-Identify personnel services provider -Identify training provider-Identify students- Request pricing- Request availability-Request/Provide course details
- Negotiate Contract forworker recruitment or training.-Agree start dates
-Register for course- Provide training materials-Interview candidates
- Make / Receive payment
-Discover discrepancy in agreed upon personnel characteristics or training components- Receive allowance or payment from vendor.-Revise training material
-Plan provision and use of transport
resources.
-Identify Vendors (like Fedex or UPS)-Identify potential customers- Request pricing- Request availability
- Negotiate contract for logistics service
- Receive logistics services-Provide shipping note-Provide dangerous goods note
- Make / Receive payment
-Discover discrepancy in agreed upon service and performance - Negotiate logistics allowances with carrier- Receive allowance or payment
-Plan manufacturing requirements-Research market for outsourced manufacturing
-Identify Provider of manufacturing services- Provide catalog- Request pricing- Request availability
- Negotiate contract for Manufacturing -Agree production schedule-Agree quality standard
-Send outsourced manufacturing inputs-Receive outsourced manufacturing outputs
- Make / Receive payment
Discover discrepancy in agreed upon quality levels- Negotiate allowance with vendor- Periodic evaluation
- Research market needs -Plan the provision of Financial Services(Insurance, Credit, Investments)
-Identify possible debt sources (banks, credit unions, etc.)- Identify financial institution with whom to purchase debt or equity financing-Identify Insurance providers-Identify potential investors
-Negotiate terms of debt or terms of equity offering with capital provider-Agree Insurance terms
- Accept transfer of debt instrument- make transfers of stock certificate- authorize and make payments & loans -Transfer funds-Pay Insurance Claims
-Review offerings & compliance -Receive monetary adjustments
-Plan and publicize regulatory requirements- Determine authorities to deal with for import/export
-Identify relevant regulatory services to enable business to operate.-Identify appropriate Taxation authority and taxpayers
-Agree time and place of inspection or other regulatory services-Negotiate payment of tax
-Accept notice of inspections, taxing, or other regulatory services performed- Request export license- Clear goods-Pay tariffs
-Make adjustments in services or payments based upon later information
-Plan Servicespecialization and provision-Plan admissions
-Register patient - Agree admission date- Decide treatment required
-Prescribe treatment- Charge / Pay for treatment
-Provide health statistics-Claim re-imbursement
?????????
General Global Taxonomies
Enterprise Specific Taxonomies
Domain Specific Taxonomies
Services
Sys
tem
Ap
plicatio
n
Pro
du
ct
Do
cum
entatio
n
En
terprise
Co
nso
rtium
Stan
dard
s Bo
dy
Domains
Namespace
Categorization & Associations of Registry Objects (Processing, Services Resources) to Global, Local, Domain Taxonomies and Ownership
W3C
W3C AIAATAOAG
MSIBMSun
W3C
UDDIReg
Boeing
ebXMLCBPCCCC
ebXMLREA
AIA?
InformationModel
ebXMLUMM
ATACSDD&AIM
Where doesUDEF fit on this?
Why doesn’t ebXMLHave a namespaceAnd domain strategyFor its work or forRegistry content? Where is ebXML Registry??
Does Taxonomy strategyIn CBPC support (discovery and comparison) handles todo web services and eBusiness?
categorization
Authoringpartitioning
BehaviorPartitioning
Ownershippartitioning
Focus/User
partitioning
UDEF
Area of Search – requires categorization handles, collections, and associations
Type of Search =Hunting
Know what the Targetis and have path
where Target was last found.
Build Time Run Time
Type of Search =Harvesting
Know the area where Target is generally
Found. Bounded Sampling
Type of Search =Browsing
Don’t know if the target
Exist or what Area it would be inBut have idea of Characteristics.
UnboundedSampling
ebXML definedCollections – artifacts
and servicesdefined by the
BP and CC teams
CollectionVersioned
Namespace
CollectionDomain
CategorizationUDEFREACBPC
Context
EventsAssociations
Handles to target in on Registry Objects
Business ProcessBusiness Process Area
Business DomainBusiness Process Category
Business ContextBusiness
Collaboration
OrganizationOwnership Domain
Registry Mirrors thesePartitioning decisions
via
Namespace Naming
Namespace ID 1MDoc V3
Agree V1CT ID 3Coll ID 1Coll ID3EG ID 1
IG 1IG 2
Domain Namespace – specialized collection of artifacts supporting Business Domain processing.
Documentation
Agreements
External GovernancesEG ID 1EG ID 2EG ID 3
Agree ID 1Agree ID 2Agree ID 3
WebServices
ConversionsTranslations
Collaborations
Internal GovernancesIG ID 1IG ID 2IG ID 3
Coll ID 1Coll ID 2Coll ID 3
CT ID 1CT ID 2CT ID 3
WS ID 1WS ID 2WS ID 3
Doc ID 1Doc ID 2Doc ID 3
Namespace ID 1ADoc V1
Agree V3WS ID 1CT ID 1CT ID 2CT ID 3Coll ID1EG ID 1
IG 1IG 2IG 3
Namespace ID 1ZDoc V3
Agree V1WS ID 1WS ID 2CT ID 3Coll ID3EG ID 1
IG 1IG 2Application or Specification Namespace –
specialized collection of artifacts supporting application processing to a specific specification or set of agreements.
Namespace ID 1MDoc V3
Agree V1CT ID 3Coll ID 1Coll ID3EG ID 1
IG 1IG 2
Domain Namespace –specialized collection of artifacts supporting Business Domain processing.
Documentation
Agreements
External GoverancesEG ID 1EG ID 2EG ID 3
Agree ID 1Agree ID 2Agree ID 3
WebServices
ConversionsTranslations
Collaborations
Internal GoverancesIG ID 1IG ID 2IG ID 3
Coll ID 1Coll ID 2Coll ID 3
CT ID 1CT ID 2CT ID 3
WS ID 1WS ID 2WS ID 3
Doc ID 1Doc ID 2Doc ID 3
Namespace ID 1ADoc V1
Agree V3WS ID 1CT ID 1CT ID 2CT ID 3Coll ID1EG ID 1
IG 1IG 2IG 3
Namespace ID 1ZDoc V3
Agree V1WS ID 1WS ID 2CT ID 3Coll ID3EG ID 1
IG 1IG 2
Namespace ID 1MDoc V3
Agree V1CT ID 3Coll ID 1Coll ID3EG ID 1
IG 1IG 2
Domain Namespace –specialized collection of artifacts supporting Business Domain processing.
Documentation
Agreements
External GoverancesEG ID 1EG ID 2EG ID 3
Agree ID 1Agree ID 2Agree ID 3
WebServices
ConversionsTranslations
Collaborations
Internal GoverancesIG ID 1IG ID 2IG ID 3
Coll ID 1Coll ID 2Coll ID 3
CT ID 1CT ID 2CT ID 3
WS ID 1WS ID 2WS ID 3
Doc ID 1Doc ID 2Doc ID 3
Namespace ID 1ADoc V1
Agree V3WS ID 1CT ID 1CT ID 2CT ID 3Coll ID1EG ID 1
IG 1IG 2IG 3
Namespace ID 1ZDoc V3
Agree V1WS ID 1WS ID 2CT ID 3Coll ID3EG ID 1
IG 1IG 2
Cross DomainNamespace ID XX-1Z
Doc yy-V3Agree 77-V1WS ID xx-1WS ID zz-2CT ID -zz3
Coll Id yy- 3EG ID xx-1IG ID xx-1IG ID ss-2
Namespace - specialized collections Governances supporting application processingAnd under configuration control. Specifications, Info Models, worksheets, structures, services,Agreements, policies,……
Namespace URI:= BaseURI/BaseURI/SourceNameSourceName//CMDateCMDate//SpecIDNameSpecIDNameNamespace URI would be translated by a Namespace Resolver Service to translateDown to a pointer to a registry interface to find resources or point down to a server.
Base URI:= (tbd)(tbd)
uncefact.org uncefact.org or uncefact.ebxml.org uncefact.ebxml.org or ebxml.org or uncefact-oasis.orgebxml.org or uncefact-oasis.org
Source Name:= (uncefact, uncefact, (“/”(“/”,, (UNBaseWG)(UNBaseWG),, “/” “/”)) | (oasis, oasis, (“/”, (OasisBaseWG)(“/”, (OasisBaseWG),, “/” “/”))UNBaseWG:= (TWG(TWG |ATG ATG || Legal) Legal) OasisBaseWG:= (MHS (MHS | | RR | CPP) RR | CPP)
CMdate:= yyyyyyyy-mmmm
SpecIDName:= (UnSubWGname | OasisSubTCname)(UnSubWGname | OasisSubTCname)UNSubWGname:= (UMM, BPCMC, BPIMES, BRIM, BET, BCP, UEB, CBPC,…)UMM, BPCMC, BPIMES, BRIM, BET, BCP, UEB, CBPC,…) OasisSubTCname := (tbd)(tbd)
Unique ID:= Namespace URI + FilePath/FileName A filepath and file name could lead to the location of resources. Or a Registry Object ID could allow discovery of the object from repository or provide URL to resource.
Namespace URI and “filepath and filename” are 2 distinct “thangs” which need XML mechanisms or registry mechanisms to help resolve to support discovery and use.
Namespace Naming Convention Proposal
W3C Example for definingNamespace URIs
and File Share URL addressing
*Completed
W3C Domain
Web Accessibility Initiative Quality Assurance TAG
InteractionDomain
Privacy ActivityP3P Specification
Patent Policy ActivityPatent Policy WG
Semantic Web ActivityRDF Core WG Web Ontology WG
XML Encryption ActivityXML Encryption WG
XML Key Mgmt ActivityXML Key Mgmt WG
XML Signature ActivityXML-Signature WG
Technology &SocietyDomain
Dev Independence ActivityCC/PP WGDev Independence WG
Multimdl Intractn ActivityMultimdl Intractn WG
Voice Browser ActivityVoice Browser WG
Synchronized Multimedia SYMM WG*
DocumentFormatsDomain
Graphics ActivitySVG WG
HTML ActivityXHTMLHTML WGXforms WG
I18N ActivityI18N WG
Math ActivityMath WG
Style ActivityCSS WG XSL WG
ArchitectureDomain
DOM ActivityDOM WG
XML ActivityXML Query WGXML Schema WGXML Linking WGXML Core WG
URI ActivityWebSrvs ActivityJigSaw Project
Quality Assurance ActivityQA WGTechnical Architecture Group
WAI Technical ActivityProtocols & Format WGUser Agent Guidelines WGAuthoring Tools Guidelines WGWeb Content Accessibility Guidelines WG
Sub-Domains
Partitioning of the WorkPartitioning of the WorkBase Domain
Sub-Sub-Domains
W3C homepage
W3C Administration &
Guidelines
W3C WG AuthoringGuideline pages
W3CCommunication
pages
W3CAboutpages
W3CMembership
Public Member & Internal
W3C MembershipGuideline pages
Web Accessibility Initiative webpage
Quality Assurance TAG webpage
InteractionDomain webpage
Technology & SocietyDomain webpage
Document FormatsDomain webpage
ArchitectureDomain web pages
TR web pages (REC, PR, CR,
WD, Note)
W3C Mailing Lists
Public WG Webpages
Public WG Webpages
Public WG Webpages
Public WG Webpages
Public WG Webpages
Public WG Webpages
Web Accessibility Initiative webpage
Quality Assurance TAG webpage
InteractionDomain webpage
Technology & SocietyDomain webpage
Document FormatsDomain webpage
ArchitectureDomain web pages
Internal WDWeb pages
WIP WG Webpages
WIP WG Webpages
WIP WG Webpages
WIP WG Webpages
WIP WG Webpages
WIP WG Webpages
W3C WG Policies
W3C NamespacePolicies & Guidelines
W3C
Search
W3C
Site In
dex
W3C
Su
bscrip
tion
W3C
Sea
rch
W3C
Sit
e In
dex
W3C
Su
bsc
rip
tio
n
Site Map for Access to Domain Work ProductsSite Map for Access to Domain Work Products
Naming ConventionNaming Conventionfor domain,for domain,Sub-domainSub-domain
And sub-sub-domainAnd sub-sub-domainNamespacesNamespaces
Base URI: www.w3.orgwww.w3.org
Namespace URI: baseURI/CM-date/AssignedNamebaseURI/CM-date/AssignedName
Configuration Management date on creation: yyyyyyyy with optional mm mm with optional dd ddAssigned Name:
WG acronym for base specification namebase specification nameWith optional sub-specification namesub-specification name
http://www.w3.org/1998/Math//MathML
http://www.w3.org/2002/01/rdf-databases/db-ont-1#/http://www.w3.org/2002/01/rdf-databases/rei-ont-1#/http://www.w3.org/2002/03/xkms/http://www.w3.org/2002/06/soap-encoding/http://www.w3.org/2002/06/soap-envelope/http://www.w3.org/2002/06/soap-faults/http://www.w3.org/2002/06/soap-rpc/http://www.w3.org/2002/06/xhtml2/http://www.w3.org/2002/06/xmldsig-filter2/
http://www.w3.org/1999/02/22/rdf-syntax-ns#/http://www.w3.org/1999/xhtml/http://www.w3.org/1999/xlink/http://www.w3.org/1999/XSL/Formathttp://www.w3.org/1999/XSL/Transform
http://www.w3.org/2001/SMIL20/http://www.w3.org/2001/Xinclude/http://www.w3.org/2001/xml-events/http://www.w3.org/2001/XMLSchema/http://www.w3.org/2001/02/xml-fragment/http://www.w3.org/2001/04//xmlenc#/http://www.w3.org/2001/10/xml-exc-c14n/http://www.w3.org/2001/12/xforms/
http://www.w3.org/2000/svg/http://www.w3.org/2000/xmlns/http://www.w3.org/2000 /09/xmldsig#/http://www.w3.org/2000 /10/xmldsig-p3p-profile/
W3C Defined NamespacesW3C Defined Namespaces
Naming Convention & Repository HierarchyNaming Convention & Repository Hierarchy
W3C Domainhttp://www.w3.orghttp://www.w3.org/Consortium/The Architecture (sub) Domainhttp://www.w3.org/Architecture/DOMhttp://www.w3.DOM/http://www.w3.org/DOM/Activity/http://www.w3.org/DOM/Group/JIGSAWhttp://www.w3.org/Jigsaw/XML: Structured Data Interchangehttp://www.w3.org/XML/Activityhttp://www.w3.org/XML/Group/Corehttp://www.w3.org/XML/Linkinghttp://www.w3.org/XML/Group/Queryhttp://www.w3.org/XML/Group/SchemasURI (Uniform Resource Identifiers) http://www.w3.org/Metadata/http://www.w3.org/Addressing/Web Serviceshttp://www.w3.org/2002/ws/[Activity*]http://www.w3.org/2002/ws/cg/http://www.w3.org/2002/ws/desc/http://www.w3.org/2000/xp/Group/http://www.w3.org/2002/ws/arch/
Domain Pagehttp://www.w3.org/DomainNameDomainName
Working Documentshttp://lists.w3.org/Archives/Public/GroupDirNameGroupDirName
Public Pagehttp://www.w3.org/GroupNameGroupName/Sub-Group-NameSub-Group-Name
Status-What’s New Pagehttp://www.w3.org/GroupNameGroupName/Activity
Working Group Pagehttp://www.w3.org/GroupNameGroupName/Group/